Skip to content

The default door: a Day with unrouted Threads opens on the arrival summary (#159) - #168

Merged
wschenk merged 2 commits into
mainfrom
cursor/day-flow-159
Aug 8, 2026
Merged

The default door: a Day with unrouted Threads opens on the arrival summary (#159)#168
wschenk merged 2 commits into
mainfrom
cursor/day-flow-159

Conversation

@wschenk

@wschenk wschenk commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Summary

The validated /prototype/day-routing flow lands in the real Day view (slice D1's UI half, docs/desk.md). Opening a Day with unrouted Threads now starts the three-step pass, rendered at the top of the day pane and driven by real local Threads and the filing seam:

  1. What came home — the day's unrouted Threads grouped by their proposed Route (thread.route ?? routeForKind(kind)), Needs-a-word flagged, one action: Start routing ().
  2. Route each one — one Thread at a time: the walker's words, media, the full Enrichment report readable in place (r), the proposed Route pre-armed with what settling it will do. accepts, s/t/n/p/x redirect, j skips. Settling is one write — route + Reviewed together via fileThread — and auto-advances. Spec routes carry the Project select. No commit gate.
  3. What happened — receipts, not a confirmation: every routed Thread under its Route, with a per-lane note saying plainly which handoffs are live (Drop's Artifact retraction) and which are recorded-only until D2/D3 land. Per-line undo runs the seam backwards (new unfileThread: reviewed: false, route: null, verdict cleared) and returns the Thread to the deck.

Desk rows keep their existing route actions from #164, so a row and a deck card produce the identical filing. The deck owns its keys only while dealing (capture-phase listener), so the desk's own row shortcuts are untouched outside the flow. The prototype is left as the record, untouched.

The second commit (.agents/skills + skills-lock.json) is the session's automated skills re-sync carried out of the ephemeral workspace, unrelated to the ticket — its own message explains; drop it if unwanted.

Closes #159

Test plan

  • Acceptance criteria from the ticket covered at the public browser seam in tests/day-flow.spec.ts: arrival summary → Start routing → settles and the count drops; one-key redirect files route + Reviewed in a single recorded write and survives reload; the full report reads on the card; receipts list every Thread under its route with undo back to the deck and New emptying for the Day; desk-row vs deck filing parity (same transport payload, same store state).
  • pnpm exec tsc --noEmit clean; eslint clean on all touched files (the pre-existing desk-workspace.tsx:860 error is on main unchanged).
  • day-flow (×3 repeats), thread-filing-ui, desk-rail-desktop, desk-keyboard-desktop, desk-working-set-desktop, day-digest-ui, navigation, threads-workspace-desktop all green locally.

…mmary (#159)

The validated day-routing prototype lands in the real Day view: three
steps — what came home, route each one, what happened — driven by the
local pile and the filing seam. Enter settles the proposed Route,
s/t/n/p/x redirect, j skips, r opens the full report on the card, and
settling is one write (route + Reviewed) with no commit gate. The
receipts screen groups every routed Thread under its Route, says which
handoffs are live and which are recorded-only until later slices, and
offers per-line undo — unfileThread runs the same seam backwards, so
the Thread returns to the deck.

Closes #159

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017YEcvhN6Le4tPBycdGnDps
@vercel

vercel Bot commented Aug 8, 2026

Copy link
Copy Markdown

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

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

Request Review

…kspace

The vendored .agents/skills tree and skills-lock.json were re-synced
from upstream by the session-start tooling, and the ask-matt
PHASE-BOUNDARIES doc sat untracked beside its skill (same content
already rescued on cursor/timeline-spot-strip-162). Committed
separately so nothing is lost with the container. Unrelated to #159.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017YEcvhN6Le4tPBycdGnDps
@wschenk
wschenk merged commit 84875ab into main Aug 8, 2026
4 checks passed
wschenk added a commit that referenced this pull request Aug 8, 2026
The To-do merge left .todo-tally unterminated, so from that line to the end of the file every rule was parsed as declarations of that block and silently discarded — .day-flow (#168) and all 39 .manual-* rules (#170) included. Nothing errored: the build passed, the pages rendered, the CSS sat right there in the file. It just never applied, and /days shipped unusable.

Restores the brace, and adds tests/globals-css.spec.ts so this cannot recur invisibly: the braces must balance, and each surface's rules (.manual-sheet, .day-flow, .todo-items, .shell) must sit at the top level rather than nested inside an earlier block or a media query. CSS is the one part of this app with no type checker, and HTTP 200s and passing suites are both blind to a dead stylesheet.

No-ticket: true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The Day flow: what came home → route each one → what happened

2 participants