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