rcf-lite 0.28.4 → 0.30.0

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

@@ -0,0 +1,109 @@
+{
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z",
+  "purpose": "Cover US-17406 (D6 bites) and US-17504 (probe seam and litmus): the four new consistency scans each have pass, fail and the named false-positive guards; countLitmusReadersAtHash reads distinct readers from probe-ledger entries at the current hash; parseLitmusFlag validates input; the readiness CLI --litmus flag exits 4 on a shortfall and documents the flag in --help; computeReadiness returns the pre-PR result when no probeRunner is passed and merges injected findings into open probe entries when one is.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17406-1",
+    "AC-17406-2",
+    "AC-17406-3",
+    "AC-17406-4",
+    "AC-17406-5",
+    "AC-17406-6",
+    "AC-17504-1",
+    "AC-17504-2",
+    "AC-17504-3",
+    "AC-17504-4",
+    "AC-17504-5"
+  ],
+  "id": "TS-232",
+  "usId": "US-17406",
+  "title": "DEFINE step 3 PR 7: D6 consistency scans, probe seam, --litmus and rcf_define_litmus",
+  "testCases": [
+    {
+      "id": "TC-232-contradictions-same-when-negated-then",
+      "acId": "AC-17406-1",
+      "description": "Two ACs on one story sharing a when clause and a negated then fail consistency:contradictions with the story id and both AC ids in the why.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (PR 7, AC-17406-1): contradictions fails a story with two ACs sharing a when and a negated then"
+    },
+    {
+      "id": "TC-232-contradictions-quoted-negation-guard",
+      "acId": "AC-17406-6",
+      "description": "A negation inside a double-quoted substring in a then does not fire consistency:contradictions on the story.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (PR 7, AC-17406-6): contradictions does not fire on a negation inside a quoted substring"
+    },
+    {
+      "id": "TC-232-unsatisfiable-undefined-field",
+      "acId": "AC-17406-2",
+      "description": "A then naming a field no recordShape defines fails consistency:unsatisfiable with id <acId>:<field>.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (PR 7, AC-17406-2): unsatisfiable fails an AC naming a field no recordShape defines"
+    },
+    {
+      "id": "TC-232-unsatisfiable-draft-recordshape",
+      "acId": "AC-17406-3",
+      "description": "A field defined in a [draft] recordShape counts as defined; consistency:unsatisfiable passes the AC.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (PR 7, AC-17406-3): unsatisfiable passes when the field lives in a [draft] recordShape"
+    },
+    {
+      "id": "TC-232-duplicates-across-stories",
+      "acId": "AC-17406-4",
+      "description": "Identical AC descriptions on two stories fail consistency:duplicates with both AC ids.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (PR 7, AC-17406-4): duplicates fails identical AC descriptions across stories"
+    },
+    {
+      "id": "TC-232-orphan-interfaces",
+      "acId": "AC-17406-5",
+      "description": "An interface no ownerRef and no deliveredBy reaches fails consistency:orphanInterfaces with id <tacId>:<name>.",
+      "status": "pending",
+      "testPointer": "test/query/gates.test.js::gates (PR 7, AC-17406-5): orphanInterfaces fails an interface no ownerRef and no deliveredBy reaches"
+    },
+    {
+      "id": "TC-232-probe-runner-injects-findings",
+      "acId": "AC-17504-1",
+      "description": "A probeRunner returning two findings for REQ-003 causes consistency:probeCount to fail; the injected findings appear as open probe entries.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (PR 7, AC-17504-1): probeRunner findings land as open probe entries that fail consistency:probeCount"
+    },
+    {
+      "id": "TC-232-no-probe-runner-matches-pre-pr",
+      "acId": "AC-17504-2",
+      "description": "No probeRunner yields the pre-PR result on the same fixture; consistency:probeCount passes.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (PR 7, AC-17504-2): no probeRunner yields the pre-PR result"
+    },
+    {
+      "id": "TC-232-litmus-reader-count",
+      "acId": "AC-17504-3",
+      "description": "countLitmusReadersAtHash reads distinct readers from probe-ledger entries whose finding begins litmus:<reader>: and whose text includes the hash; readings from the same reader are counted once.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (PR 7): countLitmusReadersAtHash reads distinct readers from probe entries"
+    },
+    {
+      "id": "TC-232-parse-litmus-flag",
+      "acId": "AC-17504-4",
+      "description": "parseLitmusFlag parses a positive integer, returns null when absent, and throws a usage error on a non-positive or non-integer value.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (PR 7): parseLitmusFlag validates its input"
+    },
+    {
+      "id": "TC-232-cli-litmus-shortfall-exits-4",
+      "acId": "AC-17504-4",
+      "description": "rcf define readiness --litmus 2 with no readers exits 4 and prints the shortfall on stderr.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness.test.js::readiness cli (PR 7, AC-17504-4): --litmus 2 with no readers exits 4 naming the shortfall"
+    },
+    {
+      "id": "TC-232-cli-litmus-no-process-spawn",
+      "acId": "AC-17504-5",
+      "description": "The --litmus flag triggers no process spawn and no network call; globalThis.fetch is left untouched by the compute and the counter.",
+      "status": "pending",
+      "testPointer": "test/query/readiness.test.js::readiness (PR 7, AC-17504-5): --litmus triggers no process spawn and no network call"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,61 @@
+{
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z",
+  "purpose": "Cover US-17702 (bundle refuses and skips): the refusal on an unfrozen tree, the --override write of freeze.override, the delta-impacted skip and the all-impacted refusal; the empty-delta frozen-tree case is byte-for-byte unchanged from 0.29.0.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17702-1",
+    "AC-17702-2",
+    "AC-17702-3",
+    "AC-17702-4",
+    "AC-17702-5"
+  ],
+  "id": "TS-233",
+  "usId": "US-17702",
+  "title": "DEFINE step 3 PR 8: rcf build bundle --next refuses, overrides and skips",
+  "testCases": [
+    {
+      "id": "TC-233-bundle-refuses-without-freeze",
+      "acId": "AC-17702-1",
+      "description": "rcf build bundle --next on an unfrozen tree exits 4 and the stderr line names rcf define readiness.",
+      "status": "pending",
+      "testPointer": "test/cli/build-bundle-next-freeze-gate.test.js::bundle --next (PR 8, AC-17702-1): refuses without a freeze record naming rcf define readiness"
+    },
+    {
+      "id": "TC-233-bundle-override-writes-freeze-override",
+      "acId": "AC-17702-2",
+      "description": "rcf build bundle --next --override \"hotfix\" on an unfrozen tree writes freeze.override { reason, by, at } through saveFreezeRecord and emits a bundle (exit 0).",
+      "status": "pending",
+      "testPointer": "test/cli/build-bundle-next-freeze-gate.test.js::bundle --next (PR 8, AC-17702-2): --override writes freeze.override and proceeds"
+    },
+    {
+      "id": "TC-233-bundle-skips-impacted-fbs",
+      "acId": "AC-17702-3",
+      "description": "On a non-empty delta impacting FBS-018, bundle --next skips FBS-018 with the reason on stderr and hands out the next unimpacted actionable FBS.",
+      "status": "pending",
+      "testPointer": "test/cli/build-bundle-next-freeze-gate.test.js::bundle --next (PR 9, AC-17702-3): skips the impacted FBS and hands out the next unimpacted FBS (exit 0)"
+    },
+    {
+      "id": "TC-233-bundle-all-impacted-refuses",
+      "acId": "AC-17702-4",
+      "description": "When every actionable FBS is impacted by the delta and no --override is given, bundle --next refuses with exit 4 and the same message pointing at --override.",
+      "status": "pending",
+      "testPointer": "test/cli/build-bundle-next-freeze-gate.test.js::bundle --next (PR 9, AC-17702-4): refuses with exit 4 when every actionable FBS is impacted and no override"
+    },
+    {
+      "id": "TC-233-bundle-empty-delta-unchanged",
+      "acId": "AC-17702-5",
+      "description": "On a frozen tree with an empty delta the bundle --next output and exit code are byte-for-byte unchanged from 0.29.0 (compared against a captured fixture).",
+      "status": "pending",
+      "testPointer": "test/cli/build-bundle-next-freeze-gate.test.js::bundle --next (PR 9, AC-17702-5): empty delta on a frozen tree matches the 0.29.0 golden bundle byte-for-byte"
+    },
+    {
+      "id": "TC-233-override-by-order",
+      "acId": "AC-17702-6",
+      "description": "freeze.override.by resolves via the git config -> GITHUB_ACTOR -> USER -> USERNAME -> operator preference order.",
+      "status": "passing",
+      "testPointer": "test/cli/build-bundle-next-freeze-gate.test.js::bundle --next (PR 9, AC-17702-6): freeze.override.by resolves via git config user.email first, then GITHUB_ACTOR, then USER/USERNAME, then operator"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,53 @@
+{
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z",
+  "purpose": "Cover US-17802 (validate findings): the four new findings on an interface kind outside the vocabulary, a bracketed AC prefix outside the known classes, a tacIds naming a non-TAC and an unresolving ownerRef or deliveredBy; the dogfood tree is clean; and absence of a class marker is NOT a finding (decision 10, kept).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17802-1",
+    "AC-17802-2",
+    "AC-17802-3",
+    "AC-17802-4"
+  ],
+  "id": "TS-234",
+  "usId": "US-17802",
+  "title": "DEFINE step 3 PR 8: rcf define validate findings",
+  "testCases": [
+    {
+      "id": "TC-234-validate-interface-kind-finding",
+      "acId": "AC-17802-1",
+      "description": "A TAC with an interface { kind: 'widget' } fails rcf define validate with a defineValidate:interfaceKind finding naming the TAC id, the interface name and the unknown kind; the exit code is 3.",
+      "status": "pending",
+      "testPointer": "test/define/validate-findings.test.js::validate findings (PR 8, AC-17802-1): interface kind outside the vocabulary is a finding"
+    },
+    {
+      "id": "TC-234-validate-ac-class-prefix-finding",
+      "acId": "AC-17802-2",
+      "description": "An AC with description '[sometimes] ...' fails rcf define validate with a defineValidate:acClassPrefix finding naming the US id, the AC id and the unknown prefix.",
+      "status": "pending",
+      "testPointer": "test/define/validate-findings.test.js::validate findings (PR 8, AC-17802-2): bracketed AC prefix outside the known classes is a finding"
+    },
+    {
+      "id": "TC-234-validate-tacids-and-ownerref-findings",
+      "acId": "AC-17802-1",
+      "description": "A US with tacIds naming a non-TAC fires defineValidate:tacIdsResolves; an AC with ownerRef { tacId, field } that does not resolve fires defineValidate:ownerRefResolves; a REQ with deliveredBy pointing at a dangling id fires defineValidate:deliveredByResolves. Each exits 3.",
+      "status": "pending",
+      "testPointer": "test/define/validate-findings.test.js::validate findings (PR 8): tacIds, ownerRef and deliveredBy each produce a finding"
+    },
+    {
+      "id": "TC-234-validate-dogfood-clean",
+      "acId": "AC-17802-3",
+      "description": "rcf define validate on the rcf-lite dogfood tree exits 0 (no new findings; no legacy finding is widened).",
+      "status": "pending",
+      "testPointer": "test/define/validate-dogfood.test.js::validate (PR 8, AC-17802-3): dogfood tree is clean"
+    },
+    {
+      "id": "TC-234-validate-no-finding-for-missing-class",
+      "acId": "AC-17802-4",
+      "description": "An AC description with no leading bracketed prefix fires no defineValidate:acClassPrefix finding (decision 10, kept); the exit code depends on other errors only.",
+      "status": "pending",
+      "testPointer": "test/define/validate-findings.test.js::validate findings (PR 8, AC-17802-4): absence of class marker is NOT a finding"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,53 @@
+{
+  "createdAt": "2026-10-03T18:30:00Z",
+  "updatedAt": "2026-10-03T18:30:00Z",
+  "purpose": "Cover US-17902 (NV-DL enforced): the five ruleset rules land with refuseByDefault:true and overrideChannel:recordedInChain; the admissibility wrap on an unfrozen tree refuses citing NV-DL-ADM-01; freeze.override satisfies the override channel; readiness compute still runs and prints under refusal.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-17902-1",
+    "AC-17902-2",
+    "AC-17902-3",
+    "AC-17902-4"
+  ],
+  "id": "TS-235",
+  "usId": "US-17902",
+  "title": "DEFINE step 3 PR 8: NV-DL-ADM-01..05 refuse by default with recordedInChain override channel",
+  "testCases": [
+    {
+      "id": "TC-235-ruleset-nvdl-shape",
+      "acId": "AC-17902-1",
+      "description": "The shipped ruleset JSON carries NV-DL-ADM-01, 02, 03, 04 and 05 under admissibilityRules; each row has refuseByDefault: true and overrideChannel: 'recordedInChain'; each has a non-empty title.",
+      "status": "pending",
+      "testPointer": "test/ruleset/ruleset-nvdl.test.js::ruleset NV-DL (PR 8, AC-17902-1): NV-DL-ADM-01..05 refuse by default with overrideChannel recordedInChain"
+    },
+    {
+      "id": "TC-235-admissibility-wrap-refuses-on-unfrozen-tree",
+      "acId": "AC-17902-2",
+      "description": "runWithAdmissibilityGate on an unfrozen tree returns a refusal citing NV-DL-ADM-01; the inner produce function is not called.",
+      "status": "pending",
+      "testPointer": "test/query/refuse-on-admissibility-nvdl.test.js::evaluateDefineStageAdmissibility (PR 9): cites ADM-02 for failing D4, ADM-03 for failing D3, ADM-04 for non-empty validate errors"
+    },
+    {
+      "id": "TC-235-admissibility-wrap-accepts-with-override",
+      "acId": "AC-17902-3",
+      "description": "runWithAdmissibilityGate on a tree whose freeze.override is set returns ok and names the override; produce is called.",
+      "status": "pending",
+      "testPointer": "test/query/refuse-on-admissibility-nvdl.test.js::runWithAdmissibilityGate (PR 9): a failing NV-BL verdict combines NV-BL rule ids with biting NV-DL rules in the refusal, and the producer does not run"
+    },
+    {
+      "id": "TC-235-readiness-compute-unchanged-under-refusal",
+      "acId": "AC-17902-4",
+      "description": "rcf define readiness on an unfrozen tree still computes and prints the readiness envelope; the admissibility refusal is informational on the compute (ADR-4123); exit code is unchanged from 0.29.0.",
+      "status": "pending",
+      "testPointer": "test/cli/readiness-nvdl-informational.test.js::readiness compute (PR 8, AC-17902-4): still runs and prints under NV-DL refusal"
+    },
+    {
+      "id": "TC-235-wrap-cites-define-stages",
+      "acId": "AC-17902-5",
+      "description": "the admissibility wrap cites NV-DL-ADM-02/03/04 when stages or validateErrors indicate a biting rule; an --ack-at-current-hash entry omits the citation.",
+      "status": "passing",
+      "testPointer": "test/query/refuse-on-admissibility-nvdl.test.js::runWithAdmissibilityGate (PR 9): a failing NV-BL verdict combines NV-BL rule ids with biting NV-DL rules in the refusal, and the producer does not run"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,50 @@
+{
+  "usId": "US-17302",
+  "prdId": "PRD-001",
+  "reqId": "REQ-173",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "update and the pointer grammar",
+  "description": "User story under REQ-173. Every ledger supports `update <id>` with field patches validated as `add` validates; `resolvedBy` on a brief statement is a closed pointer grammar validated by D2.",
+  "asA": "harness",
+  "iWant": "to patch a statement's kind, text or resolution",
+  "soThat": "a correction does not mint a duplicate",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-17302-1",
+      "description": "[happy] given statement 7, when rcf define ledger brief update 7 --kind constraint --resolved-by REQ-003 runs, then the statement carries kind constraint and resolvedBy REQ-003 and its id and addedAt are unchanged.",
+      "testable": true
+    },
+    {
+      "id": "AC-17302-2",
+      "description": "[happy] given decision 2 with one option, when rcf define ledger decisions update 2 --option a:x --option b:y --default a runs, then decisions:wellFormed passes it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17302-3",
+      "description": "[happy] given each pointer form REQ-nnn, TAD.entity:<name>, PRD.user:<name>, TAD.system:<name>, TAC-nnnn and omitted:<reason> resolving on the fixture, when D2 runs, then skeleton:resolvedBy passes the statement.",
+      "testable": true
+    },
+    {
+      "id": "AC-17302-4",
+      "description": "[failure] given --resolved-by \"loan thing\", when update runs, then it exits 2 naming the grammar and writes nothing.",
+      "testable": true
+    },
+    {
+      "id": "AC-17302-5",
+      "description": "[failure] given --resolved-by REQ-999 on a tree with no REQ-999, when D2 runs, then skeleton:resolvedBy fails the statement with \"pointer does not resolve\".",
+      "testable": true
+    },
+    {
+      "id": "AC-17302-6",
+      "description": "[must-not] given a statement whose text contains an existing REQ title and no resolvedBy, when D2 runs in 0.30.0, then skeleton:resolvedBy does not pass it on the title hit.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-4121-define-ledgers"
+  ],
+  "tags": [],
+  "createdAt": "2026-10-02T16:40:00Z",
+  "updatedAt": "2026-10-02T16:40:00Z"
+}

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

@@ -49,10 +49,22 @@
       "id": "AC-17401-8",
       "description": "checkD8Freeze enforces the tree-wide gate: every prior stage state (D1..D7 as computeReadiness composes them) is passed or acknowledged at the current hash; every AC id in the tree is bound by exactly one FBS (walker's fbsByAcId map has length 1); the queue head (computeQueue.nextActionable) is not null; validateErrors is empty. The stage is never notApplicable.",
       "testable": true
+    },
+    {
+      "id": "AC-17401-9",
+      "description": "checkD2Skeleton reads tad.dataArchitecture.dataStores and tad.dataArchitecture.coreEntities (not top-level) when evaluating skeleton:tadPersistence; a tree whose TAD places both arrays under dataArchitecture per rcf-schemas 0.6.3 passes the check and a tree with the arrays missing or empty under dataArchitecture fails with { id: 'TAD.dataArchitecture.dataStores' } / { id: 'TAD.dataArchitecture.coreEntities' }.",
+      "testable": true
+    },
+    {
+      "id": "AC-17401-10",
+      "description": "src/setup/identity-seed.js IDENTITY_TEMPLATE seeds a '## Surface' section containing one line that is one of 'viewer' | 'runningApp' | 'prDiff' (default 'prDiff' with explanatory text matching the Register section's style) so that a project immediately after 'rcf init' passes checkD1Brief's profile:surface check without further operator action. The seed stays idempotent (an existing profile.md is left byte-identical, per the slice-1 'kept' contract).",
+      "testable": true
     }
   ],
-  "tacIds": ["TAC-4122-define-gates"],
+  "tacIds": [
+    "TAC-4122-define-gates"
+  ],
   "tags": [],
   "createdAt": "2026-09-24T14:30:00Z",
-  "updatedAt": "2026-09-24T14:30:00Z"
+  "updatedAt": "2026-10-01T13:03:38Z"
 }

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

@@ -0,0 +1,55 @@
+{
+  "usId": "US-17402",
+  "prdId": "PRD-001",
+  "reqId": "REQ-174",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Persona tag on every gate check",
+  "description": "User story under REQ-174. Every entry in stages[].checks[] carries an owning persona (productOwner | engineer) declared in code next to the check, so readiness consumers (the CLI, the viewer tab, delivery-stream artefacts) can route a failing check to whoever is actually blocked.",
+  "asA": "an engineer reading a readiness report",
+  "iWant": "every failing check to say whose question it is",
+  "soThat": "product-owner questions reach the product owner and engineering gaps stay with me",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-17402-1",
+      "description": "[happy] Given any tree, when readiness is computed, then every entry in stages[].checks[] carries persona equal to 'productOwner' or 'engineer' and a non-empty question string.",
+      "testable": true
+    },
+    {
+      "id": "AC-17402-2",
+      "description": "[happy] Given the D1 checks, when readiness is computed, then brief:sinceFreeze, brief:kinds, brief:openQuestions and brief:profile carry persona 'productOwner'.",
+      "testable": true
+    },
+    {
+      "id": "AC-17402-3",
+      "description": "[happy] Given the D2 checks, when readiness is computed, then skeleton:resolvedBy and skeleton:reqIntent carry persona 'productOwner' and skeleton:reqShape, skeleton:tadPersistence and skeleton:deployAdr carry persona 'engineer'.",
+      "testable": true
+    },
+    {
+      "id": "AC-17402-4",
+      "description": "[happy] Given the D4 and D7 checks, when readiness is computed, then stories:reqHasUs and decisions:wellFormed carry persona 'productOwner' and stories:usFloors and decisions:allAnswered carry persona 'engineer'.",
+      "testable": true
+    },
+    {
+      "id": "AC-17402-5",
+      "description": "[happy] Given the D3, D5, D6 and D8 checks, when readiness is computed, then every check carries persona 'engineer'.",
+      "testable": true
+    },
+    {
+      "id": "AC-17402-6",
+      "description": "[must-not] Given any check, when readiness is computed, then no check carries a persona value other than 'productOwner' or 'engineer', and no failing item carries its own persona.",
+      "testable": true
+    },
+    {
+      "id": "AC-17402-7",
+      "description": "[failure] Given a notApplicable stage, when readiness is computed, then its stage:<D>:scope placeholder check carries the stage's STAGE_FALLBACK_PERSONA and ok true.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-4122-define-gates"
+  ],
+  "tags": [],
+  "createdAt": "2026-10-01T14:30:00Z",
+  "updatedAt": "2026-10-01T14:30:00Z"
+}

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

@@ -0,0 +1,60 @@
+{
+  "usId": "US-17403",
+  "prdId": "PRD-001",
+  "reqId": "REQ-174",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Split heterogeneous checks and detect the D3 draft marker",
+  "description": "User story under REQ-174. skeleton:reqFields and decisions:allAnswered split into homogeneous checks (per persona), and a new D3 shapes:draftSettled flags any interface whose description still carries the leading [draft] marker. L1 pre-populated shapes stay distinguishable from engineer-settled ones.",
+  "asA": "an engineer",
+  "iWant": "the mixed checks split and a draft interface distinguishable from a settled one",
+  "soThat": "a shape the L1 agent pre-populated never reads as my finished work",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-17403-1",
+      "description": "[happy] Given a REQ in scope with a TODO description and no shapeClassification, when D2 runs, then skeleton:reqIntent fails the REQ for the description and skeleton:reqShape fails the same REQ for the missing shapes.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-2",
+      "description": "[happy] Given a REQ in scope with a description and shapes but no domain, when D2 runs, then skeleton:reqIntent fails the REQ with 'domain missing' and skeleton:reqShape passes it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-3",
+      "description": "[happy] Given a TAC in scope whose only interface description starts with [draft], when D3 runs, then shapes:tacHasInterface passes the TAC and shapes:draftSettled fails <tacId>:<name> with 'draft interface pre-populated at L1, not yet settled'.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-4",
+      "description": "[happy] Given the same TAC after the [draft] marker is removed, when D3 runs, then shapes:draftSettled passes it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-5",
+      "description": "[failure] Given a [draft] interface whose kind is not in INTERFACE_KINDS, when D3 runs, then shapes:kindVocabulary fails it exactly as it would a settled interface.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-6",
+      "description": "[happy] Given a decisions ledger with one open entry that has a question, two options and a default, when D7 runs, then decisions:wellFormed passes and decisions:allAnswered fails the entry.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-7",
+      "description": "[failure] Given a decisions ledger entry with one option and no default, when D7 runs, then decisions:wellFormed fails it with 'decision is not enumerated (question, two or more options, a default)'.",
+      "testable": true
+    },
+    {
+      "id": "AC-17403-8",
+      "description": "[must-not] Given any tree, when D2 or D7 runs, then no check named skeleton:reqFields is emitted and the stage envelope shape (stage, gate, state, checks) is unchanged.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-4122-define-gates"
+  ],
+  "tags": [],
+  "createdAt": "2026-10-01T14:30:00Z",
+  "updatedAt": "2026-10-01T14:30:00Z"
+}

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

@@ -0,0 +1,51 @@
+{
+  "usId": "US-17404",
+  "prdId": "PRD-001",
+  "reqId": "REQ-174",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "D3 bites",
+  "description": "User story under REQ-174 for DEFINE step 3 PR 5 (ADR-4131). D3 gets the three bite checks the spec section 4 names (shapes:templateMarkers, shapes:entityJoin, shapes:pathsResolve), stagePolicy exposes an ackable(stage) that is true for D3, D5 and D6, and the readiness CLI --check shapes exits 4 on an unacknowledged D3 failure and 0 when acked at the current hash. D5 and D6 bites land in PRs 6 and 7.",
+  "asA": "an engineer",
+  "iWant": "D3 to run the substantive template, entity-join and path-resolution checks under --check with the same recorded-override channel D3, D5 and D6 share",
+  "soThat": "a draft shape that is missing its markers, an unjoined entity or a dangling path blocks the gate until I either fix the tree or acknowledge it at the current hash",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-17404-1",
+      "description": "[happy] given a recordShape with fields: and an httpRoute with method, path, request, response and errors, when D3 runs, then shapes:templateMarkers passes both.",
+      "testable": true
+    },
+    {
+      "id": "AC-17404-2",
+      "description": "[failure] given an httpRoute missing errors, when D3 runs, then shapes:templateMarkers fails <tacId>:<name> with \"missing marker errors\".",
+      "testable": true
+    },
+    {
+      "id": "AC-17404-3",
+      "description": "[happy] given every coreEntity named by exactly one recordShape, when D3 runs, then shapes:entityJoin passes; given one named twice, then it fails TAD.entity:<name> with \"2 record shapes\".",
+      "testable": true
+    },
+    {
+      "id": "AC-17404-4",
+      "description": "[happy] given an interface naming a path that exists in resolvedPaths, when D3 runs, then shapes:pathsResolve passes it; given a missing path marked authoredAt: D3, then it passes it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17404-5",
+      "description": "[failure] given rcf define readiness --check shapes on an unacknowledged D3 failure, when it runs, then it exits 4; acknowledged at the current hash, it exits 0.",
+      "testable": true
+    },
+    {
+      "id": "AC-17404-6",
+      "description": "[must-not] given --ack on D1, D2, D4, D7 or D8, when freeze runs, then it exits 2 unchanged from 0.29.0.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-4122-define-gates",
+    "TAC-4123-define-readiness"
+  ],
+  "tags": [],
+  "createdAt": "2026-10-03T10:50:00Z",
+  "updatedAt": "2026-10-03T10:50:00Z"
+}

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

@@ -0,0 +1,61 @@
+{
+  "usId": "US-17405",
+  "prdId": "PRD-001",
+  "reqId": "REQ-174",
+  "version": "0.1.1",
+  "status": "draft",
+  "title": "D4, D5 and D2 bite",
+  "description": "User story under REQ-174 for DEFINE step 3 PR 6 (spec section 4 rows for D4, D5 and standards citation). D4 reports closed-set and ownerRef resolution as findings (stories:closedSets, stories:ownerRefResolves). D5 ships the concern catalogue module and the crosscut:catalogue check that enumerates applicable (reqShape, concern) pairs per in-scope REQ against the concern ledger. D2 ships skeleton:standardsCited that fails any registered standards pack that is neither cited in a REQ rationale or an ADR nor waived by a concern-ledger entry with key standards:<pack>. D5 is ackable: --check crosscut rides the same --ack fold as D3, exits 4 on an unacknowledged D5 failure at the current hash and 0 when acked at the current hash. Validate adds no finding for a missing AC class marker (decision 10 kept; the validate finding rows land in PR 8).",
+  "asA": "an engineer",
+  "iWant": "D4 to flag enumeration cues without a closed set, D5 to drive the eight-concern catalogue against the concern ledger for every REQ in scope, D2 to insist every registered standards pack is cited or waived, and --check crosscut to honour the recorded override at the current hash",
+  "soThat": "an AC that invites unlisted values, an unresolved ownerRef, a REQ that forgot a crosscut concern or a registered standards pack that no document cites blocks the gate until the tree is fixed or the gate is acknowledged",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-17405-1",
+      "description": "[failure] given an AC \"status is one of the following\" with no bracketed list and no ownerRef, when D4 runs, then stories:closedSets fails it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-2",
+      "description": "[happy] given an ownerRef { tacId, field: \"interfaces[loan]\" } resolving on that TAC, when D4 runs, then stories:ownerRefResolves passes; given interfaces[missing], then it fails with \"ownerRef does not resolve\". (PR 9 R11: ownerRef resolves on any existing field path, bracket grammar -- interfaces[<name>], responsibilities[<n>], dependencies[<name>], alternativesConsidered[<n>] -- or a bare schema field name -- purpose, decision, internalStructure, etc.; interfaces[loan] still resolves, interfaces[missing] still fails.)",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-3",
+      "description": "[happy] given a persistence REQ with retention applied and timeAndTimezone waived with a reason, when D5 runs, then crosscut:catalogue passes it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-4",
+      "description": "[failure] given an httpApi REQ with no errorEnvelope entry, when D5 runs, then crosscut:catalogue fails <REQ>:errorEnvelope.",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-5",
+      "description": "[happy] given a registered standards pack cited in an ADR, when D2 runs, then skeleton:standardsCited passes; uncited and unwaived, it fails standards:<pack>.",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-6",
+      "description": "[must-not] given a story with no class marker on any AC, when rcf define validate runs, then no finding is raised for the missing marker.",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-7",
+      "description": "[happy] (PR 9 R11) given an ownerRef { tacId, field: \"responsibilities[0]\" } naming an existing responsibility index on that TAC, when D4 runs, then stories:ownerRefResolves passes; a bare field name (purpose, internalStructure, decision) resolves when the owning doc carries a non-empty value under that key.",
+      "testable": true
+    },
+    {
+      "id": "AC-17405-8",
+      "description": "[must-not] (PR 9 R11) given an ownerRef whose field uses dotted grammar (interfaces.loan, responsibilities.audit), when D4 or rcf define validate runs, then it fails with the finding naming the dotted field so the author can rewrite to bracket grammar.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-4122-define-gates",
+    "TAC-4121-define-ledgers"
+  ],
+  "tags": [],
+  "createdAt": "2026-10-03T13:30:00Z",
+  "updatedAt": "2026-10-03T20:30:00Z"
+}

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

@@ -0,0 +1,51 @@
+{
+  "usId": "US-17406",
+  "prdId": "PRD-001",
+  "reqId": "REQ-174",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "D6 bites",
+  "description": "User story under REQ-174 for DEFINE step 3 PR 7 (spec section 4 row 'D6 scans and the injectable probe runner'). D6 gets the four mechanical consistency scans the spec section 11.5 names: consistency:contradictions (two ACs on one story sharing a when clause with a negated then), consistency:unsatisfiable (a then naming a field no recordShape defines; a field defined in a [draft] recordShape counts as defined), consistency:duplicates (identical descriptions across stories, both fail), consistency:orphanInterfaces (no AC ownerRef and no REQ deliveredBy reaches it). D6 is already ackable per PR 5; flipping D6 into the biting set in src/cli/readiness.js is this PR's one-line change. Named false-positive guards: a negation inside a double-quoted substring in a then does not fire contradictions; a field defined in a [draft] recordShape counts as defined for unsatisfiable.",
+  "asA": "an engineer",
+  "iWant": "D6 to run the four substantive consistency scans and --check consistency to honour the recorded override at the current hash",
+  "soThat": "two ACs on one story that contradict each other, a then that names an undefined field, duplicate descriptions across stories or an orphaned interface block the gate until the tree is fixed or the gate is acknowledged",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-17406-1",
+      "description": "[failure] given two ACs on one story with the same when clause and a negated then, when D6 runs, then consistency:contradictions fails the story naming both ACs.",
+      "testable": true
+    },
+    {
+      "id": "AC-17406-2",
+      "description": "[failure] given a then naming a field no recordShape defines, when D6 runs, then consistency:unsatisfiable fails the AC.",
+      "testable": true
+    },
+    {
+      "id": "AC-17406-3",
+      "description": "[happy] given the field defined in a [draft] recordShape, when D6 runs, then consistency:unsatisfiable passes the AC.",
+      "testable": true
+    },
+    {
+      "id": "AC-17406-4",
+      "description": "[failure] given identical AC descriptions on two stories, when D6 runs, then consistency:duplicates fails both.",
+      "testable": true
+    },
+    {
+      "id": "AC-17406-5",
+      "description": "[failure] given an interface no ownerRef and no deliveredBy reaches, when D6 runs, then consistency:orphanInterfaces fails it.",
+      "testable": true
+    },
+    {
+      "id": "AC-17406-6",
+      "description": "[must-not] given a negation inside a quoted string in a then, when D6 runs, then consistency:contradictions does not fail the story on it.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-4122-define-gates",
+    "TAC-4123-define-readiness"
+  ],
+  "tags": [],
+  "createdAt": "2026-10-03T16:10:00Z",
+  "updatedAt": "2026-10-03T16:10:00Z"
+}