rcf-lite 0.0.1 → 0.8.0

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:19.703Z",
+  "updatedAt": "2026-07-29T12:57:19.997Z",
+  "purpose": "Verify coverage classifies requirements without stories and criteria without resolving test cases, and reports complete coverage with no gaps when everything is bound.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-401-1",
+    "AC-401-2",
+    "AC-401-3"
+  ],
+  "id": "TS-010",
+  "usId": "US-401",
+  "title": "Coverage report",
+  "testCases": [
+    {
+      "id": "TC-010-req-without-us-uncovered",
+      "acId": "AC-401-1",
+      "description": "a requirement with no user story is classified uncovered",
+      "status": "pending",
+      "testPointer": "test/query/coverage.test.js::REQ with zero US returns uncovered"
+    },
+    {
+      "id": "TC-010-ac-without-tc-uncovered",
+      "acId": "AC-401-2",
+      "description": "an acceptance criterion with no test case cross-link is classified uncovered",
+      "status": "pending",
+      "testPointer": "test/query/coverage.test.js::AC with no TC cross-link at all is absent (uncovered), not unresolved"
+    },
+    {
+      "id": "TC-010-full-coverage-no-gaps",
+      "acId": "AC-401-3",
+      "description": "a fully covered tree reports ok with zero uncovered",
+      "status": "pending",
+      "testPointer": "test/query/coverage.test.js::shallow-any default: REQ with one AC covered by one RESOLVING TC returns covered"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,44 @@
+{
+  "createdAt": "2026-07-29T12:57:20.096Z",
+  "updatedAt": "2026-07-29T13:35:15.082Z",
+  "purpose": "Verify forward and backward traversal along the intent chain. AC-402-3 is pending: forward trace deliberately surfaces FBS via cross-link (D4), contradicting the AC's never-FBS clause (see test-suites/PENDING.md).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-402-1",
+    "AC-402-2"
+  ],
+  "id": "TS-011",
+  "usId": "US-402",
+  "title": "Trace forward and back",
+  "testCases": [
+    {
+      "id": "TC-011-trace-forward-req-subtree",
+      "acId": "AC-402-1",
+      "description": "forward trace from a REQ returns the US, AC, TS and TC beneath it",
+      "status": "pending",
+      "testPointer": "test/query/trace.test.js::forward from REQ returns US -> AC -> TS -> TC subtree"
+    },
+    {
+      "id": "TC-011-trace-back-ac-ancestry",
+      "acId": "AC-402-2",
+      "description": "backward trace from an AC returns exactly US, REQ and PRD",
+      "status": "pending",
+      "testPointer": "test/query/trace.test.js::back from AC walks AC -> US -> REQ -> PRD"
+    },
+    {
+      "id": "TC-011-forward-fbs-cross-link-leaf",
+      "acId": "AC-402-3",
+      "description": "forward trace surfaces the delivering FBS as a cross-link leaf and does not walk into its dependents",
+      "status": "pending",
+      "testPointer": "test/query/trace.test.js::forward from AC includes FBS via fbsByAcId cross-link as a leaf, never traversed through (AC-402-3)"
+    },
+    {
+      "id": "TC-011-backward-intent-chain-only",
+      "acId": "AC-402-3",
+      "description": "backward trace walks the intent chain only, with no FBS nodes",
+      "status": "pending",
+      "testPointer": "test/query/trace.test.js::back from AC walks AC -> US -> REQ -> PRD"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,36 @@
+{
+  "createdAt": "2026-07-29T12:57:20.391Z",
+  "updatedAt": "2026-07-29T13:35:26.943Z",
+  "purpose": "Verify impact fan-out from architecture documents. AC-403-1 (FBS slots from a REQ pivot) and AC-403-3 (empty impact set) lack direct assertions and are pending (see test-suites/PENDING.md).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-403-2"
+  ],
+  "id": "TS-012",
+  "usId": "US-403",
+  "title": "Impact analysis",
+  "testCases": [
+    {
+      "id": "TC-012-adr-impact-reaches-fbs",
+      "acId": "AC-403-2",
+      "description": "impact from an ADR returns the FBS items referencing it as context",
+      "status": "pending",
+      "testPointer": "test/query/impact.test.js::impact from ADR: ancestor TAD; descendants include FBS via contextRequirements.adrIds"
+    },
+    {
+      "id": "TC-012-req-impact-includes-fbs-slots",
+      "acId": "AC-403-1",
+      "description": "impact from a REQ pivot includes the FBS slots whose acceptance criteria fall under it, labelled re-execute",
+      "status": "pending",
+      "testPointer": "test/query/impact.test.js::impact from REQ: ancestor PRD; descendants US -> AC -> TS -> TC and the FBS slots under it (AC-403-1)"
+    },
+    {
+      "id": "TC-012-no-dependents-empty-impact",
+      "acId": "AC-403-3",
+      "description": "impact on a document with no dependents reports an empty descendant set",
+      "status": "pending",
+      "testPointer": "test/query/impact.test.js::impact from TC: ancestors include TS, AC, US, REQ, PRD; no dependents -> empty impact set (AC-403-3)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:20.589Z",
+  "updatedAt": "2026-07-29T12:57:20.885Z",
+  "purpose": "Verify bundle assembly walks ACs to their stories, inlines architectural context, and renders as a single sectioned markdown document.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-501-1",
+    "AC-501-2",
+    "AC-501-3"
+  ],
+  "id": "TS-013",
+  "usId": "US-501",
+  "title": "Build prompt assembly",
+  "testCases": [
+    {
+      "id": "TC-013-bundle-ac-gwt-ancestry",
+      "acId": "AC-501-1",
+      "description": "each bundled AC carries its given, when and then plus usId and reqId ancestry",
+      "status": "pending",
+      "testPointer": "test/build/bundle.test.js::each AC carries usId + reqId ancestry and its own fields"
+    },
+    {
+      "id": "TC-013-bundle-inlines-tacs-adrs",
+      "acId": "AC-501-2",
+      "description": "referenced TACs and ADRs are inlined into the bundle context in authored order",
+      "status": "pending",
+      "testPointer": "test/build/bundle.test.js::tacIds / adrIds inline the referenced documents in authored order"
+    },
+    {
+      "id": "TC-013-bundle-single-markdown-document",
+      "acId": "AC-501-3",
+      "description": "the markdown bundle renders the seven sections naming the work, ACs and architectural context",
+      "status": "pending",
+      "testPointer": "test/build/formatters/markdown.test.js::bundle renders the seven D3 sections as headings, in order"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:20.986Z",
+  "updatedAt": "2026-07-29T16:45:00.000Z",
+  "purpose": "Verify dependency-respecting ordering, parallel-safe tier reporting and cycle refusal.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-502-1",
+    "AC-502-2",
+    "AC-502-3"
+  ],
+  "id": "TS-014",
+  "usId": "US-502",
+  "title": "Build order dependencies",
+  "testCases": [
+    {
+      "id": "TC-014-dependency-precedes-dependent",
+      "acId": "AC-502-1",
+      "description": "a dependent item stays blocked until its dependency is satisfied, so dependencies always precede dependents",
+      "status": "pending",
+      "testPointer": "test/build/queue.test.js::notStarted with an unsatisfied dependency is blocked, blockedBy names it"
+    },
+    {
+      "id": "TC-014-independent-items-share-tier",
+      "acId": "AC-502-2",
+      "description": "two FBS items with no dependency between them report the same parallel-safe tier group; a dependent item reports a later tier, never the same group",
+      "status": "pending",
+      "testPointer": "test/build/queue.test.js::FBS items with no dependency between them share a parallel-safe tier (AC-502-2)"
+    },
+    {
+      "id": "TC-014-cycle-detected-reported",
+      "acId": "AC-502-3",
+      "description": "a dependency cycle is detected and every member reported blocked-cycle with no partial order",
+      "status": "pending",
+      "testPointer": "test/build/queue.test.js::dependency cycle: every member is blocked (cycle), never a crash"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:21.282Z",
+  "updatedAt": "2026-07-29T12:57:21.580Z",
+  "purpose": "Verify marking advances execution status through the validating writer, touches only status fields, and refuses unknown ids.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-503-1",
+    "AC-503-2",
+    "AC-503-3"
+  ],
+  "id": "TS-015",
+  "usId": "US-503",
+  "title": "Mark a slice done",
+  "testCases": [
+    {
+      "id": "TC-015-mark-advances-status",
+      "acId": "AC-503-1",
+      "description": "mark advances executionStatus on disk with updatedAt bumped through the validating writer",
+      "status": "pending",
+      "testPointer": "test/cli/build.test.js::--mark writes through updateDocument: status changed, updatedAt bumped"
+    },
+    {
+      "id": "TC-015-mark-unknown-id-not-found",
+      "acId": "AC-503-2",
+      "description": "mark on an unknown FBS id returns a usage error from the pure planner",
+      "status": "pending",
+      "testPointer": "test/build/mark.test.js::unknown id returns a usage error"
+    },
+    {
+      "id": "TC-015-mark-touches-status-only",
+      "acId": "AC-503-3",
+      "description": "the mark write changes only executionStatus and updatedAt, with createdAt untouched",
+      "status": "pending",
+      "testPointer": "test/cli/build.test.js::--mark writes through updateDocument: status changed, updatedAt bumped"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-07-29T12:57:21.678Z",
+  "updatedAt": "2026-07-29T13:35:27.040Z",
+  "purpose": "Verify MCP tool listing and CLI parity for queries. AC-601-3 is pending: no test asserts the absence of a network listener (see test-suites/PENDING.md).",
+  "testLevel": "e2e",
+  "acIds": [
+    "AC-601-1",
+    "AC-601-2"
+  ],
+  "id": "TS-016",
+  "usId": "US-601",
+  "title": "Query and view over MCP",
+  "testCases": [
+    {
+      "id": "TC-016-tools-list-structured-schemas",
+      "acId": "AC-601-1",
+      "description": "an MCP client listing tools sees all eleven rcf tools with input and output schemas",
+      "status": "pending",
+      "testPointer": "test/mcp/stdio.e2e.test.js::e2e: tools/list returns all eleven tools with schemas"
+    },
+    {
+      "id": "TC-016-mcp-coverage-cli-parity",
+      "acId": "AC-601-2",
+      "description": "rcf_coverage over MCP deep-equals the committed CLI coverage golden",
+      "status": "pending",
+      "testPointer": "test/mcp/parity.test.js::parity: rcf_coverage structuredContent deep-equals the committed coverage golden"
+    },
+    {
+      "id": "TC-016-stdio-only-no-listener",
+      "acId": "AC-601-3",
+      "description": "a full MCP session with every listener API instrumented opens no TCP or UDP listener",
+      "status": "pending",
+      "testPointer": "test/mcp/stdio.e2e.test.js::e2e: the server communicates over stdio only and opens no network listener (AC-601-3)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:21.977Z",
+  "updatedAt": "2026-07-29T12:57:22.271Z",
+  "purpose": "Verify mutating and build operations over MCP share the CLI's validation, linkage and refusal behaviour.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-602-1",
+    "AC-602-2",
+    "AC-602-3"
+  ],
+  "id": "TS-017",
+  "usId": "US-602",
+  "title": "CRUD and build over MCP",
+  "testCases": [
+    {
+      "id": "TC-017-mcp-create-cli-validation",
+      "acId": "AC-602-1",
+      "description": "rcf_create applies the CLI per-kind mandatory-field validation over MCP",
+      "status": "pending",
+      "testPointer": "test/mcp/tools.test.js::rcf_create: per-kind mandatory fields are usage errors; body object carries extra fields"
+    },
+    {
+      "id": "TC-017-mcp-build-returns-bundle",
+      "acId": "AC-602-2",
+      "description": "rcf_build returns the assembled bundle deep-equal to the CLI output for the named FBS",
+      "status": "pending",
+      "testPointer": "test/mcp/parity.test.js::parity: rcf_build FBS-001 structuredContent deep-equals live `rcf build FBS-001 --format json`"
+    },
+    {
+      "id": "TC-017-mcp-invalid-write-refused",
+      "acId": "AC-602-3",
+      "description": "a mutating MCP call that would break the tree errors with the postWriteValidation rule",
+      "status": "pending",
+      "testPointer": "test/mcp/b5-postwrite.test.js::net-new breakage on the wedged tree still errors with the postWriteValidation rule"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-07-29T12:57:22.370Z",
+  "updatedAt": "2026-07-29T12:57:22.667Z",
+  "purpose": "Verify invalid-producing writes land nothing on disk, successful writes revalidate cleanly, and validation runs against the registered published schema bundle.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-701-1",
+    "AC-701-2",
+    "AC-701-3"
+  ],
+  "id": "TS-018",
+  "usId": "US-701",
+  "title": "Invalid writes refused",
+  "testCases": [
+    {
+      "id": "TC-018-invalid-write-writes-nothing",
+      "acId": "AC-701-1",
+      "description": "a tree-invalidating update is refused and nothing is written",
+      "status": "pending",
+      "testPointer": "test/core/store/writer-postwrite.test.js::(d) net-new breakage on the already-broken tree is still REFUSED"
+    },
+    {
+      "id": "TC-018-written-doc-validates",
+      "acId": "AC-701-2",
+      "description": "a successful create writes a document that revalidates cleanly on reload",
+      "status": "pending",
+      "testPointer": "test/core/store/writer.test.js::createDocument req writes a schema-valid child file"
+    },
+    {
+      "id": "TC-018-registered-bundle-no-drift",
+      "acId": "AC-701-3",
+      "description": "validation reuses the registered schema bundle across passes without drift",
+      "status": "pending",
+      "testPointer": "test/core/store/validator.test.js::validateDocument re-validates the registered schema (no drift)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,37 @@
+{
+  "createdAt": "2026-07-29T12:57:22.767Z",
+  "updatedAt": "2026-07-29T13:35:27.138Z",
+  "purpose": "Verify failures name field and rule and reach MCP clients as structured objects. AC-702-2 is pending: multi-failure aggregation in one document is implemented (Ajv allErrors) but not asserted (see test-suites/PENDING.md).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-702-1",
+    "AC-702-3"
+  ],
+  "id": "TS-019",
+  "usId": "US-702",
+  "title": "Clear validation errors",
+  "testCases": [
+    {
+      "id": "TC-019-failure-names-field-and-rule",
+      "acId": "AC-702-1",
+      "description": "a validation failure names the offending field and the rule it broke",
+      "status": "pending",
+      "testPointer": "test/core/errors/format.test.js::formatError verbose mode appends field and rule"
+    },
+    {
+      "id": "TC-019-mcp-errors-structured",
+      "acId": "AC-702-3",
+      "description": "validation errors over MCP pass through as structured D11 payload objects",
+      "status": "pending",
+      "testPointer": "test/mcp/map-errors.test.js::writerErrorResult passes plain validation / brokenReference errors through with the D11 payload"
+    },
+    {
+      "id": "TC-019-multi-failures-returned-together",
+      "acId": "AC-702-2",
+      "description": "two independent violations in one document surface together in the single returned error",
+      "status": "pending",
+      "testPointer": "test/core/store/validator.test.js::validateDocument returns every failure in one document together (AC-702-2)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-07-29T12:57:23.080Z",
+  "updatedAt": "2026-07-29T12:57:23.529Z",
+  "purpose": "Verify the shipped guidance pack requires a working, seeded, single-command local preview as the hosting-independent default outcome of every build.",
+  "testLevel": "contract",
+  "acIds": [
+    "AC-801-1",
+    "AC-801-2",
+    "AC-801-3",
+    "AC-801-4"
+  ],
+  "id": "TS-020",
+  "usId": "US-801",
+  "title": "Local preview guidance",
+  "testCases": [
+    {
+      "id": "TC-020-preview-in-definition-of-done",
+      "acId": "AC-801-1",
+      "description": "the build-cycle contract requires a working documented local preview in the definition of done",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-801-1/3: the build cycle requires a local preview as the hosting-independent default outcome"
+    },
+    {
+      "id": "TC-020-single-start-command",
+      "acId": "AC-801-2",
+      "description": "the playbook directs one documented start command where the stack allows",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-801-2: the local preview is startable via a single documented command where the stack allows"
+    },
+    {
+      "id": "TC-020-preview-hosting-independent",
+      "acId": "AC-801-3",
+      "description": "the preview is required whether or not a hosting target was stated",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-801-1/3: the build cycle requires a local preview as the hosting-independent default outcome"
+    },
+    {
+      "id": "TC-020-seeded-data-required",
+      "acId": "AC-801-4",
+      "description": "the guidance requires seeded or sample data so the preview is drivable, not an empty shell",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-801-4: the preview carries seeded data when the app needs data to be usable"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-07-29T12:57:23.635Z",
+  "updatedAt": "2026-07-29T12:57:24.063Z",
+  "purpose": "Verify elicitation guidance and the harness fragment order the deploy-target decision ahead of any stack commitment and capture it as an ADR.",
+  "testLevel": "contract",
+  "acIds": [
+    "AC-802-1",
+    "AC-802-2",
+    "AC-802-3",
+    "AC-802-4"
+  ],
+  "id": "TS-021",
+  "usId": "US-802",
+  "title": "Deploy target before stack",
+  "testCases": [
+    {
+      "id": "TC-021-deploy-target-question-early",
+      "acId": "AC-802-1",
+      "description": "elicitation places the deploy-target question before any stack is committed",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-802-1: elicitation places a deploy-target question early, before any stack is committed"
+    },
+    {
+      "id": "TC-021-stack-constrained-by-target",
+      "acId": "AC-802-2",
+      "description": "the stack is constrained to what the stated target can host",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-802-2: the stack choice is constrained by the deploy-target answer"
+    },
+    {
+      "id": "TC-021-target-captured-as-adr",
+      "acId": "AC-802-3",
+      "description": "the deploy target and stack constraint are captured as a visible revisable ADR",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-802-3: the deploy target and its stack implication are captured as an ADR on the project tree"
+    },
+    {
+      "id": "TC-021-fragment-forbids-early-stack",
+      "acId": "AC-802-4",
+      "description": "the harness fragment RULE 5 forbids committing a stack before the deploy target",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-802-4: the harness fragment forbids committing a stack before the deploy target is established"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-07-29T12:57:24.164Z",
+  "updatedAt": "2026-07-29T12:57:24.579Z",
+  "purpose": "Verify the guidance runs a plain-language hosting walkthrough for unsure owners, isolates human-only steps honestly, and covers account configuration.",
+  "testLevel": "contract",
+  "acIds": [
+    "AC-803-1",
+    "AC-803-2",
+    "AC-803-3",
+    "AC-803-4"
+  ],
+  "id": "TS-022",
+  "usId": "US-803",
+  "title": "Hosting-choice walkthrough",
+  "testCases": [
+    {
+      "id": "TC-022-walkthrough-not-silent-choice",
+      "acId": "AC-803-1",
+      "description": "an unsure owner triggers the hosting-choice walkthrough, never a silent choice",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-803-1: when the owner does not know, run a walkthrough rather than choosing silently"
+    },
+    {
+      "id": "TC-022-plain-language-options",
+      "acId": "AC-803-2",
+      "description": "the walkthrough explains options in plain language with no unexplained jargon",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-803-2: the walkthrough explains options in plain language with no unexplained jargon"
+    },
+    {
+      "id": "TC-022-human-steps-named-honestly",
+      "acId": "AC-803-3",
+      "description": "account-holder-only steps are isolated and named honestly, never performed silently or pretended",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-803-3: human-only steps are isolated and named honestly, not performed or pretended"
+    },
+    {
+      "id": "TC-022-covers-account-configuration",
+      "acId": "AC-803-4",
+      "description": "the walkthrough covers accounts, tokens and CLI setup beyond naming a provider",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-803-4: the walkthrough covers configuring the account, not only naming a provider"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-07-29T12:57:24.682Z",
+  "updatedAt": "2026-07-29T12:57:25.085Z",
+  "purpose": "Verify the guidance requires every verification claim to name its runtime, forbids implied deploy-runtime verification, and ships a labelled example.",
+  "testLevel": "contract",
+  "acIds": [
+    "AC-804-1",
+    "AC-804-2",
+    "AC-804-3",
+    "AC-804-4"
+  ],
+  "id": "TS-023",
+  "usId": "US-804",
+  "title": "Runtime-honest verification claims",
+  "testCases": [
+    {
+      "id": "TC-023-claims-name-runtime",
+      "acId": "AC-804-1",
+      "description": "every verification claim names the runtime it was checked against",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-804-1/2: every verification claim names its runtime and never implies an unexercised deployed runtime"
+    },
+    {
+      "id": "TC-023-no-implied-deploy-verification",
+      "acId": "AC-804-2",
+      "description": "no claim may state or imply deploy-runtime verification that did not happen",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-804-1/2: every verification claim names its runtime and never implies an unexercised deployed runtime"
+    },
+    {
+      "id": "TC-023-pr-section-runtime-label",
+      "acId": "AC-804-3",
+      "description": "the PR verification section requires the runtime label on every claim",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-804-3: the PR-authoring guidance requires the runtime label in the verification section"
+    },
+    {
+      "id": "TC-023-labelled-claim-example",
+      "acId": "AC-804-4",
+      "description": "an explicit labelled example names wrangler dev localhost as not the deployed runtime",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-804-4: an explicit labelled example exists, with a non-Cloudflare example alongside the wrangler-dev one"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,46 @@
+{
+  "createdAt": "2026-07-29T12:57:25.185Z",
+  "updatedAt": "2026-07-29T12:57:25.588Z",
+  "purpose": "Verify the guidance describes a fresh-context self-review dispatch that drives the running app against the ACs, names the defect classes, and stays subordinate to the finalise gate.",
+  "testLevel": "contract",
+  "acIds": [
+    "AC-805-1",
+    "AC-805-2",
+    "AC-805-3",
+    "AC-805-4"
+  ],
+  "id": "TS-024",
+  "usId": "US-805",
+  "title": "Interim self-review guidance",
+  "testCases": [
+    {
+      "id": "TC-024-periodic-fresh-context-review",
+      "acId": "AC-805-1",
+      "description": "a periodic and end-of-build fresh-context self-review dispatch is described",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-805-1: a periodic and end-of-build fresh-context self-review dispatch is described"
+    },
+    {
+      "id": "TC-024-reviewer-drives-the-app",
+      "acId": "AC-805-2",
+      "description": "the reviewer drives the running app against the ACs rather than reading code",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-805-2: the reviewer drives the running app against the ACs rather than reading the code"
+    },
+    {
+      "id": "TC-024-names-defect-classes",
+      "acId": "AC-805-3",
+      "description": "the review names the five target defect classes",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-805-3: the review names the target defect classes"
+    },
+    {
+      "id": "TC-024-in-loop-not-the-gate",
+      "acId": "AC-805-4",
+      "description": "the self-review is scoped as an in-loop check naming rcf finalise as the gate",
+      "status": "pending",
+      "testPointer": "test/guidance/tier1-hardening.test.js::AC-805-4: the self-review is honestly scoped as an in-loop check subordinate to the independent gate"
+    }
+  ],
+  "status": "draft"
+}