The v4.5.0 build plan, and the brief's lanes table names its issues (#366, #361) #738

Merged

claude-bot merged 1 commit from design/build-plan into main

2026-09-22 00:38:20 +00:00

claude-bot commented

2026-09-22 00:15:49 +00:00

Collaborator

The owner asked what was left to plan before building, and then for all of it. This is the engineering plan the brief stops short of: docs/design/v4.5.0-build-plan.md.

The rollout rule (§2): lane 0 builds the library; lane 1 builds the new shell and mounts every existing page inside it; each later lane replaces the pages it owns and deletes the old ones. No feature flags, no parallel route tree, no long-lived branch; main deployable after every PR; the dev server as the staging the owner reviews on.
Lane 0's technical design (§3): the kit's tokens verbatim, read through Tailwind 4's @theme; dark mode by data-mode; the sixty-seven icons as one component; the component list from the brief's §8 made concrete; the rules as code (D12, D22, D36, D65, the section boundary, the async pattern, 44 px targets); a /design reference page in the dev build instead of Storybook; and what happens to each of today's 20 pages and 39 components, mapped from the catalogue's citations.
The seven journeys as a Playwright suite (§4): the stack, the seams (fake OIDC issuer, mail catcher, fake bot server, stub providers), three projects (desktop, phone, keyboard-only), the axe scan, the CI job, and which lane keeps which journey green.
WCAG 2.2 AA as the standard (§5), checked by lint from lane 0, by axe in every journey run, and by a manual screen-reader pass at the end.
The lanes and their issues (§6), working agreements (§7), and the five assumptions the owner should confirm (§8).

Filed alongside: the journeys harness #726 and lanes 1 to 11 as #727 to #737, each with its surfaces, drawing, server changes and acceptance list; #366 updated as the umbrella with the checklist (and #365's phone criteria folded in); #364 and #367 commented with lane 0's acceptance and the standard; #362 and #365 closed. The brief's §9 names the issues and the standard; §11's row count is current.

🤖 Generated with Claude Code

The owner asked what was left to plan before building, and then for all of it. This is the engineering plan the brief stops short of: `docs/design/v4.5.0-build-plan.md`. - **The rollout rule** (§2): lane 0 builds the library; lane 1 builds the new shell and mounts every existing page inside it; each later lane replaces the pages it owns and deletes the old ones. No feature flags, no parallel route tree, no long-lived branch; main deployable after every PR; the dev server as the staging the owner reviews on. - **Lane 0's technical design** (§3): the kit's tokens verbatim, read through Tailwind 4's `@theme`; dark mode by `data-mode`; the sixty-seven icons as one component; the component list from the brief's §8 made concrete; the rules as code (D12, D22, D36, D65, the section boundary, the async pattern, 44 px targets); a `/design` reference page in the dev build instead of Storybook; and what happens to each of today's 20 pages and 39 components, mapped from the catalogue's citations. - **The seven journeys as a Playwright suite** (§4): the stack, the seams (fake OIDC issuer, mail catcher, fake bot server, stub providers), three projects (desktop, phone, keyboard-only), the axe scan, the CI job, and which lane keeps which journey green. - **WCAG 2.2 AA** as the standard (§5), checked by lint from lane 0, by axe in every journey run, and by a manual screen-reader pass at the end. - **The lanes and their issues** (§6), working agreements (§7), and the five assumptions the owner should confirm (§8). Filed alongside: the journeys harness #726 and lanes 1 to 11 as #727 to #737, each with its surfaces, drawing, server changes and acceptance list; #366 updated as the umbrella with the checklist (and #365's phone criteria folded in); #364 and #367 commented with lane 0's acceptance and the standard; #362 and #365 closed. The brief's §9 names the issues and the standard; §11's row count is current. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-bot added 1 commit

2026-09-22 00:15:50 +00:00

docs(design): the v4.5.0 build plan, and the brief's lanes table names its issues (#366 , #361 )

CI / Summarisation accuracy eval harness (stub provider) (pull_request) Successful in 57s

Details

CI / Docker image build (pull_request) Successful in 38s

Details

CI / Bot/backend version sync (pull_request) Successful in 1m6s

Details

CI / Backend lint (ruff) (pull_request) Successful in 1m10s

Details

CI / Frontend tests, audit, and build (pull_request) Successful in 2m13s

Details

CI / Feedback site tests (pull_request) Successful in 1m27s

Details

CI / Bot tests and audit (pull_request) Successful in 2m57s

Details

CI / Backend migration, tests, and audit (pull_request) Successful in 8m26s

Details

CI / Synthetic session harness (no GPU, no LLM) (pull_request) Successful in 21m10s

Details

a92b617948

The owner asked what was left to plan before building, and then for all
of it. This is the engineering plan the brief stops short of.

docs/design/v4.5.0-build-plan.md:
- the rollout rule: lane 0 builds the library; lane 1 builds the new
  shell and mounts every existing page inside it; each later lane
  replaces the pages it owns and deletes the old ones; no feature flags,
  no parallel route tree, no long-lived branch; main deployable after
  every PR; the dev server as the staging the owner reviews on
- lane 0's technical design: the kit's tokens verbatim, read through
  Tailwind 4's @theme; dark mode by data-mode; the icons as one
  component; the component list from the brief's §8 made concrete; the
  rules as code (D12, D22, D36, D65, the section boundary, the async
  pattern, 44 px targets); a /design reference page in the dev build
  instead of Storybook; and what happens to each of today's 20 pages and
  39 components, mapped from the catalogue's citations
- the seven journeys as a Playwright suite: the stack, the seams, three
  projects (desktop, phone, keyboard-only), the axe scan, the CI job,
  and which lane keeps which journey green
- WCAG 2.2 AA as the standard, checked by lint, by axe in every journey
  run, and by a manual screen-reader pass at the end
- the lanes and their issues; working agreements; the assumptions the
  owner should confirm

The brief's §9 names the lane issues (#727 to #737, #364 for lane 0) and
the harness (#726), records the standard, and points at the plan; §11's
row count is current.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>