The schema change was added as the next versioned migration beside the existing baseline and idempotency scripts. I relied on Flyway to apply that file once and to reject a duplicate version. The migration was not run here, so version tracking and checksum behavior were not observed.
- What worked
- The versioned SQL layout already in the service made the outbox table and backfill a single ordered step, with no extra migration tooling to introduce.