rcf-lite 0.22.0 → 0.23.0

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-072.json

@@ -0,0 +1,62 @@
+{
+  "createdAt": "2026-09-06T19:17:48.415Z",
+  "updatedAt": "2026-09-06T19:18:05.472Z",
+  "purpose": "Cover AC-4201-1..6 via unit tests over the shipped messaging-queue-cloudflare blueprint shape (contribution count, capabilities, suggestedCompanions, ADR standardsTraceClause), applies-clean behaviour, REQ-004 dead_letter_queue grep and retention wording, 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 queue with reserved sibling note, shelf-wide docs/topics.md row for messaging-queue-cloudflare at 29101-29899 / 30xx).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-4201-1",
+    "AC-4201-2",
+    "AC-4201-3",
+    "AC-4201-4",
+    "AC-4201-5",
+    "AC-4201-6"
+  ],
+  "id": "TS-072",
+  "usId": "US-4201",
+  "title": "messaging-queue-cloudflare v1.0.0 shelf shape, apply-clean, DLQ REQ description grep, six-probe module contract, induced-failure switches and shelf-doc consistency",
+  "testCases": [
+    {
+      "id": "TC-072-blueprint-json-shape",
+      "acId": "AC-4201-1",
+      "description": "Cover AC-4201-1 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/messaging-queue-cloudflare-anatomy.test.js::blueprint.json declares 21 contributions with capabilities queue, suggestedCompanions logging and errorHandling, and standardsTraceClause on every ADR entry (TC-072-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-072-applies-clean",
+      "acId": "AC-4201-2",
+      "description": "Cover AC-4201-2 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/messaging-queue-cloudflare-anatomy.test.js::apply messaging-queue-cloudflare lands 21 contributions on a scratch project (TC-072-applies-clean)"
+    },
+    {
+      "id": "TC-072-dlq-req-grep",
+      "acId": "AC-4201-3",
+      "description": "Cover AC-4201-3 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/messaging-queue-cloudflare-anatomy.test.js::REQ-004 description names dead_letter_queue and the 4-day DLQ retention with the Cloudflare DLQ doc URL (TC-072-dlq-req-grep)"
+    },
+    {
+      "id": "TC-072-probe-anchor-ids-cross-check",
+      "acId": "AC-4201-4",
+      "description": "Cover AC-4201-4 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/messaging-queue-cloudflare-anatomy.test.js::every probe module exports the section 3.2 verdict envelope with an anchorAcId matching a contributed AC id (TC-072-probe-anchor-ids-cross-check)"
+    },
+    {
+      "id": "TC-072-fixture-and-switches",
+      "acId": "AC-4201-5",
+      "description": "Cover AC-4201-5 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/messaging-queue-cloudflare-anatomy.test.js::sample-app fixture ships wrangler.toml, src/producer.mjs, src/consumer.mjs, src/dlq-inspector.mjs, and its README documents wrangler dev and the three wired induced-failure switches (TC-072-fixture-and-switches)"
+    },
+    {
+      "id": "TC-072-shelf-doc-consistency",
+      "acId": "AC-4201-6",
+      "description": "Cover AC-4201-6 via anatomy test",
+      "status": "pending",
+      "testPointer": "test/blueprint/messaging-queue-cloudflare-anatomy.test.js::section 6a table gains a queue row with reserved messaging-queue-postgres sibling and every shipped blueprint docs/topics.md gains a messaging-queue-cloudflare row at 29101-29899 / 30xx (TC-072-shelf-doc-consistency)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-09-07T09:11:24.816Z",
+  "updatedAt": "2026-09-07T09:12:00.080Z",
+  "purpose": "Cover AC-2901-1..3 via unit tests over the shipped deploy-cloudflare-workers v1.2.0 blueprint shape (12 REQs 15 USs 6 TACs 6 ADRs, no capabilities, suggestedCompanions logging and errorHandling unchanged, standardsTraceClause on ADR-1306 contribution entry), the assets-manifest-scan probe module contract and passing run against the cf-platform fixture, and the repo chain-slice counts and validate-clean.",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2901-1",
+    "AC-2901-2",
+    "AC-2901-3"
+  ],
+  "id": "TS-073",
+  "usId": "US-2901",
+  "title": "T-0 deploy-cloudflare-workers v1.2.0 shelf shape, apply-clean, chain-slice cross-check",
+  "testCases": [
+    {
+      "id": "TC-073-blueprint-json-shape",
+      "acId": "AC-2901-1",
+      "description": "Cover AC-2901-1 via anatomy test: blueprint.json declares slug deploy-cloudflare-workers, version 1.2.0, category deploy; contributions split 12 req, 15 us, 6 tac, 6 adr; suggestedCompanions unchanged; standardsTraceClause non-null on every ADR contribution entry including ADR-1306",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::blueprint.json declares 41 contributions with v1.2.0, delta shape and unchanged v1.1.0 companions (TC-073-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-073-probe-module-and-scan-pass",
+      "acId": "AC-2901-2",
+      "description": "Cover AC-2901-2 via anatomy test: assets-manifest-scan.mjs exports the section 3.2 verdict envelope with anchorAcId AC-12113-1 and accountBound false; the shim run-assets-manifest-scan.mjs on the cf-platform fixture exits 0 and the report carries aggregateVerdict pass with directory ./dist and no pages_build_output_dir field",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::assets-manifest-scan probe module contract and cf-platform fixture scan-pass (TC-073-probe-module-and-scan-pass)"
+    },
+    {
+      "id": "TC-073-chain-slice-cross-check",
+      "acId": "AC-2901-3",
+      "description": "Cover AC-2901-3 via anatomy test: the repo chain adds REQ-029 REQ-030 US-2901 US-2902 US-3001 TS-073 TS-074 TS-075 FBS-063 CN-209, every US carries at least one AC, every AC has a covering TC on a paired TS with a resolvable test-pointer, and rcf define validate reports the tree clean",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::T-0 chain slice adds two REQs three USs three TSs one FBS and one CN under the HQ block (TC-073-chain-slice-cross-check)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,30 @@
+{
+  "createdAt": "2026-09-07T09:11:24.993Z",
+  "updatedAt": "2026-09-07T09:12:00.427Z",
+  "purpose": "Cover AC-2902-1..2 via unit tests over the top-level elicits[] shape (id, kind, default, loader shape gate) and the cf-platform fixture files (wrangler.toml, dist/, src/, package.json, run-assets-manifest-scan.mjs, README naming the switches).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-2902-1",
+    "AC-2902-2"
+  ],
+  "id": "TS-074",
+  "usId": "US-2902",
+  "title": "T-0 deploy-cloudflare-workers v1.2.0 elicits: assets-directory and run-worker-first on blueprint.json elicits[] and cf-platform fixture",
+  "testCases": [
+    {
+      "id": "TC-074-elicits-shape",
+      "acId": "AC-2902-1",
+      "description": "Cover AC-2902-1 via anatomy test: blueprint.json elicits[] declares exactly two new entries assets-directory and run-worker-first with the correct id, kind and default; neither carries providesCapability; the loader loads blueprint.json without a validation error",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::elicits[] declares assets-directory string default empty and run-worker-first boolean default false and loader accepts blueprint.json (TC-074-elicits-shape)"
+    },
+    {
+      "id": "TC-074-cf-platform-fixture-files",
+      "acId": "AC-2902-2",
+      "description": "Cover AC-2902-2 via anatomy test: the cf-platform fixture ships wrangler.toml with the [assets] block, dist/index.html, src/index.mjs, package.json with wrangler dev script and wrangler as a devDependency, run-assets-manifest-scan.mjs shim and README naming the wrangler dev boot line, the elicit answers and the two induced-failure switches",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::cf-platform fixture ships wrangler.toml dist index.html src index.mjs package.json shim and README with SIMULATE_MIXED_SHAPE and SIMULATE_EMPTY_ASSETS switches (TC-074-cf-platform-fixture-files)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,38 @@
+{
+  "createdAt": "2026-09-07T09:11:25.167Z",
+  "updatedAt": "2026-09-07T09:12:00.950Z",
+  "purpose": "Cover AC-3001-1..3 via unit tests over the ADR-1306 body validity and standardsTraceClause on the contribution entry, the guide's new SPA-on-Workers section with the two Cloudflare URLs (fetched 200 at gate time), and the probe module driven on the three fixture states (canonical, SIMULATE_MIXED_SHAPE fails naming pages_build_output_dir, SIMULATE_EMPTY_ASSETS passes with the empty-directory record).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-3001-1",
+    "AC-3001-2",
+    "AC-3001-3"
+  ],
+  "id": "TS-075",
+  "usId": "US-3001",
+  "title": "T-0 deploy-cloudflare-workers v1.2.0 ADR-1306, guide section, and probed spaFallbackShape with induced-failure switches",
+  "testCases": [
+    {
+      "id": "TC-075-adr-1306-body-and-clause",
+      "acId": "AC-3001-1",
+      "description": "Cover AC-3001-1 via anatomy test: ADR-1306 body validates against rcf-schemas 0.6.1 (required fields present, no standardsTraceClause on body), the body carries the verbatim Cloudflare Pages landing-page quote in context or decision, and the blueprint.json contribution entry carries standardsTraceClause Cloudflare Pages landing-page recommendation (2026-09-06) with recommendedDefault true and elicited false",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::ADR-1306 body validates against 0.6.1 with verbatim Cloudflare quote and standardsTraceClause on the contribution entry (TC-075-adr-1306-body-and-clause)"
+    },
+    {
+      "id": "TC-075-guide-section-and-urls",
+      "acId": "AC-3001-2",
+      "description": "Cover AC-3001-2 via anatomy test: the guide file carries the new Workers-with-static-assets: the SPA-on-Workers shape section with both the migrate-from-Pages guide URL and the static-assets docs URL. The urls-fetched log (fetched at ship time) records both URLs at HTTP 200.",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::guide section Workers-with-static-assets adds the two Cloudflare URLs and the elicit signatures and the wrangler.toml snippet (TC-075-guide-section-and-urls)"
+    },
+    {
+      "id": "TC-075-probed-spa-fallback-shape",
+      "acId": "AC-3001-3",
+      "description": "Cover AC-3001-3 via anatomy test: the assets-manifest-scan probe run against the cf-platform fixture returns verdict pass on the canonical state; SIMULATE_MIXED_SHAPE=true returns verdict fail with a detail naming pages_build_output_dir; SIMULATE_EMPTY_ASSETS=true returns verdict pass with the empty-directory record for the bare-Worker shape",
+      "status": "pending",
+      "testPointer": "test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js::assets-manifest-scan drives three fixture states and produces the expected pass fail pass verdicts (TC-075-probed-spa-fallback-shape)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,70 @@
+{
+  "createdAt": "2026-09-07T10:15:20.121Z",
+  "updatedAt": "2026-09-07T10:15:59.868Z",
+  "purpose": "Cover AC-4301-1..7 via unit tests over the shipped jobs-background blueprint shape (contribution count, capabilities, suggestedCompanions, requiresAppliedCapabilities gate shape, ADR standardsTraceClause), the four capabilities-apply.test.js cases (bare-project refusal with tag and messaging-queue-cloudflare name, --allow-no-queue-yet override with queue-family sidecar note, happy path with messaging-queue-cloudflare applied producing appliedCapabilities including queue, and backward-compatible --allow-no-auth-yet also unblocks the override), the five-probe module contract with anchorAcId cross-check, the two induced-failure switch documentation on the fixture README, and shelf-doc consistency (section 6a table row for backgroundJobs, shelf-wide docs/topics.md row for jobs-background at 30101-30899 / 31xx).",
+  "testLevel": "unit",
+  "acIds": [
+    "AC-4301-1",
+    "AC-4301-2",
+    "AC-4301-3",
+    "AC-4301-4",
+    "AC-4301-5",
+    "AC-4301-6",
+    "AC-4301-7"
+  ],
+  "id": "TS-076",
+  "usId": "US-4301",
+  "title": "Jobs-background v1.0.0 shelf shape, apply-time refusal and override paths (via capabilities-apply tests), five-probe module contract, induced-failure switches, and shelf-doc consistency",
+  "testCases": [
+    {
+      "id": "TC-076-blueprint-json-shape",
+      "acId": "AC-4301-1",
+      "description": "blueprint.json declares 22 contributions with capabilities backgroundJobs, requiresAppliedCapabilities on queue with allowSkipFlag allow-no-queue-yet and refusalMessageId jobs-background-no-queue, and standardsTraceClause on every ADR entry",
+      "status": "pending",
+      "testPointer": "test/blueprint/jobs-background-anatomy.test.js::blueprint.json declares 22 contributions with capabilities backgroundJobs, requiresAppliedCapabilities on queue with allowSkipFlag allow-no-queue-yet and refusalMessageId jobs-background-no-queue, and standardsTraceClause on every ADR entry (TC-076-blueprint-json-shape)"
+    },
+    {
+      "id": "TC-076-bare-refusal",
+      "acId": "AC-4301-2",
+      "description": "jobs-background apply refuses on a bare project with the jobs-background-no-queue tag, names messaging-queue-cloudflare and the --allow-no-queue-yet override",
+      "status": "pending",
+      "testPointer": "test/blueprint/capabilities-apply.test.js::jobs-background apply refuses on a bare project with the jobs-background-no-queue tag, names messaging-queue-cloudflare and the --allow-no-queue-yet override (TC-051-jobs-background-refuse)"
+    },
+    {
+      "id": "TC-076-override-sidecar",
+      "acId": "AC-4301-3",
+      "description": "jobs-background --allow-no-queue-yet override writes sidecar with queue-family notes",
+      "status": "pending",
+      "testPointer": "test/blueprint/capabilities-apply.test.js::jobs-background --allow-no-queue-yet override writes sidecar with queue-family notes (TC-051-jobs-background-allow-skip)"
+    },
+    {
+      "id": "TC-076-happy-path-caps",
+      "acId": "AC-4301-4",
+      "description": "jobs-background apply passes on a project with messaging-queue-cloudflare (queue) applied",
+      "status": "pending",
+      "testPointer": "test/blueprint/capabilities-apply.test.js::jobs-background apply passes on a project with messaging-queue-cloudflare (queue) applied (TC-051-jobs-background-cap-satisfied)"
+    },
+    {
+      "id": "TC-076-probe-anchor-ids-cross-check",
+      "acId": "AC-4301-5",
+      "description": "every probe module exports the section 3.2 verdict envelope with an anchorAcId matching a contributed AC id",
+      "status": "pending",
+      "testPointer": "test/blueprint/jobs-background-anatomy.test.js::every probe module exports the section 3.2 verdict envelope with an anchorAcId matching a contributed AC id (TC-076-probe-anchor-ids-cross-check)"
+    },
+    {
+      "id": "TC-076-fixture-and-switches",
+      "acId": "AC-4301-6",
+      "description": "sample-app fixture ships jobs/ toy job-definitions plus src/jobs-runtime.mjs and src/scheduler.mjs and its README documents the two wired induced-failure switches SIMULATE_HANDLER_THROW and SIMULATE_PII_IN_JOB_INPUT",
+      "status": "pending",
+      "testPointer": "test/blueprint/jobs-background-anatomy.test.js::sample-app fixture ships jobs/ toy job-definitions plus src/jobs-runtime.mjs and src/scheduler.mjs and its README documents the two wired induced-failure switches SIMULATE_HANDLER_THROW and SIMULATE_PII_IN_JOB_INPUT (TC-076-fixture-and-switches)"
+    },
+    {
+      "id": "TC-076-shelf-doc-consistency",
+      "acId": "AC-4301-7",
+      "description": "section 6a table gains a backgroundJobs row naming jobs-background and reserved sibling posture; every shipped blueprint docs/topics.md gains a jobs-background row at 30101-30899 / 31xx",
+      "status": "pending",
+      "testPointer": "test/blueprint/jobs-background-anatomy.test.js::section 6a table gains a backgroundJobs row naming jobs-background and reserved sibling posture; every shipped blueprint docs/topics.md gains a jobs-background row at 30101-30899 / 31xx (TC-076-shelf-doc-consistency)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,45 @@
+{
+  "createdAt": "2026-09-07T09:11:05.053Z",
+  "updatedAt": "2026-09-07T09:11:05.053Z",
+  "asA": "shelf consumer applying the deploy-cloudflare-workers v1.2.0 blueprint on a fresh SPA-on-Workers project",
+  "iWant": "the shipped v1.2.0 blueprint files (blueprint.json version 1.2.0 with the seven-contribution delta on top of the v1.1.0 shipped set; two new REQ contributions deploy-cloudflare-workers-REQ-013 and REQ-014; three new US contributions in the existing 12xx band deploy-cloudflare-workers-US-12113 SPA-on-Workers deploy, US-12114 assets-directory elicitation, US-12115 migrate-from-Pages guidance; one new ADR contribution ADR-1306-deploy-cloudflare-workers-spa-shape with the verbatim Cloudflare Pages landing-page quote and standardsTraceClause Cloudflare Pages landing-page recommendation 2026-09-06; one new probe module assets-manifest-scan.mjs anchored to AC-2901-2 assetsBlockEmitted; two new elicits assets-directory and run-worker-first) proven against the cf-platform shared sample-app fixture",
+  "soThat": "a rcf-lite project applying deploy-cloudflare-workers v1.2.0 gets a Workers-with-static-assets shape ratified over Pages for greenfield SPA-on-Workers projects (per the Cloudflare Pages landing-page recommendation, verbatim quoted on ADR-1306), an elicited [assets] directory in wrangler.toml, a probed assertion of the emitted assets block, an unchanged v1.1.0 contribution set (12 REQs, 12 USs, 6 TACs, 5 ADRs, deploymentTarget global topic, suggestedCompanions logging and errorHandling), and a shared sample-app fixture that T-1 through T-3 and T-5 extend later",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-2901-1",
+      "description": "The shelf carries blueprints/deploy-cloudflare-workers/blueprint.json declaring slug deploy-cloudflare-workers, version 1.2.0, category deploy; the contributions array holds 41 entries splitting 14 req + 15 us + 6 tac + 6 adr (the probe is NOT a contribution kind under the loader's CONTRIBUTABLE_KINDS gate; assets-manifest-scan.mjs ships under contributions/probes/ as a source file only, cross-referenced from the shipped README and the applied fixture shim); the delta over v1.1.0 is six contribution-kind entries plus the probe module: 2 REQs REQ-013 and REQ-014, 3 USs US-12113 US-12114 US-12115, 1 ADR ADR-1306 with recommendedDefault true and standardsTraceClause Cloudflare Pages landing-page recommendation (2026-09-06) on the contribution entry, 1 probe contribution assets-manifest-scan with anchorAcId AC-12113-1 and accountBound false; providesRoles absent, capabilities absent, requiresAppliedCapabilities absent, suggestedCompanions unchanged with logging and errorHandling; the top-level elicits[] gains the two new entries assets-directory and run-worker-first; every ADR contribution entry carries a non-null standardsTraceClause per section 8a.2.",
+      "given": "the shelf tree after this blueprint delta lands",
+      "when": "jq queries against blueprints/deploy-cloudflare-workers/blueprint.json",
+      "then": "jq .slug returns deploy-cloudflare-workers; jq .version returns 1.2.0; jq .contributions returns an array whose kinds split 14 req, 15 us, 6 tac, 6 adr (total 41 entries); the probe module lives under blueprints/deploy-cloudflare-workers/contributions/probes/assets-manifest-scan.mjs and is NOT listed as a contribution; jq .capabilities returns null; jq .suggestedCompanions maps to logging and errorHandling; jq .elicits returns an array containing assets-directory and run-worker-first; jq .contributions[] where kind is adr yields standardsTraceClause non-null for every entry",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-2901-2",
+      "description": "The canonical AC assetsBlockEmitted (from spec section 5.0 example ACs) is realised as blueprint contribution AC-12113-1 on US-12113 with a runtime-observable then clause. The shipped probe blueprints/deploy-cloudflare-workers/contributions/probes/assets-manifest-scan.mjs exports a Node module whose default export is a scan verb returning the section 3.2 verdict envelope {verdict, detail, anchorAcId, aggregateVerdict} with anchorAcId AC-12113-1 and accountBound false; the module parses the applied fixture wrangler.toml, asserts the [assets] block directory matches the elicited assets-directory answer, and asserts the absence of any pages_build_output_dir field.",
+      "given": "the cf-platform sample-app fixture at packages/rcf-lite/test/fixtures/cf-platform/ with wrangler.toml carrying [assets] directory = ./dist and no pages_build_output_dir field",
+      "when": "the shim run-assets-manifest-scan.mjs drives the probe module against the fixture wrangler.toml",
+      "then": "the process exits 0 and the written report at .rcf/reports/blueprints/deploy-cloudflare-workers/assets-manifest-scan.json carries aggregateVerdict pass with a detail record naming directory ./dist and no pages_build_output_dir field on the parsed wrangler.toml",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-2901-3",
+      "description": "The rcf-lite repo chain is extended with the T-0 delta and validates clean; the chain adds two REQs REQ-029 and REQ-030 under PRD-001, three USs US-2901 US-2902 US-3001, three test suites TS-073 TS-074 TS-075, one FBS FBS-063, and one CN CN-209 anchoring the assets-manifest-scan.mjs probe module; every US carries at least one AC; every AC is covered by a TC on the paired TS with a resolvable test-pointer to test/blueprint/deploy-cloudflare-workers-v-1-2-0-anatomy.test.js. Repo counts bump: requirements 31 to 33, userStories 60 to 63, fbs 50 to 51, testSuite 60 to 63, codeNode 195 to 196.",
+      "given": "the extended repo chain on the T-0 branch after all define create commands have run",
+      "when": "node bin/rcf.js define validate runs from packages/rcf-lite",
+      "then": "the CLI reports rcf define validate: tree is clean and both node bin/rcf.js audit coverage --strict and node bin/rcf.js audit eval coverage --strict exit 0",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tags": [
+    "blueprint:deploy-cloudflare-workers"
+  ],
+  "usId": "US-2901",
+  "prdId": "PRD-001",
+  "reqId": "REQ-029",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-0 delta on deploy-cloudflare-workers v1.2.0 shelf: seven-contribution additive minor bump plus cf-platform fixture with the assets-manifest-scan probe passing"
+}

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

@@ -0,0 +1,36 @@
+{
+  "createdAt": "2026-09-07T09:11:05.250Z",
+  "updatedAt": "2026-09-07T09:11:05.250Z",
+  "asA": "shelf consumer applying the deploy-cloudflare-workers v1.2.0 blueprint who wants the two new elicits to appear in the operator elicit prompt with sane defaults",
+  "iWant": "the blueprint.json top-level elicits[] to declare both new entries (assets-directory kind string default empty; run-worker-first kind boolean default false), the CLI to accept --answer assets-directory=<path> and --answer run-worker-first=<bool> at blueprint add, and the generated wrangler.toml under the applied project to reflect the answered values",
+  "soThat": "a project answering assets-directory=./dist gets [assets] directory = \"./dist\" emitted in its wrangler.toml, a project not answering assets-directory keeps the bare-Worker shape without any [assets] block, and the two elicits do not affect any shipped v1.1.0 contribution",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-2902-1",
+      "description": "The blueprint.json elicits[] block gains exactly two new entries: assets-directory with id assets-directory, kind string, default empty string, prompt describing the applied static-assets root; run-worker-first with id run-worker-first, kind boolean, default false, prompt describing the SPA fallback discipline that a truthy answer runs the Worker before asset lookup. The two elicits pass the loader's validateElicits shape gate on src/blueprint/loader.js (id kebab-slug, kind one of enum|string|boolean, default matches kind). Neither elicit carries providesCapability (both are shape choices not custom-auth discovery). The spec's intended when-predicate {elicitedNonEmpty: [assets-directory]} on run-worker-first is NOT shipped this round because the loader's supported when block only accepts requiresCapability arrays; the guide names the shape trade and CONCERNS on the PR names the smallest loader extension to close the gap.",
+      "given": "the shipped blueprint.json at blueprints/deploy-cloudflare-workers/blueprint.json",
+      "when": "jq .elicits returns the top-level array and the loader loads blueprint.json without a validation error",
+      "then": "the array contains exactly two entries whose ids are assets-directory and run-worker-first, with the shapes above; jq validation and the loader both accept the shape",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-2902-2",
+      "description": "The cf-platform fixture at packages/rcf-lite/test/fixtures/cf-platform/ ships a wrangler.toml with [assets] directory = \"./dist\" and run_worker_first = true baked into the [assets] block. The fixture ships dist/index.html so the assets directory exists on disk. The fixture ships src/index.mjs as the minimal Worker entry, a package.json declaring wrangler as a devDependency and start = wrangler dev, a run-assets-manifest-scan.mjs shim requiring the probe module from blueprints/deploy-cloudflare-workers/contributions/probes/assets-manifest-scan.mjs, and a README naming the wrangler dev boot line, the two elicit answers baked into wrangler.toml, and the two induced-failure switches SIMULATE_MIXED_SHAPE (inserts a pages_build_output_dir field so the probe surfaces the mixed-shape refusal) and SIMULATE_EMPTY_ASSETS (removes the [assets] block so the probe records the bare-Worker shape and passes with an empty-directory record).",
+      "given": "the cf-platform fixture tree after this T-0 slice lands",
+      "when": "ls -R the fixture directory",
+      "then": "the fixture ships wrangler.toml with the [assets] block, dist/index.html, src/index.mjs, package.json with wrangler dev, run-assets-manifest-scan.mjs and README.md with the switches and boot line documented",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tags": [
+    "blueprint:deploy-cloudflare-workers"
+  ],
+  "usId": "US-2902",
+  "prdId": "PRD-001",
+  "reqId": "REQ-029",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-0 assets-directory and run-worker-first elicits on blueprint.json top-level elicits[] and baked into the cf-platform fixture wrangler.toml"
+}

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

@@ -0,0 +1,45 @@
+{
+  "createdAt": "2026-09-07T09:11:05.463Z",
+  "updatedAt": "2026-09-07T09:11:05.463Z",
+  "asA": "shelf consumer applying the deploy-cloudflare-workers v1.2.0 blueprint on a project migrating from Cloudflare Pages",
+  "iWant": "an ADR blessing the Workers-with-static-assets shape as the ratified SPA-on-Workers deploy shape over Pages (ADR-1306-deploy-cloudflare-workers-spa-shape) carrying the verbatim Cloudflare Pages landing-page recommendation, a guide section titled Workers-with-static-assets: the SPA-on-Workers shape that links the Cloudflare migrate-from-Pages guide, and the SPA fallback discipline elicited via run_worker_first so a truthy answer emits run_worker_first = true under the [assets] block on the generated wrangler.toml",
+  "soThat": "a project can read the ratified shape decision with its standards trace to Cloudflare's own landing-page recommendation and know exactly how to migrate its Pages routing to Workers",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-3001-1",
+      "description": "The ADR contribution entry ADR-1306-deploy-cloudflare-workers-spa-shape sits under contributions/adrs/adr-1306-deploy-cloudflare-workers-spa-shape.json and validates against the rcf-schemas 0.6.1 ADR shape (required fields adrId prdId tadId version status title context decision consequences createdAt updatedAt; optional alternativesConsidered supersededBy relatedAdrs). Its body carries the verbatim Cloudflare Pages landing-page quote Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare's primary platform for building applications. Start new projects with Workers., alongside a decision blessing Workers-with-static-assets as the SPA-on-Workers deploy shape and consequences naming the two new elicits assets-directory and run-worker-first. The ADR contribution entry in blueprint.json carries recommendedDefault true, elicited false and standardsTraceClause Cloudflare Pages landing-page recommendation (2026-09-06). The ADR body does NOT carry standardsTraceClause (per section 8a.2 the clause belongs on the contribution entry).",
+      "given": "the shipped ADR contribution",
+      "when": "jq queries against blueprint.json contribution entry and the ADR JSON body",
+      "then": "the blueprint.json entry carries standardsTraceClause set to the 2026-09-06 landing-page recommendation clause; the ADR body carries the verbatim Cloudflare Pages landing-page quote in context or decision; the ADR body does not carry standardsTraceClause; the ADR body validates against the 0.6.1 ADR schema",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-3001-2",
+      "description": "The guide at blueprints/deploy-cloudflare-workers/guide/deploy-cloudflare-workers.md gains a new section titled Workers-with-static-assets: the SPA-on-Workers shape with the verbatim Cloudflare landing-page quote, the two elicit signatures (assets-directory string default empty; run-worker-first boolean default false), a copy-paste wrangler.toml snippet showing the [assets] block with directory and the run_worker_first hint, and a link to the Cloudflare migrate-from-Pages guide at https://developers.cloudflare.com/workers/static-assets/migration-guides/migrate-from-pages/. The Cloudflare Workers static-assets doc at https://developers.cloudflare.com/workers/static-assets/ is cited in the same section. Both URLs return 200 at gate time.",
+      "given": "the updated guide file",
+      "when": "grep the guide for the new section heading and the two Cloudflare URLs",
+      "then": "the section heading appears once with the exact title; the migrate-from-Pages URL and the static-assets doc URL appear at least once each; both URLs return HTTP 200 on a plain curl -fsSI",
+      "testable": true,
+      "scope": "library"
+    },
+    {
+      "id": "AC-3001-3",
+      "description": "The spec's second canonical AC spaFallbackShape is realised in the blueprint contributions as AC-12113-2 on US-12113 with a runtime-observable then clause anchored to TAC-1302-deploy-cloudflare-workers-wrangler-manifest. The shipped probe assets-manifest-scan.mjs asserts run_worker_first presence and value under the [assets] block against the elicited answer. On the cf-platform fixture (which bakes run_worker_first = true) the probe returns verdict pass and the report carries a detail record naming runWorkerFirst true. On the SIMULATE_MIXED_SHAPE=true branch the fixture inserts a pages_build_output_dir field and the probe returns verdict fail naming the offending pages_build_output_dir line. On the SIMULATE_EMPTY_ASSETS=true branch the fixture removes the [assets] block and the probe returns verdict pass with an empty-directory record (bare-Worker shape).",
+      "given": "the shipped probe module and the cf-platform fixture with induced-failure switches",
+      "when": "run-assets-manifest-scan.mjs drives the probe on each of the three fixture states",
+      "then": "aggregateVerdict pass on the canonical state; aggregateVerdict fail on SIMULATE_MIXED_SHAPE with detail naming pages_build_output_dir; aggregateVerdict pass on SIMULATE_EMPTY_ASSETS with the empty-directory record",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tags": [
+    "blueprint:deploy-cloudflare-workers"
+  ],
+  "usId": "US-3001",
+  "prdId": "PRD-001",
+  "reqId": "REQ-030",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-0 ADR-1306-deploy-cloudflare-workers-spa-shape, guide section with migrate-from-Pages link, and probed spaFallbackShape with induced-failure switches"
+}

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

@@ -0,0 +1,69 @@
+{
+  "createdAt": "2026-09-06T19:17:37.906Z",
+  "updatedAt": "2026-09-06T19:17:37.906Z",
+  "asA": "shelf consumer applying the messaging-queue-cloudflare v1.0.0 blueprint",
+  "iWant": "the shipped blueprint files with 20 to 24 contributions, six probes, and the T-3 side of the shared sample-app fixture that boots a Cloudflare Worker under wrangler dev with a queue binding and a DLQ binding, plus gate-runnable proof that every probe passes on the canonical fixture state and refuses on each induced-failure switch",
+  "soThat": "a rcf-lite project applying this blueprint gets a producer facade over the Cloudflare Queues binding with publish, consume, ack, retry, and DLQ, a lifecycle-event sink with metadata-only fields, and the queue capability the jobs-background blueprint composes on at apply time, with runtime-observable ACs proven by probes the HQ gate runs against a real wrangler dev process",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-4201-1",
+      "description": "The shelf carries blueprints/messaging-queue-cloudflare/blueprint.json declaring slug messaging-queue-cloudflare, version 1.0.0, category messaging, 21 contributions in the 6 REQ / 8 US / 3 TAC / 4 ADR groups per infra round 5 spec section 5.3; capabilities is [queue]; suggestedCompanions declares logging and errorHandling with spec section 5.3 reasons; providesRoles is absent; requiresAppliedCapabilities is absent; every ADR contribution entry carries a non-null standardsTraceClause per section 8a.2.",
+      "given": "the shelf tree after this blueprint lands",
+      "when": "jq queries against blueprints/messaging-queue-cloudflare/blueprint.json",
+      "then": "jq .slug returns messaging-queue-cloudflare; jq .version returns 1.0.0; jq .contributions | length returns 21; jq .capabilities returns [queue]; jq .suggestedCompanions | length returns 2; jq .contributions[] | select(.kind==adr) | .standardsTraceClause returns a non-null string for every entry",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4201-2",
+      "description": "rcf define blueprint add ./blueprints/messaging-queue-cloudflare applies the 21 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.",
+      "given": "a fresh rcf init scratch project",
+      "when": "rcf define blueprint add ./blueprints/messaging-queue-cloudflare runs, then rcf define validate, then rcf audit coverage --strict, then rcf audit eval coverage --strict",
+      "then": "every command exits 0; the scratch project's rcf tree contains the 21 contributions; no globalAdrTopic conflict is raised",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4201-3",
+      "description": "REQ-004 description names the dead_letter_queue field literal (per fetched Cloudflare Queues DLQ documentation) and the DLQ retention 4 days; jq grep on the contribution set returns at least one match for dead_letter_queue and at least one match for the retention constant.",
+      "given": "the shelf blueprint contribution set",
+      "when": "jq .contributions[] | select(.id==messaging-queue-cloudflare-REQ-004) | .description on the requirement file",
+      "then": "the description mentions dead_letter_queue and 4 days retention with the source URL literal https://developers.cloudflare.com/queues/configuration/dead-letter-queues/",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4201-4",
+      "description": "The six probe modules under blueprints/messaging-queue-cloudflare/contributions/probes/ each pass against a running wrangler-dev seam brought up from the shared sample-app fixture: producer-facade-ready asserts producerReady fires with the queue name; publish-to-delivery asserts consumer receives all 5 messages with matching bodies and trace-ids; retry-and-dlq asserts DLQ contents at attempt-counter 3 and messageDeadLettered fires; event-secrecy asserts no PII fixture text in any event record; real-account-concurrency-smoke exits 0 with accountBoundSkipped true without CI_HAS_CLOUDFLARE_ACCOUNT or runs a real 500-message round-trip when the env var is set. Each per-blueprint probe report at .rcf/reports/blueprints/messaging-queue-cloudflare/<probe-name>.json carries aggregateVerdict pass.",
+      "given": "the shared sample-app fixture at packages/rcf-lite/test/fixtures/infra-s3-and-queue/ with the T-3 wrangler-dev seam booted (or the in-memory queue-driver mode active for probes needing no live Wrangler process)",
+      "when": "each of the six run-<probe-name>.mjs shims runs against the fixture in sequence",
+      "then": "every shim exits 0; every per-blueprint report file carries aggregateVerdict pass; every result carries an anchorAcId matching a contributed AC id on the blueprint",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4201-5",
+      "description": "The sample-app fixture's three induced-failure switches surface each probe's negative-run behaviour: SIMULATE_CONSUMER_RETRY=true drives the retry-and-dlq probe's re-delivery path and (at max-attempts) the DLQ landing; SIMULATE_DLQ_OVERFLOW=true drives the retry-and-dlq probe past max-attempts on the first delivery so the message lands on the DLQ within one delivery cycle; SIMULATE_PII_IN_BODY=true drives the event-secrecy probe with a PII fixture body and asserts the event record whitelist enforces (no PII leak).",
+      "given": "the shared fixture with the T-3 seam active",
+      "when": "each named induced-failure switch is set in turn and the paired probe runs",
+      "then": "SIMULATE_CONSUMER_RETRY true yields retry-and-dlq report with attempt-counter increments to 3 and messageDeadLettered fires; SIMULATE_DLQ_OVERFLOW true yields retry-and-dlq report reaching DLQ on first cycle with aggregateVerdict pass; SIMULATE_PII_IN_BODY true yields event-secrecy report with aggregateVerdict pass proving the whitelist blocks the PII leak (or fail if the whitelist is bypassed); the fixture README documents each switch and the paired probe",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4201-6",
+      "description": "The blueprint ships a sample-app fixture entry, a README, a CHANGELOG, a guide, and a docs/topics.md entry; the shelf-wide id-band registry table gains a messaging-queue-cloudflare row at US band 29101-29899 / ADR-TAC suffix block 30xx across every shipped blueprint's docs/topics.md; packages/rcf-lite/docs/blueprint-authoring.md section 6a capability-declaration table gains one row for queue naming the reserved messaging-queue-postgres sibling per infra round 5 spec section 5.6 and Baz decision 7.",
+      "given": "the shelf tree after this blueprint lands",
+      "when": "grep queries walk every blueprint's docs/topics.md and the section 6a table",
+      "then": "packages/rcf-lite/docs/blueprint-authoring.md contains a table row beginning | queue | with the reserved messaging-queue-postgres sibling note; every shipped blueprint's docs/topics.md carries a row beginning | messaging-queue-cloudflare | with the 29101-29899 band and 30xx suffix; blueprints/messaging-queue-cloudflare/README.md, CHANGELOG.md, guide/messaging-queue-cloudflare.md, docs/topics.md, and the extended packages/rcf-lite/test/fixtures/infra-s3-and-queue/ all exist; the fixture README names the wrangler dev incantation and three wired induced-failure switches",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "usId": "US-4201",
+  "prdId": "PRD-001",
+  "reqId": "REQ-042",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "The messaging-queue-cloudflare blueprint ships on the shelf with four wrangler-dev probes plus one accountBound real-account concurrency smoke"
+}

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

@@ -0,0 +1,78 @@
+{
+  "createdAt": "2026-09-06T20:28:34.000Z",
+  "updatedAt": "2026-09-06T20:28:34.000Z",
+  "asA": "shelf consumer applying the jobs-background v1.0.0 blueprint",
+  "iWant": "the shipped blueprint files with 22 contributions, five probes, an extension to the shared sample-app fixture wiring the jobs runtime and scheduler on top of the T-3 in-memory queue seam, plus gate-runnable proof that apply refuses on a bare project with exit 3 and the stable message id, --allow-no-queue-yet writes a sidecar note, and every probe passes on the canonical fixture state",
+  "soThat": "a rcf-lite project applying this blueprint gets a job-definition contract with retry policy and timeout, an elicited scheduler (inProcess for now, workerCron or external for shipped adapters, workflows reserved for v1.1.0), a metadata-only run-log event stream at four moments, and the backgroundJobs capability future consumer blueprints can compose on; the T-5 capability-consumer mechanism is exercised end to end through the queue-capability path with runtime-observable ACs proven by probes the HQ gate runs against the shared sample-app fixture",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-4301-1",
+      "description": "The shelf carries blueprints/jobs-background/blueprint.json declaring slug jobs-background, version 1.0.0, category jobs, 22 contributions in the 6 REQ / 9 US / 3 TAC / 4 ADR groups per infra round 5 spec section 5.4; capabilities is [backgroundJobs]; suggestedCompanions declares logging and errorHandling with spec section 5.4 reasons; providesRoles is absent; requiresAppliedCapabilities equals {capabilities:[queue],allowSkipFlag:allow-no-queue-yet,refusalMessageId:jobs-background-no-queue}; every ADR contribution entry carries a non-null standardsTraceClause per section 8a.2.",
+      "given": "the shelf tree after this blueprint lands",
+      "when": "jq queries against blueprints/jobs-background/blueprint.json",
+      "then": "jq .slug returns jobs-background; jq .version returns 1.0.0; jq .contributions | length returns 22; jq .capabilities returns [backgroundJobs]; jq .suggestedCompanions | length returns 2; jq .requiresAppliedCapabilities.capabilities returns [queue]; jq .requiresAppliedCapabilities.allowSkipFlag returns allow-no-queue-yet; jq .requiresAppliedCapabilities.refusalMessageId returns jobs-background-no-queue; jq .contributions[] | select(.kind==adr) | .standardsTraceClause returns a non-null string for every entry",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4301-2",
+      "description": "rcf define blueprint add ./blueprints/jobs-background on a bare fresh init project with no queue-capability provider applied refuses with exit 3 and the stderr message opens with the tag [jobs-background-no-queue] and explicitly names messaging-queue-cloudflare as the shipped provider and --allow-no-queue-yet as the override, per infra round 5 spec section 10 Q3 default asserting BOTH exit code AND stable message id.",
+      "given": "a fresh rcf init scratch project with no applied blueprints",
+      "when": "rcf define blueprint add ./blueprints/jobs-background runs",
+      "then": "exit code is 3; stderr contains the substring [jobs-background-no-queue]; stderr contains the substring messaging-queue-cloudflare; stderr contains the substring --allow-no-queue-yet; nothing is written to rcf/manifest.json under blueprints[] for jobs-background",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4301-3",
+      "description": "rcf define blueprint add ./blueprints/jobs-background --allow-no-queue-yet on the same bare project exits 0 and writes the sidecar rcf/blueprints/jobs-background.applied.json with allowNoAuthYet true, appliedCapabilities [], and a notes field naming the missing queue capability and the --allow-no-queue-yet override flag (queue-family prose, not auth-family prose); the T-5 mechanism's shipped sidecar path supersedes the spec section 5.4 prose reference to manifest.blueprints[jobs-background].source.notes because the applied-blueprint-record schema in rcf-schemas 0.6.1 is closed and cannot carry the notes field.",
+      "given": "a fresh rcf init scratch project with no applied blueprints",
+      "when": "rcf define blueprint add ./blueprints/jobs-background --allow-no-queue-yet runs",
+      "then": "exit code is 0; the file rcf/blueprints/jobs-background.applied.json exists; its slug is jobs-background; its allowNoAuthYet is true; its appliedCapabilities is []; its notes contains the substring no queue yet and the substring --allow-no-queue-yet and the substring queue; its notes does NOT contain the substring no auth yet nor no secrets-management yet",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4301-4",
+      "description": "rcf define blueprint add ./blueprints/jobs-background on a fresh init project that first applied messaging-queue-cloudflare exits 0 and the sidecar rcf/blueprints/jobs-background.applied.json records appliedCapabilities containing queue via the T-5 capability discovery mechanism (union across applied blueprint capability declarations); the spec section 5.4 prose reference to jq '.blueprints[] | select(.slug==\"jobs-background\") | .appliedCapabilities' rcf/manifest.json is superseded by the shipped mechanism which lives on the sidecar.",
+      "given": "a fresh rcf init scratch project with messaging-queue-cloudflare applied first",
+      "when": "rcf define blueprint add ./blueprints/jobs-background runs",
+      "then": "exit code is 0; the file rcf/blueprints/jobs-background.applied.json exists; its slug is jobs-background; its appliedCapabilities contains the string queue; its allowNoAuthYet is undefined; its notes is undefined",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4301-5",
+      "description": "Every probe module under blueprints/jobs-background/contributions/probes/ exports the spec section 3.2 verdict envelope with an anchorAcId matching a contributed AC id on the blueprint (apply-time-refusal.mjs anchorAcId AC-jobs-requiresQueue, apply-time-override.mjs AC-jobs-overrideRecorded, fake-clock-cron.mjs AC-jobs-scheduledRunsOnCron, retry-and-fail.mjs AC-jobs-retryOnHandlerFailure, event-secrecy.mjs AC-jobs-eventSecrecy); every run-<probe-name>.mjs shim exits 0 on a fresh run of the shared sample-app fixture with the T-3 in-memory queue seam active; every per-blueprint report at .rcf/reports/blueprints/jobs-background/<probe-name>.json carries aggregateVerdict pass.",
+      "given": "the shared sample-app fixture at packages/rcf-lite/test/fixtures/infra-s3-and-queue/ with the T-3 in-memory queue-driver seam active (SDR-3-a coordinator ruling: wrangler dev is not on this build host and the in-memory realisation of the Cloudflare Queues binding shape is the shipped local seam)",
+      "when": "each of the five run-<probe-name>.mjs shims runs against the fixture in sequence",
+      "then": "every shim exits 0; every per-blueprint report file carries aggregateVerdict pass; every result carries an anchorAcId matching a contributed AC id on the blueprint",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4301-6",
+      "description": "The shared sample-app fixture at packages/rcf-lite/test/fixtures/infra-s3-and-queue/ grows a jobs/ directory carrying two toy job-definition modules (send-welcome-email.mjs with retryPolicy {maxAttempts:3,backoff:exponential} and timeoutMs 60000, refresh-cache.mjs with retryPolicy {maxAttempts:5,backoff:constant} timeoutMs 10000 and cron every-minute), src/jobs-runtime.mjs realising the run-time (reads applied capabilities from the sidecar, registers job handlers with the queue consumer, fires the four lifecycle events per REQ-005), src/scheduler.mjs realising the inProcess scheduler with a fake-clock seam; two induced-failure switches SIMULATE_HANDLER_THROW and SIMULATE_PII_IN_JOB_INPUT are WIRED and driven live by the retry-and-fail.mjs and event-secrecy.mjs probes; the fixture README documents the two toy jobs, the jobs/ convention, the fake-clock switch, the elicited parameters and both induced-failure switches with paired probes.",
+      "given": "the shared fixture with the T-3 in-memory queue-driver seam and the T-4 jobs-runtime+scheduler wired on top",
+      "when": "each of the two induced-failure switches is set in turn and the paired probe runs",
+      "then": "SIMULATE_HANDLER_THROW true yields retry-and-fail report with attempts counter 1,2,3 across three jobStarted events with the same jobId followed by jobFailed with terminal code; SIMULATE_PII_IN_JOB_INPUT true yields event-secrecy report with aggregateVerdict pass proving the event whitelist blocks every PII input field; the fixture README documents each switch and the paired probe module by name",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-4301-7",
+      "description": "The blueprint ships a README, a CHANGELOG, a guide, and a docs/topics.md entry; the shelf-wide id-band registry table gains a jobs-background row at US band 30101-30899 / ADR-TAC suffix block 31xx across every shipped blueprint's docs/topics.md; packages/rcf-lite/docs/blueprint-authoring.md section 6a capability-declaration table gains one row for backgroundJobs naming the reserved sibling posture per infra round 5 spec section 5.6.",
+      "given": "the shelf tree after this blueprint lands",
+      "when": "grep queries walk every blueprint's docs/topics.md and the section 6a table",
+      "then": "packages/rcf-lite/docs/blueprint-authoring.md contains a table row beginning | backgroundJobs | naming jobs-background and the reserved sibling posture; every shipped blueprint's docs/topics.md carries a row beginning | jobs-background | with the 30101-30899 band and 31xx suffix; blueprints/jobs-background/README.md, CHANGELOG.md, guide/jobs-background.md, docs/topics.md, and the extended packages/rcf-lite/test/fixtures/infra-s3-and-queue/ all exist; the fixture README names the jobs-runtime boot line and the two wired induced-failure switches",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "usId": "US-4301",
+  "prdId": "PRD-001",
+  "reqId": "REQ-043",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "The jobs-background blueprint ships on the shelf with five probes wired to the T-3 in-memory queue seam"
+}