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