rcf-lite 0.32.4 → 0.33.0

package/rcf/requirements/req-002.json

@@ -2,7 +2,7 @@
   "reqId": "REQ-002",
   "prdId": "PRD-001",
   "title": "Visual review surface",
-  "description": "Build Lite renders the whole RCF tree as a diagram and as a browsable static page, so a non-coding owner can see the documents and their links without reading any JSON. The view is read-only and generated from the on-disk tree on demand. Build/DAG sub-tab lays FBS by `dependsOnFbsIds` depth with click-to-highlight closure, dependency inspector, filters, unconnected lane and `#tab=build&sub=dag&entity=` deep links, per viewer UI refresh design section 7. ID lookup over a server-built `./index.json` of every document id and AC, opened by the SearchButton or Cmd/Ctrl+F, navigates to `#tab=<tab>&entity=<id>` preserving `embed` and `theme`, per viewer UI refresh design section 6. Embedding proof: a same-origin test-host fixture mounts the viewer with `embed=1` and `theme=` and the three lints keep framing headers, `target='_top'` and localStorage namespace in place, per viewer UI refresh design section 9 and Dex's wespa requirements of 2026-10-02. Standalone viewer carries a visible three-state theme control (Light|Dark|Auto) in the header right of the SearchButton that persists its setting under `rcf-view:v1:theme` in non-embed mode only (ADR-4137); under `embed=1` the control is absent from the DOM and the key is never read or written. Every text and control colour pair meets WCAG 2.1 AA (>= 4.5:1 for text, >= 3:1 for large text and non-text UI boundaries) in both themes, pinned by a static CSS-contrast audit test (US-207) that enumerates every rule and state in `src/view/style.css` and fails the suite on any below-threshold pair.",
+  "description": "Build Lite renders the whole RCF tree as a diagram and as a browsable static page, so a non-coding owner can see the documents and their links without reading any JSON. The view is read-only and generated from the on-disk tree on demand. Build/DAG sub-tab lays FBS by `dependsOnFbsIds` depth with click-to-highlight closure, dependency inspector, filters, unconnected lane and `#tab=build&sub=dag&entity=` deep links, per viewer UI refresh design section 7. ID lookup over a server-built `./index.json` of every document id and AC, opened by the SearchButton or Cmd/Ctrl+F, navigates to `#tab=<tab>&entity=<id>` preserving `embed` and `theme`, per viewer UI refresh design section 6. Embedding proof: a same-origin test-host fixture mounts the viewer with `embed=1` and `theme=` and the three lints keep framing headers, `target='_top'` and localStorage namespace in place, per viewer UI refresh design section 9 and Dex's wespa requirements of 2026-10-02. Standalone viewer carries a visible three-state theme control (Light|Dark|Auto) in the header right of the SearchButton that persists its setting under `rcf-view:v1:theme` in non-embed mode only (ADR-4137); under `embed=1` the control is absent from the DOM and the key is never read or written. Every text and control colour pair meets WCAG 2.1 AA (>= 4.5:1 for text, >= 3:1 for large text and non-text UI boundaries) in both themes, pinned by a static CSS-contrast audit test (US-207) that enumerates every rule and state in `src/view/style.css` and fails the suite on any below-threshold pair. Query routes and the trace matrix (DEFINE 2026-10-07, discovery-viewer-command-page): the viewer serves trace, impact and coverage for a selected node as three GET JSON routes (./trace.json, ./impact.json, ./coverage.json) computed from the current walked state and cached by state.version, bypassing the admissibility gate as the CLI coverage, impact and trace verbs do; the Readiness tab's Trace sub-tab renders a trace matrix for a pivot chosen through the lookup modal or a Trace action on any id (rows: stories and criteria; columns: suites, cases, build specs, components; cells coloured by resolution), and the per-requirement Mermaid slice on the Requirements tab is retired so no Mermaid is user-facing on these surfaces.",
   "category": "functional",
   "domain": "view",
   "priority": "must",
@@ -16,5 +16,8 @@
   "version": "0.1.0",
   "status": "draft",
   "createdAt": "2026-06-25T00:00:00Z",
-  "updatedAt": "2026-10-04T14:00:00.000Z"
+  "updatedAt": "2026-10-07T13:46:36.188Z",
+  "deliveredBy": {
+    "tacId": "TAC-4136-view-query-routes"
+  }
 }

package/rcf/requirements/req-180.json

@@ -1,10 +1,10 @@
 {
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-02T19:30:00Z",
+  "updatedAt": "2026-10-07T13:46:35.361Z",
   "reqId": "REQ-180",
   "prdId": "PRD-001",
   "title": "Readiness tab as tab 1 and the Overview-to-PRD rename",
-  "description": "src/view/readiness.js lands and html-page.js wires it as the first tab. The former Overview tab becomes PRD (same panel content; the rename is label-only). The Readiness panel renders the computeReadiness object top-to-bottom in the layout the DEFINE step 2 spec section 5 pins: tree line (formatTreeLine), two verdict pills with formatVerdictLines strings as the labels and blockedBy.length as the count, two per-persona next-action lines anchored into the stage detail, D1..D8 state chips with reason/acknowledgement text on hover, blockers grouped by persona (profile register orders the pair; the non-register group collapses with its count visible, never omitted), delta list grouped by REQ ancestor with a document-level diff on changed items (criterion-level diff deferred to the UX review per ADR-4127), per-stage check detail with persona pill and findings list when not ok, coverage tree-versus-delta with re-verify and re-execute counts, decisions outstanding in the #241 numbered format, a Freeze now control enabled iff levels.readyToBuild.ok (showing the `rcf define freeze` command and what it will record; disabled it names the failing gates from levels.readyToBuild.blockedBy; no intent-complete button), and the loaded freeze record (hash, when, note, counts, acknowledged gates with reasons). The view is pure: it never recomputes readiness, so the tab and `rcf define readiness --json` cannot disagree on the same tree hash. question cards grouped by source span rendering the questions object, per the viewer UI refresh design section 8.",
+  "description": "src/view/readiness.js lands and html-page.js wires it as the first tab. The former Overview tab becomes PRD (same panel content; the rename is label-only). The Readiness panel is the command page (DEFINE 2026-10-07, discovery-viewer-command-page): it renders the computeReadiness object as linked tables, counts and links, split into sub-tabs (Overview, Questions, Blocking, Coverage, Trace) whose key rides in the hash as sub=. Overview: tree line (formatTreeLine), two verdict cards at equal height (Ready for engineers, Ready to build; each count a link into the table it counts; chain term muted), a stage grid (D1 to D8 by tree and delta scope, pass/total per cell, failing count linked into the blocking table, acknowledged state with its reason from stages[].state), delta as counts with an on-demand per-document list, decisions outstanding in the #241 numbered format, and the freeze state in words (what blocks a freeze and what resolves it; no button, no command text). Questions: one table row per readiness.questions[] entry carrying number, the plain question, where it lives as a link, what settles it in plain words, a one-line copy handle (id plus ask, no command) and state; grouped by source span as a column. Blocking: one table row per failing item across every stage with stage, check, id as a resolving link (composite ids split on the first colon), the gate's why and what resolved looks like; no row cap; filterable by stage and persona. Coverage: a coverage summary with family counts, the three class totals as a stacked bar with the percentage, and an unresolved-pointers table, followed by the thin-requirements table fed by every signal that names a thin requirement (no story, zero criteria, criteria with no resolving test, D4 floor failures, no plain description). The For-engineers DocRow wrapper, the question cards, the blocker cards and the Freeze now control are retired; every engineer item survives in a named table or block (AC-18002-3). The profile register orders the first paint (product owner first unless the profile says engineer) and never hides a block (ADR-4127, ADR-4135). The view is pure: it never recomputes readiness, never renders a shell command and never writes, so the tab and rcf define readiness --json cannot disagree on the same tree hash. Every colour is an existing --sv-* token; the panel stays embed-safe under embed=1 and both themes.",
   "category": "functional",
   "domain": "defineDetection",
   "priority": "must",
@@ -27,5 +27,8 @@
   "rationale": "Baz ruling 2026-09-22 (DEFINE step 2 spec section 2.4, decision 2): one object, two renderers. The CLI (REQ-175, PR B) and the tab (REQ-180, PR C) read the same computeReadiness result so they cannot disagree. Readiness is where an operator starts, so it must be tab 1. The Overview panel is just the PRD body today (phase 3.6 dropped the diagram) so the rename is honest; keeping the hash-anchor `#tab-overview` preserves every existing link into the surface. The L1 pre-population posture (ADR-4126) requires the tab to visibly distinguish [draft] shapes from settled ones, which the shapes:draftSettled check row makes legible.",
   "tags": [
     "capability:define-detection"
-  ]
+  ],
+  "deliveredBy": {
+    "tacId": "TAC-4135-readiness-command-page"
+  }
 }

package/rcf/tacs/tac-4127-readiness-view.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-06T12:00:00Z",
+  "updatedAt": "2026-10-07T13:46:37.736Z",
   "tacId": "TAC-4127-readiness-view",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
@@ -46,5 +46,5 @@
       "description": "[draft] Decide persona ordering from profile.md text; same contract as the CLI helper (productOwner | engineer | unstated)."
     }
   ],
-  "notes": "The 0.29.0 scope keeps the diff component document-level only; criterion-level before-and-after is deferred to the UX review per ADR-4127. The pill component is additive and never changes the Product Map `pm-mini` or Requirements `status-chip` markup in this PR; those swaps are follow-ups once a mechanical mapping is established."
+  "notes": "The 0.29.0 scope keeps the diff component document-level only; criterion-level before-and-after is deferred to the UX review per ADR-4127. The pill component is additive and never changes the Product Map `pm-mini` or Requirements `status-chip` markup in this PR; those swaps are follow-ups once a mechanical mapping is established. Amended by DEFINE 2026-10-07 (TAC-4135-readiness-command-page, ADR-4139): the Freeze now control is removed (Q4: the freeze block shows the state and what resolves it, no button, no command text), the first-paint per-document delta list becomes counts with an on-demand list (Q2), the blocker cards and their 20-id cap become the blocking table, and renderCoverage is replaced by renderCoverageSummary reading coverage.tree.totals."
 }

package/rcf/tacs/tac-4133-readiness-po-layer.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-10-02T19:30:00Z",
-  "updatedAt": "2026-10-02T19:30:00Z",
+  "updatedAt": "2026-10-07T13:46:36.966Z",
   "tacId": "TAC-4133-readiness-po-layer",
   "prdId": "PRD-001",
   "tadId": "TAD-001",
@@ -33,5 +33,5 @@
       "description": "[draft] renderStageLegend(stages) returns the StageLegend dialog HTML (D1..D8 by name, one-line meaning, posture)."
     }
   ],
-  "notes": "Depends on PR 2's DocRow component, PR 1's AppShell and relative-script policy, and PR 2's SubTabStrip (not used here but shared vocabulary). Amends TAC-4127-readiness-view: the old engineer rendering is kept but is now the body of the For-engineers DocRow at the foot of the panel; nothing is removed from the engineer-level DOM (AC-18002-3). The phrasebook ships now (design doc section 11 recommendation 4); when DEFINE step 3 PR 2 lands `readiness.questions`, the adapter switches source with a one-line feature detect and the call site is unchanged. No em-dash is ever written in the phrasebook strings."
+  "notes": "Depends on PR 2's DocRow component, PR 1's AppShell and relative-script policy, and PR 2's SubTabStrip (not used here but shared vocabulary). Amends TAC-4127-readiness-view: the old engineer rendering is kept but is now the body of the For-engineers DocRow at the foot of the panel; nothing is removed from the engineer-level DOM (AC-18002-3). The phrasebook ships now (design doc section 11 recommendation 4); when DEFINE step 3 PR 2 lands `readiness.questions`, the adapter switches source with a one-line feature detect and the call site is unchanged. No em-dash is ever written in the phrasebook strings. Amended by DEFINE 2026-10-07 (TAC-4135-readiness-command-page, ADR-4139): the question cards and the For-engineers DocRow are superseded by the questions table and the blocking table; renderReadinessPO keeps its name and composes the tables; toQuestions and the phrasebook are unchanged; AC-18002-3 is satisfied by the blocking table (nothing engineer-level leaves the DOM)."
 }

package/rcf/tacs/tac-4135-readiness-command-page.json

@@ -0,0 +1,94 @@
+{
+  "createdAt": "2026-10-07T13:46:20.782Z",
+  "updatedAt": "2026-10-07T13:46:20.782Z",
+  "purpose": "Render the Readiness tab as the command page: every question and every blocking item is a row in a linked table, counts are links into the tables they count, the delta is counts with an on-demand list, coverage is a summary with real numbers, thin requirements are fed by every signal that names one, and the panel is split into sub-tabs (Overview, Questions, Blocking, Coverage, Trace) whose key rides in the hash as sub=. The page is read-only: it never renders a shell command, never offers a write control and never writes under rcf/. Each row carries what a human needs to brief their agent: the item id, the plain-English ask or finding, the chain location, a link that opens the item in full context, and what resolved looks like; the questions table adds a one-line copy handle (id plus ask, no command text). Sub-tabs are the designed shape; one long page with anchor navigation is the named alternative (decision Q5 is ruled on the rendered sketches, see notes).",
+  "responsibilities": [
+    "src/view/readiness/tables.js: renderQuestionsTable(readiness) and renderBlockingTable(readiness, opts) emit one HTML table each from readiness.questions[] and stages[].checks[].failing[]; no row cap; composite ids split through splitCompositeId; every href is a hash route the page-init router resolves.",
+    "src/view/readiness/coverage-summary.js: renderCoverageSummary(readiness, model) reads coverage.tree.totals, requirements[].coverageClass and unresolvedTestPointers[] plus family counts from the tree model; prints numbers or the words coverage unavailable, never a blank.",
+    "src/view/readiness/thin-reqs.js: buildThinReqRows(readiness, model) joins D4 stories:usFloors failing US ids to their REQ via us.reqId, stories with zero criteria, criteria with no resolving test from coverage acs[].covered, D2 skeleton:reqIntent and stories:reqHasUs; renderThinReqsTable renders the rows the two verdict cards link to.",
+    "src/view/readiness/grid.js: renderVerdictGrid(readiness) groups stages[].checks[] by stage and over (tree, delta), prints pass/total per cell and links the failing count into the blocking table filtered to that stage; the acknowledged state and its reason come from stages[].state and one reason helper, never from freezeRecord.gates directly.",
+    "src/view/readiness.js: renderReadinessPanel keeps its signature; it now composes the sub-tab strip (SubTabStrip with hashKey readiness) and the five sub-views; the For-engineers DocRow wrapper, the Freeze now control, the per-document delta list on first paint and the blocker cards are removed, their content living in the named tables and blocks; the CLI verdict strings still render so parity with rcf define readiness --json is unchanged.",
+    "src/view/page-init.js: the router reads sub= for the readiness tab the way it does for build, restores it after an SSE swap, drops an unknown value back to overview, and wires the Copy for your agent control through the existing toast component.",
+    "src/view/style.css: new .rcf-cmd-* rules use only existing --sv-* tokens on known surfaces so test/view/contrast-aa.test.js stays green in both themes; tables collapse to stacked rows under 720px and never force horizontal page scroll under data-embed=1."
+  ],
+  "internalStructure": "Pure server-rendered HTML string builders under src/view/readiness/ (tables.js, coverage-summary.js, thin-reqs.js, grid.js, composite-id.js), one composition site in src/view/readiness.js, and client wiring in page-init.js for the sub-tab strip and the copy handle. No new query module: every number is read from the computeReadiness result that src/view/index.js already folds (readiness.questions, stages, delta, coverage, levels, personas) and from BuiltTreeModel lengths. computeReadiness keeps its signature; renderModelToPage keeps its return additive. No inline script; no new localStorage key; no new dependency.",
+  "interfaces": [
+    {
+      "name": "renderQuestionsTable",
+      "kind": "other",
+      "description": "renderQuestionsTable(readiness) returns the questions table HTML: one QuestionRow per readiness.questions[] entry, group label as a sortable column, the location link, what settles it in plain words, the copy handle, the state. Empty questions[] renders the intent-complete verdict line (AC-18002-2 preserved)."
+    },
+    {
+      "name": "renderBlockingTable",
+      "kind": "other",
+      "description": "renderBlockingTable(readiness, { stage, persona }) returns the blocking table HTML: one BlockingRow per failing item across stages[].checks[].failing[], filterable by stage and persona through the existing FilterBar, no row cap, every id a resolving link."
+    },
+    {
+      "name": "splitCompositeId",
+      "kind": "other",
+      "description": "splitCompositeId(id) returns { docId, fragment } by splitting on the first colon; a plain document id returns fragment null. Used for every href the tables emit so a composite finding id such as AC-060-3:userID links to AC-060-3."
+    },
+    {
+      "name": "renderCoverageSummary",
+      "kind": "other",
+      "description": "renderCoverageSummary(readiness, model) returns the coverage block HTML: family stat tiles, one stacked bar from the three class totals, the percentage covered and the unresolved-pointers table; prints coverage unavailable when totals are absent."
+    },
+    {
+      "name": "renderThinReqsTable",
+      "kind": "other",
+      "description": "renderThinReqsTable(rows) returns the thin-requirements table HTML from ThinReqRow[]; sortable, filterable by reason; the row count is the number the verdict card links to."
+    },
+    {
+      "name": "renderVerdictGrid",
+      "kind": "other",
+      "description": "renderVerdictGrid(readiness) returns the stage grid HTML: eight stage rows, tree and delta columns, pass/total per VerdictGridCell, failing count linked into the blocking table filtered to that stage; replaces the chip row and the stage detail on the Overview sub-tab."
+    },
+    {
+      "name": "renderDeltaCounts",
+      "kind": "other",
+      "description": "renderDeltaCounts(readiness, freezeRecord) returns the delta block HTML as six counts (DeltaCounts) with a details element that renders the per-document list and diff only when the reader expands it; the first paint never carries the per-document rows."
+    },
+    {
+      "name": "readinessSubTabs",
+      "kind": "other",
+      "description": "The readiness tab's SubTabStrip (hashKey readiness) with keys overview, questions, blocking, coverage and trace. The router writes and reads sub= for readiness exactly as it does for build, restores it after an SSE innerHTML swap and resolves an unknown key to overview."
+    },
+    {
+      "name": "QuestionRow",
+      "kind": "recordShape",
+      "description": "One row of the questions table.\nfields: number, id, ask, location, locationHref, settles, briefHandle, state\nnotes: number is the display ordinal; id is the readiness question id; location is the chain location in words (statement n, profile field, requirement id); locationHref is the hash route that opens the item in full context; settles is the plain-English resolved state; briefHandle is the one-line id-plus-ask copy text; state is open or answered."
+    },
+    {
+      "name": "BlockingRow",
+      "kind": "recordShape",
+      "description": "One row of the blocking table.\nfields: stage, check, id, docId, fragment, href, why, resolved\nnotes: stage is D1 to D8; check is the check id; id is the finding id as the gate emitted it; docId and fragment are the splitCompositeId halves; href is the resolving hash route; why is the gate's finding text; resolved is what the resolved state looks like in plain words."
+    },
+    {
+      "name": "ThinReqRow",
+      "kind": "recordShape",
+      "description": "One row of the thin-requirements table.\nfields: reqId, stories, criteria, covered, thinReason, openHref, traceHref\nnotes: stories and criteria are counts; covered is the count of criteria with a resolving test; thinReason is the thin reason in words; openHref opens the requirement; traceHref opens the Trace sub-tab pivoted on it."
+    },
+    {
+      "name": "CoverageSummary",
+      "kind": "recordShape",
+      "description": "The coverage block's data.\nfields: families, totals, percentCovered, unresolvedPointers\nnotes: families is the per-family document count (requirements, stories, criteria, suites, cases, buildSpecs); totals is coverage.tree.totals verbatim; percentCovered is covered over requirements; unresolvedPointers is coverage.tree.unresolvedTestPointers verbatim."
+    },
+    {
+      "name": "VerdictGridCell",
+      "kind": "recordShape",
+      "description": "One cell of the stage grid.\nfields: stage, over, pass, total, failing, state, href\nnotes: over is tree or delta; pass and total are summed over the stage's checks in that scope; failing is the count of failing items; state is the stage state (passed, failing, acknowledged, notApplicable); href links into the blocking table filtered to the stage."
+    },
+    {
+      "name": "DeltaCounts",
+      "kind": "recordShape",
+      "description": "The delta block's data on first paint.\nfields: changed, added, removed, briefSince, impacted, impactedFbs, expanded\nnotes: the six counts are readiness.delta lengths; expanded is false on first paint and true only after the reader opens the per-document list."
+    }
+  ],
+  "notes": "Supersedes the layout pinned by REQ-180's earlier description and the question-card and For-engineers DocRow blocks of TAC-4133-readiness-po-layer (renderReadinessPO keeps its name and now composes the tables; toQuestions is unchanged); amends TAC-4127-readiness-view by removing the Freeze now control and the first-paint delta list. Rulings carried: Q1 (viewer read-only, no CLI command text anywhere on the page, rows carry id, ask or finding, chain location, link, resolved state; the copy handle is a design candidate shown in the wireframe); Q2 (delta on an unfrozen tree is counts only with on-demand expand); Q3 (thin requirements table lists all three flavours: zero criteria, unresolved tests, D4 floor failures); Q4 (no freeze button, no command text; show the state and what resolves it). Q5 alternative: one long page with anchor navigation instead of sub-tabs; the two sketches discovery-viewer-command-page-5-subtabs.html and discovery-viewer-command-page-6-one-page.html under guidance/discovery/ carry the same data in both shapes and the product owner rules on the render; if the one-page shape is chosen, readinessSubTabs becomes an anchor strip and sub= is dropped, nothing else in this TAC changes. Embed and theme contract (issues 263 and 264): every href is relative or a hash route, no new route is added by this TAC, no new localStorage key, the control row stays inside the panel under data-embed=1, and every colour is an existing --sv-* token on a known surface. On-me vocabulary: the Overview sub-tab names what waits on the product owner as On me and what waits on engineers as On engineers. No Mermaid anywhere on the tab.",
+  "tacId": "TAC-4135-readiness-command-page",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "name": "Readiness command page: linked tables, verdict grid, delta counts, coverage summary, thin requirements, sub-tabs"
+}

package/rcf/tacs/tac-4136-view-query-routes.json

@@ -0,0 +1,68 @@
+{
+  "createdAt": "2026-10-07T13:46:28.216Z",
+  "updatedAt": "2026-10-07T13:46:28.216Z",
+  "purpose": "Expose the pure trace, impact and coverage computes the CLI already calls as three GET JSON routes on the viewer server, computed from the current walked state and cached per state.version, and render a trace matrix for a selected node on the Readiness tab's Trace sub-tab with a Trace action on every id. Admissibility statement: the three routes do NOT call runWithAdmissibilityGate; they bypass the gate exactly as src/cli/coverage.js, src/cli/impact.js and src/cli/trace.js do (issues 316 and 317 context), so a tree that fails admissibility still answers trace, impact and coverage in the viewer; only readiness and freeze consult the gate. The routes are read-only, GET and HEAD only like every other route, and never write under rcf/.",
+  "responsibilities": [
+    "src/server/routes.js: three handlers after /index.json, each reading deps.currentState(), answering 503 view server initialising before the first walk, 404 unknown-id for an unknown pivot, 400 bad-direction for a bad direction, and application/json with cache-control: no-store otherwise. Relative to the viewer mount so a reverse proxy sees ./trace.json under the mount point; release-noted so host allow-lists (the WESPA proxy added ./page-init.js by hand for 0.29.0) are extended before a version pin bump.",
+    "src/view/index.js: renderModelToPage keeps the walked tree on the returned state (additive) so the routes compute per request from the same tree the page was rendered from; a per-version memo (queryCache) keyed by state.version and the pivot plus direction holds each computed result so a repeated request is served from memory and a rewalk discards the previous version's entries.",
+    "src/query/: unchanged. computeTrace(tree, { id, direction }), computeImpact(tree, { id }) and computeCoverage(tree, { testPointers, mode }) are imported as they are; no new query module.",
+    "src/view/readiness/trace-matrix.js: renderTraceMatrix(trace, coverage, model) builds the matrix from a forward trace: rows are the stories and criteria under the pivot, columns are suites, cases, build specs and components (component via usByTacId), cells coloured by resolution from coverage acs[]; a row filter appears past 200 rows; the empty state names an unknown pivot.",
+    "src/view/page-init.js: wireTraceMatrix fetches ./trace.json and ./coverage.json for the pivot from the hash (entity= on sub=trace), caches the result in memory keyed by state.version, re-renders after an SSE swap and marks the result stale until the next fetch; every table row's Trace action and the lookup modal's readiness hits write #tab=readiness&sub=trace&entity=<id>.",
+    "src/view/html-page.js and src/view/mermaid-diagram.js: the per-requirement Mermaid slice (allRequirementSubdiagrams and the rcf-req-slice details) is removed; no Mermaid is rendered user-facing by this capability."
+  ],
+  "internalStructure": "Server half: route handlers in src/server/routes.js that call the pure query functions on the state's tree and memoise by (version, pivot, direction) in a Map held on the server closure; the memo is replaced wholesale on every rewalk. Client half: wireTraceMatrix in page-init.js (fetch, cache, render, stale marking) and the pure renderer in src/view/readiness/trace-matrix.js. No inline script; no new dependency; no new localStorage key (the cache is a page-lifetime Map); theme by --sv-* tokens only.",
+  "interfaces": [
+    {
+      "name": "GET /trace.json",
+      "kind": "httpRoute",
+      "description": "method: GET\npath: /trace.json?id=<id>&direction=<forward|back|both>\nrequest: query id (a document id or inline AC or TC id), direction defaulting to forward\nresponse: application/json, the computeTrace result verbatim (pivot, direction, found, nodes[], edges[] or ancestors[] and descendants[] for both); cache-control: no-store\nerrors: 503 text before the first walk; 404 QueryRouteError unknown-id; 400 QueryRouteError bad-direction; 405 for any method other than GET or HEAD"
+    },
+    {
+      "name": "GET /impact.json",
+      "kind": "httpRoute",
+      "description": "method: GET\npath: /impact.json?id=<id>\nrequest: query id\nresponse: application/json, the computeImpact result verbatim (pivot, found, nodes[] with actionNeeded, edges[]); cache-control: no-store\nerrors: 503 text before the first walk; 404 QueryRouteError unknown-id; 405 for any method other than GET or HEAD"
+    },
+    {
+      "name": "GET /coverage.json",
+      "kind": "httpRoute",
+      "description": "method: GET\npath: /coverage.json?scope=<id>\nrequest: optional query scope narrowing to a PRD, REQ or US subtree as the CLI positional does; omitted means the whole tree; strict per-AC mode always\nresponse: application/json, the computeCoverage result verbatim (totals, requirements[] with acs[], unresolvedTestPointers[]); cache-control: no-store\nerrors: 503 text before the first walk; 400 QueryRouteError bad-scope for a below-AC or unknown scope id; 405 for any method other than GET or HEAD"
+    },
+    {
+      "name": "queryCache",
+      "kind": "other",
+      "description": "Server-side memo keyed by state.version plus pivot plus direction (or scope). One compute per key per version; replaced wholesale when the walker publishes a new version. Never persisted; never written under rcf/."
+    },
+    {
+      "name": "renderTraceMatrix",
+      "kind": "other",
+      "description": "renderTraceMatrix(trace, coverage, model) returns the matrix HTML for a forward trace: TraceMatrixRow per story and criterion, columns for suites, cases, build specs and components, TraceMatrixCell per intersection coloured by resolution; empty state when trace.found is false; row filter when rows exceed 200."
+    },
+    {
+      "name": "wireTraceMatrix",
+      "kind": "other",
+      "description": "Client wiring in page-init.js: reads entity= under sub=trace, fetches ./trace.json and ./coverage.json relative to the mount, caches by state.version in a page-lifetime Map, renders through renderTraceMatrix's client mirror, re-renders after an SSE innerHTML swap and marks stale; also decorates every id in the readiness tables with the Trace action and routes lookup hits for readiness rows."
+    },
+    {
+      "name": "TraceMatrixRow",
+      "kind": "recordShape",
+      "description": "One row of the matrix.\nfields: usId, acId, title, cells\nnotes: usId and acId identify the story and criterion; title is the criterion text; cells is the TraceMatrixCell list in column order."
+    },
+    {
+      "name": "TraceMatrixCell",
+      "kind": "recordShape",
+      "description": "One cell of the matrix.\nfields: columnId, columnKind, reached, resolution\nnotes: columnKind is ts, tc, fbs or tac; reached is true when the trace reaches the column from the row's criterion; resolution is resolving, unresolved or none, read from coverage acs[] for tc columns and none otherwise."
+    },
+    {
+      "name": "QueryRouteError",
+      "kind": "recordShape",
+      "description": "The JSON error body the three routes return on 400 and 404.\nfields: error, id, direction, scope\nnotes: error is unknown-id, bad-direction or bad-scope; id, direction and scope echo the request values that were present."
+    }
+  ],
+  "notes": "Decision taken (ADR-4140): GET per pivot, cached by version, no whole-tree dump (PRD-001 forward on the largest consumer tree is 2,972 nodes and 1.5 MB of JSON), matrix not sunburst, no Mermaid user-facing, and the admissibility bypass stated above. Embed and theme contract (issues 263 and 264): the three routes are relative to the mount and release-noted for proxy allow-lists; the client cache is a page-lifetime Map, not localStorage; the matrix uses only --sv-success, --sv-warning, --sv-danger and --sv-muted on --sv-surface so test/view/contrast-aa.test.js is unaffected. Deferred and named: an impact sub-view with action labels per row and keyboard row navigation (discovery capabilities 10 and 13), a readiness timeline (17), and the Product Map trace bucket realignment to resolution-gated coverage; none of them is in the five FBS of this DEFINE.",
+  "tacId": "TAC-4136-view-query-routes",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "name": "View query routes: trace, impact and coverage as JSON, the trace matrix and Trace actions"
+}

package/rcf/tacs/tac-4141-verify-modes.json

@@ -0,0 +1,25 @@
+{
+  "createdAt": "2026-10-08T15:39:45.639Z",
+  "updatedAt": "2026-10-08T15:39:45.639Z",
+  "purpose": "Implement the ADR-4141 decision: `rcf verify run` gains a `--mode <agentScreenshotCritique|deterministic>` flag (default agentScreenshotCritique); the deterministic engine runs in-process (`src/verify/engine/deterministic.js`) with a reachability HTTP probe on runStats and a per-AC skip ledger recorded on blockedAcs[] as critique-only, so the aggregate verdict is BLOCKED. The CLI stamps runStats.mode and runStats.counts on the report. `rcf build finalise` gains the same `--mode` flag, threads it through to the fresh verify subprocess via buildVerifyArgs, preseeds the --out path with a `{ status: pending, launchFailure.reason: preseed }` stub BEFORE the spawn, overwrites that stub with a `{ status: aborted }` record if verify exits non-zero without writing (so ingest never surfaces ENOENT), and refuses promotion with the counts line when a deterministic run skipped any AC (ADR-4112 verified invariant). The HOLD-authority branch treats a preseed-only report as unreadable (NIT-3 'unreadable is not a pass').",
+  "responsibilities": [
+    "Add src/verify/engine/deterministic.js with VERIFY_MODES, DEFAULT_VERIFY_MODE, isVerifyMode, probeHttpReachability, and runDeterministic. The last returns { findings: [], blockedAcs: [{acId, reason: 'critique-only...', mode: 'deterministic'}], runStats: { mode, httpProbe, counts, startedAtMs, finishedAtMs } }.",
+    "Branch the engine's launcher step on opts.mode === 'deterministic': call runDeterministic in-process, merge its blockedAcs into the provisioning-side list, and skip the agent CLI launcher entirely.",
+    "Stamp runStats.mode on every report path (normal, NOT-DEPLOYED, LAUNCH-FAILURE).",
+    "Add `--mode` to src/verify/cli/run.js and src/cli/finalise.js with an isVerifyMode guard (unknown value exits 2).",
+    "Thread `--mode` through src/finalise/spawn.js buildVerifyArgs.",
+    "Preseed the --out path in finalise before spawn with `{ verdict: 'LAUNCH-FAILURE', verdictAuthority: null, launchFailure: { status: 'aborted', reason: 'preseed' } }`.",
+    "On a non-zero spawn exit whose report is still the preseed, overwrite with a real `{ status: 'aborted', reason: 'rcf verify exited <code> without writing a report', exitCode }` record.",
+    "In the HOLD-authority branch, detect a preseed-only report and surface it as unreadable (never a silent promotion).",
+    "Add the deterministic refusal line: if runStats.mode === 'deterministic' and (counts.skipped > 0 OR counts.verified < counts.total), refuse promotion with the counts line and reference ADR-4112."
+  ],
+  "internalStructure": "Branch at step 6 of runVerification. Deterministic is a straight-line reducer over chain.acs; agent mode is unchanged. The CLI changes are a flag + a one-line thread-through. Finalise's preseed is an upfront writeFile; the overwrite is in the gate-NOT-passed branch, guarded by `report?.launchFailure?.reason === 'preseed'` so a legitimate verify-authored launch-failure report is not clobbered.",
+  "interfaces": [],
+  "notes": "Behavioural addition, not a change: agent-mode runs are unchanged. Deterministic mode's BLOCKED verdict already trips the existing gate (verify exit 5 -> finalise exit 4); the new refusal line is UX for the operator so they see the counts and the ADR reference immediately. No rcf-schemas bump: runStats and launchFailure both accept additional fields today.",
+  "tacId": "TAC-4141-verify-modes",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "0.1.0",
+  "status": "draft",
+  "name": "verify modes CLI + deterministic engine + preseed partial report"
+}

package/rcf/test-suites/ts-223.json

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-06T12:00:00Z",
+  "updatedAt": "2026-10-08T16:43:35.128Z",
   "purpose": "Cover US-18001 (Readiness as tab 1 and the PRD rename, plus the live-client resync SSOT guard added for issue 297) and US-18101 (shared pill, findings-list and diff components). Shares the readiness fixture builders with TS-222 so the tab and the CLI assertions ride the same shapes.",
   "testLevel": "unit",
   "acIds": [
@@ -37,16 +37,16 @@
     {
       "id": "TC-223-po-blockers-as-findings-list",
       "acId": "AC-18001-3",
-      "description": "Each PO blocker renders as a findings list headed by its question with its ids as anchor links into the document tabs.",
+      "description": "Each PO blocker id appears in the questions table under its question group with the id as an anchor link into the document tabs.",
       "status": "pending",
-      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-3 PO blockers render as findings lists with id anchors"
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-3 PO blocker ids appear in the questions table"
     },
     {
       "id": "TC-223-register-orders-persona-groups",
       "acId": "AC-18001-4",
-      "description": "With a profile register of productOwner, the PO group is expanded first and the engineer group collapses with its count visible.",
+      "description": "With a profile register of productOwner, the questions table precedes the blocking table.",
       "status": "pending",
-      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-4 register orders the pair and collapses the opposite"
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-4 register orders the questions and blocking tables"
     },
     {
       "id": "TC-223-no-blocker-id-omitted",
@@ -58,9 +58,9 @@
     {
       "id": "TC-223-freeze-now-disabled",
       "acId": "AC-18001-6",
-      "description": "When levels.readyToBuild.ok is false the Freeze now control is disabled and names the failing gates from levels.readyToBuild.blockedBy.",
+      "description": "When levels.readyToBuild.ok is false the freeze state block names the failing gates from levels.readyToBuild.blockedBy in plain words and no freeze control is rendered.",
       "status": "pending",
-      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-6 Freeze now is disabled and names the failing gates"
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-6 freeze state names failing gates in plain words, no freeze control"
     },
     {
       "id": "TC-223-ids-on-tab-match-cli-json",

package/rcf/test-suites/ts-237.json

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-10-07T13:47:03.889Z",
+  "updatedAt": "2026-10-08T17:03:01.078Z",
+  "purpose": "Cover every acceptance criterion of US-18003 with one node:test case each in test/view/readiness-tables.test.js; DEFINE lands the named declarations flagged not yet built so the strict coverage audit binds each criterion, and BUILD (FBS-204) removes the flags as it makes them pass.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-18003-1",
+    "AC-18003-2",
+    "AC-18003-3",
+    "AC-18003-4",
+    "AC-18003-5",
+    "AC-18003-6",
+    "AC-18003-7",
+    "AC-18003-8"
+  ],
+  "testCases": [
+    {
+      "id": "TC-237-18003-1-happy",
+      "acId": "AC-18003-1",
+      "description": "[happy] Given readiness.questions is non-empty, when the questions sub-view renders, then it is one table with one QuestionRow per question carrying QuestionRow.number, QuestionRow.ask, QuestionRow.location as a link that opens the item in full context, QuestionRow.settles in plain words and QuestionRow.state, and the group label is a sortable column rather than a heading.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-1 happy: readinessquestions is nonempty"
+    },
+    {
+      "id": "TC-237-18003-2-edge",
+      "acId": "AC-18003-2",
+      "description": "[edge] Given a question whose itemId is not a document id (a brief statement such as \"brief-ledger\" or a profile field such as \"profile:surface\"), when the row renders, then QuestionRow.locationHref is \"#tab=readiness&sub=questions&entity=<itemId>\" and the router lands on that row, so the page never emits a dead anchor.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-2 edge: a question whose itemid is not a document id a b"
+    },
+    {
+      "id": "TC-237-18003-3-happy",
+      "acId": "AC-18003-3",
+      "description": "[happy] Given every failing check across stages, when the blocking sub-view renders, then it is one table with one BlockingRow per failing item carrying BlockingRow.stage, BlockingRow.check, BlockingRow.docId as a link, BlockingRow.why from the gate and BlockingRow.resolved in plain words, with no cap on the number of rows and a FilterBar by stage and persona.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-3 happy: every failing check across stages"
+    },
+    {
+      "id": "TC-237-18003-4-edge",
+      "acId": "AC-18003-4",
+      "description": "[edge] Given a composite failing id such as \"AC-060-3:userID\" or \"TAC-4122-define-gates:checkPersona\", when its row renders, then BlockingRow.docId is the text before the first colon, BlockingRow.fragment is the remainder and BlockingRow.href targets the document id so the link resolves through findByDocId.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-4 edge: a composite failing id such as ac0603userid or t"
+    },
+    {
+      "id": "TC-237-18003-5-happy",
+      "acId": "AC-18003-5",
+      "description": "[happy] Given a question row, when the copy control renders, then QuestionRow.briefHandle is one line holding the item id and the plain-English ask, the control is labelled \"Copy for your agent\" and copies that line through the existing toast feedback, and the line holds no command text.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-5 happy: a question row"
+    },
+    {
+      "id": "TC-237-18003-6-failure",
+      "acId": "AC-18003-6",
+      "description": "[failure] Given readiness could not be computed (the readiness object is null), when the Readiness tab renders, then the existing \"could not be computed\" placeholder is shown and no table is rendered.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-6 failure: readiness could not be computed the readiness ob"
+    },
+    {
+      "id": "TC-237-18003-7-mustnot",
+      "acId": "AC-18003-7",
+      "description": "[must-not] Given any register and any tree, when the panel renders for the command page, then the viewer emits no shell command text: no code element carries a command, no Run or Freeze-now affordance exists; chain ids are content, rendered as a prefix link with a plain-English label from the chain, and the full composite id stays in the DOM in a data attribute.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-7 must-not: no shell command text, chain ids as prefix link with full id in data attribute"
+    },
+    {
+      "id": "TC-237-18003-8-happy",
+      "acId": "AC-18003-8",
+      "description": "[happy] Given the profile register is \"engineer\", when the tab first paints, then the blocking table precedes the questions table; given \"productOwner\" or no profile, the questions table precedes the blocking table; in both cases both tables are present in the DOM.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tables.test.js::AC-18003-8 happy: the profile register is engineer"
+    }
+  ],
+  "id": "TS-237",
+  "usId": "US-18003",
+  "title": "US-18003 command page suite (readiness-tables)",
+  "status": "draft"
+}

package/rcf/test-suites/ts-238.json

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-10-07T13:47:04.672Z",
+  "updatedAt": "2026-10-09T10:01:25.009Z",
+  "purpose": "Cover every acceptance criterion of US-18004 with one node:test case each in test/view/readiness-coverage-summary.test.js; DEFINE lands the named declarations flagged not yet built so the strict coverage audit binds each criterion, and BUILD (FBS-205) removes the flags as it makes them pass.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-18004-1",
+    "AC-18004-2",
+    "AC-18004-3",
+    "AC-18004-4",
+    "AC-18004-5",
+    "AC-18004-6",
+    "AC-18004-7"
+  ],
+  "testCases": [
+    {
+      "id": "TC-238-18004-1-happy",
+      "acId": "AC-18004-1",
+      "description": "[happy] Given readiness.coverage.tree carries totals, when the coverage sub-view renders, then CoverageSummary.totals shows requirements, covered, coveredUnresolved and uncovered as numbers and CoverageSummary.percentCovered as a percentage, never a blank value.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-1 happy: readinesscoveragetree carries totals"
+    },
+    {
+      "id": "TC-238-18004-2-happy",
+      "acId": "AC-18004-2",
+      "description": "[happy] Given the tree model, when the coverage sub-view renders, then CoverageSummary.families lists the document counts per family (requirements, stories, criteria, suites, cases, build specs) as stat tiles and one stacked bar whose three widths are the three class totals, using only the --sv-success, --sv-warning and --sv-danger tokens on --sv-surface.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-2 happy: the tree model"
+    },
+    {
+      "id": "TC-238-18004-3-happy",
+      "acId": "AC-18004-3",
+      "description": "[happy] Given coverage.tree.unresolvedTestPointers is non-empty, when the coverage sub-view renders, then an unresolved-pointers table lists each pointer with its suite id as a link, its case id, the pointer text and the reason word the CLI prints (for example \"test-missing\" or \"file-missing\").",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-3 happy: coveragetreeunresolvedtestpointers is nonempty"
+    },
+    {
+      "id": "TC-238-18004-4-happy",
+      "acId": "AC-18004-4",
+      "description": "[happy] Given a requirement that fails at least one thin reason from the list [no story | zero criteria on a story | a criterion with no resolving test | a story failing the D4 floors | no plain description], when the thin-requirements table renders, then it carries one ThinReqRow for that requirement with ThinReqRow.stories, ThinReqRow.criteria, ThinReqRow.covered, ThinReqRow.thinReason, ThinReqRow.openHref and ThinReqRow.traceHref.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-4 happy: a requirement that fails at least one thin reaso"
+    },
+    {
+      "id": "TC-238-18004-5-happy",
+      "acId": "AC-18004-5",
+      "description": "[happy] Given the two verdict cards, when the overview sub-view renders, then the question count on the Ready for engineers card is a link to the questions table, the engineer item count on the Ready to build card is a link to the blocking table, and the former What happens next paragraph is folded into the cards as one sentence each.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-5 happy: the two verdict cards"
+    },
+    {
+      "id": "TC-238-18004-6-failure",
+      "acId": "AC-18004-6",
+      "description": "[failure] Given a coverage result with no totals (a partial tree or an older compute), when the coverage sub-view renders, then it shows the words \"coverage unavailable\" and the rest of the panel still renders.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-6 failure: a coverage result with no totals a partial tree"
+    },
+    {
+      "id": "TC-238-18004-7-mustnot",
+      "acId": "AC-18004-7",
+      "description": "[must-not] Given any tree, when the coverage sub-view renders, then it never prints an empty number: a value the coverage result does not carry renders as \"coverage unavailable\", not as a blank.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-coverage-summary.test.js::AC-18004-7 must-not: any tree"
+    }
+  ],
+  "id": "TS-238",
+  "usId": "US-18004",
+  "title": "US-18004 command page suite (readiness-coverage-summary)",
+  "status": "draft"
+}

package/rcf/test-suites/ts-239.json

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-10-07T13:47:05.533Z",
+  "updatedAt": "2026-10-09T12:09:27.300Z",
+  "purpose": "Cover every acceptance criterion of US-18005 with one node:test case each in test/view/readiness-layout.test.js; DEFINE lands the named declarations flagged not yet built so the strict coverage audit binds each criterion, and BUILD (FBS-206) removes the flags as it makes them pass.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-18005-1",
+    "AC-18005-2",
+    "AC-18005-3",
+    "AC-18005-4",
+    "AC-18005-5",
+    "AC-18005-6",
+    "AC-18005-7",
+    "AC-18005-8"
+  ],
+  "testCases": [
+    {
+      "id": "TC-239-18005-1-happy",
+      "acId": "AC-18005-1",
+      "description": "[happy] Given readiness.stages, when the overview sub-view renders, then a stage grid shows each stage as a row and the scopes \"tree\" and \"delta\" as columns, each VerdictGridCell carrying VerdictGridCell.pass, VerdictGridCell.total and VerdictGridCell.state, with VerdictGridCell.failing rendered as a link into the blocking table filtered to that stage.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-1 happy: stage grid renders rows x (tree, delta) with pass/total/state and failing-count link"
+    },
+    {
+      "id": "TC-239-18005-2-happy",
+      "acId": "AC-18005-2",
+      "description": "[happy] Given the Readiness tab, when it renders, then a SubTabStrip offers \"Overview\", \"Questions\", \"Blocking\", \"Coverage\" and \"Trace\", the active key is written into the hash as sub=, and the router restores it on load and after an SSE innerHTML swap of #rcf-live-content.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-2 happy: the SubTabStrip offers five keys, activeSub is reflected, and the router restores sub= on load and after an SSE swap"
+    },
+    {
+      "id": "TC-239-18005-3-happy",
+      "acId": "AC-18005-3",
+      "description": "[happy] Given an unfrozen tree, when the delta block renders, then DeltaCounts.changed, DeltaCounts.added, DeltaCounts.removed, DeltaCounts.briefSince, DeltaCounts.impacted and DeltaCounts.impactedFbs render as numbers and the per-document list with its diff widgets renders only after the reader expands the details element (DeltaCounts.expanded true).",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-3 happy: delta counts render six numbers; per-document list only after expand"
+    },
+    {
+      "id": "TC-239-18005-4-happy",
+      "acId": "AC-18005-4",
+      "description": "[happy] Given the profile register is \"engineer\", when the tab renders, then the For-engineers DocRow wrapper is absent and every engineer item (failing ids with why, next action, stage states, coverage counts, decisions outstanding, freeze state) is present in a named table or block of the sub-views.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-4 happy: engineer register has no For-engineers DocRow wrapper and every engineer item is present in a named block"
+    },
+    {
+      "id": "TC-239-18005-5-happy",
+      "acId": "AC-18005-5",
+      "description": "[happy] Given ready-to-build is \"no\", when the freeze block renders, then it names each failing gate in plain words with what resolves it, with no button and no command text; given ready-to-build is \"yes\", it states that the tree can be frozen and what a freeze would record.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-5 happy: freeze state words - names failing gates when not ready; names what a freeze records when ready"
+    },
+    {
+      "id": "TC-239-18005-6-edge",
+      "acId": "AC-18005-6",
+      "description": "[edge] Given a stage acknowledged at the current tree hash, when the grid renders, then VerdictGridCell.state is \"acknowledged\" and the reason shows on hover, read from stages[].state and one reason helper rather than from freezeRecord.gates directly.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-6 edge: acknowledged cell state comes from stages[].state and the ack reason via one helper"
+    },
+    {
+      "id": "TC-239-18005-7-mustnot",
+      "acId": "AC-18005-7",
+      "description": "[must-not] Given embed mode (data-embed=\"1\") and a viewport narrower than 720px, when the Readiness tab renders, then no table forces horizontal page scroll: tables collapse to stacked rows and the SubTabStrip stays inside the panel.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-7 must-not: embed + <720px keeps tables stacked and SubTabStrip inside the panel"
+    },
+    {
+      "id": "TC-239-18005-8-failure",
+      "acId": "AC-18005-8",
+      "description": "[failure] Given a hash whose sub= value is not a known readiness sub-tab key, when the router runs, then the overview sub-view is activated and the unknown value is dropped from the hash.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-layout.test.js::AC-18005-8 failure: unknown sub= drops to overview and is removed from the hash"
+    }
+  ],
+  "id": "TS-239",
+  "usId": "US-18005",
+  "title": "US-18005 command page suite (readiness-layout)",
+  "status": "draft"
+}