| name | data-migration-compat |
| description | Data compatibility workflow for OpenReader. Use when changing GORM models, SQLite migrations, cache, library, uploads, local store, backup/restore, WebDAV storage, or persistent settings. |
Data Migration Compatibility
Use this skill when a change can affect persisted user data.
Hard rules
- Do not silently redesign persistent data.
- Preserve existing
data/, cache/, and library/ mounted directories.
- Do not break old SQLite databases without a migration path.
- Do not delete cache/library files as part of schema cleanup unless explicitly requested and backed up.
Workflow
- Identify old data format and location.
- Identify new data format and location.
- Document compatibility in
docs/compat/data-migration.md.
- Add testdata when possible.
- Add migration or compatibility shim.
- Test against an existing-volume scenario.
Required checks
Run full backend tests and, for release-sensitive changes, scripts/docker-volume-backup-smoke.sh.