UX review: the stack is deployed, and the handoff says so
Three sessions running, the handoff opened with "nothing deployed" and closed by recommending item 3b — which had shipped two sessions earlier. Both are now false, and a stale recommendation is worse than none: it sends the next session to re-scope finished work. Claude-Session: https://claude.ai/code/session_016y6gyuHkQXPiEuW8RGQyua
This commit is contained in:
+22
-3
@@ -495,9 +495,28 @@ topic branches. **Merging and deploying that stack is the obvious next move**
|
||||
— three sessions of work she hasn't seen. Untouched: 6, 7, 8, item 3's
|
||||
incremental half, and item 5's re-scoped Translate card type.)*
|
||||
|
||||
**Suggested next:** item 3b, the instant local rules layer — but it is
|
||||
**largely already built, in `main`**, and the item as written doesn't know
|
||||
that. Before writing any rules engine, read:
|
||||
*(Sixth session: **the stack is merged and live.** Items 3b, 2 and 4 went to
|
||||
`main` as one `--no-ff` merge (`963fc17`), pushed to gitea, and the VPS is
|
||||
rebuilt on it — all five containers healthy, frontend build
|
||||
`014b43cdf44f`, migration `0014` (`checked_chunks`) applied cleanly on the
|
||||
real database. Green before merging: `go test ./...`, `tsc --noEmit`, 195
|
||||
vitest tests. So the three sessions of work she hasn't seen, she can now
|
||||
see. Untouched: 6, 7, 8, item 3's incremental half, item 5's re-scoped
|
||||
Translate card type.)*
|
||||
|
||||
**Suggested next (sixth session onward):** items 6, 7, 8 are all untouched
|
||||
and all small; item 5's re-scoped Translate card type is the cheapest
|
||||
*visible* win (see its Status note — the span is already detected and
|
||||
already rendered in English, it's only mislabeled as Clarity), and
|
||||
`internal/suggestions/translate.go` already exists — read it before
|
||||
designing a new type. Item 3's incremental-surfacing half now has the
|
||||
chunking it was waiting on, but still needs streaming, which the current
|
||||
`/check` response shape doesn't do.
|
||||
|
||||
*The advice below was written for the second session and is kept for its
|
||||
reading list, not its recommendation: item 3b is done and deployed.* It was
|
||||
**largely already built, in `main`**, and the item as written didn't know
|
||||
that. Before touching the rules engine, read:
|
||||
|
||||
- `web/src/components/Companion/prose.ts` — the deterministic rules engine,
|
||||
client-side, already the single source of non-LLM detection. Sibling
|
||||
|
||||
Reference in New Issue
Block a user