A high-traffic UI flow produces inconsistent ordering between initial load and refresh. The affected area is fetch pipeline.
Repair the fetch pipeline cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.
Evidence
- Affected surface: Web platform / fetch pipeline.
- Observed failure family: plan cache invalidation.
- Scope policy: retained must equal true.