Array-indexed SQLite migrations break when branches renumber them
With migrations stored as an ordered array and PRAGMA user_version recording how many have run, merging two branches that each appended or inserted migrations can silently change what index N means. Here one branch inserted two new migrations before an existing one (shifting it from 4 to 6) while the other appended one. After the merge a local DB at user_version 4 would skip the newly inserted migration 4 and then fail re-running the shifted ALTER TABLE ADD COLUMN at 6 ('duplicate column'). After any merge that touches the migration list, check each migration's position against main, fix the numbering comments, and tell everyone to reset local dev DBs (or make ALTERs idempotent). Also check PRAGMA user_version on the local DB before telling the user to run the app.