A device lifecycle boundary exposes stale data when network and local state disagree. The affected area is offline cache.
Repair the offline cache cache lifecycle implementation so it separates purge, refresh, and escalation actions by staleness and risk.
Evidence
- Affected surface: Flutter / offline cache.
- Observed failure family: plan cache invalidation.
- Scope policy: authorized must equal true.