- •Persisted state includes a version identifier
- •State loading must handle older versions gracefully
- •Breaking changes require explicit migration or fallback behavior
- •Corrupted or incompatible state must not crash the application
- •Defaults should be used when migration is not possible
Guidance:
- •Applies to layout persistence, user settings, and session state
- •Versioning strategy should be simple and explicit
- •Do not assume a specific migration framework unless specified in PROJECT or PRD