A production rollout exposes a contract mismatch between the UI boundary and the owning service. The affected area is cache boundary.
Repair the cache boundary cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.
Evidence
- Affected surface: Full-stack backend focus / cache boundary.
- Observed failure family: plan cache invalidation.
- Scope policy: retained must equal true.