intake: keep shipped work out of the dashboard's Recent feed

[Jammy2211]

Follow-up to #249. Recent shipped listing the complete/ ledger alongside live work. On this Mind that made it a list of receipts: ~200 records a month means the twenty newest dates are almost all completions, so the section whose whole job is the work in hand was mostly things nobody can act on.

The change

The feed is live work only — issued, parked, filed — and complete/ is never opened to render it, rather than being read and then filtered.

That removes more than it adds:

• completed_records, its bounded newest-first month walk, and the RECENT_MONTHS / _RECORD_HEAD_BYTES / _RECORD_DATE machinery
• _record_date, which existed to date the ~20% of records stating their date in prose rather than a completed: field
• the live-first selection rule from intake: read task dates and render the dashboard's Recent table #249, which only existed to stop completions crowding live rows out — with no completions in the feed a plain date sort is simply correct
• census()["completed"]

EVENT_LABEL loses its completed/shipped entries. Both keys stay in DATE_KEYS, deliberately: a registry entry that dates itself shipped: is still sitting in a live registry, and dropping the key would make that row undated and silently vanish from the feed rather than showing what it is.

Testing

• test_shipped_work_is_not_in_the_feed and test_the_complete_ledger_is_never_opened replace the three completion-scan tests; the merged-feed test now covers the live states only.
• python3 -m pytest tests/ — 394 passed.
• bin/pyauto-brain intake dashboard --check — clean against the regenerated PyAutoMind pages (10 rows, all live).

Merge before the paired PyAutoMind PR — that repo's refresh check renders the dashboard using this repo's main.

---

Generated by Claude Code