rcf-lite 0.28.4 → 0.29.0

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

@@ -0,0 +1,100 @@
+{
+  "createdAt": "2026-10-01T16:00:00Z",
+  "updatedAt": "2026-10-01T16:00:00Z",
+  "purpose": "Cover US-17503: --level and --persona flags, the exit matrix (section 3.2), the two verdict lines (section 2.3) and the persona-grouped text report (section 4) of the DEFINE step 2 persona-levels spec. Shares `formatVerdictLines` with the Readiness tab (PR C).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17503-1",
+    "AC-17503-2",
+    "AC-17503-3",
+    "AC-17503-4",
+    "AC-17503-5",
+    "AC-17503-6",
+    "AC-17503-7",
+    "AC-17503-8",
+    "AC-17503-9"
+  ],
+  "id": "TS-222",
+  "usId": "US-17503",
+  "title": "rcf define readiness --level / --persona flags, exit matrix and verdict wording",
+  "testCases": [
+    {
+      "id": "TC-222-exit-matrix",
+      "acId": "AC-17503-1",
+      "description": "Parameterised exit matrix across all rows of spec section 3.2 (no flag, --check <stage>, --check all, --level intent, --level build, --level + --check).",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-1 exit matrix (parameterised: --check + --level combinations)"
+    },
+    {
+      "id": "TC-222-level-intent-pass",
+      "acId": "AC-17503-2",
+      "description": "--level intent exits 0 on a tree where every PO check passes.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-2 --level intent exits 0 when PO is clean"
+    },
+    {
+      "id": "TC-222-level-intent-fail",
+      "acId": "AC-17503-3",
+      "description": "--level intent exits 4 when any PO check fails.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-3 --level intent exits 4 when PO fails"
+    },
+    {
+      "id": "TC-222-level-build-strict-ack",
+      "acId": "AC-17503-4",
+      "description": "--level build exits 4 on an unacknowledged D3 failure even when every blocking stage passes; the [warn] line still prints.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-4 --level build exits 4 on a failing tree and prints warn lines for unacked warn-with-ack stages"
+    },
+    {
+      "id": "TC-222-check-all-unchanged",
+      "acId": "AC-17503-5",
+      "description": "--check all exit behaviour unchanged on a warn-with-ack-only failure: 0 with a stderr [warn] line.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-5 --check all unchanged on warn-with-ack"
+    },
+    {
+      "id": "TC-222-persona-collapses-other",
+      "acId": "AC-17503-6",
+      "description": "--persona productOwner collapses the engineer block to one line and leaves the exit code identical to the no-flag invocation; same for engineer and the PO block.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-6 --persona filters text and does not change exit"
+    },
+    {
+      "id": "TC-222-unknown-values-exit-2-level",
+      "acId": "AC-17503-7",
+      "description": "--level ship exits 2 with the usage line naming intent|build.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-7 unknown --level exits 2 with usage line"
+    },
+    {
+      "id": "TC-222-unknown-values-exit-2-persona",
+      "acId": "AC-17503-7",
+      "description": "--persona architect exits 2 with the usage line naming productOwner|engineer.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-7 unknown --persona exits 2 with usage line"
+    },
+    {
+      "id": "TC-222-json-meta-level",
+      "acId": "AC-17503-8",
+      "description": "--json --level intent emits _meta.level === 'intent' and carries levels and personas.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-8 --json --level intent carries _meta.level and preserves levels + personas"
+    },
+    {
+      "id": "TC-222-text-persona-grouping",
+      "acId": "AC-17503-9",
+      "description": "On a failing tree the text report puts the product-owner block before the engineer block and every per-check line carries the persona inside the parenthesis after over.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-9 text report groups PO before engineer with persona in detail lines"
+    },
+    {
+      "id": "TC-222-verdict-lines-four-strings",
+      "acId": "AC-17503-1",
+      "description": "formatVerdictLines builds the four exact strings in spec section 2.3 (L1 ok, L1 not ok, L2 ok, L2 not ok) from crafted fixture results.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126): formatVerdictLines returns the section 2.3 wording"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,94 @@
+{
+  "createdAt": "2026-10-01T18:00:00Z",
+  "updatedAt": "2026-10-01T18:00:00Z",
+  "purpose": "Cover US-18001 (Readiness as tab 1 and the PRD rename) 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": [
+    "AC-18001-1",
+    "AC-18001-2",
+    "AC-18001-3",
+    "AC-18001-4",
+    "AC-18001-5",
+    "AC-18001-6",
+    "AC-18001-7",
+    "AC-18101-1",
+    "AC-18101-2",
+    "AC-18101-3"
+  ],
+  "id": "TS-223",
+  "usId": "US-18001",
+  "title": "Readiness tab layout, PRD rename and shared pill, findings-list and diff components",
+  "testCases": [
+    {
+      "id": "TC-223-tab-order-and-rename",
+      "acId": "AC-18001-1",
+      "description": "First tab button is Readiness, second is PRD; the PRD panel contains the former Overview body unchanged.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-1 tab order and PRD rename"
+    },
+    {
+      "id": "TC-223-verdict-pills-match-cli",
+      "acId": "AC-18001-2",
+      "description": "The two verdict pills carry formatVerdictLines(result) strings as labels; variant pins the verdict family and the value class carries yes/no.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-2 verdict pill labels equal formatVerdictLines"
+    },
+    {
+      "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.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-3 PO blockers render as findings lists with id anchors"
+    },
+    {
+      "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.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-4 register orders the pair and collapses the opposite"
+    },
+    {
+      "id": "TC-223-no-blocker-id-omitted",
+      "acId": "AC-18001-5",
+      "description": "Under any register, every PO blocker id and every engineer blocker id appears somewhere in the DOM.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-5 no blocker id is omitted from the DOM"
+    },
+    {
+      "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.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-6 Freeze now is disabled and names the failing gates"
+    },
+    {
+      "id": "TC-223-ids-on-tab-match-cli-json",
+      "acId": "AC-18001-7",
+      "description": "Walking the rendered anchors and matching against the --json for the same tree hash: every id on the tab is present in the JSON.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18001-7 every id on the tab appears in the CLI --json for the same tree"
+    },
+    {
+      "id": "TC-223-pill-vocabulary",
+      "acId": "AC-18101-1",
+      "description": "pill renders the same markup shape with a per-value vocabulary class for a gate state, a level verdict, a persona and an AC class.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18101-1 pill emits one shape with per-value vocabulary classes"
+    },
+    {
+      "id": "TC-223-findings-list-markup",
+      "acId": "AC-18101-2",
+      "description": "findingsList called with identical inputs from the Readiness and Product Map call paths returns byte-identical markup.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18101-2 findingsList is byte-identical across call sites"
+    },
+    {
+      "id": "TC-223-no-existing-tab-tests-change",
+      "acId": "AC-18101-3",
+      "description": "No existing Product Map or Requirements test expectation changes; only the Readiness-specific additions land.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-tab.test.js::readiness tab: AC-18101-3 existing Product Map and Requirements tests retain their expectations"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-10-02T19:00:00Z",
+  "updatedAt": "2026-10-02T19:00:00Z",
+  "purpose": "Cover US-204 (engineer sees the FBS DAG): depth columns from dependsOnFbsIds, click-to-highlight closure, inspector with needs/waits links and Open-in-Specs, deep links on #tab=build&sub=dag&entity=<id>, filters that keep the selection, cycle handling and the no-outbound-postMessage guard. Points at the twelve new DAG unit tests under test/view/build-tab.test.js.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-204-1",
+    "AC-204-2",
+    "AC-204-3",
+    "AC-204-4",
+    "AC-204-5",
+    "AC-204-6",
+    "AC-204-7"
+  ],
+  "id": "TS-224",
+  "usId": "US-204",
+  "title": "Build/DAG sub-tab: layout, closure, inspector, deep links, filters, cycles, no outbound postMessage",
+  "testCases": [
+    {
+      "id": "TC-224-depth-columns",
+      "acId": "AC-204-1",
+      "description": "buildDagLayout places every connected FBS in a column whose index equals its longest dependency depth from dependsOnFbsIds; rows inside a column are ordered by buildOrder ascending.",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::buildDagLayout: columns are dependency-depth tiers from dependsOnFbsIds (AC-204-1)"
+    },
+    {
+      "id": "TC-224-closures-upstream-downstream",
+      "acId": "AC-204-2",
+      "description": "buildDagLayout carries upstream and downstream closures transitively per node; renderBuildDag outlines upstream in link colour and downstream in warning (checked via data-rcf-dag-role on nodes and edges in the client wiring markers).",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::buildDagLayout: closures carry upstream and downstream transitively (AC-204-2 / AC-204-3)"
+    },
+    {
+      "id": "TC-224-inspector-payload",
+      "acId": "AC-204-3",
+      "description": "buildDagInspectorPayload emits status, area, buildOrder, acCount, buildable, needs and waits (direct + transitive totals) plus needsMeta/waitsMeta for every node, so the client inspector lists them without recomputing the layout.",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::buildDagInspectorPayload: carries status/area/order/AC/buildable + needs and waits (AC-204-3)"
+    },
+    {
+      "id": "TC-224-hash-round-trip",
+      "acId": "AC-204-4",
+      "description": "page-init.js carries the Build/DAG wiring: click-to-highlight writes #tab=build&sub=dag&entity=<id>, applyBuildHash restores the selection and scrolls the node into view (auto-pressing Show-unconnected when the restored node sits in the unconnected lane).",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::page-init.js carries the Build/DAG wiring (click-to-highlight, hash round-trip, filters)"
+    },
+    {
+      "id": "TC-224-filters-keep-selection",
+      "acId": "AC-204-5",
+      "description": "DAG filter chips (status, area, Buildable-now, Critical-path, Show-unconnected) in the DagToolbar; applyDagFilters keeps the current selection intact across toggles; renderBuildDag emits the toolbar with the six filter controls and the unconnected count.",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::renderBuildDag: toolbar renders status chips, area select, three toggles and the unconnected count"
+    },
+    {
+      "id": "TC-224-cycle-handling",
+      "acId": "AC-204-6",
+      "description": "buildDagLayout surfaces cycle members as cycleIds and excludes them from the depth layout; non-cycle FBS still render.",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::buildDagLayout: cycles are surfaced as cycleIds and excluded from depth layout (AC-204-6)"
+    },
+    {
+      "id": "TC-224-no-outbound-postmessage",
+      "acId": "AC-204-7",
+      "description": "The rendered Build tab slice (DAG panel) does not contain any postMessage( call site; the inspector payload rides on a data-rcf-dag-inspector-data attribute, not a function call.",
+      "status": "pending",
+      "testPointer": "test/view/build-tab.test.js::Build/DAG renderer never emits window.postMessage (AC-204-7, no outbound postMessage)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-10-03T00:00:00Z",
+  "updatedAt": "2026-10-03T00:00:00Z",
+  "purpose": "Cover US-205 (engineer jumps to any document or AC by id): id-first ranking (exact / prefix / contains), word-match title above snippet, single-char ids-only, hash pick lands and expands the entity, mount URL round-trip, embed/theme preservation, empty-state on fetch failure, no outbound postMessage / storage / cookies. Points at the 22 new unit tests under test/view/id-lookup.test.js.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-205-1",
+    "AC-205-2",
+    "AC-205-3",
+    "AC-205-4",
+    "AC-205-5",
+    "AC-205-6",
+    "AC-205-7",
+    "AC-205-8"
+  ],
+  "id": "TS-225",
+  "usId": "US-205",
+  "title": "ID lookup: ranking, hash pick, embed/theme round-trip, empty state, no outbound side effects",
+  "testCases": [
+    {
+      "id": "TC-225-id-exact-prefix-first",
+      "acId": "AC-205-1",
+      "description": "rankLookupRows ranks an exact id match first, a prefix match second and a contains match third; the first ranked row is pre-highlighted in the LookupModal shell.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::rankLookupRows: exact id ranks first (AC-205-1)"
+    },
+    {
+      "id": "TC-225-word-title-above-snippet",
+      "acId": "AC-205-2",
+      "description": "rankLookupRows ranks a word match in the title above a word match in the snippet when the id does not match; every query word must match title or snippet.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::rankLookupRows: a title match ranks above a snippet-only match (AC-205-2)"
+    },
+    {
+      "id": "TC-225-single-char-ids-only",
+      "acId": "AC-205-3",
+      "description": "rankLookupRows with a one-character query returns only id matches; the title / snippet word-match pass is skipped.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::rankLookupRows: single-character queries search ids only (AC-205-3)"
+    },
+    {
+      "id": "TC-225-pick-writes-hash",
+      "acId": "AC-205-4",
+      "description": "wireLookup pick writes `#tab=<tab>&entity=<id>` through writeHash; the Router activates the tab, opens every ancestor DocRow and the entity, scrolls into view and flashes the target.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::page-init.js carries the wireLookup contract: Cmd/Ctrl+F binding, lazy fetch, up/down/Enter/Esc"
+    },
+    {
+      "id": "TC-225-mount-url-round-trip",
+      "acId": "AC-205-5",
+      "description": "A mount URL of `?tab=requirements&entity=US-304` lands on the same position at first paint via the Router (PR 1 contract), independent of the LookupModal.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::page-init.js urlWithHash preserves ?tab=&entity= + any other query at mount (AC-205-5)"
+    },
+    {
+      "id": "TC-225-embed-theme-preserved",
+      "acId": "AC-205-6",
+      "description": "A pick with `?embed=1&theme=dark` on the URL leaves both query params in place; only the hash fragment changes. Verified against writeHash + the hash-preservation helpers.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::page-init.js writeHash preserves ?embed= and ?theme= through every pick (AC-205-6)"
+    },
+    {
+      "id": "TC-225-empty-state-on-fetch-failure",
+      "acId": "AC-205-7",
+      "description": "A non-2xx / malformed `./index.json` response renders the empty state (The index could not be loaded.) with a visible Reload index button; no result rows show; the reload affordance re-fetches on click.",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::renderLookupModal carries the empty-state + reload affordance markers (AC-205-7)"
+    },
+    {
+      "id": "TC-225-no-outbound-side-effects",
+      "acId": "AC-205-8",
+      "description": "wireLookup never calls window.postMessage, never writes to localStorage / sessionStorage / document.cookie, and makes no outbound fetch other than `./index.json`; asserted by a source-level scan of page-init.js (no postMessage, no storage, no cookie writes in wireLookup).",
+      "status": "pending",
+      "testPointer": "test/view/id-lookup.test.js::page-init.js does not add outbound postMessage, localStorage, sessionStorage or cookies in the lookup wiring (AC-205-8)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,158 @@
+{
+  "createdAt": "2026-10-02T18:00:00Z",
+  "updatedAt": "2026-10-02T18:00:00Z",
+  "purpose": "Cover US-18601 (the question set), US-18602 (the verb and the tools) and US-18603 (write-back and termination): computeQuestions turns every failing PO item into a question carrying its write-back; the CLI verb and the MCP tool emit the same object; the scripted loop converges; engineer edits never re-open the PO loop.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-18601-1",
+    "AC-18601-2",
+    "AC-18601-3",
+    "AC-18601-4",
+    "AC-18601-5",
+    "AC-18601-6",
+    "AC-18601-7",
+    "AC-18602-1",
+    "AC-18602-2",
+    "AC-18602-3",
+    "AC-18602-4",
+    "AC-18602-5",
+    "AC-18602-6",
+    "AC-18603-1",
+    "AC-18603-2",
+    "AC-18603-3",
+    "AC-18603-4",
+    "AC-18603-5"
+  ],
+  "id": "TS-226",
+  "usId": "US-18601",
+  "title": "DEFINE step 3 PR 2: computeQuestions, the questions verb, MCP tools and loop convergence",
+  "testCases": [
+    {
+      "id": "TC-226-q-shape",
+      "acId": "AC-18601-1",
+      "description": "On a fixture failing brief:openQuestions, skeleton:resolvedBy and stories:reqHasUs, computeQuestions(persona=productOwner) returns one entry per failing item with id, stage, check, itemId, heading, ask, answerKinds, writeBack and blocks intent.",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-1: openQuestions + resolvedBy + reqHasUs failing items each produce one question with the full shape"
+    },
+    {
+      "id": "TC-226-q-deterministic",
+      "acId": "AC-18601-2",
+      "description": "Two consecutive computeQuestions runs on the same tree return deep-equal questions[] ordered D1, D2, D4, D7 then by source span.",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-2: two runs are deep-equal and ordered D1, D2, D4, D7 then by source span"
+    },
+    {
+      "id": "TC-226-q-optional-decisions",
+      "acId": "AC-18601-3",
+      "description": "An open decision with two options and a default appears in optional[] with blocks build and not in questions[].",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-3: a two-option decision with a default appears in optional[], not questions[]"
+    },
+    {
+      "id": "TC-226-q-empty-when-ok",
+      "acId": "AC-18601-4",
+      "description": "On a tree where levels.intentComplete.ok, computeQuestions(persona=productOwner) returns ok:true and empty questions[].",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-4: ok tree returns ok:true and empty questions[]"
+    },
+    {
+      "id": "TC-226-q-engineer-persona",
+      "acId": "AC-18601-5",
+      "description": "computeQuestions(persona=engineer) returns one entry per failing engineer item in failing stages with blocks build.",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-5: persona engineer returns engineer blockers in failing stages, blocks: build"
+    },
+    {
+      "id": "TC-226-q-usage-error",
+      "acId": "AC-18601-6",
+      "description": "computeQuestions throws a usage error naming productOwner and engineer when given any other persona value.",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-6: unknown persona throws naming the accepted values"
+    },
+    {
+      "id": "TC-226-q-writes-nothing",
+      "acId": "AC-18601-7",
+      "description": "computeQuestions never creates or modifies a file under rcf/ (mtime guard); every writeBack.command names a verb registered in the CLI help.",
+      "status": "pending",
+      "testPointer": "test/query/questions.test.js::AC-18601-7: computeQuestions is pure; every writeBack.command names a registered verb"
+    },
+    {
+      "id": "TC-226-cli-json",
+      "acId": "AC-18602-1",
+      "description": "rcf define questions --json on a failing tree prints the computeQuestions object to stdout and exits 0.",
+      "status": "pending",
+      "testPointer": "test/cli/questions.test.js::AC-18602-1: --json on a failing tree prints the questions object and exits 0"
+    },
+    {
+      "id": "TC-226-cli-persona-default",
+      "acId": "AC-18602-2",
+      "description": "Without --persona, the verb picks engineer on a profile whose register is engineer, else productOwner.",
+      "status": "pending",
+      "testPointer": "test/cli/questions.test.js::AC-18602-2: persona defaults from profile register"
+    },
+    {
+      "id": "TC-226-cli-stage-limit",
+      "acId": "AC-18602-3",
+      "description": "--stage skeleton --limit 2 caps questions[] to two D2 entries and reports remaining counting every D2 item.",
+      "status": "pending",
+      "testPointer": "test/cli/questions.test.js::AC-18602-3: --stage brief --limit 1 caps the output but keeps remaining honest"
+    },
+    {
+      "id": "TC-226-mcp-parity",
+      "acId": "AC-18602-4",
+      "description": "MCP tool rcf_define_questions returns structuredContent deep-equal to the verb's --json output on the same tree.",
+      "status": "pending",
+      "testPointer": "test/mcp/define-questions.test.js::AC-18602-4: rcf_define_questions structuredContent deep-equals the verb --json"
+    },
+    {
+      "id": "TC-226-cli-usage-persona",
+      "acId": "AC-18602-5",
+      "description": "--persona architect exits 2 with the usage line naming productOwner and engineer.",
+      "status": "pending",
+      "testPointer": "test/cli/questions.test.js::AC-18602-5: --persona architect exits 2 naming productOwner and engineer"
+    },
+    {
+      "id": "TC-226-cli-writes-nothing",
+      "acId": "AC-18602-6",
+      "description": "No file under rcf/ is created or modified during any invocation of rcf define questions.",
+      "status": "pending",
+      "testPointer": "test/cli/questions.test.js::AC-18602-6: questions writes nothing under rcf/"
+    },
+    {
+      "id": "TC-226-loop-convergence",
+      "acId": "AC-18603-1",
+      "description": "Scripted loop fixture: applying each writeBack and recomputing drives questions count strictly down each turn and to zero.",
+      "status": "pending",
+      "testPointer": "test/query/questions-loop.test.js::AC-18603-1: scripted loop converges strictly to zero within a bounded number of turns"
+    },
+    {
+      "id": "TC-226-loop-new-req",
+      "acId": "AC-18603-2",
+      "description": "A statement resolved to a new REQ carrying description and domain passes skeleton:reqIntent and raises stories:reqHasUs once.",
+      "status": "pending",
+      "testPointer": "test/query/questions-loop.test.js::AC-18603-2: a new REQ with description and domain passes reqIntent and asks reqHasUs once"
+    },
+    {
+      "id": "TC-226-loop-l1-draft-stable",
+      "acId": "AC-18603-3",
+      "description": "At L1, adding [draft] entities, TAC stubs and interfaces leaves intentComplete.ok true and the PO question set empty.",
+      "status": "pending",
+      "testPointer": "test/query/questions-loop.test.js::AC-18603-3: at L1 adding engineer-only draft entities keeps the PO question set empty"
+    },
+    {
+      "id": "TC-226-loop-decision-wellformed",
+      "acId": "AC-18603-4",
+      "description": "An openQuestion promoted to a decision with one option and no default makes decisions:wellFormed ask once and brief:openQuestions pass.",
+      "status": "pending",
+      "testPointer": "test/query/questions-loop.test.js::AC-18603-4: an openQuestion promoted to a one-option decision asks decisions:wellFormed once"
+    },
+    {
+      "id": "TC-226-loop-engineer-isolation",
+      "acId": "AC-18603-5",
+      "description": "No product-owner check changes from ok to failing after an engineer-only edit.",
+      "status": "pending",
+      "testPointer": "test/query/questions-loop.test.js::AC-18603-5: an engineer-only edit never changes the PO question set"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-10-03T09:30:00Z",
+  "updatedAt": "2026-10-03T09:30:00Z",
+  "purpose": "Cover US-18002 (the Readiness tab renders question cards grouped by source span): the questions block lists each group with its asks and every id is in the JSON (AC-18002-1), the empty questions set renders the intent-complete verdict line (AC-18002-2), and engineer blockers are never removed from the DOM in any register (AC-18002-3). Points at the three AC tests under test/view/readiness-po-layer.test.js.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-18002-1",
+    "AC-18002-2",
+    "AC-18002-3"
+  ],
+  "id": "TS-227",
+  "usId": "US-18002",
+  "title": "Readiness PO question cards: groups and asks, intent-complete empty state, engineer DOM preserved across registers",
+  "testCases": [
+    {
+      "id": "TC-227-groups-and-asks",
+      "acId": "AC-18002-1",
+      "description": "renderReadinessPO is given a readiness object with questions[] non-empty; every group label, every ask and every question id appears in the panel, and data-rcf-source=\"readiness.questions\" is stamped so the source path is unambiguous.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-po-layer.test.js::PO layer: AC-18002-1 given questions[] non-empty, the block lists each group with its asks and every id is in the JSON"
+    },
+    {
+      "id": "TC-227-empty-questions-verdict",
+      "acId": "AC-18002-2",
+      "description": "renderReadinessPO is given a clean readiness object with both levels ok and no blockers; the panel renders the exact intent-complete verdict line (formatVerdictLines(result).intentComplete) inside the questions block and marks the section data-rcf-empty=\"yes\".",
+      "status": "pending",
+      "testPointer": "test/view/readiness-po-layer.test.js::PO layer: AC-18002-2 given questions[] empty, the block shows the intent-complete verdict line"
+    },
+    {
+      "id": "TC-227-engineer-dom-preserved",
+      "acId": "AC-18002-3",
+      "description": "renderReadinessPanel across every register (null / productOwner / engineer) keeps every engineer blocker id in the DOM, keeps every PO blocker id in the DOM and renders the CLI verdict strings verbatim inside the For-engineers DocRow; the For-engineers DocRow is closed under productOwner / unstated and open under engineer.",
+      "status": "pending",
+      "testPointer": "test/view/readiness-po-layer.test.js::PO layer: AC-18002-3 engineer blockers are not removed from the DOM in any register"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,86 @@
+{
+  "createdAt": "2026-10-03T00:00:00Z",
+  "updatedAt": "2026-10-03T00:00:00Z",
+  "purpose": "Cover US-18801 (the draft homes) and US-18202 (the DEFINE-stage guidance pack): parseInterfaceDraft and shapes:draftSettled extended to TAC.purpose, coreEntities[].description and TAC.interfaces[].description with the three id forms; a draft-only tree is L1-neutral; the guidance manifest advertises the two new slugs and five prompts; the register scan rejects an em-dash in any new guidance file; the managed block regeneration keeps every existing rule.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-18801-1",
+    "AC-18801-2",
+    "AC-18801-3",
+    "AC-18801-4",
+    "AC-18801-5",
+    "AC-18202-1",
+    "AC-18202-2",
+    "AC-18202-3",
+    "AC-18202-4"
+  ],
+  "id": "TS-228",
+  "usId": "US-18801",
+  "title": "DEFINE step 3 PR 3: draft marker extension, DISCOVERY prototypes guidance and prompts",
+  "testCases": [
+    {
+      "id": "TC-228-draft-coreentity",
+      "acId": "AC-18801-1",
+      "description": "A coreEntities entry whose description starts with [draft] fails shapes:draftSettled with id TAD.entity:<name>.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (REQ-188, AC-18801-1): draft on coreEntity description fails draftSettled with TAD.entity:<name>"
+    },
+    {
+      "id": "TC-228-draft-tac-purpose",
+      "acId": "AC-18801-2",
+      "description": "A TAC whose purpose starts with [draft] fails shapes:draftSettled with id <tacId>; shapes:tacHasInterface counts the TAC as present.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (REQ-188, AC-18801-2): draft on TAC.purpose fails draftSettled with <tacId>, tacHasInterface counts it present"
+    },
+    {
+      "id": "TC-228-draft-cleared",
+      "acId": "AC-18801-3",
+      "description": "When every [draft] marker across the three homes is cleared, shapes:draftSettled passes.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (REQ-188, AC-18801-3): three draft homes cleared, draftSettled passes"
+    },
+    {
+      "id": "TC-228-draft-template-markers",
+      "acId": "AC-18801-4",
+      "description": "A [draft] recordShape without fields: fails shapes:templateMarkers exactly as a settled one. (shapes:templateMarkers lands in PR 5; this TC is pending PR 5.)",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (REQ-188, AC-18801-4 pending PR 5): draft recordShape without fields fails templateMarkers"
+    },
+    {
+      "id": "TC-228-draft-no-po-read",
+      "acId": "AC-18801-5",
+      "description": "No productOwner check reads any [draft] content: every productOwner check on a draft-only tree is ok (L1-neutral).",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (REQ-188, AC-18801-5): draft-only tree keeps every productOwner check ok (L1-neutral)"
+    },
+    {
+      "id": "TC-228-guidance-prints",
+      "acId": "AC-18202-1",
+      "description": "rcf guidance define-intent and rcf guidance discovery-prototypes each print their file byte-faithfully.",
+      "status": "pending",
+      "testPointer": "test/guidance/verbs.test.js::guidance (REQ-182, AC-18202-1): rcf guidance define-intent and discovery-prototypes each print their file"
+    },
+    {
+      "id": "TC-228-manifest-prompts",
+      "acId": "AC-18202-2",
+      "description": "The manifest lists rcf_define_intent, rcf_define_intake, rcf_define_draft_shapes and rcf_discover_prototype as argument-free; rcf_define_litmus is recorded as pending PR 7.",
+      "status": "pending",
+      "testPointer": "test/guidance/inventory.test.js::guidance (REQ-182, AC-18202-2): four argument-free DEFINE prompts present, litmus pending PR 7"
+    },
+    {
+      "id": "TC-228-register-scan-em-dash",
+      "acId": "AC-18202-3",
+      "description": "A new guidance file containing an em-dash fails the register scan.",
+      "status": "pending",
+      "testPointer": "test/guidance/canonical-text-lint.test.js::guidance (REQ-182, AC-18202-3): em-dash in a new guidance file fails the register scan"
+    },
+    {
+      "id": "TC-228-managed-block-preserves-rules",
+      "acId": "AC-18202-4",
+      "description": "The managed block regeneration keeps every existing rule: regenerating never removes a line.",
+      "status": "pending",
+      "testPointer": "test/guidance/fragment.test.js::guidance (REQ-182, AC-18202-4): managed-block regeneration keeps every existing rule"
+    }
+  ],
+  "status": "draft"
+}