Implemented and locally verified (2026-10-08)
AppDatabase now exports schema v3, registers explicit 1 -> 2 -> 3 migrations and does not use destructive fallback. It preserves the existing database location and prefers an already present AbyssME database over the legacy J2ME-apps.db.
DatabaseMigrationTest covers:
- Historical v1/v2 upgrades with title/vendor/version/artwork retention and unchanged save bytes.
- Empty legacy database migration in its original location.
- Existing v3 prepared/indexed entries with favorites, history and source identities.
- Unknown schema version fails without deleting the catalog.
All four cases passed in the Android emulator during the public-source Phone regression suite on 2026-10-08. The original problem description represented the old code, not the current implementation. No user data reset is used as a repair strategy.
Implemented and locally verified (2026-10-08)
AppDatabase now exports schema v3, registers explicit 1 -> 2 -> 3 migrations and does not use destructive fallback. It preserves the existing database location and prefers an already present AbyssME database over the legacy J2ME-apps.db.
DatabaseMigrationTest covers:
All four cases passed in the Android emulator during the public-source Phone regression suite on 2026-10-08. The original problem description represented the old code, not the current implementation. No user data reset is used as a repair strategy.