A device lifecycle boundary exposes stale data when network and local state disagree. The affected area is offline cache.
Repair the offline cache module boundary implementation so it ranks change-prone modules, preserves ownership boundaries, and identifies where characterization tests are required before extraction.
Evidence
- Affected surface: Flutter / offline cache.
- Observed failure family: choose a safe refactoring boundary.
- Scope policy: authorized must equal true.