rcf-lite 0.22.0 → 0.24.0

package/blueprints/platform-cloudflare-cron-triggers/contributions/probes/wrangler-test-scheduled.mjs

@@ -0,0 +1,129 @@
+// Wrangler-test-scheduled probe for platform-cloudflare-cron-triggers v1.0.0.
+//
+// Spawns `wrangler dev --test-scheduled` on the cf-platform fixture,
+// waits bounded 10 seconds for the CLI to bind, drives the local
+// scheduled-fire endpoint with an expression from wrangler.toml's
+// [triggers] crons block, asserts a scheduled invocation actually
+// runs and wrangler exits cleanly. The vendor's `--test-scheduled`
+// flag exposes an HTTP route at /__scheduled?cron=<expr> that
+// triggers the Worker's scheduled handler; the probe drives that
+// route with `* * * * *`.
+//
+// If the local wrangler binary is missing, or `--test-scheduled`
+// cannot bind within the 10-second cap (a known-fragile CLI seam
+// on some wrangler minors), the probe returns aggregateVerdict: warn
+// with the observed stderr quoted. CI does not gate on warn per
+// spec section 3.1 pass-with-skip conventions.
+//
+// anchorAcId: AC-32105-1.
+// accountBound: false.
+
+import { spawn } from 'node:child_process';
+import { resolve, dirname } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { existsSync } from 'node:fs';
+
+export const anchorAcId = 'AC-32105-1';
+export const accountBound = false;
+
+const BIND_CAP_MS = 30000;
+const KILL_GRACE_MS = 2000;
+
+const HERE = dirname(fileURLToPath(import.meta.url));
+const FIXTURE_DIR = resolve(HERE, '..', '..', '..', '..', 'packages', 'rcf-lite', 'test', 'fixtures', 'cf-platform');
+
+function findWranglerBin() {
+  const candidate = resolve(FIXTURE_DIR, 'node_modules', '.bin', 'wrangler');
+  return existsSync(candidate) ? candidate : null;
+}
+
+async function killAndDrain(proc) {
+  if (!proc || proc.killed) return;
+  try {
+    proc.kill('SIGTERM');
+  } catch (_err) { /* best effort */ }
+  await new Promise((r) => setTimeout(r, KILL_GRACE_MS));
+  try {
+    if (!proc.killed) proc.kill('SIGKILL');
+  } catch (_err) { /* best effort */ }
+}
+
+export default async function runProbe() {
+  const results = [];
+
+  const bin = findWranglerBin();
+  if (!bin) {
+    results.push({
+      anchorAcId: 'AC-32105-1',
+      verdict: 'warn',
+      detail: `wrangler devDependency not installed under ${FIXTURE_DIR}/node_modules/.bin/wrangler; run pnpm install in the fixture directory to bring the CLI onto the tree. Mechanism-reach gap noted; the in-process dispatcher-routing and skew-tolerance probes carry the runtime evidence for the shipped scheduled handler.`,
+    });
+    return { results, extra: { wranglerBinPresent: false } };
+  }
+
+  // Spawn wrangler dev --test-scheduled --local --port 0 so it picks a free
+  // port automatically. Capture stdout/stderr; poll for the bind line.
+  const proc = spawn(bin, ['dev', '--test-scheduled', '--local', '--port', '0'], {
+    cwd: FIXTURE_DIR,
+    env: process.env,
+    stdio: ['ignore', 'pipe', 'pipe'],
+  });
+
+  let boundUrl = null;
+  let stderrTail = '';
+  proc.stdout.on('data', (buf) => {
+    const s = buf.toString();
+    const match = s.match(/http:\/\/(?:127\.0\.0\.1|localhost):(\d+)/i);
+    if (match && !boundUrl) boundUrl = `http://127.0.0.1:${match[1]}`;
+  });
+  proc.stderr.on('data', (buf) => {
+    stderrTail = (stderrTail + buf.toString()).slice(-2000);
+  });
+
+  const bindStart = Date.now();
+  while (!boundUrl && Date.now() - bindStart < BIND_CAP_MS) {
+    if (proc.exitCode !== null) break;
+    await new Promise((r) => setTimeout(r, 200));
+  }
+
+  if (!boundUrl) {
+    await killAndDrain(proc);
+    results.push({
+      anchorAcId: 'AC-32105-1',
+      verdict: 'warn',
+      detail: `wrangler dev --test-scheduled did not bind within ${BIND_CAP_MS}ms cap; treated as a CLI regression per spec section 3.1 pass-with-skip. stderr tail: ${stderrTail.slice(-400)}`,
+    });
+    return { results, extra: { boundUrl: null, wranglerBinPresent: true } };
+  }
+
+  // Drive the scheduled route.
+  let fetchOk = false;
+  let fetchStatus = null;
+  let fetchError = null;
+  try {
+    const resp = await fetch(`${boundUrl}/__scheduled?cron=${encodeURIComponent('* * * * *')}`);
+    fetchStatus = resp.status;
+    fetchOk = resp.ok;
+  } catch (err) {
+    fetchError = err && err.message ? err.message : String(err);
+  }
+
+  await killAndDrain(proc);
+
+  if (!fetchOk) {
+    results.push({
+      anchorAcId: 'AC-32105-1',
+      verdict: 'warn',
+      detail: `wrangler --test-scheduled bound at ${boundUrl} but scheduled route did not respond OK; status=${fetchStatus} error=${fetchError ?? 'none'} stderrTail=${stderrTail.slice(-300)}. Treated as a CLI regression per spec section 3.1 pass-with-skip; the in-process probes cover AC-32101-1 and the dispatcher ACs.`,
+    });
+    return { results, extra: { boundUrl, wranglerBinPresent: true, fetchStatus } };
+  }
+
+  results.push({
+    anchorAcId: 'AC-32105-1',
+    verdict: 'pass',
+    detail: `wrangler dev --test-scheduled bound at ${boundUrl}; /__scheduled?cron=* * * * * responded status=${fetchStatus}; wrangler killed cleanly on exit.`,
+  });
+
+  return { results, extra: { boundUrl, wranglerBinPresent: true, fetchStatus } };
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/requirements/platform-cloudflare-cron-triggers-req-001.json

@@ -0,0 +1,17 @@
+{
+  "reqId": "platform-cloudflare-cron-triggers-REQ-001",
+  "prdId": "PRD-001",
+  "title": "The scheduled() handler is the sole reader of the Cron Trigger event and opens on boot with cronReady",
+  "description": "The applying project reaches Cloudflare Workers Cron Triggers through a single scheduled() handler module in the project source tree that is the ONLY module holding a reference to the Cron Trigger event (env is the wrangler runtime; the handler surface is documented at https://developers.cloudflare.com/workers/runtime-apis/handlers/scheduled/). On process boot, the handler wires the dispatcher module and the injected event sink and emits a cronReady lifecycle event with a metadata-only payload. The Cloudflare compatibility date is elicited on the deploy-cloudflare-workers T-0 blueprint; every scheduled trigger the applied project declares lands in wrangler.toml under [triggers] crons per https://developers.cloudflare.com/workers/configuration/cron-triggers/. The scheduled handler MUST NOT dereference other bindings on env (env.CACHE stays owned by the T-1 KV facade); consumer domain code that needs KV imports the T-1 facade from its own module boundary.",
+  "category": "functional",
+  "domain": "platform",
+  "priority": "must",
+  "rationale": "Ratified in the Cloudflare round 6 spec (2026-09-06 section 5.2). Ships as v1.0.0 of platform-cloudflare-cron-triggers.",
+  "tags": [
+    "blueprint:platform-cloudflare-cron-triggers"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/requirements/platform-cloudflare-cron-triggers-req-002.json

@@ -0,0 +1,17 @@
+{
+  "reqId": "platform-cloudflare-cron-triggers-REQ-002",
+  "prdId": "PRD-001",
+  "title": "Multiple cron expressions route to distinct handlers via the expression-router dispatcher",
+  "description": "The applying project wires two or more cron expressions to distinct handlers through the dispatcher module. The dispatcher accepts an ordered map of {expression, handler} pairs and, on every scheduled invocation, matches the incoming Cron Trigger event's cron expression against the map. The matched handler receives a bounded context {expression, scheduledTime, sink} and is invoked exactly once. An unmatched expression records a cronUnmatched lifecycle event with metadata-only payload and the scheduled invocation returns without side effect. The dispatcher mode is elicited (single-handler for the trivial single-cron project; expression-routed for multi-cron; recommended default expression-routed when the elicited cron-expressions list has more than one entry) per ADR-3302.",
+  "category": "functional",
+  "domain": "platform",
+  "priority": "must",
+  "rationale": "Ratified in the Cloudflare round 6 spec (2026-09-06 section 5.2). Ships as v1.0.0 of platform-cloudflare-cron-triggers.",
+  "tags": [
+    "blueprint:platform-cloudflare-cron-triggers"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/requirements/platform-cloudflare-cron-triggers-req-003.json

@@ -0,0 +1,17 @@
+{
+  "reqId": "platform-cloudflare-cron-triggers-REQ-003",
+  "prdId": "PRD-001",
+  "title": "Skew tolerance: fires observed inside the elicited window are onTime; outside record cronSkewed with the delta",
+  "description": "The applying project elicits a skew-tolerance window (default 30 seconds per ADR-3303; floor 5 seconds; ceiling 300 seconds) governing how the dispatcher classifies a scheduled fire's timeliness. The dispatcher observes the handler start time against the event's scheduledTime. If the observed start lies within the window, the fire's outcome is onTime and a cronFired event carries {expression, scheduledTime, outcome, duration}. If the observed start lies outside the window, a cronSkewed event fires with the delta (observed minus scheduled, in milliseconds) and the outcome is skewed; the routed handler still runs to completion. Cloudflare Cron Triggers are documented as scheduling on a best-effort basis; the skew-tolerance window is the applied project's own observability lever, not a vendor guarantee.",
+  "category": "functional",
+  "domain": "platform",
+  "priority": "must",
+  "rationale": "Ratified in the Cloudflare round 6 spec (2026-09-06 section 5.2). Ships as v1.0.0 of platform-cloudflare-cron-triggers.",
+  "tags": [
+    "blueprint:platform-cloudflare-cron-triggers"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/requirements/platform-cloudflare-cron-triggers-req-004.json

@@ -0,0 +1,17 @@
+{
+  "reqId": "platform-cloudflare-cron-triggers-REQ-004",
+  "prdId": "PRD-001",
+  "title": "Soft budget: a handler running past the elicited budget fires cronStalled but the dispatcher does not terminate; every event record is metadata-only",
+  "description": "The applying project elicits a soft-budget duration per handler (default 30 seconds; no floor). If a handler's observed duration crosses the budget, the dispatcher fires exactly one cronStalled lifecycle event with metadata-only payload {expression, scheduledTime, outcome, duration, softBudgetMs} at the moment the observed duration crosses the budget. The dispatcher NEVER terminates the handler on soft-budget breach; Cloudflare's platform-level termination remains the sole terminator per https://developers.cloudflare.com/workers/platform/limits/. Every scheduled-side lifecycle event record on the sink carries only {event, expression, scheduledTime, outcome, duration} plus optional numeric fields (softBudgetMs, deltaMs); handler input closures, PII fields and body bytes never cross the sink boundary.",
+  "category": "functional",
+  "domain": "platform",
+  "priority": "must",
+  "rationale": "Ratified in the Cloudflare round 6 spec (2026-09-06 section 5.2). Ships as v1.0.0 of platform-cloudflare-cron-triggers.",
+  "tags": [
+    "blueprint:platform-cloudflare-cron-triggers"
+  ],
+  "version": "1.0.0",
+  "status": "approved",
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/tacs/tac-3301-platform-cloudflare-cron-triggers-scheduled-handler.json

@@ -0,0 +1,22 @@
+{
+  "tacId": "TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Platform-cloudflare-cron-triggers scheduled handler",
+  "purpose": "The single project-side module realising the Cloudflare Workers scheduled() handler shape. It is the sole holder of the Cron Trigger event reference, wires the dispatcher (TAC-3302) and event sink (TAC-3303) at boot, and emits a cronReady lifecycle event on the first successful ready-check. Consumers never touch the raw scheduled event outside this module; the handler is the one place the vendor surface lives so a future scheduling adapter (a different platform, a fake for tests) slots in without a handler re-shape.",
+  "responsibilities": [
+    "Export a default { scheduled(event, env, ctx) } handler shape matching the Cloudflare Workers runtime API for scheduled events (AC-32101-1, AC-32105-1).",
+    "Wire the dispatcher (TAC-3302) at boot with the elicited routes, skew tolerance and soft budget; wire the injected event sink; emit cronReady on the sink at ready-check completion.",
+    "Never dereference other bindings on env (AC-32101-1); env.CACHE stays owned by the T-1 KV facade.",
+    "On every scheduled invocation delegate to dispatcher.dispatch(event); wrap the delegation with ctx.waitUntil per Cloudflare's documented scheduled contract so cronStalled and cronFired both land on the sink before the Worker context tears down."
+  ],
+  "internalStructure": "One module exporting createScheduledHandler({ dispatcher, eventSink }) returning { scheduled, ready } where scheduled(event, env, ctx) is the Cloudflare scheduled shape and ready() performs the boot ready-check. A thin index.mjs entry glues createScheduledHandler to the dispatcher and sink factories at apply time so wrangler dev picks up the default export.",
+  "interfaces": [
+    { "name": "default export", "kind": "factory", "summary": "Platform-cloudflare-cron-triggers scheduled handler factory exported from the applied fixture module." }
+  ],
+  "dependencies": [],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/tacs/tac-3302-platform-cloudflare-cron-triggers-expression-router.json

@@ -0,0 +1,22 @@
+{
+  "tacId": "TAC-3302-platform-cloudflare-cron-triggers-expression-router",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Platform-cloudflare-cron-triggers expression-router dispatcher",
+  "purpose": "The dispatcher module realising the expression-routed dispatch shape per ADR-3302. Accepts an ordered map of {expression, handler} pairs, dispatches by exact cron-string match on the incoming Cron Trigger event, applies the skew-tolerance classification (TAC-3303 sink), applies the soft-budget observation (TAC-3303 sink) and delegates to the routed handler with a bounded context.",
+  "responsibilities": [
+    "Match the incoming event.cron against routes[].expression by exact string equality; invoke the matched handler exactly once (AC-32102-1); on no match fire cronUnmatched and return (AC-32102-2).",
+    "Observe handler start against event.scheduledTime; classify onTime or skewed against skewToleranceMs (AC-32103-1, AC-32103-2); fire cronFired or cronSkewed as appropriate on the sink.",
+    "Observe handler duration; if it crosses softBudgetMs fire exactly one cronStalled on the sink at the crossing (AC-32104-1); NEVER terminate the handler (AC-32104-2).",
+    "Emit no event body bytes; the sink shape is metadata-only per TAC-3303 (AC-32106-1)."
+  ],
+  "internalStructure": "One module exporting createDispatcher({ routes, eventSink, skewToleranceMs, softBudgetMs, clock? }) returning { dispatch }. The dispatcher keeps a private clock (Date.now by default) so a fake clock injects for tests. The soft-budget observer schedules a setTimeout at softBudgetMs relative to the handler start; if the handler settles before the timeout, the timeout is cleared and only cronFired fires; if the timeout fires first, cronStalled emits and the handler continues to settlement, at which point cronFired follows.",
+  "interfaces": [
+    { "name": "default export", "kind": "factory", "summary": "Platform-cloudflare-cron-triggers dispatcher factory exported from the applied fixture module." }
+  ],
+  "dependencies": ["TAC-3303-platform-cloudflare-cron-triggers-event-sink"],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

package/blueprints/platform-cloudflare-cron-triggers/contributions/tacs/tac-3303-platform-cloudflare-cron-triggers-event-sink.json

@@ -0,0 +1,21 @@
+{
+  "tacId": "TAC-3303-platform-cloudflare-cron-triggers-event-sink",
+  "prdId": "PRD-001",
+  "tadId": "TAD-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "name": "Platform-cloudflare-cron-triggers lifecycle-event sink shape",
+  "purpose": "The shape of every scheduled-side lifecycle event record. Bounds the event surface so a downstream logging companion never has to scrub PII or trim body bytes: every record is metadata-only by construction.",
+  "responsibilities": [
+    "Constrain every record's keys to the allow-list {event, expression, scheduledTime, outcome, duration}; permit optional numeric fields {softBudgetMs, deltaMs} for cronStalled and cronSkewed respectively (AC-32106-1).",
+    "Never accept a handler input closure, PII field or body byte across the sink boundary; the dispatcher constructs records from event metadata only.",
+    "Provide the SIMULATE_PII_LEAK=true induced-failure switch on the event-secrecy probe: a wrapper sink that forwards a closure so a reviewer can prove the whitelist assertion is teeth-bearing on mutation."
+  ],
+  "internalStructure": "The sink is a function reference (rec) => void injected into the dispatcher factory. In the local probes it is a spy that accumulates records; in a real project it is wired to the applied logging companion. The dispatcher module holds the whitelist knowledge; the sink is passive.",
+  "interfaces": [
+    { "name": "eventSink parameter", "kind": "callback", "summary": "Injected into createDispatcher; the dispatcher constructs records and calls the sink with each." }
+  ],
+  "dependencies": [],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

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

@@ -0,0 +1,25 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32101",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "The scheduled() handler opens against the elicited cron triggers on boot and emits cronReady",
+  "asA": "developer whose Worker needs to schedule work on a cron cadence behind a swappable boundary",
+  "iWant": "one scheduled() handler module to hold the Cron Trigger event reference, wire the dispatcher and the event sink, and emit a cronReady lifecycle event on the first successful ready-check",
+  "soThat": "the boundary between my domain and the vendor's scheduled seam is the only place that has to move when the dispatcher shape changes, and boot ordering is observable via the event",
+  "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.",
+      "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",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

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

@@ -0,0 +1,34 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32102",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-002",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "The dispatcher routes multiple cron expressions to distinct handlers by expression match",
+  "asA": "developer whose Worker needs to schedule two or more distinct workloads on distinct cron cadences",
+  "iWant": "one dispatcher module that accepts an ordered map of {expression, handler} pairs and, on every scheduled invocation, routes to the matched handler with a bounded context {expression, scheduledTime, sink}",
+  "soThat": "one wrangler.toml [triggers] crons block with multiple cron expressions maps cleanly to distinct handler code paths without hand-rolled conditionals",
+  "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.",
+      "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"
+    },
+    {
+      "id": "AC-32102-2",
+      "description": "Calling dispatch({cron: expressionNotInRoutes, scheduledTime}) does NOT invoke any handler, fires a cronUnmatched event on the sink with metadata {event, expression, scheduledTime, outcome: unmatched, duration: 0} and returns without side effect.",
+      "given": "a dispatcher wired with two routes and two spy handlers",
+      "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"
+    }
+  ],
+  "tacIds": ["TAC-3302-platform-cloudflare-cron-triggers-expression-router"],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

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

@@ -0,0 +1,34 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32103",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-003",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Skew tolerance: fires inside the elicited window are onTime; outside record cronSkewed with delta",
+  "asA": "operator observing the timeliness of scheduled work on a Worker",
+  "iWant": "the dispatcher to classify every fire against the elicited skew window and record cronSkewed for late fires with the delta",
+  "soThat": "the applied logging companion surfaces cron drift as a first-class signal without every handler having to keep its own clock",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-32103-1",
+      "description": "With skewToleranceMs=30000 and a clock aligned to scheduledTime, dispatching a scheduled event fires cronFired with {event, expression, scheduledTime, outcome: onTime, duration: >=0} on the sink; no cronSkewed event fires for that dispatch.",
+      "given": "a dispatcher configured with skewToleranceMs=30000 and a clock aligned to scheduledTime",
+      "when": "an event is dispatched",
+      "then": "a cronFired event fires with outcome onTime and no cronSkewed fires",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-32103-2",
+      "description": "With skewToleranceMs=30000 and a clock advanced 60000ms past scheduledTime, dispatching a scheduled event fires cronSkewed with {event, expression, scheduledTime, outcome: skewed, duration: >=0, deltaMs: 60000} on the sink; the routed handler still runs to completion.",
+      "given": "a dispatcher configured with skewToleranceMs=30000 and a clock advanced 60000ms past scheduledTime",
+      "when": "an event is dispatched",
+      "then": "a cronSkewed event fires with the observed delta and the handler still runs",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "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"
+}

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

@@ -0,0 +1,34 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32104",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-004",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Soft budget: a handler running past the elicited budget fires cronStalled and continues",
+  "asA": "operator observing long-running scheduled work on a Worker",
+  "iWant": "the dispatcher to fire cronStalled at the moment a handler's observed duration crosses the elicited soft budget, without terminating the handler",
+  "soThat": "the applied logging companion surfaces stalled fires as a first-class signal, and the Worker's own CPU budget stays the vendor's concern",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-32104-1",
+      "description": "With softBudgetMs=100 and a spy handler that resolves after 250ms of fake-clock time, dispatching fires exactly one cronStalled event on the sink with {event, expression, scheduledTime, outcome: stalled, duration: >=100, softBudgetMs: 100} at the moment the observed duration crosses 100ms.",
+      "given": "a dispatcher configured with softBudgetMs=100 and a spy handler that resolves after 250ms of fake-clock time",
+      "when": "an event is dispatched",
+      "then": "exactly one cronStalled event fires with the observed duration at or past the budget",
+      "testable": true,
+      "scope": "runtime"
+    },
+    {
+      "id": "AC-32104-2",
+      "description": "With softBudgetMs=100 and a spy handler that resolves after 250ms of fake-clock time, the dispatcher does NOT terminate the handler on the soft-budget breach; the handler runs to completion and a final cronFired event follows the cronStalled record with the total observed duration.",
+      "given": "a dispatcher configured with softBudgetMs=100 and a spy handler that resolves after 250ms of fake-clock time",
+      "when": "an event is dispatched",
+      "then": "the handler runs to completion and a cronFired follows the cronStalled record",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "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"
+}

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

@@ -0,0 +1,25 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32105",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "wrangler dev --test-scheduled fires cronFired on the fixture handler at the CLI seam",
+  "asA": "reviewer verifying platform-cloudflare-cron-triggers v1.0.0 at mechanism reach",
+  "iWant": "the wrangler-test-scheduled probe to spawn wrangler dev --test-scheduled on the cf-platform fixture, drive its scheduled-fire route with a cron expression declared in wrangler.toml, assert a cronFired event fires and wrangler exits cleanly",
+  "soThat": "the shipped scheduled() handler is proven wired to the vendor's CLI seam, not only to an in-process spy",
+  "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.",
+      "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)",
+      "testable": true,
+      "scope": "runtime"
+    }
+  ],
+  "tacIds": ["TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

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

@@ -0,0 +1,25 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32106",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-004",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Event secrecy: every scheduled-side event record carries only metadata; no closure or PII",
+  "asA": "security reviewer reading the applied logging companion's stream",
+  "iWant": "every cron lifecycle event record to carry only {event, expression, scheduledTime, outcome, duration} plus optional numeric fields; never a handler input, closure or PII substring",
+  "soThat": "the logging stream stays safe to ship to any downstream sink without a per-blueprint scrub pass",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-32106-1",
+      "description": "The event-secrecy probe drives the dispatcher with a spy handler that receives a PII fixture ({userId, ssn}) via a closure, and drives put/get/delete-style operations. The probe asserts (layer 1) every event record's keys are a subset of the allow-list {event, expression, scheduledTime, outcome, duration, softBudgetMs, deltaMs}; and (layer 2) the JSON serialisation of every record (excluding the expression field, which is a legitimate literal from wrangler.toml) contains no PII substring (userId numeric, ssn placeholder). SIMULATE_PII_LEAK=true wraps the sink so it forwards the closure onto the record; the probe surfaces the forbidden keys and the leaked substrings and returns aggregateVerdict: fail.",
+      "given": "the event-secrecy probe run under both modes",
+      "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"
+    }
+  ],
+  "tacIds": ["TAC-3303-platform-cloudflare-cron-triggers-event-sink"],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

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

@@ -0,0 +1,25 @@
+{
+  "usId": "platform-cloudflare-cron-triggers-US-32107",
+  "prdId": "PRD-001",
+  "reqId": "platform-cloudflare-cron-triggers-REQ-001",
+  "version": "1.0.0",
+  "status": "approved",
+  "title": "Real-account live-cron smoke fires cronFired at least once against a real Cloudflare Worker",
+  "asA": "operator validating platform-cloudflare-cron-triggers v1.0.0 against a real Cloudflare account",
+  "iWant": "the real-account-scheduled-smoke probe to schedule a per-minute cron on a real Worker and assert cronFired fires within a bounded wait",
+  "soThat": "the shipped scheduled() surface is proven against the vendor's global cron scheduler, not only against wrangler dev",
+  "acceptanceCriteria": [
+    {
+      "id": "AC-32107-1",
+      "description": "The real-account-scheduled-smoke probe, when CI_HAS_CLOUDFLARE_ACCOUNT=true and the paired CF_ACCOUNT_ID / CF_WORKER_NAME / CF_API_TOKEN env vars are set, polls the Cloudflare Workers Analytics or observability API for the named Worker every 5 seconds, waits bounded 90 seconds for a scheduled event to appear at least once, and returns aggregateVerdict: pass on observation. Without CI_HAS_CLOUDFLARE_ACCOUNT the probe records accountBoundSkipped: true and aggregates to pass per spec section 3.5.",
+      "given": "a real Cloudflare account with the paired env vars, or no such account and CI_HAS_CLOUDFLARE_ACCOUNT unset",
+      "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"
+    }
+  ],
+  "tacIds": ["TAC-3301-platform-cloudflare-cron-triggers-scheduled-handler"],
+  "createdAt": "2026-09-07T12:35:00.000Z",
+  "updatedAt": "2026-09-07T12:35:00.000Z"
+}

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

@@ -0,0 +1,71 @@
+# platform-cloudflare-cron-triggers blueprint coordination vocabulary
+
+This file is the platform-cloudflare-cron-triggers half of the cross-blueprint contract. The Phase 1 conflict detector matches scope:global ADR topics by EXACT string equality, and AC ids are unnamespaced by the 0.4.4 grammar. Any blueprint intended to compose with this one must reuse these exact strings and respect these bands.
+
+## Global ADR topics this blueprint contributes (exact strings)
+
+| 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 |
+
+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).
+
+Rules for new topics: lower camel case, one concept per topic, no version suffixes. A topic names the decision area, not the chosen answer.
+
+## Id number bands (registry bootstrap)
+
+This table is maintained shelf-wide across every blueprint's `docs/topics.md`. Rows are recorded at ship, never predicted.
+
+| Blueprint | US band | ADR/TAC suffix block | Status | Global topics |
+|---|---|---|---|---|
+| application-spa | 1101-1899 | 2xx | shipped v1.3.0 | `clientRouting`, `theming`, `clientState`, `errorEnvelope`, `authModel` |
+| application-api-rest | 2101-2899 | 3xx | shipped v1.0.0 | `errorEnvelope`, `authModel`, `apiVersioning`, `logging` |
+| security-auth-magic-link | 3101-3899 | 5xx | shipped v1.0.0 | `authModel` |
+| email-smtp-resend | 4101-4899 | 4xx | shipped v1.0.0 | none |
+| hello-panel (walkthrough exemplar) | 4101-4899 | 4xx | doc-reserved; teaching exemplar in `packages/rcf-lite/docs/blueprint-authoring-walkthrough.md`, not shipped as a blueprint directory | `operatorPanel` |
+| persistence-data-sqlite | 5101-5899 | 6xx | shipped v1.0.0 | `persistenceStore`, `migrationDiscipline` |
+| delivery-ci-workflows | 6101-6899 | 7xx | shipped v2.0.0 (renamed from ci-pipeline) | `ciGates`, `strictCoverageGate`, `releaseArtefacts` |
+| observability-essentials | 7101-7899 | 8xx | shipped v2.0.0 | `statusPageContract` |
+| security-secrets-management | 8101-8899 | 9xx | shipped v1.0.1 | `secretsSource` |
+| security-auth-clerk | 9101-9899 | 10xx | shipped v1.0.0 | `authModel` |
+| security-auth-oauth2 | 10101-10899 | 11xx | shipped v1.0.0 | `authModel` |
+| security-auth-keycloak | 11101-11899 | 12xx | shipped v1.0.0 | `authModel` |
+| deploy-cloudflare-workers | 12101-12899 | 13xx | shipped v1.2.0 | `deploymentTarget` |
+| persistence-data-d1 | 13101-13899 | 14xx | shipped v1.0.0 | `persistenceStore`, `migrationDiscipline` |
+| observability-probe-endpoints | 14101-14899 | 15xx | shipped v1.1.0 | `healthProbes`, `readinessSemantics` |
+| observability-logging | 15101-15899 | 16xx | shipped v1.0.0 | `logging` |
+| application-error-handling | 16101-16899 | 17xx | shipped v1.0.0 | `errorHandling` |
+| application-datatable | 17101-17899 | 18xx | shipped v1.0.0 | none |
+| application-charts | 18101-18899 | 19xx | shipped v1.0.0 | none |
+| application-dashboard | 19101-19899 | 20xx | shipped v1.0.0 | none |
+| application-notifications-in-app | 20101-20899 | 21xx | shipped v1.0.0 | none |
+| application-admin-console | 21101-21899 | 22xx | shipped v1.1.0 | `adminConsoleSignInSurface` |
+| application-empty-error-states | 22101-22899 | 23xx | shipped v1.0.0 | none |
+| application-file-upload | 23101-23899 | 24xx | shipped v1.0.0 | none |
+| application-forms-wizard | 24101-24899 | 25xx | shipped v1.0.0 | none |
+| application-account-settings | 25101-25899 | 26xx | shipped v1.0.0 | none |
+| application-onboarding-tour | 26101-26899 | 27xx | shipped v1.0.0 | none |
+| persistence-data-postgres | 27101-27899 | 28xx | shipped v1.0.0 | `persistenceStore`, `migrationDiscipline` |
+| object-storage-s3 | 28101-28899 | 29xx | shipped v1.0.0 | `objectStorageContract` |
+| messaging-queue-cloudflare | 29101-29899 | 30xx | shipped v1.0.0 | `deliverySemantics` |
+| jobs-background | 30101-30899 | 31xx | shipped v1.0.0 | `backgroundJobModel` |
+| platform-cloudflare-kv | 31101-31899 | 32xx | shipped v1.0.0 | `keyValueStoreContract` |
+| platform-cloudflare-cron-triggers | 32101-32899 | 33xx | shipped v1.0.0 | `scheduledTriggerContract` |
+| platform-cloudflare-durable-objects | 33101-33899 | 34xx | shipped v1.0.0 | `strongConsistencyCellContract`, `websocketHubContract` |
+| edge-cloudflare-access | 34101-34899 | 35xx | shipped v1.0.0 | `edgeAuthenticationGate` |
+| edge-cloudflare-turnstile | 35101-35899 | 36xx | shipped v1.0.0 | `humanVerificationGate` |
+| edge-cloudflare-rate-limiting | 36101-36899 | 37xx | shipped v1.0.0 | `edgeThrottleContract` |
+
+US 32101-32107 sit at the LOW end of the 32101-32899 band on purpose (watchpost run-4 lesson). A project-side story mechanically derived from a platform-cloudflare-cron-triggers REQ id into the number 32110 would collide against a shipped US-32110; band headroom (32108-32899) leaves that space.
+
+ADR/TAC suffixes for this blueprint use the 3301-3399 block, continuing the shelf pattern.
+
+## 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.
+
+## Deliberate-conflict statement
+
+This blueprint's ADR-3301 on `scheduledTriggerContract` is a first shipped answer to a topic that will conflict, by design, with a future non-Cron-Triggers sibling. Applying `platform-cloudflare-cron-triggers` alongside such a sibling would raise one `globalAdrTopic` conflict the operator resolves via one of the four documented resolutions per topic (adopt one, keep the existing one, author a project-level supersede ADR, or `--resolve <topic>=project:<ADR-id>` on the add).