rcf-lite 0.28.4 → 0.30.0

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

@@ -1,6 +1,6 @@
 {
   "createdAt": "2026-09-24T14:30:00Z",
-  "updatedAt": "2026-09-24T14:30:00Z",
+  "updatedAt": "2026-10-01T13:12:16Z",
   "purpose": "Cover the DEFINE stage-gate check functions D1..D8 (AC-17401-1..8) with unit tests over hand-built TreeModel and ledger fixtures.",
   "testLevel": "unit",
   "acIds": [
@@ -11,7 +11,9 @@
     "AC-17401-5",
     "AC-17401-6",
     "AC-17401-7",
-    "AC-17401-8"
+    "AC-17401-8",
+    "AC-17401-9",
+    "AC-17401-10"
   ],
   "id": "TS-216",
   "usId": "US-17401",
@@ -72,7 +74,21 @@
       "description": "checkD8Freeze asserts prior stages passed/acknowledged, every AC owned by exactly one FBS, computeQueue nextActionable not null, validateErrors empty.",
       "status": "pending",
       "testPointer": "test/query/gates.test.js::gates: D8 tree-wide freeze checks"
+    },
+    {
+      "id": "TC-216-d2-data-architecture",
+      "acId": "AC-17401-9",
+      "description": "checkD2Skeleton reads tad.dataArchitecture.{dataStores,coreEntities} per rcf-schemas 0.6.3; a tree with populated dataArchitecture passes skeleton:tadPersistence and empty/missing/wrong-top-level trees fail with the schema-anchored ids.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates: D2 skeleton:tadPersistence reads tad.dataArchitecture.* per schema 0.6.3"
+    },
+    {
+      "id": "TC-216-identity-seed-surface",
+      "acId": "AC-17401-10",
+      "description": "IDENTITY_TEMPLATE carries a '## Surface' section between '## Register' and '## Project-scoped notes' naming viewer/runningApp/prDiff and seeded to 'prDiff'; writeIdentityTemplate on a fresh dir seeds a profile that satisfies checkD1Brief surface markers; an existing profile.md is left byte-identical (slice-1 'kept' contract).",
+      "status": "pending",
+      "testPointer": "test/setup/identity-register.test.js::IDENTITY_TEMPLATE carries a ## Surface heading between ## Register and ## Project-scoped notes"
     }
   ],
   "status": "draft"
-}
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-09-24T16:33:15Z",
+  "updatedAt": "2026-09-24T16:33:15Z",
+  "purpose": "Cover rcf define freeze (AC-17601-1..8) with CLI spawn tests over an initProject scratch tree; add a targeted test for the freeze-record override-nullable-required contract; add a targeted test that CHANGELOG.md and the readiness CLI stage header no longer carry the ' -- ' double-dash pattern this slice replaces.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17601-1",
+    "AC-17601-2",
+    "AC-17601-3",
+    "AC-17601-4",
+    "AC-17601-5",
+    "AC-17601-6",
+    "AC-17601-7",
+    "AC-17601-8"
+  ],
+  "id": "TS-218",
+  "usId": "US-17601",
+  "title": "rcf define freeze CLI + freeze-record override + hygiene",
+  "testCases": [
+    {
+      "id": "TC-218-happy",
+      "acId": "AC-17601-1",
+      "description": "On a scratch project seeded so computeReadiness returns freezeable=true (initProject + a minimal brief statement + profile markers + one deploy ADR + one REQ with US, AC classes and TAC + one FBS at the queue head), rcf define freeze exits 0, writes rcf/define/freeze.json with the required shape, and a follow-up computeDelta over the live tree + new record reports every list empty.",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: happy path writes freeze.json and produces an empty delta"
+    },
+    {
+      "id": "TC-218-refuse",
+      "acId": "AC-17601-2",
+      "description": "On a scratch project that fails D1 (no brief statement), rcf define freeze exits 4, writes no freeze.json, and prints the failing-stage block + rcf define readiness --check brief hint on stderr.",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: refuses with exit 4 on any failing stage and writes nothing"
+    },
+    {
+      "id": "TC-218-ack",
+      "acId": "AC-17601-3",
+      "description": "--ack define.shapes --reason 'templates deferred' is accepted, --ack define.brief --reason 'x' is a usage refusal (exit 2 with a message naming the accepted set), --ack without --reason is a usage refusal, and an acked D3 lands in freeze.gates as { state: 'acknowledged', at.hash: <currentTreeHash>, at.reason: 'templates deferred', failing: [...] } which the next readiness run reports as 'acknowledged'.",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: --ack only accepts D3/D5/D6 and persists as acknowledged at hash"
+    },
+    {
+      "id": "TC-218-summary",
+      "acId": "AC-17601-4",
+      "description": "First-freeze summary matches 'first freeze at <shortHash>: <req> REQ, <us> stories, <ac> criteria, <interfaces> interfaces, <tac> TAC, <adr> ADR, <fbs> FBS.'; incremental-freeze summary (a second freeze after editing one US) matches 'frozen at <shortHash>: 0 REQ, 0 stories, 0 criteria, 0 interfaces added; <US-id> amended; 0 re-execute.'; --json emits { record, summary, delta }.",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: summary line follows section 2.5 for first and incremental freezes"
+    },
+    {
+      "id": "TC-218-status",
+      "acId": "AC-17601-5",
+      "description": "--status on a never-frozen project prints 'never frozen' and exits 0 (--json: record null, delta unfrozen); --status on a frozen project prints the record block + delta summary line; --status runs no gates and never writes the record (mtime unchanged after --status).",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: --status is read-only and reports the record + live delta"
+    },
+    {
+      "id": "TC-218-admissibility",
+      "acId": "AC-17601-6",
+      "description": "When runWithAdmissibilityGate returns 'refused-admissibility' (simulated by a chain-rulesetVersion mismatch or a construct-time refusal fixture), the CLI still runs the freeze compute and writes the record on freezeable=true; the refusal is a stderr [warn] line and never sets exit 4 on its own.",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: admissibility refusal is informational, never a freeze refusal"
+    },
+    {
+      "id": "TC-218-override",
+      "acId": "AC-17601-7",
+      "description": "validateFreezeRecord({ ...validRecord, override: undefined }) throws FreezeRecordError with field 'override'; loadFreezeRecord defaults a missing override key to null on read; saveFreezeRecord refuses to write a body that omits override.",
+      "status": "pending",
+      "testPointer": "test/define/freeze-record.test.js::freeze-record: override is required (nullable) and the loader defaults missing keys to null"
+    },
+    {
+      "id": "TC-218-hygiene",
+      "acId": "AC-17601-8",
+      "description": "The readiness CLI stage header line uses a colon between stage id and state ('D1 (define.brief): failing') and never a ' -- ' double-dash; the CHANGELOG.md line for the TODO regex is likewise colon-punctuated; a grep for ' -- ' in the two touched files scoped to the slice-added lines returns no matches.",
+      "status": "pending",
+      "testPointer": "test/cli/freeze.test.js::freeze cli: readiness stage header and CHANGELOG no longer use ' -- '"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-10-01T14:30:00Z",
+  "updatedAt": "2026-10-01T14:30:00Z",
+  "purpose": "Cover US-17402: every entry in stages[].checks[] carries persona (productOwner | engineer) and a non-empty question string; CHECK_PERSONA / CHECK_QUESTION / STAGE_FALLBACK_PERSONA maps are total; the notApplicable placeholder uses the stage fallback (ADR-4126).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17402-1",
+    "AC-17402-2",
+    "AC-17402-3",
+    "AC-17402-4",
+    "AC-17402-5",
+    "AC-17402-6",
+    "AC-17402-7"
+  ],
+  "id": "TS-219",
+  "usId": "US-17402",
+  "title": "Persona tag + question on every gate check",
+  "testCases": [
+    {
+      "id": "TC-219-every-check-has-persona-and-question",
+      "acId": "AC-17402-1",
+      "description": "For every stage function, every entry in checks[] carries persona (productOwner|engineer) and a non-empty question string.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17402-1): every check carries persona + question"
+    },
+    {
+      "id": "TC-219-d1-personas",
+      "acId": "AC-17402-2",
+      "description": "The four D1 check names (brief:sinceFreeze, brief:kinds, brief:openQuestions, brief:profile) carry persona 'productOwner' in CHECK_PERSONA.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126): CHECK_PERSONA and CHECK_QUESTION cover every check name"
+    },
+    {
+      "id": "TC-219-d2-personas",
+      "acId": "AC-17402-3",
+      "description": "D2 personas: skeleton:resolvedBy + skeleton:reqIntent are productOwner; skeleton:reqShape, skeleton:tadPersistence, skeleton:deployAdr are engineer.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126): CHECK_PERSONA and CHECK_QUESTION cover every check name"
+    },
+    {
+      "id": "TC-219-d4-d7-personas",
+      "acId": "AC-17402-4",
+      "description": "D4 personas: stories:reqHasUs productOwner, stories:usFloors engineer. D7 personas: decisions:wellFormed productOwner, decisions:allAnswered engineer.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126): CHECK_PERSONA and CHECK_QUESTION cover every check name"
+    },
+    {
+      "id": "TC-219-engineer-stages",
+      "acId": "AC-17402-5",
+      "description": "D3 (shapes:*), D5 (crosscut:*), D6 (consistency:*) and D8 (freeze:*) checks are all engineer in CHECK_PERSONA.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126): CHECK_PERSONA and CHECK_QUESTION cover every check name"
+    },
+    {
+      "id": "TC-219-persona-vocabulary-closed",
+      "acId": "AC-17402-6",
+      "description": "No check carries a persona value other than 'productOwner' or 'engineer', and no failing { id, why } entry carries its own persona field.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17402-1): every check carries persona + question"
+    },
+    {
+      "id": "TC-219-not-applicable-placeholder-persona",
+      "acId": "AC-17402-7",
+      "description": "A notApplicable stage emits one stage:<D>:scope placeholder check with ok true and persona equal to STAGE_FALLBACK_PERSONA[D].",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17402-7): notApplicable placeholder carries stage fallback persona and ok true"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-10-01T14:30:00Z",
+  "updatedAt": "2026-10-01T14:30:00Z",
+  "purpose": "Cover US-17403: the skeleton:reqFields split into reqIntent + reqShape, the decisions:allAnswered split into wellFormed + allAnswered, and the new D3 shapes:draftSettled check for interface descriptions carrying the [draft] marker (ADR-4126).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17403-1",
+    "AC-17403-2",
+    "AC-17403-3",
+    "AC-17403-4",
+    "AC-17403-5",
+    "AC-17403-6",
+    "AC-17403-7",
+    "AC-17403-8"
+  ],
+  "id": "TS-220",
+  "usId": "US-17403",
+  "title": "Split checks and the D3 draft marker",
+  "testCases": [
+    {
+      "id": "TC-220-todo-no-shapes-fails-both",
+      "acId": "AC-17403-1",
+      "description": "A REQ with a TODO description and no shapeClassification fails skeleton:reqIntent for the description AND skeleton:reqShape for the missing shapes.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-1): TODO description + missing shapes fails BOTH reqIntent AND reqShape on same REQ"
+    },
+    {
+      "id": "TC-220-shapes-no-domain-fails-req-intent-only",
+      "acId": "AC-17403-2",
+      "description": "A REQ with description and shapes but no domain fails skeleton:reqIntent (domain missing) and passes skeleton:reqShape.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-2): shapes present + no domain fails reqIntent only"
+    },
+    {
+      "id": "TC-220-draft-fails-draft-settled",
+      "acId": "AC-17403-3",
+      "description": "A TAC whose only interface description starts with [draft] passes shapes:tacHasInterface and fails shapes:draftSettled with id <tacId>:<name>.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-3 / 4): draft interface fails draftSettled, passes tacHasInterface"
+    },
+    {
+      "id": "TC-220-marker-removed-passes-draft-settled",
+      "acId": "AC-17403-4",
+      "description": "After the [draft] marker is removed from the interface description, shapes:draftSettled passes it.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-3 / 4): draft interface fails draftSettled, passes tacHasInterface"
+    },
+    {
+      "id": "TC-220-draft-kind-vocabulary-still-applies",
+      "acId": "AC-17403-5",
+      "description": "A [draft] interface whose kind is not in INTERFACE_KINDS fails shapes:kindVocabulary exactly as a settled interface would.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-5): kindVocabulary applies to drafts just like settled interfaces"
+    },
+    {
+      "id": "TC-220-enumerated-passes-well-formed-fails-all-answered",
+      "acId": "AC-17403-6",
+      "description": "An open decision with a question, two options and a default naming one of them passes decisions:wellFormed and fails decisions:allAnswered.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-6): enumerated open decision passes wellFormed, fails allAnswered"
+    },
+    {
+      "id": "TC-220-one-option-no-default-fails-well-formed",
+      "acId": "AC-17403-7",
+      "description": "A decisions-ledger entry with one option and no default fails decisions:wellFormed with 'decision is not enumerated (question, two or more options, a default)'.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-7): one option, no default fails wellFormed"
+    },
+    {
+      "id": "TC-220-no-req-fields-emitted",
+      "acId": "AC-17403-8",
+      "description": "No check named skeleton:reqFields is emitted; the stage envelope shape (stage, gate, state, checks) is unchanged.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (ADR-4126, AC-17403-8): no check named skeleton:reqFields is emitted"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-10-01T14:30:00Z",
+  "updatedAt": "2026-10-01T14:30:00Z",
+  "purpose": "Cover US-17502: computeReadiness folds levels.intentComplete and levels.readyToBuild plus personas.productOwner and personas.engineer from stages[].checks[]; the folds are additive and no file under rcf/ is written (ADR-4126).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17502-1",
+    "AC-17502-2",
+    "AC-17502-3",
+    "AC-17502-4",
+    "AC-17502-5",
+    "AC-17502-6",
+    "AC-17502-7",
+    "AC-17502-8"
+  ],
+  "id": "TS-221",
+  "usId": "US-17502",
+  "title": "Two readiness levels folded on one object",
+  "testCases": [
+    {
+      "id": "TC-221-po-ok-engineer-failing",
+      "acId": "AC-17502-1",
+      "description": "A tree where every productOwner check is ok and at least one engineer check fails has levels.intentComplete.ok true and levels.readyToBuild.ok false.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126, AC-17502-1): PO ok + engineer failing => L1 ok, L2 not ok"
+    },
+    {
+      "id": "TC-221-freezeable-implies-l1",
+      "acId": "AC-17502-2",
+      "description": "A tree where freezeable is true has levels.readyToBuild.ok true and levels.intentComplete.ok true.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness: freezeable is true on a well-formed tree (every stage passed / notApplicable)"
+    },
+    {
+      "id": "TC-221-brief-profile-l1-blocker",
+      "acId": "AC-17502-3",
+      "description": "A tree where brief:profile fails has levels.intentComplete.ok false and a single blocker for D1 brief:profile with persona productOwner and ids profile:surface and profile:register.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126, AC-17502-3): brief:profile failing yields L1 blocker and PO next action"
+    },
+    {
+      "id": "TC-221-acknowledged-absent-from-l2",
+      "acId": "AC-17502-4",
+      "description": "An engineer failure inside a D3 stage acknowledged at the current hash is absent from levels.readyToBuild.blockedBy.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126, AC-17502-4): acknowledged D3 engineer failure is absent from readyToBuild.blockedBy"
+    },
+    {
+      "id": "TC-221-personas-mirror-levels",
+      "acId": "AC-17502-5",
+      "description": "personas.productOwner.blockers deep-equals levels.intentComplete.blockedBy and levels.readyToBuild.nextAction deep-equals nextAction.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126, AC-17502-5): personas.productOwner.blockers deep-equals L1 blockedBy; readyToBuild.nextAction equals nextAction"
+    },
+    {
+      "id": "TC-221-persona-next-action-picks-first-failing-stage",
+      "acId": "AC-17502-6",
+      "description": "With engineer failures in D2 and D4 and a PO failure in D4 only, personas.productOwner.nextAction names D4 and personas.engineer.nextAction names D2.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126, AC-17502-6): PO-nextAction prefers first PO-failing stage; engineer-nextAction prefers first engineer-failing stage"
+    },
+    {
+      "id": "TC-221-no-write-on-invocation",
+      "acId": "AC-17502-7",
+      "description": "readiness cli (text and --json) does not create or modify any file under rcf/; the existing readiness cli test suite TS-217 continues to pass unchanged.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17502-7 rcf/ tree is byte-stable across a readiness run (no mutation)"
+    },
+    {
+      "id": "TC-221-backwards-compat-fields",
+      "acId": "AC-17502-8",
+      "description": "Every 0.28.4 top-level field (tree, delta, stages, nextAction, coverage, decisions, freezeable) is present on the 0.29.0 result with its 0.28.4 type.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (ADR-4126, AC-17502-8): 0.28.4 fields present with their types"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,100 @@
+{
+  "createdAt": "2026-10-01T16:00:00Z",
+  "updatedAt": "2026-10-03T12:10: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; ADR-4131 D3 bite)"
+    },
+    {
+      "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 exits 4 on an unacknowledged D3 bite failure under ADR-4131 (0.30.0 PR 5 amends AC-17503-5 for this bite); warn-with-ack posture on D5/D6 preserved until PRs 6 and 7.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli: AC-17503-5 --check all exits 4 on blocking failures (D3 bites in PR 5)"
+    },
+    {
+      "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"
+}