diff --git a/server/migrations/200_issue_status.down.sql b/server/migrations/202_issue_status.down.sql
similarity index 100%
rename from server/migrations/200_issue_status.down.sql
rename to server/migrations/202_issue_status.down.sql
diff --git a/server/migrations/200_issue_status.up.sql b/server/migrations/202_issue_status.up.sql
similarity index 96%
rename from server/migrations/200_issue_status.up.sql
rename to server/migrations/202_issue_status.up.sql
index d413bc828e..0bec773899 100644
--- a/server/migrations/200_issue_status.up.sql
+++ b/server/migrations/202_issue_status.up.sql
@@ -11,7 +11,7 @@
 -- reference; tenant consistency and cleanup are enforced in app code (the
 -- workspace-delete path removes these rows in the same transaction). All
 -- indexes are created CONCURRENTLY in their own single-statement follow-up
--- migrations (201-204) because Postgres forbids CREATE INDEX CONCURRENTLY
+-- migrations (203-206) because Postgres forbids CREATE INDEX CONCURRENTLY
 -- inside this table-create transaction.
 CREATE TABLE issue_status (
     id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
diff --git a/server/migrations/201_issue_status_name_index.down.sql b/server/migrations/203_issue_status_name_index.down.sql
similarity index 100%
rename from server/migrations/201_issue_status_name_index.down.sql
rename to server/migrations/203_issue_status_name_index.down.sql
diff --git a/server/migrations/201_issue_status_name_index.up.sql b/server/migrations/203_issue_status_name_index.up.sql
similarity index 100%
rename from server/migrations/201_issue_status_name_index.up.sql
rename to server/migrations/203_issue_status_name_index.up.sql
diff --git a/server/migrations/202_issue_status_system_key_index.down.sql b/server/migrations/204_issue_status_system_key_index.down.sql
similarity index 100%
rename from server/migrations/202_issue_status_system_key_index.down.sql
rename to server/migrations/204_issue_status_system_key_index.down.sql
diff --git a/server/migrations/202_issue_status_system_key_index.up.sql b/server/migrations/204_issue_status_system_key_index.up.sql
similarity index 100%
rename from server/migrations/202_issue_status_system_key_index.up.sql
rename to server/migrations/204_issue_status_system_key_index.up.sql
diff --git a/server/migrations/203_issue_status_category_default_index.down.sql b/server/migrations/205_issue_status_category_default_index.down.sql
similarity index 100%
rename from server/migrations/203_issue_status_category_default_index.down.sql
rename to server/migrations/205_issue_status_category_default_index.down.sql
diff --git a/server/migrations/203_issue_status_category_default_index.up.sql b/server/migrations/205_issue_status_category_default_index.up.sql
similarity index 100%
rename from server/migrations/203_issue_status_category_default_index.up.sql
rename to server/migrations/205_issue_status_category_default_index.up.sql
diff --git a/server/migrations/204_issue_status_workspace_id_index.down.sql b/server/migrations/206_issue_status_workspace_id_index.down.sql
similarity index 100%
rename from server/migrations/204_issue_status_workspace_id_index.down.sql
rename to server/migrations/206_issue_status_workspace_id_index.down.sql
diff --git a/server/migrations/204_issue_status_workspace_id_index.up.sql b/server/migrations/206_issue_status_workspace_id_index.up.sql
similarity index 87%
rename from server/migrations/204_issue_status_workspace_id_index.up.sql
rename to server/migrations/206_issue_status_workspace_id_index.up.sql
index 5870ea6101..3c8df0f378 100644
--- a/server/migrations/204_issue_status_workspace_id_index.up.sql
+++ b/server/migrations/206_issue_status_workspace_id_index.up.sql
@@ -1,5 +1,5 @@
 -- Non-partial (workspace_id) index covering ALL rows, including archived ones.
--- The three catalog uniqueness indexes (201-203) are partial (active rows /
+-- The three catalog uniqueness indexes (203-205) are partial (active rows /
 -- non-NULL system_key), so none of them can serve the workspace-scoped
 -- delete/cleanup path that must remove every issue_status row for a workspace
 -- regardless of archived_at. Built CONCURRENTLY in its own single-statement
diff --git a/server/migrations/205_issue_status_id_column.down.sql b/server/migrations/207_issue_status_id_column.down.sql
similarity index 100%
rename from server/migrations/205_issue_status_id_column.down.sql
rename to server/migrations/207_issue_status_id_column.down.sql
diff --git a/server/migrations/205_issue_status_id_column.up.sql b/server/migrations/207_issue_status_id_column.up.sql
similarity index 91%
rename from server/migrations/205_issue_status_id_column.up.sql
rename to server/migrations/207_issue_status_id_column.up.sql
index 9bc6aad754..06785e3006 100644
--- a/server/migrations/205_issue_status_id_column.up.sql
+++ b/server/migrations/207_issue_status_id_column.up.sql
@@ -2,5 +2,5 @@
 -- window. No FK (CLAUDE.md); resolved to issue_status in app code. Nothing
 -- reads or writes it yet -- the legacy issue.status TEXT column stays the
 -- source of truth until the Phase 2 double-write lands. Its index is created
--- CONCURRENTLY in migration 206.
+-- CONCURRENTLY in migration 208.
 ALTER TABLE issue ADD COLUMN IF NOT EXISTS status_id UUID;
diff --git a/server/migrations/206_issue_status_id_index.down.sql b/server/migrations/208_issue_status_id_index.down.sql
similarity index 100%
rename from server/migrations/206_issue_status_id_index.down.sql
rename to server/migrations/208_issue_status_id_index.down.sql
diff --git a/server/migrations/206_issue_status_id_index.up.sql b/server/migrations/208_issue_status_id_index.up.sql
similarity index 100%
rename from server/migrations/206_issue_status_id_index.up.sql
rename to server/migrations/208_issue_status_id_index.up.sql