rcf-lite 0.20.0 → 0.22.0

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-09-06T16:56:55.746Z",
+  "updatedAt": "2026-09-06T16:57:22.760Z",
+  "purpose": "Cover AC-2501-1 through AC-2501-7 via unit tests over the shipped application-file-upload blueprint.json contribution shape (18 contributions in the 5 REQ / 7 US / 3 TAC / 3 ADR groups), the applies-clean pass on a fresh init project, the pack-loader accepting the shipped pack file with every check id cross-checked against blueprint AC ids and appliesTo referencing BOTH tacIds and route, the sample-app fixture serving both transport branches multipart POST and tus.io, the negative-run behaviour on the ?break=no-input ?break=no-live-region ?break=send-refused and ?break=no-chunks switches, the state-and-transport enumeration parity across README guide pack and docs/topics.md registry, and the README mechanism-reach gaps and CHANGELOG 1.0.0 entry.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2501-1",
+    "AC-2501-2",
+    "AC-2501-3",
+    "AC-2501-4",
+    "AC-2501-5",
+    "AC-2501-6",
+    "AC-2501-7"
+  ],
+  "id": "TS-054",
+  "usId": "US-2501",
+  "title": "application-file-upload v1.0.0 shelf shape, probe pack cross-check and sample-app fixture",
+  "testCases": [
+    {
+      "id": "TC-054-blueprint-json-shape",
+      "acId": "AC-2501-1",
+      "description": "blueprint.json declares slug, version 1.0.0, category application, 18 contributions in 5/7/3/3 groups; providesRoles absent; capabilities absent; requiresAppliedCapabilities absent; suggestedCompanions logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::blueprint.json declares 18 contributions with no capabilities and no requiresAppliedCapabilities (TC-054-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-054-applies-clean",
+      "acId": "AC-2501-2",
+      "description": "Fresh init project applies application-file-upload cleanly and reports the tree clean",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::applies cleanly on a fresh init project and adds 18 documents to the tree (TC-054-applies-clean)"
+    },
+    {
+      "id": "TC-054-pack-checks-cross-check",
+      "acId": "AC-2501-3",
+      "description": "Every pack check id matches a contributed AC id; pack-level appliesTo references BOTH tacIds and route; withUrl helper used for every URL string",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::every pack check id matches a contributed AC id and appliesTo binds tacIds AND route (TC-054-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-054-fixture-serves-transports",
+      "acId": "AC-2501-4",
+      "description": "Sample-app fixture serves the multipart POST default and the tus.io elicited alternative honestly on their default branches and via ?transport= switch",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::sample-app fixture serves both transport branches on the default branch (TC-054-fixture-serves-transports)"
+    },
+    {
+      "id": "TC-054-negative-runs",
+      "acId": "AC-2501-5",
+      "description": "Break switches surface the four defects on the DOM or network layer for the corresponding pack checks",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::sample-app fixture break switches surface the four defects on the DOM (TC-054-negative-runs)"
+    },
+    {
+      "id": "TC-054-state-and-transport-parity",
+      "acId": "AC-2501-6",
+      "description": "Four state slugs and two transport slugs appear identically across README, guide, pack checks[] and docs/topics.md registry",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::four state slugs and two transport slugs appear identically across README guide pack and docs (TC-054-state-and-transport-parity)"
+    },
+    {
+      "id": "TC-054-readme-gaps-and-changelog",
+      "acId": "AC-2501-7",
+      "description": "README lists mechanism-reach gaps individually; CHANGELOG carries one 1.0.0 entry; docs/topics.md carries the T-2 shelf registry row",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-file-upload-anatomy.test.js::README lists mechanism-reach gaps and CHANGELOG carries 1.0.0 and topics carries the T-2 row (TC-054-readme-gaps-and-changelog)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,77 @@
+{
+  "createdAt": "2026-09-06T19:04:07.390Z",
+  "updatedAt": "2026-09-06T19:04:27.043Z",
+  "purpose": "Cover AC-2601-1 through AC-2601-7 via unit tests over the shipped application-forms-wizard blueprint.json contribution shape (19 contributions in the 5 REQ / 8 US / 3 TAC / 3 ADR groups), the applies-clean pass on a fresh init project, the pack-loader accepting the shipped pack file with every check id cross-checked against blueprint AC ids and appliesTo referencing BOTH tacIds and route, the sample-app fixture serving the four wizard surfaces honestly and both save-and-return transports on their query branches, the negative-run behaviour on the ?break=task-list-vocab ?break=no-summary ?break=no-retain and ?break=no-draft switches, the vocabulary-and-transport enumeration parity across README guide pack and docs/topics.md registry, and the README mechanism-reach gaps and CHANGELOG 1.0.0 entry.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2601-1",
+    "AC-2601-2",
+    "AC-2601-3",
+    "AC-2601-4",
+    "AC-2601-5",
+    "AC-2601-6",
+    "AC-2601-7"
+  ],
+  "id": "TS-055",
+  "usId": "US-2601",
+  "title": "application-forms-wizard v1.0.0 shelf shape, probe pack cross-check and sample-app fixture",
+  "testCases": [
+    {
+      "id": "TC-055-blueprint-json-shape",
+      "acId": "AC-2601-1",
+      "description": "blueprint.json declares slug, version 1.0.0, category application, 19 contributions in 5/8/3/3 groups; providesRoles absent; capabilities absent; requiresAppliedCapabilities absent; suggestedCompanions logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::blueprint.json declares 19 contributions with no capabilities and no requiresAppliedCapabilities (TC-055-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-055-applies-clean",
+      "acId": "AC-2601-2",
+      "description": "Fresh init project applies application-forms-wizard cleanly and reports the tree clean",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::applies cleanly on a fresh init project and adds 19 documents to the tree (TC-055-applies-clean)"
+    },
+    {
+      "id": "TC-055-pack-checks-cross-check",
+      "acId": "AC-2601-3",
+      "description": "Every pack check id matches a contributed AC id; pack-level appliesTo references BOTH tacIds and route; withUrl helper used for every URL string",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::every pack check id matches a contributed AC id and appliesTo binds tacIds AND route (TC-055-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-055-pack-loader-discovers",
+      "acId": "AC-2601-3",
+      "description": "Pack loader discovers the shipped pack against an applied scratch project",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::application-forms-wizard: pack loader discovers the shipped pack against an applied scratch project (TC-055-pack-loader-discovers)"
+    },
+    {
+      "id": "TC-055-fixture-serves-surfaces",
+      "acId": "AC-2601-4",
+      "description": "Sample-app fixture serves the four wizard surfaces honestly and the two draft-store transports on their query branches",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::sample-app fixture serves the four wizard surfaces and both draft-store transports (TC-055-fixture-serves-surfaces)"
+    },
+    {
+      "id": "TC-055-negative-runs",
+      "acId": "AC-2601-5",
+      "description": "Break switches surface the four defects on the DOM or storage layer for the corresponding pack checks",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::sample-app fixture break switches surface the four defects on the DOM (TC-055-negative-runs)"
+    },
+    {
+      "id": "TC-055-vocabulary-and-transport-parity",
+      "acId": "AC-2601-6",
+      "description": "Closed GOV.UK vocabulary strings and the two transport slugs appear identically across README, guide, pack checks[] and docs/topics.md registry",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::four state slugs and two transport slugs appear identically across README guide pack and docs (TC-055-vocabulary-and-transport-parity)"
+    },
+    {
+      "id": "TC-055-readme-gaps-and-changelog",
+      "acId": "AC-2601-7",
+      "description": "README lists mechanism-reach gaps individually; CHANGELOG carries one 1.0.0 entry; docs/topics.md carries the T-3 shelf registry row and the cross-reference to application-empty-error-states",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-forms-wizard-anatomy.test.js::README lists mechanism-reach gaps and CHANGELOG carries 1.0.0 and topics carries the T-3 row (TC-055-readme-gaps-and-changelog)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-09-06T21:13:07.603Z",
+  "updatedAt": "2026-09-06T21:13:07.603Z",
+  "purpose": "Cover AC-2701-1 through AC-2701-8 via unit tests over the shipped application-account-settings blueprint.json contribution shape (24 contributions in the 6 REQ / 10 US / 4 TAC / 4 ADR groups), the applies-clean pass on a fresh init project with security-auth-magic-link applied, the bare-SPA refusal at exit 3 with the shipped refusal template, the --allow-no-auth-yet override sidecar note, the Q3 refusal for an operator answering security-surface-shape without applied credentialSelfService or hostedIdentityUi, the pack-loader accepting the shipped pack file with every check id cross-checked against blueprint AC ids and appliesTo referencing BOTH tacIds and route, the sample-app fixture serving the five conditional surfaces honestly and refusing on the four break switches, the section 6a capability table extension in blueprint-authoring.md, and the four amended auth blueprints and observability-logging blueprint carrying their new capabilities[] and CHANGELOG entries.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2701-1",
+    "AC-2701-2",
+    "AC-2701-3",
+    "AC-2701-4",
+    "AC-2701-5",
+    "AC-2701-6",
+    "AC-2701-7",
+    "AC-2701-8"
+  ],
+  "id": "TS-056",
+  "usId": "US-2701",
+  "title": "application-account-settings v1.0.0 shelf shape, probe pack cross-check, sample-app fixture, auth-minor and observability-logging minor bumps, mechanism minor for Q3 refusal",
+  "testCases": [
+    {
+      "id": "TC-056-blueprint-json-shape",
+      "acId": "AC-2701-1",
+      "description": "blueprint.json declares 24 contributions with requiresAppliedCapabilities and elicits[] (TC-056-blueprint-json-shape)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::blueprint.json declares 24 contributions with requiresAppliedCapabilities and elicits[] (TC-056-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-056-applies-clean",
+      "acId": "AC-2701-2",
+      "description": "applies cleanly on a magic-link project with 24 contributions and appliedCapabilities=[principalDirectory] (TC-056-applies-clean)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::applies cleanly on a magic-link project with 24 contributions and appliedCapabilities=[principalDirectory] (TC-056-applies-clean)"
+    },
+    {
+      "id": "TC-056-apply-refusal-and-override",
+      "acId": "AC-2701-3",
+      "description": "apply refuses on bare SPA with the [application-account-settings-bare-spa] message; --allow-no-auth-yet applies with a scaffolding note (TC-056-apply-refusal-and-override)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::apply refuses on bare SPA with the [application-account-settings-bare-spa] message; --allow-no-auth-yet applies with a scaffolding note (TC-056-apply-refusal-and-override)"
+    },
+    {
+      "id": "TC-056-q3-refusal",
+      "acId": "AC-2701-8",
+      "description": "Q3 gate: security-surface-shape answered without applied credentialSelfService or hostedIdentityUi is silently gated at apply; the sidecar records no shape entry; the TAC-2603 hosted-ui-bridge enforces the refusal at surface load time",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::Q3 gate: security-surface-shape is silently gated when neither credentialSelfService nor hostedIdentityUi is applied; sidecar records no shape entry; TAC-2603 hosted-ui-bridge enforces the refusal at surface load (TC-056-q3-refusal)"
+    },
+    {
+      "id": "TC-056-pack-checks-cross-check",
+      "acId": "AC-2701-4",
+      "description": "every pack check id matches a contributed AC id; pack-level appliesTo names tacIds AND route; per-check appliesTo gates on the applied capability (TC-056-pack-checks-cross-check)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::every pack check id matches a contributed AC id; pack-level appliesTo names tacIds AND route; per-check appliesTo gates on the applied capability (TC-056-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-056-fixture-and-switches",
+      "acId": "AC-2701-5",
+      "description": "sample-app fixture serves the five conditional surfaces honestly (TC-056-fixture-and-switches)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::sample-app fixture serves the five conditional surfaces honestly (TC-056-fixture-and-switches)"
+    },
+    {
+      "id": "TC-056-negative-runs",
+      "acId": "AC-2701-6",
+      "description": "sample-app fixture break switches surface the four defects (TC-056-negative-runs)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::sample-app fixture break switches surface the four defects (TC-056-negative-runs)"
+    },
+    {
+      "id": "TC-056-shelf-doc-consistency",
+      "acId": "AC-2701-7",
+      "description": "four amended auth blueprints declare the ratified capability sets and observability-logging declares sessionInventory (TC-056-shelf-doc-consistency)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-account-settings-anatomy.test.js::four amended auth blueprints declare the ratified capability sets and observability-logging declares sessionInventory (TC-056-shelf-doc-consistency)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-09-06T23:05:23.898Z",
+  "updatedAt": "2026-09-06T23:19:05.155Z",
+  "purpose": "Cover AC-2801-1 through AC-2801-8 via unit tests over the shipped application-onboarding-tour blueprint.json contribution shape (17 contributions in the 4 REQ / 7 US / 3 TAC / 3 ADR groups), the ADR shape and standardsTraceClause discipline on the ADR contribution entries per spec section 8a, the applies-clean pass on a fresh init project (no requiresAppliedCapabilities), the pack-loader accepting the shipped pack file with every check id cross-checked against blueprint AC ids and appliesTo referencing BOTH tacIds and route, the sample-app fixture serving the tour surface honestly on both apps=dashboard and apps= (empty) branches plus multiple store branches, the four break switches surfacing the four defects (no-role, focus-escape, no-collapse, no-persist), the docs consistency (README, guide, topics.md, blueprint CHANGELOG) and the withUrl helper plus browser.resize breakpoint usage (WCAG 2.4.11) in the pack source.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2801-1",
+    "AC-2801-2",
+    "AC-2801-3",
+    "AC-2801-4",
+    "AC-2801-5",
+    "AC-2801-6",
+    "AC-2801-7",
+    "AC-2801-8"
+  ],
+  "id": "TS-057",
+  "usId": "US-2801",
+  "title": "application-onboarding-tour v1.0.0 shelf shape, probe pack cross-check, sample-app fixture with dashboard-and-settings-page checklist branches and multiple completion-store branches, and the four break switches under Q4 spa-local-storage fallback",
+  "testCases": [
+    {
+      "id": "TC-057-blueprint-json-shape",
+      "acId": "AC-2801-1",
+      "description": "blueprint.json declares 17 contributions with no requiresAppliedCapabilities and elicits[] (TC-057-blueprint-json-shape)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::blueprint.json declares 17 contributions with no requiresAppliedCapabilities and elicits[] (TC-057-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-057-adr-shape",
+      "acId": "AC-2801-2",
+      "description": "ADR JSON documents validate against 0.6.1 and standardsTraceClause is non-null on ADR contribution entries (TC-057-adr-shape)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::ADR JSON documents validate against 0.6.1 and standardsTraceClause is non-null on ADR contribution entries (TC-057-adr-shape)"
+    },
+    {
+      "id": "TC-057-applies-clean",
+      "acId": "AC-2801-3",
+      "description": "applies cleanly on a fresh project with 17 contributions and no requiresAppliedCapabilities refusal (TC-057-applies-clean)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::applies cleanly on a fresh project with 17 contributions and no requiresAppliedCapabilities refusal (TC-057-applies-clean)"
+    },
+    {
+      "id": "TC-057-pack-checks-cross-check",
+      "acId": "AC-2801-4",
+      "description": "every pack check id matches a contributed AC id; pack-level appliesTo names tacIds AND route; withUrl helper used; browser.resize breakpoints appear (TC-057-pack-checks-cross-check)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::every pack check id matches a contributed AC id; pack-level appliesTo names tacIds AND route; withUrl helper used; browser.resize breakpoints appear (TC-057-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-057-fixture-and-switches",
+      "acId": "AC-2801-5",
+      "description": "sample-app fixture serves the honest tour on both apps=dashboard and apps= (empty) branches and multiple store branches (TC-057-fixture-and-switches)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::sample-app fixture serves the honest tour on both apps=dashboard and apps= (empty) branches and multiple store branches (TC-057-fixture-and-switches)"
+    },
+    {
+      "id": "TC-057-negative-runs",
+      "acId": "AC-2801-6",
+      "description": "sample-app fixture break switches surface the four defects (TC-057-negative-runs)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::sample-app fixture break switches surface the four defects (TC-057-negative-runs)"
+    },
+    {
+      "id": "TC-057-shelf-doc-consistency",
+      "acId": "AC-2801-7",
+      "description": "AC ids and cross-reference blueprint slugs appear identically across README, guide, pack descriptions and topics.md (TC-057-shelf-doc-consistency)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::AC ids and cross-reference blueprint slugs appear identically across README, guide, pack descriptions and topics.md (TC-057-shelf-doc-consistency)"
+    },
+    {
+      "id": "TC-057-changelog-guide-and-mechanism-reach",
+      "acId": "AC-2801-8",
+      "description": "README lists mechanism-reach gaps per AC and guide names WCAG SCs and the ARIA APG dialog-modal pattern with URLs (TC-057-changelog-guide-and-mechanism-reach)",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-onboarding-tour-anatomy.test.js::README lists mechanism-reach gaps per AC and guide names WCAG SCs and the ARIA APG dialog-modal pattern with URLs (TC-057-changelog-guide-and-mechanism-reach)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,62 @@
+{
+  "createdAt": "2026-09-06T17:02:27.310Z",
+  "updatedAt": "2026-09-06T17:02:29.479Z",
+  "purpose": "Cover AC-4001-1..6 via unit tests over the shipped persistence-data-postgres blueprint shape, applies-clean behaviour, DELIBERATE conflict surface on persistenceStore and migrationDiscipline, six Node-only probe module contract, induced-failure switches, and shelf-doc consistency.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-4001-1",
+    "AC-4001-2",
+    "AC-4001-3",
+    "AC-4001-4",
+    "AC-4001-5",
+    "AC-4001-6"
+  ],
+  "id": "TS-070",
+  "usId": "US-4001",
+  "title": "persistence-data-postgres v1.0.0 shelf shape, conflict-on-topics-surface, six-probe module contract and shelf-doc consistency",
+  "testCases": [
+    {
+      "id": "TC-070-blueprint-json-shape",
+      "acId": "AC-4001-1",
+      "description": "Cover AC-4001-1 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/persistence-data-postgres-anatomy.test.js::blueprint.json declares 26 contributions with capabilities relationalStore and suggestedCompanions logging and errorHandling (TC-070-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-070-applies-clean-no-persistence",
+      "acId": "AC-4001-2",
+      "description": "Cover AC-4001-2 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/persistence-data-postgres-anatomy.test.js::apply persistence-data-postgres on a bare scratch project writes 26 contributions and validate plus strict audits exit zero (TC-070-applies-clean-no-persistence)"
+    },
+    {
+      "id": "TC-070-conflict-with-d1",
+      "acId": "AC-4001-3",
+      "description": "Cover AC-4001-3 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/persistence-data-postgres-anatomy.test.js::apply persistence-data-postgres on a d1-applied scratch project surfaces globalAdrTopic conflict on persistenceStore and migrationDiscipline (TC-070-conflict-with-d1)"
+    },
+    {
+      "id": "TC-070-probe-anchor-ids-cross-check",
+      "acId": "AC-4001-4",
+      "description": "Cover AC-4001-4 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/persistence-data-postgres-anatomy.test.js::every probe module exports the section 3.2 verdict envelope with an anchorAcId matching a contributed AC id (TC-070-probe-anchor-ids-cross-check)"
+    },
+    {
+      "id": "TC-070-fixture-and-switches",
+      "acId": "AC-4001-5",
+      "description": "Cover AC-4001-5 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/persistence-data-postgres-anatomy.test.js::sample-app fixture ships docker-compose.yml, migrations, store.mjs, recovery.mjs, and its README documents both induced-failure switches (TC-070-fixture-and-switches)"
+    },
+    {
+      "id": "TC-070-shelf-doc-consistency",
+      "acId": "AC-4001-6",
+      "description": "Cover AC-4001-6 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/persistence-data-postgres-anatomy.test.js::section 6a table gains a relationalStore row and every shipped blueprint docs/topics.md gains a persistence-data-postgres row at 27101-27899 / 28xx (TC-070-shelf-doc-consistency)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,62 @@
+{
+  "createdAt": "2026-09-06T17:50:13.712Z",
+  "updatedAt": "2026-09-06T17:51:32.845Z",
+  "purpose": "Cover AC-4101-1..6 via unit tests over the shipped object-storage-s3 blueprint shape (contribution count, capabilities, suggestedCompanions, ADR standardsTraceClause), applies-clean-with-secrets and refuses-without behaviour, six Node-only probe module contract with anchorAcId cross-check, induced-failure switch documentation on the fixture README, and shelf-doc consistency (section 6a table row for objectStorage, shelf-wide docs/topics.md row for object-storage-s3 at 28101-28899 / 29xx).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-4101-1",
+    "AC-4101-2",
+    "AC-4101-3",
+    "AC-4101-4",
+    "AC-4101-5",
+    "AC-4101-6"
+  ],
+  "id": "TS-071",
+  "usId": "US-4101",
+  "title": "object-storage-s3 v1.0.0 shelf shape, apply-on-secrets-present, apply-refusal-on-bare, six-probe module contract, induced-failure switches and shelf-doc consistency",
+  "testCases": [
+    {
+      "id": "TC-071-blueprint-json-shape",
+      "acId": "AC-4101-1",
+      "description": "Cover AC-4101-1 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/object-storage-s3-anatomy.test.js::blueprint.json declares 21 contributions with capabilities objectStorage, suggestedCompanions logging and errorHandling, and standardsTraceClause on every ADR entry (TC-071-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-071-applies-clean-with-secrets",
+      "acId": "AC-4101-2",
+      "description": "Cover AC-4101-2 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/object-storage-s3-anatomy.test.js::apply object-storage-s3 lands 21 contributions on a scratch project with security-secrets-management applied (TC-071-applies-clean-with-secrets)"
+    },
+    {
+      "id": "TC-071-apply-refusal-and-override",
+      "acId": "AC-4101-3",
+      "description": "Cover AC-4101-3 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/object-storage-s3-anatomy.test.js::apply object-storage-s3 refuses on a bare fixture without security-secrets-management and lands with --allow-no-secrets-yet (TC-071-apply-refusal-and-override)"
+    },
+    {
+      "id": "TC-071-probe-anchor-ids-cross-check",
+      "acId": "AC-4101-4",
+      "description": "Cover AC-4101-4 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/object-storage-s3-anatomy.test.js::every probe module exports the section 3.2 verdict envelope with an anchorAcId matching a contributed AC id (TC-071-probe-anchor-ids-cross-check)"
+    },
+    {
+      "id": "TC-071-fixture-and-switches",
+      "acId": "AC-4101-5",
+      "description": "Cover AC-4101-5 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/object-storage-s3-anatomy.test.js::sample-app fixture ships docker-compose.yml, package.json, src/object-store.mjs, src/secrets.mjs, and its README documents docker and podman and the four wired induced-failure switches (TC-071-fixture-and-switches)"
+    },
+    {
+      "id": "TC-071-shelf-doc-consistency",
+      "acId": "AC-4101-6",
+      "description": "Cover AC-4101-6 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/object-storage-s3-anatomy.test.js::section 6a table gains an objectStorage row and every shipped blueprint docs/topics.md gains an object-storage-s3 row at 28101-28899 / 29xx (TC-071-shelf-doc-consistency)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,56 @@
+{
+  "createdAt": "2026-09-04T17:59:40.838Z",
+  "updatedAt": "2026-09-04T18:51:45.216Z",
+  "usId": "US-1701",
+  "prdId": "PRD-001",
+  "reqId": "REQ-017",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "Blueprint-shipped browser-verify probe packs load, scope to real surfaces, and gate ship on runtime failure",
+  "asA": "blueprint author shipping runtime-observable visual ACs alongside contributions",
+  "iWant": "the browser-verify runner to discover, scope and run my blueprint's probe pack, and record each check against the AC it names",
+  "soThat": "a runtime-observable AC that a Node build-scan cannot see (grid announcements, keyboard traversal, live-region text after a synthetic event) is compelled at ship the same way an invariant or an auth-smoke fail is compelled, and the run-4 pack-fires-on-every-FBS residual is cured at load time",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1701-1",
+      "description": "The pack loader discovers `.pack.js` and `.pack.mjs` modules under `blueprints/<slug>/probe-packs/` for every applied blueprint, imports each with a dynamic ESM import, validates the exported default object against the pack schema (`packName` starts with the owning blueprint's slug and matches `^[a-z][a-z0-9]*(?:-[a-z0-9]+)*$`, `version` semver, `blueprintSlug` matches the directory, `checks[]` non-empty with each entry carrying `id`, `severity` in {block, warn, advisory}, `description` and async `run`), and refuses at load (exit 2) with a diagnostic that names the pack path and the offending field on any violation. A valid pack registers on the run.",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-2",
+      "description": "The applicability predicate `appliesTo({ fbs, uiBaseline, manifest })` is a required top-level field on every pack; its source (`appliesTo.toString()`) MUST reference at least one of `route`, `tacIds`, or the `blueprint:` US-tag prefix, and an unqualified predicate (a body that references none of the three, including the default `() => true`) is refused at load with exit 2 and a diagnostic that names the pack, the requirement and the three legal scoping seams. A pack whose `appliesTo` returns `false` for an FBS records `applicable: false` on the record for that FBS with a one-line reason drawn from the predicate context and no `run` function is invoked.",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-3",
+      "description": "The loader cross-checks every `checks[].id` against the AC ids the pack's blueprint contributes through `blueprint.json:contributions[]` (reading each US contribution file and enumerating `acceptanceCriteria[].id`). A pack whose check names an AC id the blueprint does not contribute is refused at load (exit 2) with a diagnostic that names the pack, the offending check id and the AC ids the blueprint actually contributes.",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-4",
+      "description": "The runner runs the pack pass after invariants and after auth-smoke on `agentScreenshotCritique` mode. For each applicable pack the runner invokes every check's `run({ browser, fetch, runtimeUrl, route, theme })` (browser and fetch injected by the runner), records `{ id, verdict, severity, detail? }` on the pack record, and appends the pack record to `browserVerification.probePacks[]` on the composed record. The aggregate verdict extends the existing rule: `block` on any pack check whose severity is `block` and verdict is `fail`; `warn` on any pack check whose severity is `warn` and verdict is `fail` (and no block from invariants, auth-smoke or pack); `pass` otherwise.",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-5",
+      "description": "`rcf verify browser <fbs-id> --probe-pack <name>` restricts one run to one pack by name; a `--probe-pack` value that resolves to no discovered pack (nothing loaded under any applied blueprint's `probe-packs/` matches the name) exits 2 with a diagnostic that names the value and the packs that were discovered. When omitted, every discovered and applicable pack runs; when a pack's `appliesTo` returns false for the FBS, the pack record carries `applicable: false` and no browser check runs against it.",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-6",
+      "description": "A pack MAY declare `preChecks[]`: an array of `{ id, description, run: async () => ({ verdict, detail? }) }` Node build-scan fast-fail checks that the runner invokes before any browser check on the same pack. A pre-check with verdict `fail` records on the pack record and every browser check that names it under `dependsOn` records verdict `skipped` with detail `skipped-by-pre-check:<preCheckId>`; browser checks with no `dependsOn` on a failing pre-check still run. Pre-check verdicts fold into the aggregate the same way pack checks do (a `fail` at `severity: block` blocks ship).",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-7",
+      "description": "The `packBrowser` seam the runner injects into every pack check is a real headless browser provisioned through the pinned Playwright MCP server (`PLAYWRIGHT_MCP_VERSION` in `src/verify/engine/launcher.js`, spawned as `npx -y @playwright/mcp@<pin>` over stdio) via a thin in-package JSON-RPC 2.0 client (zero new npm dependencies in rcf-lite; no LLM call). Every check receives a stable API: `goto(url)`, `snapshot()` returning accessibility-tree text, `evaluate(fn, arg?)` returning a parsed value, `click(selector, hint?)`, `type(selector, text, hint?)`, `press(key)`, `screenshot(filename?)`, `close()`. When the consuming project already resolves `playwright` from its own `node_modules`, the runner MAY take that cheaper direct route and expose the identical API; the pinned MCP version remains the source of the browser otherwise. The CLI provisions the browser only when at least one applicable pack is loaded and `--no-browser` was not passed; `deps.packBrowser` on the CLI handler overrides the provisioning for tests.",
+      "testable": true
+    },
+    {
+      "id": "AC-1701-8",
+      "description": "A pack MAY declare a `boot: { bootCommand, waitForUrl, waitForSelector }` object. Before running the pack pass, the CLI probes the runtime URL; when it responds with any HTTP status the boot is skipped and the running server is used unchanged. When the runtime is not answering AND `boot.bootCommand` is a non-empty string, the CLI spawns `bootCommand` from the project root (Node.js child_process, cwd=projectRoot, no shell), polls `waitForUrl` at a bounded interval until a timeout, and when the URL responds runs the packs; when `waitForSelector` is set and a browser is available, the CLI navigates the browser to `waitForUrl` and polls the accessibility snapshot for a substring match on the selector until a bounded timeout (soft-failure only, packs still run). The CLI stops any process it started in reverse order after the pack pass completes (SIGTERM then SIGKILL fallback after 3s). `--no-boot` disables the fallback and forces packs to run against whatever the runtime URL currently answers. When the runtime is unreachable AND no `bootCommand` is declared, the CLI records the note and proceeds; the pack's own runtime checks then surface the failure.",
+      "testable": true
+    }
+  ],
+  "description": "As a blueprint author shipping a runtime-observable visual surface (row order after sort, live-region announcement text, focus return after dialog close, refetch on timeframe change), I want to ship a Playwright probe pack alongside my blueprint contributions and have `rcf verify browser` load and run it as a required ship gate on any FBS whose surface realises what the pack scopes, so that runtime failures refuse ship the same way invariants and auth-smoke already do, and a pack never fires on an FBS whose surface does not exist."
+}

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

@@ -0,0 +1,40 @@
+{
+  "createdAt": "2026-09-04T20:05:20.719Z",
+  "updatedAt": "2026-09-04T20:05:44.478Z",
+  "usId": "US-1801",
+  "prdId": "PRD-001",
+  "reqId": "REQ-018",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "The application-datatable blueprint ships on the shelf and its probe pack refuses ship on a broken surface",
+  "asA": "shelf consumer applying the application-datatable v1.0.0 blueprint",
+  "iWant": "the shipped blueprint files, its Playwright probe pack, and a sample-app fixture proving both to load, apply and gate ship the way the T-0 runner extension expects",
+  "soThat": "a project consuming rcf-lite gets the datatable ACs, the pack that runs them, and a golden fixture the pack refuses on a broken surface",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1801-1",
+      "description": "The shelf carries blueprints/application-datatable/blueprint.json declaring slug application-datatable, version 1.0.0, category application, and 22 contributions (6 REQs, 9 USs, 3 TACs, 4 ADRs); the suggestedCompanions array declares logging and errorHandling with reasons from the ratified spec section 5.1.",
+      "testable": true
+    },
+    {
+      "id": "AC-1801-2",
+      "description": "rcf define blueprint add ./blueprints/application-datatable applies the 22 contributions cleanly on a fresh init project; rcf define validate reports the tree clean; both rcf audit coverage --strict and rcf audit eval coverage --strict exit 0 on the scratch project.",
+      "testable": true
+    },
+    {
+      "id": "AC-1801-3",
+      "description": "The shipped probe pack blueprints/application-datatable/probe-packs/application-datatable.pack.js loads via T-0's pack-loader against a scratch project with the blueprint applied; each of its six check ids (AC-17101-1, AC-17102-1, AC-17103-2, AC-17104-3, AC-17105-1, AC-17106-1) resolves to an AC id contributed by the blueprint per T-0 AC-1701-3.",
+      "testable": true
+    },
+    {
+      "id": "AC-1801-4",
+      "description": "The sample-app fixture at packages/rcf-lite/test/fixtures/probe-pack-application-datatable/ ships a dependency-free Node HTTP server (server.js) with a start script; when started, its shell route realises every surface the pack's six checks probe, and running the pack against the fixture returns verdict=pass on every check (severity block, aggregate pass).",
+      "testable": true
+    },
+    {
+      "id": "AC-1801-5",
+      "description": "The probe pack refuses ship on a broken fixture: with the aria-live status region wrapper removed from the shell, running the pack returns verdict=fail on AC-17103-2 at severity=block and the aggregate verdict is block.",
+      "testable": true
+    }
+  ]
+}

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

@@ -0,0 +1,40 @@
+{
+  "createdAt": "2026-09-04T21:08:30.292Z",
+  "updatedAt": "2026-09-04T21:08:30.292Z",
+  "asA": "shelf consumer applying the application-charts v1.0.0 blueprint",
+  "iWant": "the shipped blueprint files, its Playwright probe pack anchoring non-colour distinction, text-alternative table and keyboard traversal, and a sample-app fixture proving both to load, apply and gate ship the way the T-0 runner extension expects",
+  "soThat": "a project consuming rcf-lite gets the chart-accessibility ACs, the pack that runs them, and a golden fixture the pack refuses on a chart surface that drops the text-alternative table or the non-colour pattern.",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-1901-1",
+      "description": "The shelf carries blueprints/application-charts/blueprint.json declaring slug application-charts, version 1.0.0, category application, and 15 contributions (4 REQs, 6 USs, 2 TACs, 3 ADRs); the suggestedCompanions array declares logging and errorHandling with reasons from the ratified spec section 5.2; providesRoles is absent (leaf blueprint per spec).",
+      "testable": true
+    },
+    {
+      "id": "AC-1901-2",
+      "description": "rcf define blueprint add ./blueprints/application-charts applies the 15 contributions cleanly on a fresh init project; rcf define validate reports the tree clean; both rcf audit coverage --strict and rcf audit eval coverage --strict exit 0 on the scratch project.",
+      "testable": true
+    },
+    {
+      "id": "AC-1901-3",
+      "description": "The shipped probe pack blueprints/application-charts/probe-packs/application-charts.pack.mjs loads via T-0's pack-loader against a scratch project with the blueprint applied; each of its three check ids (AC-18102-1 non-colour distinction, AC-18103-1 text-alternative table, AC-18104-1 keyboard traversal with reduced motion) resolves to an AC id contributed by the blueprint per T-0 AC-1701-3; every check carries a description field per spec section 9.",
+      "testable": true
+    },
+    {
+      "id": "AC-1901-4",
+      "description": "The sample-app fixture at packages/rcf-lite/test/fixtures/probe-pack-application-charts/ ships a dependency-free Node HTTP server (server.js) with a start script; when started, its chart route renders at least one bar chart and one line chart with two series each (colour plus pattern plus direct label), a visually-hidden focus-reachable table carrying the same values, keyboard-focusable data points announcing series x y unit, and a prefers-reduced-motion media rule; running the pack against the fixture returns verdict pass on every check (severity block, aggregate pass).",
+      "testable": true
+    },
+    {
+      "id": "AC-1901-5",
+      "description": "The probe pack refuses ship on a broken fixture: with the text-alternative table removed via the ?break=table switch, running the pack returns verdict fail on AC-18103-1 at severity block and the aggregate verdict is block; with the pattern attributes removed via the ?break=pattern switch, verdict fail on AC-18102-1 at severity block; with keyboard focus removed via the ?break=keyboard switch, verdict fail on AC-18104-1 at severity block.",
+      "testable": true
+    }
+  ],
+  "usId": "US-1901",
+  "prdId": "PRD-001",
+  "reqId": "REQ-019",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "The application-charts blueprint ships on the shelf and its probe pack refuses ship on a broken chart surface"
+}