Description
A scheduled function’s invocations should follow its declared schedule, so a dashboard can compare actual runs per window with expected runs. Capture the scheduler service’s own CloudWatch metrics for a scheduled function target, then let a function declare a cadence and add a failure mode that skips or delays scheduled runs.
Acceptance Criteria
- #1 A live capture of scheduler metrics for a scheduled function target is recorded positive-only in signals/cw.md
- #2 A function can declare a schedule cadence; its invocations per period follow it, and a failure mode skips or delays scheduled runs, proven red then green through the real loader
- #3 Shipped default blueprints and rates are unchanged
Definition of Done
- #1 just check (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump — inventory diffed against signals/
Implementation Notes
Closeout dependency hold: no scheduled-function capture ran. Resume with ownership-admitted bounded capture and sourced cadence/scheduler semantics; no guessed schedule metrics, forced emission or new construct admitted.
Scheduler capture/cadence remains dependency-held: no schedule or source/backend metric evidence was admitted from the held capture. Do not invent telemetry or treat resource creation as data proof.
Capture dependency remains unsatisfied: no schedule or invocation was created, no scheduler source/backend positive was admitted. Known capture footprint has been removed and shared stream verified unchanged. Fresh attempt is owner-held; no synthetic implementation or completion claim authorized from the failed attempt.
Terminal dependency hold: no schedule, scheduled invocation or admitted scheduler telemetry. Known capture footprint removed; resume only with owner-authorized new capture and sourced cadence evidence, not metadata or cleanup as telemetry proof.
loop57: capture 2026-10-24 (InvocationAttemptCount only observed); scheduler construct 9e3dad5 with opt-in documented-not-observed failure metrics; shipped blueprints unchanged.