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