Phase-3 review (LOW/safety net, high blast radius). MigrationTest reflectively discovers all Migration vals and replay-tests them, but NOTHING asserts DatabaseModule.addMigrations(...) registers all of them. Since there's (correctly) no destructive fallback, a future migration authored + schema-committed but forgotten in addMigrations passes every test yet crash-loops ALL upgrading users at DB open. Fix: a test asserting the Room builder's registered set equals allAppMigrations (or generate addMigrations from the same reflective source).
Phase-3 review (LOW/safety net, high blast radius). `MigrationTest` reflectively discovers all `Migration` vals and replay-tests them, but NOTHING asserts `DatabaseModule.addMigrations(...)` registers all of them. Since there's (correctly) no destructive fallback, a future migration authored + schema-committed but forgotten in `addMigrations` passes every test yet crash-loops ALL upgrading users at DB open. **Fix:** a test asserting the Room builder's registered set equals `allAppMigrations` (or generate `addMigrations` from the same reflective source).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Phase-3 review (LOW/safety net, high blast radius).
MigrationTestreflectively discovers allMigrationvals and replay-tests them, but NOTHING assertsDatabaseModule.addMigrations(...)registers all of them. Since there's (correctly) no destructive fallback, a future migration authored + schema-committed but forgotten inaddMigrationspasses every test yet crash-loops ALL upgrading users at DB open. Fix: a test asserting the Room builder's registered set equalsallAppMigrations(or generateaddMigrationsfrom the same reflective source).