Worker Cron Change

Trigger And Exclusions

Use for cron/lease work and approved runtime qualification, not unrelated Worker/API work.

Classify The Operation

Select schedule/dispatch, lease/abandonment recovery, compatibility-date qualification, or approved replication evaluation before reading branch context.

Mandatory Core

• worker/src/cron/AGENTS.md; Cron source of truth, connection-budget assumption, and Cron Scheduling.
• Inventory worker/wrangler.toml, worker/wrangler.heavy.toml, shared/lib/cron-jobs.ts, and shared/lib/scheduled-runner-registry.ts: cadence, aliases, role, status identity, runner, connection/CPU budget and explicit cpuPlacement. Both configs own deployed expressions; cron metadata owns schedules/budgets; runner registry owns role/slot topology. Never duplicate that truth.
• Preserve the public/heavy union growth gate; treat 5/6 as full for new fetch-heavy work. Consume or cancel each response body before later fetches; the trigger-wide budget is six.
• Never clear a live lease or let a late finalizer overwrite a takeover. A green deploy is not runtime health: changed cron/scheduler/memory/ingestion paths require first-production-run evidence.
• The replication benchmark is retired: no supported restore/deploy shortcut. Future evaluation needs separate approval and a reviewed Access-only copied-dataset harness; retirement does not authorize remote deletion or replication mutation.

Branch Reads And Actions

• Schedule/dispatch: read new scheduled work and slot capacity. Fit work into an audited slot; update its exact schedule-bound CRON_CONNECTION_BUDGET_ENTRIES row. For a new logical lane, explicitly choose cpuPlacement in CRON_SCHEDULE_DEFINITIONS: hourly-physical-required requires single-minute hourly physical aliases; sub-hourly-allowed permits the existing physical form. Existing declarations encode reviewed behavior; reclassification needs measured Worker operations owner review. Add a physical trigger only after the growth gate and consolidation/rebalance review. Review both worker/wrangler.toml and worker/wrangler.heavy.toml; put triggers in their owner's config. In worker/src/handlers/scheduled.ts, preserve dispatch parity, role ownership, serial/parallel order and runner entrypoint; misowned invocations skip neutrally. Inspect worker/src/lib/scheduled-slot-fence.ts, worker/src/lib/cron-lease-primitives.ts, and worker/src/lib/scheduled-slot-reconciliation.ts for takeover, heartbeat, cancellation, terminal fencing and stale-artifact reconciliation.
• Lease/abandonment recovery: read Cron Slot Abandonment, Lease And Breaker Recovery, and Health & Status Endpoints; inspect the fence/lease/reconciliation sources above. Fresh matching status progress bars lease clearing.
• Compatibility date: read qualification. Require Public/Heavy × baseline/candidate evidence; isolated Heavy neutral admission is not producer success. Advance/roll back both roles together in a dedicated date-only release, never mixed with schema, methodology, recovery, data repair, or replication changes.
• Approved replication evaluation only: read retired benchmark and future evaluation, including production-operation authorization, credential, correctness/benefit, propagation, and orphan-resource stops. Historical Git provenance is research-only.

Checks Owned By The Verifier

The assigned verifier runs checks after writers finish; implementation agents return required checks and do not independently claim validation.

• Topology/runtime: npm run check:cron-sync, npm run check:cron-connections, npm run check:fetch-body-timeouts, npm run validate:worker-scheduled-smoke.
• Dispatch/leases: npx vitest run worker/src/handlers/scheduled/__tests__/scheduled-runner-contract.test.ts worker/src/lib/__tests__/cron-leases-scheduled-slot.test.ts.
• CPU placement: npx vitest run shared/lib/__tests__/cron-jobs.test.ts checks declared placement and required-hourly aliases across all logical schedules; topology checks inventory both worker/wrangler.toml and worker/wrangler.heavy.toml.
• Experiments: use only the selected branch's qualification gates. After an authorized risk-bearing deployment, observe the first relevant execution with npm run ops:watch-worker-cron and the status endpoint; route anomalies to the incident branch.

Completion Evidence

Report changed schedule/slot/runner, connection and CPU-budget evidence, checks actually run (or handed to the verifier), first production execution or pending acceptance, and abandonment/lease/experiment-cleanup/rollback follow-up.