diff --git a/api/migrations/versions/2026_08_20_1545-c8e7f6a5b4d3_merge_skill_debug_and_agent_drive_heads.py b/api/migrations/versions/2026_08_20_1545-c8e7f6a5b4d3_merge_skill_debug_and_agent_drive_heads.py
new file mode 100644
index 00000000000..96b0d93ed93
--- /dev/null
+++ b/api/migrations/versions/2026_08_20_1545-c8e7f6a5b4d3_merge_skill_debug_and_agent_drive_heads.py
@@ -0,0 +1,26 @@
+"""restore deploy/dev alembic revision c8e7f6a5b4d3
+
+Revision ID: c8e7f6a5b4d3
+Revises: 89919253ca7a
+Create Date: 2026-08-20 15:45:00.000000
+
+The deploy/dev database is stamped at this revision. The original file
+was an empty merge of skill/debug heads and later disappeared when
+deploy/dev was rewritten. Keep the revision id so flask db upgrade can
+locate the database, and parent it at remove_agent_drive — the last
+shared revision that was actually applied — so later migrations still run.
+"""
+
+# revision identifiers, used by Alembic.
+revision: str = "c8e7f6a5b4d3"
+down_revision = "89919253ca7a"
+branch_labels = None
+depends_on = None
+
+
+def upgrade() -> None:
+    pass
+
+
+def downgrade() -> None:
+    pass
diff --git a/api/migrations/versions/2026_09_01_1748-ae0c8e7b4d31_merge_c8e7_onto_legacy_model_types.py b/api/migrations/versions/2026_09_01_1748-ae0c8e7b4d31_merge_c8e7_onto_legacy_model_types.py
new file mode 100644
index 00000000000..b26d1a5c261
--- /dev/null
+++ b/api/migrations/versions/2026_09_01_1748-ae0c8e7b4d31_merge_c8e7_onto_legacy_model_types.py
@@ -0,0 +1,21 @@
+"""merge c8e7f6a5b4d3 onto current deploy/dev head
+
+Revision ID: ae0c8e7b4d31
+Revises: c8e7f6a5b4d3, 5578e028b2f2
+Create Date: 2026-09-01 17:48:00.000000
+
+"""
+
+# revision identifiers, used by Alembic.
+revision: str = "ae0c8e7b4d31"
+down_revision = ("c8e7f6a5b4d3", "5578e028b2f2")
+branch_labels = None
+depends_on = None
+
+
+def upgrade() -> None:
+    pass
+
+
+def downgrade() -> None:
+    pass