rcf-lite 0.21.0 → 0.23.0

package/rcf/requirements/req-042.json

@@ -0,0 +1,59 @@
+{
+  "createdAt": "2026-09-06T19:16:55.365Z",
+  "updatedAt": "2026-09-06T19:16:55.402Z",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "description": "The rcf-lite shelf ships the messaging-queue-cloudflare v1.0.0 blueprint (blueprints/messaging-queue-cloudflare/) with 20 to 24 contributions per the ratified infra round 5 spec section 5.3: 6 REQs (producer facade sole-reader of the Queues binding with producerReady on boot; publish/consume/ack with stable message-id and producer-supplied trace-id; retry contract; DLQ contract with default max-attempts 3 and 4-day retention per Cloudflare Queues dead-letter documentation; batch consume bounded by Cloudflare max 100 messages and max 60 seconds per Cloudflare Queues platform limits; four lifecycle events with metadata-only fields), 8 USs 29101-29108 binding runtime-observable ACs, 3 TACs (3001 producer facade, 3002 consumer registration on the Worker queue handler, 3003 event sink), 4 ADRs (3001 adapter Cloudflare Queues shipped first adapter, 3002 deliverySemantics scope global at-least-once, 3003 max-attempts default 3 floor 1 ceiling 100, 3004 batch size default 10 batch timeout default 5 seconds). The blueprint declares suggestedCompanions logging and errorHandling with spec section 5.3 reasons, providesRoles absent, capabilities [queue], requiresAppliedCapabilities absent (composes on deploy-cloudflare-workers transitively via the wrangler binding, not through the capability mechanism). Contributes ADR-3002 as scope:global on new topic deliverySemantics with at-least-once as the shipped shape so future exactly-once or at-most-once siblings conflict here by design. Ships six probe modules under blueprints/messaging-queue-cloudflare/contributions/probes/ each exporting the spec section 3.2 verdict envelope with an anchorAcId matching a contributed AC id, and matching run-shims writing per-blueprint reports at .rcf/reports/blueprints/messaging-queue-cloudflare/. Four probes local-first (accountBound false); real-account-concurrency-smoke carries accountBound true and records the accountBoundSkipped shape per spec section 3.5 without CI_HAS_CLOUDFLARE_ACCOUNT. Ships the T-3 side of the shared sample-app fixture at packages/rcf-lite/test/fixtures/infra-s3-and-queue/ with a wrangler.toml declaring a Cloudflare Worker with queue binding RCF_TEST_QUEUE and DLQ binding RCF_TEST_DLQ, an in-memory queue driver enabling Node-only probes without live Cloudflare Queues, producer and consumer modules realising the facade contract, three wired induced-failure switches (SIMULATE_CONSUMER_RETRY, SIMULATE_DLQ_OVERFLOW, SIMULATE_PII_IN_BODY), and a README extension naming the wrangler dev boot line and the elicited parameters. Extends packages/rcf-lite/docs/blueprint-authoring.md section 6a capability-declaration table with one row for queue naming the reserved messaging-queue-postgres sibling per Baz decision 7 and spec section 5.6. Appends one row for messaging-queue-cloudflare at US band 29101-29899 / ADR-TAC suffix block 30xx to the shelf-wide id-band registry table under docs/topics.md on every shipped blueprint. Minted with dex reserved-block chain ids via --id per HQ mid-flight ruling on repo-chain id blocks per train. Miniflare Queues sub-page is NOT cited (spec confirmed 404); the Cloudflare Queues local-development page is the citation for the wrangler dev seam.",
+  "reqId": "REQ-042",
+  "prdId": "PRD-001",
+  "title": "Messaging-queue-cloudflare v1.0.0 blueprint on the shelf",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "webUi",
+      "httpApi",
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-09-06T19:16:55.400Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "httpApi",
+        "match": "post"
+      },
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "page"
+      },
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "page"
+      }
+    ]
+  }
+}

package/rcf/requirements/req-043.json

@@ -0,0 +1,39 @@
+{
+  "createdAt": "2026-09-06T20:28:34.000Z",
+  "updatedAt": "2026-09-07T10:18:08.299Z",
+  "category": "functional",
+  "domain": "application",
+  "priority": "must",
+  "description": "The rcf-lite shelf ships the jobs-background v1.0.0 blueprint (blueprints/jobs-background/) with 22 contributions per the ratified infra round 5 spec section 5.4: 6 REQs (requires an applied queue capability via the T-5 mechanism and refuses apply on a bare project with exit 3 plus stable message id jobs-background-no-queue; job-definition contract carrying name, handler, input schema opaque per project, retry policy, timeout; scheduler contract carrying POSIX cron string and one-shot delayed; retry contract inheriting the applied queue's max-attempts ceiling; job-run event log at four moments jobScheduled jobStarted jobCompleted jobFailed with metadata-only fields; operator-facing surface elicited between cli httpEndpoint none), 9 USs 30101-30109 binding runtime-observable ACs (one US per REQ plus three cross-cutting cases apply-time refusal on bare scheduled fire on cron and retry-then-DLQ), 3 TACs (3101 job-definition module 3102 scheduler 3103 run log), 4 ADRs (3101 scope:global on new topic backgroundJobModel retry-and-schedule as the shipped shape; 3102 scheduler mode elicited between inProcess workerCron and external with a reserved v1.1.0 workflows slot per spec section 5.7 and round-6 proposal decision b; 3103 requires capabilities:[queue] with allowSkipFlag allow-no-queue-yet and refusalMessageId jobs-background-no-queue; 3104 default handler timeout 60 seconds floor 1 second ceiling bounded by the applied queue's consumer wall-clock which for Cloudflare Queues is 15 minutes per limits doc). The blueprint declares suggestedCompanions logging and errorHandling with spec section 5.4 reasons, providesRoles absent, capabilities [backgroundJobs], requiresAppliedCapabilities {capabilities:[queue],allowSkipFlag:allow-no-queue-yet,refusalMessageId:jobs-background-no-queue} per Baz decision 5 verbatim. Contributes ADR-3101 as scope:global on new topic backgroundJobModel with retry-and-schedule as the shipped shape so future stateful-workflow siblings (Temporal-shape Airflow-shape) conflict here by design; the round-6 Workflows minor bump inside jobs-background itself does NOT mint a sibling per spec section 5.6 (it lives inside the same blueprint as an elicited scheduler mode value at ADR-3102). Ships five probe modules under blueprints/jobs-background/contributions/probes/ each exporting the spec section 3.2 verdict envelope with an anchorAcId matching a contributed AC id and matching run-shims writing per-blueprint reports at .rcf/reports/blueprints/jobs-background/: apply-time-refusal.mjs (bare project rcf define blueprint add refuses exit 3 with tag jobs-background-no-queue on stderr and names messaging-queue-cloudflare explicitly per Q3 default asserting both exit code and message id), apply-time-override.mjs (same bare project with --allow-no-queue-yet exits 0 and sidecar rcf/blueprints/jobs-background.applied.json records a note naming the missing capability and the override flag; the spec section 5.4 prose reference to manifest.blueprints[jobs-background].source.notes is superseded by the shipped T-5 mechanism which writes the note on the sidecar because the applied-blueprint-record schema is closed), fake-clock-cron.mjs (with messaging-queue-cloudflare and jobs-background both applied on the shared sample-app fixture drives the in-memory queue seam from T-3 through one fake-clock cron minute and asserts jobStarted fires within the elicited fire-tolerance window plus jobCompleted within the elicited timeout), retry-and-fail.mjs (schedules a job with a handler throwing under SIMULATE_HANDLER_THROW drives through maxAttempts re-deliveries and asserts jobStarted fires 3 times with matching job-id and incrementing attempt counter plus jobFailed fires with terminal code), event-secrecy.mjs (schedules a job with PII fixture input drives to completion and asserts every event record carries only {jobId,jobName,attempts,duration,timestamp} whitelist and NO input fields NO output fields NO user id NO SSN NO email). All five probes accountBound false. Extends the shared sample-app fixture at packages/rcf-lite/test/fixtures/infra-s3-and-queue/ (T-2/T-3 have already landed the fixture directory) with a jobs/ directory carrying two toy job-definition modules (send-welcome-email.mjs with retry policy {maxAttempts:3,backoff:exponential} timeout 60 seconds and refresh-cache.mjs with retry policy {maxAttempts:5,backoff:constant} timeout 10 seconds cron every-minute), src/jobs-runtime.mjs realising the runtime that reads applied queue capability from the sidecar registers job handlers with the queue consumer dispatches per message fires the four lifecycle events per REQ-005 and respects the elicited timeout and retry policy per job definition, src/scheduler.mjs realising the inProcess scheduler with a fake-clock seam the fake-clock-cron probe drives, package.json start:jobs script, and README extension naming the two toy jobs the jobs/ directory convention the fake-clock switch the elicited parameters the induced-failure switches SIMULATE_HANDLER_THROW and SIMULATE_PII_IN_JOB_INPUT and the gate-reviewer two-line boot. Extends packages/rcf-lite/src/cli/blueprint.js OPTION_SPEC with allow-no-queue-yet boolean flag piped into allowNoAuthYet, and packages/rcf-lite/src/blueprint/apply.js buildOverrideNote family derivation to detect queue from the flag name (so sidecar notes read no queue yet: applied under --allow-no-queue-yet). Extends packages/rcf-lite/test/blueprint/capabilities-apply.test.js with four cases covering jobs-background bare refusal (tag and messaging-queue-cloudflare name assertions), --allow-no-queue-yet override (sidecar notes queue-family assertion), happy path with messaging-queue-cloudflare applied (appliedCapabilities includes queue), and legacy allow-no-auth-yet also unblocks the override (backward-compatible OR piping). Extends packages/rcf-lite/docs/blueprint-authoring.md section 6a capability-declaration table with one row for backgroundJobs naming the reserved sibling posture per spec section 5.6. Appends one row for jobs-background at US band 30101-30899 / ADR-TAC suffix block 31xx to the shelf-wide id-band registry table under docs/topics.md on every shipped blueprint. Minted with dex reserved-block chain ids via --id per HQ mid-flight ruling on repo-chain id blocks per train (REQ-043 / US-4301 / TS-076 / FBS-064 / CN-214..217 (originally TS-073 / FBS-063 / CN-209..212, re-minted at next-free after HQ round-6 T-0 PR #164 landed on origin/main 321371e and consumed the original block; REQ-043 and US-4301 did not collide and are unchanged) continuing the block after T-3 landed at 042/4201/072/062/206..208). Wrangler is not on this build host so probes run against the in-memory queue-driver seam T-3 landed on the fixture (SDR-3-a coordinator ruling accepted the in-memory realisation of the Cloudflare Queues binding shape); the live wrangler-dev cron-trigger path is enumerated as a per-AC mechanism-reach gap in the README per round-3 checklist 6.g form.",
+  "reqId": "REQ-043",
+  "prdId": "PRD-001",
+  "title": "Jobs-background v1.0.0 blueprint on the shelf",
+  "version": "0.1.0",
+  "status": "draft",
+  "shapeClassification": {
+    "shapes": [
+      "webUi",
+      "httpApi",
+      "persistence"
+    ],
+    "reason": "keyword-scan",
+    "classifiedAt": "2026-09-06T20:28:34.000Z",
+    "signals": [
+      {
+        "source": "description",
+        "shape": "webUi",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "persistence",
+        "match": "table"
+      },
+      {
+        "source": "description",
+        "shape": "httpApi",
+        "match": "endpoint"
+      }
+    ]
+  }
+}

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-09-06T15:39:17.193Z",
+  "updatedAt": "2026-09-06T15:39:17.193Z",
+  "testCases": [
+    {
+      "id": "TC-053-blueprint-json-shape",
+      "acId": "AC-2401-1",
+      "description": "blueprint.json declares slug, version 1.0.0, category application, 19 contributions in 5/8/3/3 groups; providesRoles absent; requiresAppliedCapabilities absent; suggestedCompanions logging and errorHandling",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-empty-error-states-anatomy.test.js::blueprint.json declares 19 contributions with no capabilities and no requiresAppliedCapabilities (TC-053-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-053-applies-clean",
+      "acId": "AC-2401-2",
+      "description": "Fresh init project applies application-empty-error-states cleanly and reports the tree clean",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-empty-error-states-anatomy.test.js::applies cleanly on a fresh init project and adds 19 documents to the tree (TC-053-applies-clean)"
+    },
+    {
+      "id": "TC-053-pack-checks-cross-check",
+      "acId": "AC-2401-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-empty-error-states-anatomy.test.js::every pack check id matches a contributed AC id and appliesTo binds tacIds AND route (TC-053-pack-checks-cross-check)"
+    },
+    {
+      "id": "TC-053-fixture-serves-states",
+      "acId": "AC-2401-4",
+      "description": "Sample-app fixture serves every one of the eight states honestly on its default branch and via ?state= switch",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-empty-error-states-anatomy.test.js::sample-app fixture serves every one of the eight states on the default branch (TC-053-fixture-serves-states)"
+    },
+    {
+      "id": "TC-053-negative-runs",
+      "acId": "AC-2401-5",
+      "description": "Break switches surface the four defects on the DOM for the corresponding pack checks",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-empty-error-states-anatomy.test.js::sample-app fixture break switches surface the four defects on the DOM (TC-053-negative-runs)"
+    },
+    {
+      "id": "TC-053-state-enumeration-parity",
+      "acId": "AC-2401-6",
+      "description": "Eight state slugs appear identically across README, guide, pack checks[] and docs/topics.md registry",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-empty-error-states-anatomy.test.js::eight state slugs appear identically across README guide pack and docs (TC-053-state-enumeration-parity)"
+    },
+    {
+      "id": "TC-053-readme-gaps-and-changelog",
+      "acId": "AC-2401-7",
+      "description": "README lists mechanism-reach gaps individually; CHANGELOG carries one 1.0.0 entry; docs/topics.md carries the T-1 shelf registry row",
+      "status": "pending",
+      "testPointer": "test/blueprint/application-empty-error-states-anatomy.test.js::README lists mechanism-reach gaps and CHANGELOG carries 1.0.0 and topics carries the T-1 row (TC-053-readme-gaps-and-changelog)"
+    }
+  ],
+  "status": "draft",
+  "purpose": "Cover AC-2401-1 through AC-2401-7 via unit tests over the shipped application-empty-error-states 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 all eight state branches, the negative-run behaviour on the ?break=stack-trace, ?break=leak-id, ?break=no-recovery and ?break=no-live-region switches, the state-slug 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-2401-1",
+    "AC-2401-2",
+    "AC-2401-3",
+    "AC-2401-4",
+    "AC-2401-5",
+    "AC-2401-6",
+    "AC-2401-7"
+  ],
+  "id": "TS-053",
+  "usId": "US-2401",
+  "title": "application-empty-error-states v1.0.0 shelf shape, probe pack cross-check and sample-app fixture"
+}

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"
+}