rcf-lite 0.32.4 → 0.33.0

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-10-07T13:47:06.367Z",
+  "updatedAt": "2026-10-08T18:05:44.868Z",
+  "purpose": "Cover every acceptance criterion of US-208 with one node:test case each in test/view/query-routes.test.js; DEFINE lands the named declarations flagged not yet built so the strict coverage audit binds each criterion, and BUILD (FBS-207) removes the flags as it makes them pass.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-208-1",
+    "AC-208-2",
+    "AC-208-3",
+    "AC-208-4",
+    "AC-208-5",
+    "AC-208-6",
+    "AC-208-7"
+  ],
+  "testCases": [
+    {
+      "id": "TC-240-208-1-happy",
+      "acId": "AC-208-1",
+      "description": "[happy] Given a running viewer and a known id, when GET \"./trace.json?id=<id>&direction=forward\" is requested, then the response is application/json carrying the computeTrace result for that pivot (pivot, direction, found, nodes, edges), computed from the current state and served with \"cache-control: no-store\" relative to the viewer mount.",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-1 happy: a running viewer and a known id"
+    },
+    {
+      "id": "TC-240-208-2-happy",
+      "acId": "AC-208-2",
+      "description": "[happy] Given a running viewer and a known id, when GET \"./impact.json?id=<id>\" is requested, then the response is application/json carrying the computeImpact result (pivot, found, nodes with actionNeeded per node, edges) with \"cache-control: no-store\".",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-2 happy: a running viewer and a known id"
+    },
+    {
+      "id": "TC-240-208-3-happy",
+      "acId": "AC-208-3",
+      "description": "[happy] Given a running viewer, when GET \"./coverage.json\" is requested with no scope, then the response is application/json carrying the strict computeCoverage result for the whole tree (totals, requirements, unresolvedTestPointers); given \"?scope=<id>\" naming a PRD, REQ or US, the result is narrowed to that subtree as the CLI positional narrows it.",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-3 happy: a running viewer"
+    },
+    {
+      "id": "TC-240-208-4-failure",
+      "acId": "AC-208-4",
+      "description": "[failure] Given an unknown id, when trace or impact is requested, then the response is 404 application/json with QueryRouteError.error \"unknown-id\" and QueryRouteError.id echoing the request; given a direction outside forward, back and both, the response is 400 with QueryRouteError.error \"bad-direction\"; given a below-AC or unknown scope on coverage, the response is 400 with QueryRouteError.error \"bad-scope\".",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-4 failure: an unknown id"
+    },
+    {
+      "id": "TC-240-208-5-mustnot",
+      "acId": "AC-208-5",
+      "description": "[must-not] Given any request to the three routes, when the server handles it, then runWithAdmissibilityGate is not called (the routes bypass the gate the way src/cli/coverage.js and src/cli/impact.js do) and nothing under rcf/ is written.",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-5 must-not: any request to the three routes"
+    },
+    {
+      "id": "TC-240-208-6-edge",
+      "acId": "AC-208-6",
+      "description": "[edge] Given a rewalk that publishes a new state.version, when a route is requested, then the served result reflects the new tree and the memo entries of the previous version are discarded; within one version a repeated request for the same pivot and direction is served from the memo without recomputing.",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-6 edge: a rewalk that publishes a new stateversion"
+    },
+    {
+      "id": "TC-240-208-7-failure",
+      "acId": "AC-208-7",
+      "description": "[failure] Given the server before the first walk completes, when a trace, impact or coverage request arrives, then the response is 503 text \"view server initialising\", as ./index.json answers today.",
+      "status": "pending",
+      "testPointer": "test/view/query-routes.test.js::AC-208-7 failure: the server before the first walk completes"
+    }
+  ],
+  "id": "TS-240",
+  "usId": "US-208",
+  "title": "US-208 command page suite (query-routes)",
+  "status": "draft"
+}

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-10-07T13:47:07.194Z",
+  "updatedAt": "2026-10-09T13:40:25.258Z",
+  "purpose": "Cover every acceptance criterion of US-209 with one node:test case each in test/view/trace-matrix.test.js; DEFINE lands the named declarations flagged not yet built so the strict coverage audit binds each criterion, and BUILD (FBS-208) removes the flags as it makes them pass.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-209-1",
+    "AC-209-2",
+    "AC-209-3",
+    "AC-209-4",
+    "AC-209-5",
+    "AC-209-6",
+    "AC-209-7"
+  ],
+  "testCases": [
+    {
+      "id": "TC-241-209-1-happy",
+      "acId": "AC-209-1",
+      "description": "[happy] Given the Trace sub-tab and a pivot id in the hash, when the client fetches \"./trace.json\" for it, then a matrix renders with one TraceMatrixRow per story and criterion under the pivot and columns for suites, cases, build specs and components, each TraceMatrixCell.reached true where the forward trace reaches the column from the row's criterion.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-1 happy: the trace subtab and a pivot id in the hash"
+    },
+    {
+      "id": "TC-241-209-2-happy",
+      "acId": "AC-209-2",
+      "description": "[happy] Given coverage data for the pivot's criteria, when a cell renders, then TraceMatrixCell.resolution is \"resolving\" on the --sv-success token, \"unresolved\" on the --sv-warning token or \"none\" on the --sv-muted token, with no new colour token introduced.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-2 happy: coverage data for the pivots criteria"
+    },
+    {
+      "id": "TC-241-209-3-happy",
+      "acId": "AC-209-3",
+      "description": "[happy] Given any id rendered in the questions, blocking, thin-requirements or coverage tables, when the row renders, then it carries a \"Trace\" action linking to \"#tab=readiness&sub=trace&entity=<id>\", and a lookup modal hit on a readiness row navigates to the same hash preserving embed and theme.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-3 happy: any id rendered in the questions blocking thinre"
+    },
+    {
+      "id": "TC-241-209-4-edge",
+      "acId": "AC-209-4",
+      "description": "[edge] Given an SSE tree-update that swaps #rcf-live-content while the Trace sub-tab shows a matrix, when the swap lands, then the matrix is re-rendered from the client cache keyed by state.version and marked stale until the next fetch completes, never dropped.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-4 edge: an sse treeupdate that swaps rcflivecontent whil"
+    },
+    {
+      "id": "TC-241-209-5-mustnot",
+      "acId": "AC-209-5",
+      "description": "[must-not] Given the Requirements tab, when a requirement renders, then no Mermaid slice diagram is rendered for it (the per-requirement slice and its details element are gone) and no Mermaid is rendered anywhere on the Readiness tab.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-5 must-not: the requirements tab"
+    },
+    {
+      "id": "TC-241-209-6-failure",
+      "acId": "AC-209-6",
+      "description": "[failure] Given a pivot the route reports with found false, when the Trace sub-tab renders, then an empty state names the id and offers the lookup modal, and no partial matrix is drawn.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-6 failure: a pivot the route reports with found false"
+    },
+    {
+      "id": "TC-241-209-7-edge",
+      "acId": "AC-209-7",
+      "description": "[edge] Given a pivot whose forward trace yields more than 200 TraceMatrixRow entries, when the matrix renders, then a row filter by story id or criterion id is shown, the full TraceMatrixRow.cells set is retained in memory and nothing is truncated silently.",
+      "status": "pending",
+      "testPointer": "test/view/trace-matrix.test.js::AC-209-7 edge: a pivot whose forward trace yields more than 200"
+    }
+  ],
+  "id": "TS-241",
+  "usId": "US-209",
+  "title": "US-209 command page suite (trace-matrix)",
+  "status": "draft"
+}

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

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-10-08T15:50:28.920Z",
+  "updatedAt": "2026-10-08T15:50:43.321Z",
+  "purpose": "Cover the --mode flag on rcf verify run and rcf build finalise, the deterministic engine output shape (findings/blockedAcs/runStats), the finalise preseed partial-report fallback, and the ADR-4112 deterministic-mode refusal line.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-16503-1",
+    "AC-16503-2",
+    "AC-16503-3",
+    "AC-16503-4"
+  ],
+  "id": "TS-242",
+  "usId": "US-16503",
+  "title": "Verify-modes CLI + deterministic engine + preseed partial report",
+  "testCases": [
+    {
+      "id": "TC-242-16503-1-happy",
+      "acId": "AC-16503-1",
+      "description": "run --mode deterministic emits BLOCKED with critique-only blockedAcs on every testable AC",
+      "status": "pending",
+      "testPointer": "test/verify/cli/run-mode-deterministic.test.js::run --mode deterministic: BLOCKED with critique-only blockedAcs on every AC"
+    },
+    {
+      "id": "TC-242-16503-2-refuse",
+      "acId": "AC-16503-2",
+      "description": "finalise refuses promotion on a deterministic PASS with skipped>0, naming the counts line and ADR-4112",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-deterministic-mode.test.js::finalise: deterministic-mode PASS with skipped>0 is REFUSED (never silently promotes)"
+    },
+    {
+      "id": "TC-242-16503-3-abort",
+      "acId": "AC-16503-3",
+      "description": "finalise overwrites the preseed stub with a status: aborted record when verify exits non-zero without writing",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-deterministic-mode.test.js::finalise: verify exits non-zero without writing report -> partial `aborted` record overwrites the preseed stub"
+    },
+    {
+      "id": "TC-242-16503-4-usage",
+      "acId": "AC-16503-4",
+      "description": "verify run --mode and finalise --mode refuse an unknown value with exit 2",
+      "status": "pending",
+      "testPointer": "test/cli/finalise-deterministic-mode.test.js::finalise: --mode unknown value is a usage error (exit 2)"
+    }
+  ],
+  "status": "draft"
+}

package/rcf/user-stories/us-16503.json

@@ -0,0 +1,51 @@
+{
+  "createdAt": "2026-10-08T15:39:52.219Z",
+  "updatedAt": "2026-10-08T15:40:58.645Z",
+  "asA": "operator running `rcf build finalise` from a dispatched worker that may not spawn the agent CLI",
+  "iWant": "a `--mode deterministic` option on `rcf verify run` and `rcf build finalise` that runs the gate in-process with a per-AC skip ledger, and a partial-report fallback that names the mode and the reason when verify exits without writing a report",
+  "soThat": "the finalise gate always surfaces a readable report, deterministic runs never silently promote to verified (ADR-4112), and the parent-session `agentScreenshotCritique` mode is unchanged for operators who can spawn the agent CLI",
+  "usId": "US-16503",
+  "prdId": "PRD-001",
+  "reqId": "REQ-165",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "US-16503: a dispatched worker can run the finalise gate without spawning the agent CLI",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-16503-1",
+      "description": "rcf verify run --mode deterministic produces a BLOCKED report with runStats.mode='deterministic' and a per-AC critique-only blockedAcs ledger when every AC in the chain requires critique.",
+      "testable": true,
+      "given": "a scaffolded RCF chain whose user stories carry acceptance criteria but no per-AC deterministic probe shape",
+      "when": "rcf verify run --repo <chain> --profile ci --url http://localhost:3000 --out <path> --mode deterministic --provision-mode skip is invoked",
+      "then": "the exit code is 5 (BLOCKED trips the default severity gate), the written report has verdict 'BLOCKED', run.runStats.mode='deterministic', run.runStats.counts.total matches the number of testable ACs with counts.verified=0 and counts.skipped=counts.total, and every entry in blockedAcs carries reason matching /critique-only/ and mode='deterministic'",
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-16503-2",
+      "description": "placeholder",
+      "testable": true,
+      "given": "an FBS at status 'complete' and a verify report whose run.runStats.mode='deterministic' and counts.skipped>0",
+      "when": "rcf build finalise <fbsId> --url ... is invoked",
+      "then": "the exit code is 4, the FBS stays at 'complete', and stderr matches /deterministic mode verified \\d+ of \\d+ ACs/ and /ADR-4112/"
+    },
+    {
+      "id": "AC-16503-3",
+      "description": "placeholder",
+      "testable": true,
+      "given": "an FBS at status 'complete' and a spawnVerify seam that returns exit code 1 WITHOUT writing to --out",
+      "when": "rcf build finalise <fbsId> --url ... --mode deterministic is invoked",
+      "then": "the exit code is non-zero, the --out file is readable, run.runStats.mode='deterministic', run.runStats.status='aborted', run.runStats.exitCode=1, launchFailure.status='aborted', and the FBS stays at 'complete'"
+    },
+    {
+      "id": "AC-16503-4",
+      "description": "placeholder",
+      "testable": true,
+      "given": "any scaffold",
+      "when": "rcf verify run --mode foo or rcf build finalise <fbsId> --url ... --mode foo is invoked",
+      "then": "the exit code is 2 and stderr matches /--mode must be one of/"
+    }
+  ],
+  "tacIds": [
+    "TAC-4141-verify-modes"
+  ]
+}

package/rcf/user-stories/us-18001.json

@@ -22,12 +22,12 @@
     },
     {
       "id": "AC-18001-3",
-      "description": "[happy] Given personas.productOwner.blockers non-empty, when the tab renders, then each blocker is a findings list headed by its question with its ids as anchor links into the document tabs.",
+      "description": "[happy] Given personas.productOwner.blockers non-empty, when the tab renders, then each PO blocker id appears in the questions table under its question group with the id as an anchor link into the document tabs.",
       "testable": true
     },
     {
       "id": "AC-18001-4",
-      "description": "[happy] Given a profile register of productOwner, when the tab renders, then the product-owner group is expanded first and the engineer group is collapsed with its count visible.",
+      "description": "[happy] Given a profile register of productOwner, when the tab first renders, then the questions table precedes the blocking table.",
       "testable": true
     },
     {
@@ -37,7 +37,7 @@
     },
     {
       "id": "AC-18001-6",
-      "description": "[failure] Given a tree where levels.readyToBuild.ok is false, when the tab renders, then the Freeze now control is disabled and names the failing gates from levels.readyToBuild.blockedBy.",
+      "description": "[failure] Given a tree where levels.readyToBuild.ok is false, when the tab renders, then the freeze state block names the failing gates from levels.readyToBuild.blockedBy in plain words and no freeze control is rendered.",
       "testable": true
     },
     {
@@ -56,5 +56,5 @@
   ],
   "tags": [],
   "createdAt": "2026-10-01T18:00:00Z",
-  "updatedAt": "2026-10-06T12:00:00Z"
+  "updatedAt": "2026-10-08T16:43:30.032Z"
 }

package/rcf/user-stories/us-18003.json

@@ -0,0 +1,79 @@
+{
+  "createdAt": "2026-10-07T13:46:47.389Z",
+  "updatedAt": "2026-10-08T16:43:22.541Z",
+  "description": "User story under REQ-180 for the command page (discovery-viewer-command-page sections 4 rank 1, 2 and 16; FBS-204). The question cards and the blocker cards become two tables over readiness.questions[] and stages[].checks[].failing[]: every row carries the item id, the plain-English ask or finding, where it lives on the chain, a link that opens the item in full context, and what resolved looks like. Composite finding ids split on the first colon so every link resolves. No row cap. The questions table carries a one-line copy handle (id plus ask) for briefing an agent; no CLI command is rendered anywhere on the page and the Freeze now button is gone (Q1 and Q4 rulings, ADR-4139). First paint keeps the profile register ordering (product owner first unless the profile says engineer).",
+  "asA": "a product owner or an engineer opening the Readiness tab",
+  "iWant": "every question waiting on me and every blocking item as a table row I can sort, count and open where it lives",
+  "soThat": "I can brief my agent from the row without reading prose or a terminal",
+  "tacIds": [
+    "TAC-4135-readiness-command-page"
+  ],
+  "acceptanceCriteria": [
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[renderQuestionsTable]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[QuestionRow]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[renderBlockingTable]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[splitCompositeId]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[BlockingRow]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true
+    },
+    {
+      "id": "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.",
+      "testable": true
+    },
+    {
+      "id": "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.",
+      "testable": true
+    }
+  ],
+  "usId": "US-18003",
+  "prdId": "PRD-001",
+  "reqId": "REQ-180",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "the Readiness tab lists questions and blocking items as linked tables, read-only, with no command text"
+}

package/rcf/user-stories/us-18004.json

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-10-07T13:46:49.207Z",
+  "updatedAt": "2026-10-07T13:46:49.207Z",
+  "description": "User story under REQ-180 for the command page (discovery sections 4 rank 3, 4 and 14; FBS-205). The Coverage block that prints blanks (it reads pass and total, the result carries totals) is replaced by a coverage summary: family counts as stat tiles, the three class totals as one stacked bar with the percentage covered, and an unresolved-pointers table with the reason the CLI prints. The thin-requirements table keeps its shape and widens its feed to every flavour the Q3 ruling names: zero criteria, criteria with no resolving test, D4 floor failures, plus no story and no plain description. The verdict card counts become links into the tables they count and the What happens next paragraph folds into the cards.",
+  "asA": "an engineer or product owner reading the Readiness tab",
+  "iWant": "to see how much of the chain is covered by resolving tests and which requirements are thin, as numbers and rows with links",
+  "soThat": "I can see the traceability reach without the CLI and open a thin requirement where it lives",
+  "tacIds": [
+    "TAC-4135-readiness-command-page"
+  ],
+  "acceptanceCriteria": [
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[renderCoverageSummary]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[CoverageSummary]"
+      }
+    },
+    {
+      "id": "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\").",
+      "testable": true
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[renderThinReqsTable]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[ThinReqRow]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true
+    },
+    {
+      "id": "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.",
+      "testable": true
+    }
+  ],
+  "usId": "US-18004",
+  "prdId": "PRD-001",
+  "reqId": "REQ-180",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "the Readiness tab shows a coverage summary with real numbers and a thin-requirements table fed by every signal"
+}

package/rcf/user-stories/us-18005.json

@@ -0,0 +1,79 @@
+{
+  "createdAt": "2026-10-07T13:46:51.015Z",
+  "updatedAt": "2026-10-07T13:46:51.015Z",
+  "description": "User story under REQ-180 for the command page (discovery sections 4 rank 5, 6, 11 and 14; FBS-206). The chip row and the stage detail become one stage grid above the fold (D1 to D8 by tree and delta scope, pass/total per cell, failing count linked into the blocking table). The panel is split into five sub-tabs through the shared SubTabStrip with sub= in the hash, restored after an SSE swap. The delta on an unfrozen tree is counts with an on-demand per-document list (Q2). The For-engineers DocRow wrapper is removed and every engineer item survives in a named table or block. The freeze block shows the state and what resolves it in words (Q4). Sub-tabs are the designed shape; one long page with anchor navigation is the named alternative ruled on the rendered sketches (Q5).",
+  "asA": "an engineer opening the Readiness tab on a large unfrozen tree",
+  "iWant": "the stage states as a grid above the fold, the page split into sub-views, and the delta as counts rather than every document in the tree",
+  "soThat": "the command page loads light, reads top-down and never buries the failing ids under a thousand delta rows",
+  "tacIds": [
+    "TAC-4135-readiness-command-page"
+  ],
+  "acceptanceCriteria": [
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[renderVerdictGrid]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[readinessSubTabs]"
+      }
+    },
+    {
+      "id": "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).",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[renderDeltaCounts]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[VerdictGridCell]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4135-readiness-command-page",
+        "field": "interfaces[DeltaCounts]"
+      }
+    },
+    {
+      "id": "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.",
+      "testable": true
+    },
+    {
+      "id": "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.",
+      "testable": true
+    },
+    {
+      "id": "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.",
+      "testable": true
+    }
+  ],
+  "usId": "US-18005",
+  "prdId": "PRD-001",
+  "reqId": "REQ-180",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "the Readiness tab is laid out as a stage grid with sub-tabs and delta counts, the For-engineers row retired"
+}

package/rcf/user-stories/us-208.json

@@ -0,0 +1,74 @@
+{
+  "createdAt": "2026-10-07T13:46:52.774Z",
+  "updatedAt": "2026-10-07T13:46:52.774Z",
+  "description": "User story under REQ-002 for the query routes (discovery section 4 rank 7, server half; FBS-207; TAC-4136, ADR-4140). Three GET routes on the viewer server expose computeTrace, computeImpact and computeCoverage per pivot from the current walked state, memoised by state.version, relative to the mount and release-noted so host proxies allow-list them as they did ./index.json and ./page-init.js. The routes bypass runWithAdmissibilityGate exactly as the CLI coverage, impact and trace verbs do (issues 316 and 317). GET and HEAD only; nothing is written under rcf/.",
+  "asA": "an engineer or an embedding host using the viewer",
+  "iWant": "trace, impact and coverage for any id as JSON from the running viewer, computed from the same tree the page shows",
+  "soThat": "the viewer can render traceability on demand and an agent or host can read the same numbers without a terminal",
+  "tacIds": [
+    "TAC-4136-view-query-routes"
+  ],
+  "acceptanceCriteria": [
+    {
+      "id": "AC-208-1",
+      "description": "[happy] Given a running viewer and a known id, when GET \"./trace.json?id=<id>&direction=forward\" is requested, then the response is application/json carrying the computeTrace result for that pivot (pivot, direction, found, nodes, edges), computed from the current state and served with \"cache-control: no-store\" relative to the viewer mount.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4136-view-query-routes",
+        "field": "interfaces[GET /trace.json]"
+      }
+    },
+    {
+      "id": "AC-208-2",
+      "description": "[happy] Given a running viewer and a known id, when GET \"./impact.json?id=<id>\" is requested, then the response is application/json carrying the computeImpact result (pivot, found, nodes with actionNeeded per node, edges) with \"cache-control: no-store\".",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4136-view-query-routes",
+        "field": "interfaces[GET /impact.json]"
+      }
+    },
+    {
+      "id": "AC-208-3",
+      "description": "[happy] Given a running viewer, when GET \"./coverage.json\" is requested with no scope, then the response is application/json carrying the strict computeCoverage result for the whole tree (totals, requirements, unresolvedTestPointers); given \"?scope=<id>\" naming a PRD, REQ or US, the result is narrowed to that subtree as the CLI positional narrows it.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4136-view-query-routes",
+        "field": "interfaces[GET /coverage.json]"
+      }
+    },
+    {
+      "id": "AC-208-4",
+      "description": "[failure] Given an unknown id, when trace or impact is requested, then the response is 404 application/json with QueryRouteError.error \"unknown-id\" and QueryRouteError.id echoing the request; given a direction outside forward, back and both, the response is 400 with QueryRouteError.error \"bad-direction\"; given a below-AC or unknown scope on coverage, the response is 400 with QueryRouteError.error \"bad-scope\".",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4136-view-query-routes",
+        "field": "interfaces[QueryRouteError]"
+      }
+    },
+    {
+      "id": "AC-208-5",
+      "description": "[must-not] Given any request to the three routes, when the server handles it, then runWithAdmissibilityGate is not called (the routes bypass the gate the way src/cli/coverage.js and src/cli/impact.js do) and nothing under rcf/ is written.",
+      "testable": true
+    },
+    {
+      "id": "AC-208-6",
+      "description": "[edge] Given a rewalk that publishes a new state.version, when a route is requested, then the served result reflects the new tree and the memo entries of the previous version are discarded; within one version a repeated request for the same pivot and direction is served from the memo without recomputing.",
+      "testable": true,
+      "ownerRef": {
+        "tacId": "TAC-4136-view-query-routes",
+        "field": "interfaces[queryCache]"
+      }
+    },
+    {
+      "id": "AC-208-7",
+      "description": "[failure] Given the server before the first walk completes, when a trace, impact or coverage request arrives, then the response is 503 text \"view server initialising\", as ./index.json answers today.",
+      "testable": true
+    }
+  ],
+  "usId": "US-208",
+  "prdId": "PRD-001",
+  "reqId": "REQ-002",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "the viewer serves trace, impact and coverage for a selected node as JSON routes computed from the current tree"
+}