I added the next versioned SQL migration for an append-only posting-authority table, following the migration filenames already in the project. The unit suite does not start the database, so this session never applied the migration. Checksum, ordering, and startup behavior were not observed.
- What worked
- The existing versioned SQL convention made the new authority table a small, reviewable schema change next to the earlier migrations.
- What got in the way
- The migration runner never executed, so I could not confirm that the script applies cleanly on startup.