rcf-lite 0.22.0 → 0.24.0

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:28.334Z",
+  "updatedAt": "2026-09-07T21:41:28.623Z",
+  "purpose": "Cover AC-10101-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10101-1"
+  ],
+  "id": "TS-131",
+  "usId": "US-10101",
+  "title": "T-6 AC-10101-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-131-guide-management-surface-doc",
+      "acId": "AC-10101-1",
+      "description": "AC-10101-1 anatomy proof (T-6 rate-limiting slice, TC-131-guide-management-surface-doc)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10101-1 anatomy proof (TC-131-guide-management-surface-doc)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:28.913Z",
+  "updatedAt": "2026-09-07T21:41:29.200Z",
+  "purpose": "Cover AC-10201-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10201-1"
+  ],
+  "id": "TS-132",
+  "usId": "US-10201",
+  "title": "T-6 AC-10201-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-132-real-account-burst-and-429-or-skipped",
+      "acId": "AC-10201-1",
+      "description": "AC-10201-1 anatomy proof (T-6 rate-limiting slice, TC-132-real-account-burst-and-429-or-skipped)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10201-1 anatomy proof (TC-132-real-account-burst-and-429-or-skipped)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:29.506Z",
+  "updatedAt": "2026-09-07T21:41:29.793Z",
+  "purpose": "Cover AC-10301-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10301-1"
+  ],
+  "id": "TS-133",
+  "usId": "US-10301",
+  "title": "T-6 AC-10301-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-133-drift-audit-runner-diff",
+      "acId": "AC-10301-1",
+      "description": "AC-10301-1 anatomy proof (T-6 rate-limiting slice, TC-133-drift-audit-runner-diff)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10301-1 anatomy proof (TC-133-drift-audit-runner-diff)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:30.086Z",
+  "updatedAt": "2026-09-07T21:41:30.375Z",
+  "purpose": "Cover AC-10401-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10401-1"
+  ],
+  "id": "TS-134",
+  "usId": "US-10401",
+  "title": "T-6 AC-10401-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-134-composition-guide-section",
+      "acId": "AC-10401-1",
+      "description": "AC-10401-1 anatomy proof (T-6 rate-limiting slice, TC-134-composition-guide-section)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10401-1 anatomy proof (TC-134-composition-guide-section)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:30.663Z",
+  "updatedAt": "2026-09-07T21:41:30.952Z",
+  "purpose": "Cover AC-10601-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10601-1"
+  ],
+  "id": "TS-135",
+  "usId": "US-10601",
+  "title": "T-6 AC-10601-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-135-manifest-schema-validate-pass-and-fail",
+      "acId": "AC-10601-1",
+      "description": "AC-10601-1 anatomy proof (T-6 rate-limiting slice, TC-135-manifest-schema-validate-pass-and-fail)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10601-1 anatomy proof (TC-135-manifest-schema-validate-pass-and-fail)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:31.243Z",
+  "updatedAt": "2026-09-07T21:41:31.532Z",
+  "purpose": "Cover AC-10701-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10701-1"
+  ],
+  "id": "TS-136",
+  "usId": "US-10701",
+  "title": "T-6 AC-10701-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-136-event-secrecy-pass-and-leak",
+      "acId": "AC-10701-1",
+      "description": "AC-10701-1 anatomy proof (T-6 rate-limiting slice, TC-136-event-secrecy-pass-and-leak)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10701-1 anatomy proof (TC-136-event-secrecy-pass-and-leak)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,22 @@
+{
+  "createdAt": "2026-09-07T21:41:31.821Z",
+  "updatedAt": "2026-09-07T21:41:32.111Z",
+  "purpose": "Cover AC-10801-1 via the T-6 anatomy test in test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js.",
+  "testLevel": "integration",
+  "acIds": [
+    "AC-10801-1"
+  ],
+  "id": "TS-137",
+  "usId": "US-10801",
+  "title": "T-6 AC-10801-1 anatomy proof",
+  "testCases": [
+    {
+      "id": "TC-137-manifest-presence-missing-fail",
+      "acId": "AC-10801-1",
+      "description": "AC-10801-1 anatomy proof (T-6 rate-limiting slice, TC-137-manifest-presence-missing-fail)",
+      "status": "pending",
+      "testPointer": "test/blueprint/edge-cloudflare-rate-limiting-anatomy.test.js::T-6 rate-limiting AC-10801-1 anatomy proof (TC-137-manifest-presence-missing-fail)"
+    }
+  ],
+  "status": "draft"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:02.422Z",
+  "updatedAt": "2026-09-07T21:41:02.422Z",
+  "asA": "shelf consumer applying the edge-cloudflare-rate-limiting v1.0.0 blueprint on a Workers project using the cf-edge fixture",
+  "iWant": "the elicited manifest directory to hold at least one committed JSON file per rate-limit rule, each carrying the seven documented fields and no plaintext secret",
+  "soThat": "the rules are source-controlled and reviewable and the operator has a stable source of truth to apply to the live zone",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10001-1",
+      "description": "The cf-edge fixture's cloudflare/rate-limits/ directory holds at least one JSON file per rule; every file parses; every file carries id, expression, threshold, period, characteristics, action, duration; no file body carries a plaintext bearer token, private key or inline CF_API_TOKEN reference.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3701-edge-cloudflare-rate-limiting-manifest-schema"
+  ],
+  "usId": "US-10001",
+  "prdId": "PRD-001",
+  "reqId": "REQ-100",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 rate-limit manifest present in cf-edge cloudflare/rate-limits/ carrying seven required fields without plaintext secrets"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:02.760Z",
+  "updatedAt": "2026-09-07T21:41:02.760Z",
+  "asA": "operator on the applying project preparing to push rate-limit rules from the local manifest to the live Cloudflare zone",
+  "iWant": "a documented flow with both wrangler command steps and a Cloudflare dashboard walkthrough",
+  "soThat": "I can pick the flow that suits my operating discipline and reproduce the apply from the manifest",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10101-1",
+      "description": "The blueprint guide documents an operator-facing management surface with a wrangler command flow and a Cloudflare dashboard flow; the guide references https://developers.cloudflare.com/waf/rate-limiting-rules/.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3702-edge-cloudflare-rate-limiting-management-surface-doc"
+  ],
+  "usId": "US-10101",
+  "prdId": "PRD-001",
+  "reqId": "REQ-101",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 operator-facing management surface: wrangler command flow and Cloudflare dashboard flow documented in the guide"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:03.086Z",
+  "updatedAt": "2026-09-07T21:41:03.086Z",
+  "asA": "operator running the real-account burst probe against a scheduled HQ-owned URL",
+  "iWant": "the probe to fire an undici burst above the rule threshold and observe the (N+1)th and subsequent requests return HTTP 429 with Retry-After and Cf-Ray, or record accountBoundSkipped in CI",
+  "soThat": "the over-threshold behaviour is verified against a real Cloudflare account when the account is available, and CI without an account records the honest verdict per ruling 6",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10201-1",
+      "description": "With CI_HAS_CLOUDFLARE_ACCOUNT=true and CF_RATE_LIMIT_URL set, the burst probe returns 429 with Retry-After and Cf-Ray on over-threshold requests; without either env var it records accountBoundSkipped: true and aggregates to pass per spec section 3.5 and ruling 6.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3701-edge-cloudflare-rate-limiting-manifest-schema"
+  ],
+  "usId": "US-10201",
+  "prdId": "PRD-001",
+  "reqId": "REQ-102",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 real-account burst returns 429 with Retry-After and Cf-Ray on over-threshold requests, or accountBoundSkipped in CI per ruling 6"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:03.411Z",
+  "updatedAt": "2026-09-07T21:41:03.411Z",
+  "asA": "operator on the applying project running the scheduled drift-audit runner behind the elicited cadence",
+  "iWant": "the runner to fetch the live rules via the Cloudflare API and diff each against the local manifest, constructing metadata-only drift records",
+  "soThat": "manifest drift is surfaced through the logging companion rather than lingering unnoticed",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10301-1",
+      "description": "Given a fixture manifest with threshold 60 and a fake live-zone response with threshold 90 on the same rule id, the runner constructs one drift record with {ruleId, clientIpHash, outcome, timestamp, diff:[{field:threshold, manifestValue:60, liveValue:90}]}; no full IP, body or user-agent field is present.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3703-edge-cloudflare-rate-limiting-drift-audit-runner"
+  ],
+  "usId": "US-10301",
+  "prdId": "PRD-001",
+  "reqId": "REQ-103",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 drift-audit runner reads live rules and diffs against manifest, constructing metadata-only drift records"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:03.736Z",
+  "updatedAt": "2026-09-07T21:41:03.736Z",
+  "asA": "operator applying both edge-cloudflare-rate-limiting and security-auth-magic-link on the same project",
+  "iWant": "the guide to name the ADR-3702 layering explicitly with a copy-paste example",
+  "soThat": "I understand the two-rule shape at apply time rather than by trial and error",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10401-1",
+      "description": "The guide contains a Composition with security-auth-magic-link section referencing ADR-3702, naming the two characteristic sets (IP-per-URL and per-email per-minute) verbatim, and showing a copy-paste example of both blueprints applied.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3702-edge-cloudflare-rate-limiting-management-surface-doc"
+  ],
+  "usId": "US-10401",
+  "prdId": "PRD-001",
+  "reqId": "REQ-104",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 composition with security-auth-magic-link: zone rule layers over the per-email application rule per ADR-3702, documented in the guide"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:04.062Z",
+  "updatedAt": "2026-09-07T21:41:04.062Z",
+  "asA": "operator committing new rate-limit rule files under the elicited manifest directory",
+  "iWant": "the shipped JSON Schema to validate every rule file and the manifest-schema-validate probe to surface any file that violates the shape",
+  "soThat": "invalid manifest changes are caught in the fixture probe rather than at operator apply time",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10601-1",
+      "description": "The manifest-schema-validate probe validates every manifest file against the shipped rate-limit-rule.schema.json (draft-07); valid files pass; a manifest file missing threshold (SIMULATE_SCHEMA_INVALID=true) fails validation with the offending field named in the detail.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3701-edge-cloudflare-rate-limiting-manifest-schema"
+  ],
+  "usId": "US-10601",
+  "prdId": "PRD-001",
+  "reqId": "REQ-100",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 manifest schema validates every rule file against the shipped draft-07 schema and refuses invalid shapes"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:04.389Z",
+  "updatedAt": "2026-09-07T21:41:04.389Z",
+  "asA": "operator reading drift-audit reports and rate-limit event records through the applied logging companion",
+  "iWant": "every drift-audit record to carry only metadata-safe fields, never a full IP, request body or user agent string",
+  "soThat": "the audit trail is safe to store, forward and read without additional PII scrubbing",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10701-1",
+      "description": "The event-secrecy probe drives the drift-audit runner with a synthetic input pair; every record carries only {ruleId, clientIpHash, outcome, timestamp, diff}; SIMULATE_EVENT_LEAK_IP=true injects a full IP into the outcome so the probe surfaces the leak.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3703-edge-cloudflare-rate-limiting-drift-audit-runner"
+  ],
+  "usId": "US-10701",
+  "prdId": "PRD-001",
+  "reqId": "REQ-103",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 drift-audit event records carry ruleId, clientIpHash, outcome, timestamp, diff only; no full IP, body or user-agent"
+}

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

@@ -0,0 +1,23 @@
+{
+  "createdAt": "2026-09-07T21:41:04.712Z",
+  "updatedAt": "2026-09-07T21:41:04.712Z",
+  "asA": "operator that accidentally deletes or moves a manifest file",
+  "iWant": "the manifest-presence probe to surface the missing file at fixture probe time",
+  "soThat": "a manifest under-population defect is caught in CI rather than at operator apply time",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-10801-1",
+      "description": "With SIMULATE_MANIFEST_MISSING=true the manifest-presence probe returns aggregateVerdict: fail and names the missing file basename in the detail; without the switch the probe passes.",
+      "testable": true
+    }
+  ],
+  "tacIds": [
+    "TAC-3701-edge-cloudflare-rate-limiting-manifest-schema"
+  ],
+  "usId": "US-10801",
+  "prdId": "PRD-001",
+  "reqId": "REQ-100",
+  "version": "0.1.0",
+  "status": "draft",
+  "title": "T-6 manifest-presence probe refuses a missing manifest file and names the basename in the detail"
+}

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