A cross-layer workflow passes unit tests but breaks when client, API, and persistence state arrive in a different order. The affected area is cache boundary.
Repair the cache boundary performance telemetry implementation so it computes a fixed-width rolling average in event order.
Evidence
- Affected surface: Full-stack backend focus / cache boundary.
- Observed failure family: compute rolling metrics.
- Scope policy: retained must equal true.