rcf-lite 0.26.0 → 0.27.0

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32101.json

@@ -11,15 +11,96 @@
   "acceptanceCriteria": [
     {
       "id": "AC-32101-1",
-      "description": "On process boot, the scheduled handler binds against the elicited cron triggers (the [triggers] crons block in wrangler.toml on the fixture), wires the dispatcher and the injected event sink; the ready() call fires cronReady on the sink with a payload of exactly {event, key, size, ttl, timestamp} where key is null, size is 0 and ttl is null. The scheduled handler does NOT dereference other bindings on env; env.CACHE (the T-1 KV binding) is not read by this module.",
+      "description": "On process boot, the scheduled handler binds against the elicited cron triggers (the [triggers] crons block in wrangler.toml on the fixture), wires the dispatcher and the injected sink; the ready() call fires cronReady on the sink with a payload of exactly {event, expression, scheduledTime, outcome, duration} per TAC-3303 where expression is null, scheduledTime is null, outcome is 'ready' and duration is 0. The scheduled handler module (src/scheduled.mjs) does NOT dereference env.CACHE (the KV binding) or any other env binding; a source-tree grep of that file returns zero hits for env.CACHE.",
       "given": "a Node or Worker process with the scheduled handler module imported and its factory invoked with the elicited configuration",
       "when": "the process boots and the scheduled handler ready() call resolves",
-      "then": "a cronReady event fires on the injected event sink with the metadata-only payload; the module does not dereference env.CACHE",
+      "then": "a cronReady event fires on the injected sink carrying the cron-vocabulary metadata payload {event, expression, scheduledTime, outcome, duration}; the scheduled.mjs source has zero env.CACHE references",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "responsibilities.cronReady"
+      },
+      "vendorCitation": {
+        "url": "https://developers.cloudflare.com/workers/runtime-apis/handlers/scheduled/",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-32101-2",
+      "description": "createScheduledHandler({routes: []}) throws a named error kind CRON_HANDLER_INVALID_ROUTES before any binding is dereferenced; no cronReady event fires on the sink. Same for routes omitted or routes not an array.",
+      "given": "a call to createScheduledHandler with routes as an empty array (or not an array at all)",
+      "when": "the factory is invoked",
+      "then": "the factory throws CRON_HANDLER_INVALID_ROUTES and no event is emitted on the sink",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      }
+    },
+    {
+      "id": "AC-32101-3",
+      "description": "createScheduledHandler called with the sink argument not a function (per TAC-3303) throws a named error kind CRON_HANDLER_INVALID_SINK before any binding is dereferenced.",
+      "given": "a call to createScheduledHandler with the sink argument not a function",
+      "when": "the factory is invoked",
+      "then": "the factory throws CRON_HANDLER_INVALID_SINK and no event is emitted",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3303-platform-cloudflare-cron-triggers-event-sink",
+        "field": "interfaces.eventSink parameter"
+      }
+    },
+    {
+      "id": "AC-32101-4",
+      "description": "Repeat-boot idempotency: two sequential createScheduledHandler(...).ready() calls emit two cronReady records on the sink, both with identical shape {event:\"cronReady\", expression:null, scheduledTime:null, outcome:\"ready\", duration:0}. No accumulator drift; no shared state leaks between instances.",
+      "given": "two independent createScheduledHandler instances constructed with identical arguments",
+      "when": "ready() is called on each in turn",
+      "then": "the sink receives two cronReady records with identical payload shape",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "responsibilities.cronReady"
+      }
+    },
+    {
+      "id": "AC-32101-5",
+      "description": "Sole-reader source-tree scan: a recursive scan of the cf-platform fixture src/ tree greps every .mjs file for the substrings \"event?.cron\", \"event.cron\" and \"event?.scheduledTime\"; the only file carrying these tokens is src/scheduled.mjs. Any other module carrying the raw Cron Trigger event field access surfaces as a leak with the file path.",
+      "given": "the cf-platform fixture src/ tree and the sole-reader scan probe",
+      "when": "the scan walks every .mjs file matching the token list",
+      "then": "the only file with matches is src/scheduled.mjs; every other file returns zero matches",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "responsibilities.solereader"
+      }
+    },
+    {
+      "id": "AC-32101-6",
+      "description": "The applied blueprint's manifest declares the `scheduledTrigger` capability token and the applied project ships the single scheduled() handler module per AC-32101-1; therefore the `scheduledTrigger` promise the manifest carries is backed by the live handler the deployed Worker registers.",
+      "given": "the applied blueprint manifest at `blueprints/platform-cloudflare-cron-triggers/blueprint.json` and the applied fixture with the shipped scheduled() handler module",
+      "when": "the anatomy test reads the blueprint manifest and asserts the handler module presence per AC-32101-1",
+      "then": "the manifest carries `scheduledTrigger` on its `capabilities[]` list and the applied handler module is present, so `scheduledTrigger` is a live promise the applying project can act on",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "responsibilities.cronReady"
+      }
     }
   ],
-  "tacIds": ["TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"],
+  "tacIds": [
+    "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-10T00:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32102.json

@@ -11,12 +11,17 @@
   "acceptanceCriteria": [
     {
       "id": "AC-32102-1",
-      "description": "createDispatcher({routes, eventSink, skewToleranceMs, softBudgetMs, clock?}) returns a dispatch(event) function. Calling dispatch({cron, scheduledTime}) invokes exactly the handler whose expression string-equals the cron field, passes {expression, scheduledTime, sink} to it, and returns without invoking any other route's handler.",
+      "description": "createDispatcher({routes, sink, skewToleranceMs, softBudgetMs, clock?}) returns a dispatch(event) function. Calling dispatch({cron, scheduledTime}) invokes exactly the handler whose expression string-equals the cron field, passes {expression, scheduledTime, sink} to it, and returns without invoking any other route's handler.",
       "given": "a dispatcher wired with two routes and two spy handlers",
       "when": "dispatch is called with a specific expression matching one route",
       "then": "only the matched spy handler is invoked exactly once with the bounded context",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "interfaces.dispatch"
+      },
+      "disposition": "template"
     },
     {
       "id": "AC-32102-2",
@@ -25,10 +30,69 @@
       "when": "dispatch is called with an expression not in the routes",
       "then": "no spy is called, a cronUnmatched event fires, and dispatch returns without side effect",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "template"
+    },
+    {
+      "id": "AC-32102-3",
+      "description": "Single-handler mode: createDispatcher({routes:[{expression:\"*/5 * * * *\", handler}], mode:\"single-handler\", sink, ...}) invokes the single handler on EVERY dispatch regardless of the incoming event.cron value. A dispatch({cron:\"1 2 3 4 5\", scheduledTime}) still invokes the single handler with bounded context {expression:\"1 2 3 4 5\", scheduledTime, sink}; no cronUnmatched event fires because unmatched has no meaning in single-handler mode.",
+      "given": "a dispatcher with mode:\"single-handler\" and exactly one route",
+      "when": "dispatch is called with an expression different from the routed one",
+      "then": "the single handler is invoked with the incoming expression as bounded context; no cronUnmatched event fires",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "template",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "interfaces.dispatch"
+      }
+    },
+    {
+      "id": "AC-32102-4",
+      "description": "Malformed event: dispatch({cron:null, scheduledTime}) or dispatch({}) does NOT invoke any handler, fires a cronMalformed event on the sink with metadata {event:\"cronMalformed\", expression:null, scheduledTime, outcome:\"malformed\", duration:0} and returns without side effect.",
+      "given": "a dispatcher wired with two routes",
+      "when": "dispatch is called with a missing or null cron field",
+      "then": "no handler is invoked, a cronMalformed event fires on the sink, and dispatch returns without side effect",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "interfaces.dispatch"
+      }
+    },
+    {
+      "id": "AC-32102-5",
+      "description": "Duplicate expressions refuse: createDispatcher({routes:[{expression:\"* * * * *\", handler:h1}, {expression:\"* * * * *\", handler:h2}], ...}) throws a named error kind CRON_DISPATCHER_DUPLICATE_EXPRESSION at construction time, naming the duplicated expression string. No route is registered.",
+      "given": "a call to createDispatcher with two routes carrying the same expression",
+      "when": "the factory is invoked",
+      "then": "the factory throws CRON_DISPATCHER_DUPLICATE_EXPRESSION naming the duplicated expression",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "interfaces.default export"
+      }
+    },
+    {
+      "id": "AC-32102-6",
+      "description": "Empty routes refuse: createDispatcher({routes:[], sink, ...}) throws a named error kind CRON_DISPATCHER_EMPTY_ROUTES at construction time; no dispatch function is returned.",
+      "given": "a call to createDispatcher with an empty routes array",
+      "when": "the factory is invoked",
+      "then": "the factory throws CRON_DISPATCHER_EMPTY_ROUTES",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "interfaces.default export"
+      }
     }
   ],
-  "tacIds": ["TAC-3302-platform-cloudflare-cron-triggers-expression-router"],
+  "tacIds": [
+    "TAC-3302-platform-cloudflare-cron-triggers-expression-router"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-09T23:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32103.json

@@ -16,7 +16,8 @@
       "when": "an event is dispatched",
       "then": "a cronFired event fires with outcome onTime and no cronSkewed fires",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-32103-2",
@@ -25,10 +26,56 @@
       "when": "an event is dispatched",
       "then": "a cronSkewed event fires with the observed delta and the handler still runs",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-32103-3",
+      "description": "Boundary at exactly skewToleranceMs: with skewToleranceMs=30000 and a clock advanced EXACTLY 30000ms past scheduledTime, dispatch classifies onTime (inclusive boundary) and fires cronFired with outcome:\"onTime\"; no cronSkewed record emits for that dispatch.",
+      "given": "a dispatcher with skewToleranceMs=30000 and a clock at scheduledTime + 30000ms",
+      "when": "an event is dispatched",
+      "then": "a cronFired event fires with outcome:\"onTime\" and no cronSkewed emits",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.skewClassification"
+      }
+    },
+    {
+      "id": "AC-32103-4",
+      "description": "One millisecond past skewToleranceMs: with skewToleranceMs=30000 and a clock advanced 30001ms past scheduledTime, dispatch classifies skewed and fires cronSkewed with deltaMs:30001; the routed handler still runs to completion.",
+      "given": "a dispatcher with skewToleranceMs=30000 and a clock at scheduledTime + 30001ms",
+      "when": "an event is dispatched",
+      "then": "a cronSkewed event fires with deltaMs:30001 and the handler runs",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.skewClassification"
+      }
+    },
+    {
+      "id": "AC-32103-5",
+      "description": "Early fire (clock BEFORE scheduledTime): with skewToleranceMs=30000 and a clock 5000ms before scheduledTime, dispatch classifies onTime and fires cronFired with outcome:\"onTime\"; no cronSkewed record emits and no negative deltaMs ever lands on the sink (the skew signal is lateness-only).",
+      "given": "a dispatcher with skewToleranceMs=30000 and a clock at scheduledTime - 5000ms",
+      "when": "an event is dispatched",
+      "then": "a cronFired event fires with outcome:\"onTime\" and no cronSkewed emits with a negative deltaMs",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.skewClassification"
+      }
     }
   ],
-  "tacIds": ["TAC-3302-platform-cloudflare-cron-triggers-expression-router", "TAC-3303-platform-cloudflare-cron-triggers-event-sink"],
+  "tacIds": [
+    "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+    "TAC-3303-platform-cloudflare-cron-triggers-event-sink"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-09T22:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32104.json

@@ -16,7 +16,8 @@
       "when": "an event is dispatched",
       "then": "exactly one cronStalled event fires with the observed duration at or past the budget",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
     },
     {
       "id": "AC-32104-2",
@@ -25,10 +26,70 @@
       "when": "an event is dispatched",
       "then": "the handler runs to completion and a cronFired follows the cronStalled record",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-32104-3",
+      "description": "Handler throws BEFORE the soft-budget crossing: with softBudgetMs=100 and a spy handler that rejects at 50ms of fake-clock time with an application error, the dispatcher fires exactly one cronFailed event on the sink with {event:\"cronFailed\", expression, scheduledTime, outcome:\"failed\", duration:>=50}; no cronStalled and no cronFired emits for that dispatch. The error propagates through the returned dispatch promise.",
+      "given": "a dispatcher with softBudgetMs=100 and a spy handler that rejects at 50ms of fake-clock time",
+      "when": "an event is dispatched",
+      "then": "exactly one cronFailed event fires with outcome:\"failed\"; no cronStalled or cronFired emits",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.softBudget"
+      }
+    },
+    {
+      "id": "AC-32104-4",
+      "description": "Handler throws AFTER the soft-budget crossing: with softBudgetMs=100 and a spy handler that rejects at 250ms of fake-clock time, the dispatcher fires cronStalled at the 100ms crossing then cronFailed at the 250ms rejection with {outcome:\"failed\", duration:>=250}; no cronFired emits for that dispatch.",
+      "given": "a dispatcher with softBudgetMs=100 and a spy handler that rejects at 250ms of fake-clock time",
+      "when": "an event is dispatched",
+      "then": "cronStalled fires at 100ms, cronFailed fires at 250ms, and no cronFired emits",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.softBudget"
+      }
+    },
+    {
+      "id": "AC-32104-5",
+      "description": "Exact-boundary at softBudgetMs: with softBudgetMs=100 and a spy handler that resolves at EXACTLY 100ms of fake-clock time, the dispatcher fires cronFired only (no cronStalled). The soft-budget observer treats the crossing as strict greater-than: a duration equal to softBudgetMs does not trip the stall record.",
+      "given": "a dispatcher with softBudgetMs=100 and a spy handler that resolves at 100ms of fake-clock time",
+      "when": "an event is dispatched",
+      "then": "only cronFired emits; no cronStalled record fires at the boundary",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.softBudget"
+      }
+    },
+    {
+      "id": "AC-32104-6",
+      "description": "Idempotency: a single dispatch produces exactly one cronStalled record even if the internal soft-budget observer re-arms or the setTimeout is re-scheduled. A test that observes the sink after a stall-then-complete cycle finds cronStalled.length === 1 and cronFired.length === 1 for that dispatch.",
+      "given": "a dispatcher with softBudgetMs=100 and a spy handler that resolves at 500ms",
+      "when": "an event is dispatched and the sink is inspected after completion",
+      "then": "cronStalled records for that dispatch count exactly one; cronFired records count exactly one",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+        "field": "responsibilities.softBudget"
+      }
     }
   ],
-  "tacIds": ["TAC-3302-platform-cloudflare-cron-triggers-expression-router", "TAC-3303-platform-cloudflare-cron-triggers-event-sink"],
+  "tacIds": [
+    "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+    "TAC-3303-platform-cloudflare-cron-triggers-event-sink"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-09T22:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32105.json

@@ -11,15 +11,78 @@
   "acceptanceCriteria": [
     {
       "id": "AC-32105-1",
-      "description": "The wrangler-test-scheduled probe spawns wrangler dev --test-scheduled from the cf-platform fixture, waits bounded 30 seconds for the CLI to bind, drives its scheduled-fire endpoint with an expression declared in wrangler.toml, asserts a cronFired event fires on the injected sink with metadata {event, expression, scheduledTime, outcome, duration}, kills wrangler cleanly on exit, and returns aggregateVerdict: pass. On a shipped wrangler regression that prevents --test-scheduled from binding, the probe returns aggregateVerdict: warn with the observed stderr quoted and the mechanism-reach gap noted; the CI does not gate on warn.",
+      "description": "The wrangler-test-scheduled probe spawns wrangler dev --test-scheduled from the cf-platform fixture, waits bounded 30 seconds for the CLI to bind, drives its scheduled-fire endpoint with an expression declared in wrangler.toml, asserts a cronFired event fires on the injected sink with metadata {event, expression, scheduledTime, outcome, duration}, kills wrangler cleanly on exit, and returns aggregateVerdict: pass. On a shipped wrangler regression that prevents --test-scheduled from binding, the probe returns aggregateVerdict: warn with the observed stderr quoted and the mechanism-reach gap noted; AC-32105-2 owns the harness gate on that verdict.",
       "given": "wrangler installed as a devDependency on the cf-platform fixture and the [triggers] crons block declared in wrangler.toml",
       "when": "the probe runs from the fixture directory",
-      "then": "wrangler dev --test-scheduled binds, the scheduled-fire route drives a cronFired event, wrangler exits cleanly, and the probe returns pass (or warn on a documented CLI regression)",
+      "then": "wrangler dev --test-scheduled binds, the scheduled-fire route drives a cronFired event, wrangler exits cleanly, and the probe returns pass (or warn on a documented CLI regression, which AC-32105-2 gates)",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-32105-2",
+      "description": "CI gate on bind or fire failures: the probe harness at packages/rcf-lite/test/blueprint/platform-cloudflare-cron-triggers-anatomy.test.js treats aggregateVerdict !== \"pass\" (including \"warn\" AND \"fail\") as a hard gate failure and exits non-zero. A wrangler regression that would otherwise return warn surfaces as a red CI check on the branch, per the operator ruling that documented failure paths are ACs, not warnings.",
+      "given": "the probe harness invoked from packages/rcf-lite/test/blueprint under Node 24",
+      "when": "the probe returns aggregateVerdict warn or fail",
+      "then": "the anatomy test asserts verdict === \"pass\" and exits non-zero on any other value",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      },
+      "vendorCitation": {
+        "url": "https://developers.cloudflare.com/workers/wrangler/commands/",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-32105-3",
+      "description": "Bounded-wait timeout: if wrangler dev --test-scheduled does not bind within the 30-second cap, the probe kills the child, records the observed stderr and returns aggregateVerdict:\"fail\" with a reason field naming CRON_WRANGLER_BIND_TIMEOUT. Under AC-32105-2 the CI harness treats this as a hard failure.",
+      "given": "a probe run where wrangler cannot bind within 30 seconds (simulated by an invalid PORT or a stubbed missing binary)",
+      "when": "the probe caps the wait at 30 seconds",
+      "then": "the probe returns aggregateVerdict \"fail\" with reason CRON_WRANGLER_BIND_TIMEOUT and the observed stderr",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      }
+    },
+    {
+      "id": "AC-32105-4",
+      "description": "Wrangler exits non-zero mid-run: if the wrangler child exits with a non-zero code during the probe (crash after bind), the probe surfaces the observed exit code and stderr and returns aggregateVerdict:\"fail\". Under AC-32105-2 the CI harness treats this as a hard failure.",
+      "given": "a probe run where wrangler crashes after binding (simulated by SIGTERM injection)",
+      "when": "the probe observes the child exit",
+      "then": "aggregateVerdict is \"fail\" with the exit code and stderr in the reason field",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      }
+    },
+    {
+      "id": "AC-32105-5",
+      "description": "Probe teardown: the probe kills the wrangler child on exit (normal or exceptional) via SIGTERM followed by SIGKILL after a 2-second grace period. A test that interrupts the probe with a rejection at the assertion step still observes the wrangler child terminated within 3 seconds.",
+      "given": "a probe run that is interrupted by an assertion rejection after the CLI binds",
+      "when": "the probe teardown runs",
+      "then": "the wrangler child is terminated within 3 seconds; no orphan process remains",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      }
     }
   ],
-  "tacIds": ["TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"],
+  "tacIds": [
+    "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-09T23:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32106.json

@@ -16,10 +16,69 @@
       "when": "the shipped code path runs without the switch; the mutation path runs with SIMULATE_PII_LEAK=true",
       "then": "shipped: aggregateVerdict pass with zero forbidden keys and zero PII hits. Switch on: aggregateVerdict fail with the leaked fields named.",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-32106-2",
+      "description": "Allow-list boundary: an event record whose top-level keys include ANY key outside the allow-list {event, expression, scheduledTime, outcome, duration, softBudgetMs, deltaMs} fails layer 1 of the event-secrecy probe. Under SIMULATE_PII_LEAK=true a wrapped sink adds a \"handlerInput\" key onto every record and the probe surfaces the forbidden key by name, returning aggregateVerdict:\"fail\".",
+      "given": "the event-secrecy probe run under SIMULATE_PII_LEAK=true",
+      "when": "the wrapper sink adds a forbidden key onto every record",
+      "then": "layer 1 asserts fail naming the forbidden key; aggregateVerdict is \"fail\"",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3303-platform-cloudflare-cron-triggers-event-sink",
+        "field": "responsibilities.allowList"
+      }
+    },
+    {
+      "id": "AC-32106-3",
+      "description": "Empty payload boundary: a spy handler that receives NO domain payload (all inputs undefined) still produces cronFired records carrying every required key {event, expression, scheduledTime, outcome, duration}. No allow-list key is silently dropped when the payload is empty; expression is the wrangler-supplied string, scheduledTime the observed millis, outcome \"onTime\" or the classified value.",
+      "given": "the dispatcher run against a spy handler with an undefined input payload",
+      "when": "a dispatch fires",
+      "then": "the cronFired record carries all five required allow-list keys with non-null values (except where the vocabulary permits null)",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3303-platform-cloudflare-cron-triggers-event-sink",
+        "field": "responsibilities.allowList"
+      }
+    },
+    {
+      "id": "AC-32106-4",
+      "description": "Expression literal is not PII: the layer-2 substring scan explicitly excludes the expression field from the PII test because the expression string is a legitimate literal copied from wrangler.toml. A layer-2 test with a wrangler.toml expression containing the digits \"12345\" (which also appear in the PII fixture body) does not trip the scan; the exclusion is documented in the probe source.",
+      "given": "the event-secrecy probe with a wrangler expression carrying the digits \"12345\" and a PII fixture SSN containing the same digits",
+      "when": "the layer-2 substring scan runs",
+      "then": "the expression field is excluded from the scan and no false-positive PII hit fires",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3303-platform-cloudflare-cron-triggers-event-sink",
+        "field": "responsibilities.allowList"
+      }
+    },
+    {
+      "id": "AC-32106-5",
+      "description": "Closure-over-fixture: a spy handler that captures a PII fixture ({userId, ssn}) via a JavaScript closure and mutates a scratch object each call still produces sink records whose JSON serialisation contains no userId or ssn substring. The layer-2 scan on the shipped path returns zero hits; layer 1 returns zero forbidden keys. Aggregate: pass.",
+      "given": "a spy handler closing over a PII fixture on the shipped path",
+      "when": "the event-secrecy probe runs without the mutation switch",
+      "then": "the layer-1 and layer-2 scans return zero hits and aggregateVerdict is \"pass\"",
+      "testable": true,
+      "scope": "runtime",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3303-platform-cloudflare-cron-triggers-event-sink",
+        "field": "responsibilities.allowList"
+      }
     }
   ],
-  "tacIds": ["TAC-3303-platform-cloudflare-cron-triggers-event-sink"],
+  "tacIds": [
+    "TAC-3303-platform-cloudflare-cron-triggers-event-sink"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-09T22:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/contributions/user-stories/platform-cloudflare-cron-triggers-us-32107.json

@@ -16,10 +16,63 @@
       "when": "the probe runs",
       "then": "with the account: a scheduled event is observed within 90s and the probe passes. Without the account: the probe records accountBoundSkipped: true and exits 0.",
       "testable": true,
-      "scope": "runtime"
+      "scope": "runtime",
+      "disposition": "fixed"
+    },
+    {
+      "id": "AC-32107-2",
+      "description": "Bounded-wait timeout on the real-account probe: if the 90-second poll observes no scheduled event, the probe returns aggregateVerdict:\"fail\" with a reason field naming CRON_REAL_ACCOUNT_NO_FIRE, the observed poll count and the last response body from the Cloudflare observability API.",
+      "given": "a real Cloudflare account with the paired env vars, and a Worker whose cron trigger fails to fire for 90+ seconds",
+      "when": "the probe polls the Analytics or observability API every 5 seconds up to 90 seconds",
+      "then": "the probe returns aggregateVerdict:\"fail\" naming CRON_REAL_ACCOUNT_NO_FIRE and the last response body",
+      "testable": true,
+      "scope": "deployed",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      },
+      "vendorCitation": {
+        "url": "https://developers.cloudflare.com/workers/configuration/cron-triggers/",
+        "verifiedOn": "2026-09-09"
+      }
+    },
+    {
+      "id": "AC-32107-3",
+      "description": "Partial env-var configuration: with CI_HAS_CLOUDFLARE_ACCOUNT=true set but CF_API_TOKEN missing, the probe refuses BEFORE making any API request with a named error kind CF_MISSING_TOKEN naming the missing env var. Same for CF_ACCOUNT_ID or CF_WORKER_NAME missing.",
+      "given": "CI_HAS_CLOUDFLARE_ACCOUNT=true and CF_API_TOKEN unset",
+      "when": "the probe runs",
+      "then": "the probe refuses with CF_MISSING_TOKEN naming the missing variable and exits non-zero",
+      "testable": true,
+      "scope": "deployed",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      }
+    },
+    {
+      "id": "AC-32107-4",
+      "description": "Non-2xx API response: if the Cloudflare Analytics or observability API returns a non-2xx status (401, 403, 429 or 5xx) during polling, the probe surfaces the observed status and response body and returns aggregateVerdict:\"fail\" with reason CF_ANALYTICS_HTTP_ERROR. The probe does not retry on 4xx; it retries once on 5xx before failing.",
+      "given": "a real-account probe run where the Analytics API returns 403",
+      "when": "the probe polls",
+      "then": "aggregateVerdict:\"fail\" with reason CF_ANALYTICS_HTTP_ERROR, HTTP status and body in the record",
+      "testable": true,
+      "scope": "deployed",
+      "disposition": "fixed",
+      "ownerRef": {
+        "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+        "field": "interfaces.default export"
+      },
+      "vendorCitation": {
+        "url": "https://developers.cloudflare.com/workers/platform/limits/",
+        "verifiedOn": "2026-09-09"
+      }
     }
   ],
-  "tacIds": ["TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"],
+  "tacIds": [
+    "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"
+  ],
   "createdAt": "2026-09-07T12:35:00.000Z",
-  "updatedAt": "2026-09-07T12:35:00.000Z"
+  "updatedAt": "2026-09-09T22:00:00.000Z"
 }

package/blueprints/platform-cloudflare-cron-triggers/docs/topics.md

@@ -6,7 +6,7 @@ This file is the platform-cloudflare-cron-triggers half of the cross-blueprint c
 
 | Topic string | platform-cloudflare-cron-triggers contribution | Origin | Composition note |
 |---|---|---|---|
-| `scheduledTriggerContract` | ADR-3301-platform-cloudflare-cron-triggers-scheduled-trigger-contract | Minted by this blueprint. Names the wire-shape contract for a scheduled trigger the applied Workers project reads through the scheduled() handler; the shipped answer is Cloudflare Workers Cron Triggers per https://developers.cloudflare.com/workers/configuration/cron-triggers/. | The one project-wide decision on the scheduled-trigger contract at the handler boundary. A future non-Cron-Triggers scheduler (a cross-region cron on a different platform, a durable-workflow scheduler on the round-6 T-3 Durable Objects sibling, the round-6 Workflows adapter on jobs-background v1.1.0 per spec section 5.7) would contribute the same topic string with a different answer, forcing a DELIBERATE conflict the operator resolves with a project-level ADR |
+| `scheduledTriggerContract` | ADR-3301-platform-cloudflare-cron-triggers-scheduled-trigger-contract | Minted by this blueprint. Names the wire-shape contract for a scheduled trigger the applied Workers project reads through the scheduled() handler; the shipped answer is Cloudflare Workers Cron Triggers per https://developers.cloudflare.com/workers/configuration/cron-triggers/. | The one project-wide decision on the scheduled-trigger contract at the handler boundary. A future non-Cron-Triggers scheduler (a cross-region cron on a different platform, a durable-workflow scheduler on the round-6 Durable Objects sibling, the round-6 Workflows adapter on jobs-background v1.1.0 per spec section 5.7) would contribute the same topic string with a different answer, forcing a DELIBERATE conflict the operator resolves with a project-level ADR |
 
 The platform-cloudflare-cron-triggers blueprint claims one global topic. Every other contribution is scope-local (ADR-3302 dispatcher mode and ADR-3303 default skew tolerance do not contribute global topics; a composing blueprint that holds an opinion on either authors its own project-level ADR).
 
@@ -66,8 +66,8 @@ ADR/TAC suffixes for this blueprint use the 3301-3399 block, continuing the shel
 ## Shared expectations for future composing blueprints
 
 - Reuse `scheduledTriggerContract` exactly as spelled here when your blueprint holds an opinion on the scheduled-trigger contract at the handler boundary; contribute your own scope:global ADR on that string and let composition surface the pairing.
-- A future non-Cron-Triggers scheduler (a cross-region cron on a different platform, a durable-workflow scheduler on the round-6 T-3 Durable Objects sibling, the round-6 Workflows adapter on jobs-background v1.1.0 per spec section 5.7) mints on demand; each claims `scheduledTriggerContract` and conflicts by design.
-- Consumer blueprints reading the `scheduledTrigger` capability declared on `blueprint.json` per section 6a of `blueprint-authoring.md` obtain the scheduled handler wiring at apply time via the T-5 visual-round capability-declaration mechanism.
+- A future non-Cron-Triggers scheduler (a cross-region cron on a different platform, a durable-workflow scheduler on the round-6 Durable Objects sibling, the round-6 Workflows adapter on jobs-background v1.1.0 per spec section 5.7) mints on demand; each claims `scheduledTriggerContract` and conflicts by design.
+- Consumer blueprints reading the `scheduledTrigger` capability declared on `blueprint.json` per section 6a of `blueprint-authoring.md` obtain the scheduled handler wiring at apply time via the visual-round capability-declaration mechanism.
 
 ## Deliberate-conflict statement