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