The To-do destination: routed tasks land on a list the walker can work (#160)

[wschenk]

Summary

route = "todo" Threads get their real destination (docs/desk.md, slice D2):

• The task list — a new /todo surface (linked from the Days header) lists every Thread routed to To-do as a checkable item in the walker's own words: the first Capture's text, never the Enrichment's title. It re-reads after each sync cycle, so a to-do routed on another device lands live.
• Check-off is destination-surface state, not Filing — a new todoDoneAt field rides its own seam (POST /api/sync/todo → ThreadRepository.setThreadTodoDone) and deliberately never touches reviewedAt or route, so checking an item off cannot reopen or re-file the Thread. It persists in the local store (IndexedDB), round-trips through the memory and Neon repositories (todo_done_at column), and hydrates across devices in mergeRemoteThreads the way the review decision does.
• The day digest checklist draws from routed to-dos instead of re-deriving. The day chat sends the day's routed to-dos with every ask; buildDayDigestPrompt carries them verbatim (- [ ] / - [x]), and DAY_DIGEST_SYSTEM_INSTRUCTION makes them the checklist when the section is present — deriving from reports only for callers that predate the field.
• Un-routing removes the item by construction — the list is fed by route = "todo" itself, not a copy, so clearing or redirecting the route at the desk takes the item off the list. This composes with the Day flow's unfileThread (The default door: a Day with unrouted Threads opens on the arrival summary (#159) #168), which clears the route.

Closes #160

Merged with main (662a5cc)

This branch was last of the five-way fan-out, so it carries a merge of main at 84875ab (after #167 timeline, #166 journal, #169 spec routing, #168 day flow). Six files conflicted and every one was resolved by keeping both sides' additions — no sibling's work was dropped:

File	Resolution
lib/local-capture/types.ts	todoDoneAt + specHandoff on LocalThread and applyRemoteThreads
lib/sync/types.ts	both fields on ServerThread; setThreadTodoDone + recordSpecHandoff both on the repository interface
lib/sync/hydrate.ts	both fields at all three sites in mergeRemoteThreads
lib/sync/memory-repository.ts	both on StoredThread and the listThreads mapping
lib/sync/neon-repository.ts	both columns (separate ADD COLUMN migrations), both in the SELECT, the row type, and the mapping
app/globals.css	append-vs-append; both style blocks kept in sequence

Note for whoever merges this file next: lib/sync/hydrate.ts contains a literal NUL byte in a join() separator, so git classifies it as binary, refuses to merge it, and keeps one side wholesale with no conflict markers. Trusting "no markers = resolved" here would silently drop the other side's field from the adopt-list while still compiling. This merge diffed both sides and reapplied the additions byte-wise, preserving the NULs. Replacing that separator with an ordinary string is worth a follow-up.

Test plan

• Acceptance criteria from the ticket covered at the named seams:
  • tests/todo-destination.spec.ts (memory repositories / pure seams): routing to To-do lists the walker's words; check-off round-trips without re-filing; todoDoneAt hydrates both ways; un-routing and redirecting remove the item; the digest prompt and system instruction carry routed to-dos, with absence keeping the old derive behavior.
  • tests/todo-destination-ui.spec.ts (public browser seam, thread-filing-ui pattern): route via the desk filing UI → item appears on /todo in the walker's words → check-off sticks across reload → the day still reads "All filed" → un-routing empties the list; the day-digest ask POSTs routedTodos for that day.
• Verified on the merged tree: pnpm exec tsc --noEmit clean; eslint clean on every changed file; 48 passed / 1 skipped / 0 failed across todo-destination, todo-destination-ui, thread-filing, thread-filing-ui, day-flow, sync-hydrate, sync-repository, day-digest, day-digest-ui. (The skip is the Clerk setup project, which skips without preview keys.)
• Both neighbours' behavior confirmed alongside mine: all seven Day-flow tests pass (receipts and undo included), and routedTodos survives end to end.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
walking-thoughts	Ready	Preview	Aug 8, 2026 9:27am