Task · SKT-0180

Do not fail readiness on quiet request-driven delivery lanes

Description

Readiness requires every expected delivery lane to have a fresh success, including request-driven lanes (logs, traces) that legitimately emit nothing in low-traffic periods. A realistic weekend-evening blueprint reports delivery_stale/delivery_not_attempted while metrics flow. The delivery manifest already classifies lanes as scheduled vs request-driven; readiness should require freshness only for scheduled lanes and still fail request-driven lanes on current errors.

Definition of Done

Implementation Notes

loop57: landed on main (see codex/loop57/BATCH*.md).

View the source file on GitHub