The Field Manual is a page in the app - #170
Merged
Merged
Conversation
The walk-to-filed loop, written down where the walker can reach it: /manual, in the app's own Quadrangle voice — condensed mastheads, the walker's words in the serif italic, and the Route legend coloured by the same strict roles the desk uses. The legend is derived, not transcribed: the Kinds proposing each Route come from routeForKind and KIND_LABELS, and the rows from THREAD_ROUTES, so the manual cannot drift from the vocabulary it documents. Where a destination is not live it says so plainly — Spec needs SPEC_HANDOFF_GITHUB_TOKEN, the task list lands with #160 — rather than describing an aspiration. Reachable from the desk header beside Interview, and from the foot of the Interview page. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Mm4zPLAX77USAqyk12jgc1
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
4 tasks
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The walk-to-filed loop, written down where the walker can actually reach it:
/manual, in the app's own Quadrangle voice rather than as an external doc — condensed mastheads, the walker's words in the serif italic, and the Route legend coloured by the same strict roles the desk uses.It reads start to finish: on the trail (Capture, offline, one Thread each) → on the way home (title, Kind, Project guess, report, or a question back) → at the desk (the three-step flow) → the legend → where things end up → the backlog → what still needs setup.
The legend is derived, not transcribed. The Kinds proposing each Route come from
routeForKindandKIND_LABELS; the rows come fromTHREAD_ROUTES. Adding a Kind or a Route updates the manual on its own, so it cannot drift from the vocabulary it documents.It states what is not live. Spec is marked Needs a token (
SPEC_HANDOFF_GITHUB_TOKEN, per ADR 0018) and To-do Landing next (#160 is still open), rather than describing an aspiration as though it worked.Reachable from the desk header beside Interview, and from the foot of the Interview page.
Test plan
/manualand was reviewed in a real browser at three scroll positions — masthead, the three step cards, and the full legend — inside the app's own chrome and tab barmain, not the prototype: the keys (⏎ s t n p x r j) againstcomponents/day-flow.tsx, the ~25 m spot clustering,/journal/notebook, and the spec-handoff messagespnpm exec tsc --noEmitclean; eslint clean on every file this PR adds or touches (the pre-existingdesk-workspace.tsx:860error onmainis untouched)No-ticket: true
🤖 Generated with Claude Code
https://claude.ai/code/session_01Mm4zPLAX77USAqyk12jgc1
Generated by Claude Code