From 5f12c5f0d838837a421e230cbcb3febf246a1024 Mon Sep 17 00:00:00 2001
From: Nebu Kaga <nebu.kaga@openagents.org>
Date: Thu, 9 Jul 2026 07:32:38 +0000
Subject: [PATCH] fix(workspace/db): repair channels stuck at alembic 025
 without orchestration columns

Two migrations were both authored as revision "025":
  - 025_add_channel_orchestration (this lineage): adds
    channels.orchestration_mode + orchestration_instruction
  - 025_add_evaluation_jobs (experimental SWE-bench lineage): creates
    the evaluation_jobs table

Any DB that ran the evaluation-jobs variant first got stamped
alembic_version='025', so a later `alembic upgrade head` treated the DB
as already at head and never created the orchestration columns. Every
channel-list / /v1/discover query then 500s with
"column channels.orchestration_mode does not exist".

Add migration 026 that idempotently ensures both columns exist
(ADD COLUMN IF NOT EXISTS), repairing a DB stuck at 025 while being a
no-op where 025 already applied cleanly.
---
 .../026_ensure_channel_orchestration.py       | 56 +++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 workspace/backend/alembic/versions/026_ensure_channel_orchestration.py

diff --git a/workspace/backend/alembic/versions/026_ensure_channel_orchestration.py b/workspace/backend/alembic/versions/026_ensure_channel_orchestration.py
new file mode 100644
index 000000000..929845c51
--- /dev/null
+++ b/workspace/backend/alembic/versions/026_ensure_channel_orchestration.py
@@ -0,0 +1,56 @@
+# -*- coding: utf-8 -*-
+"""Ensure channel orchestration columns exist (repair for stuck revision 025).
+
+Revision ID: 026
+Revises: 025
+Create Date: 2026-07-09
+
+Background
+----------
+Two divergent migrations were both authored as revision "025":
+
+  - ``025_add_channel_orchestration`` (this lineage / origin/develop /
+    release) adds ``channels.orchestration_mode`` and
+    ``channels.orchestration_instruction``.
+  - ``025_add_evaluation_jobs`` (an experimental SWE-bench lineage) creates
+    the ``evaluation_jobs`` table.
+
+Because both declared ``revision = "025"``, any database that ran the
+evaluation-jobs variant first got stamped ``alembic_version = '025'``. When
+the orchestration code later deployed, ``alembic upgrade head`` saw the DB
+already at "025" and became a no-op — so the orchestration columns were
+never created. Every channel-list / ``/v1/discover`` query then 500s with
+``column channels.orchestration_mode does not exist``.
+
+This migration re-applies the orchestration columns idempotently so a
+database stuck at "025" (missing the columns) is repaired on the next
+deploy, while a database that already has them is left untouched. Uses
+Postgres ``ADD COLUMN IF NOT EXISTS`` for true idempotency.
+"""
+
+from alembic import op
+
+
+revision = "026"
+down_revision = "025"
+branch_labels = None
+depends_on = None
+
+
+def upgrade() -> None:
+    # Idempotent: repairs DBs stuck at "025" without the columns, and is a
+    # no-op where 025_add_channel_orchestration already applied them.
+    op.execute(
+        "ALTER TABLE channels "
+        "ADD COLUMN IF NOT EXISTS orchestration_mode TEXT NOT NULL DEFAULT 'dynamic'"
+    )
+    op.execute(
+        "ALTER TABLE channels "
+        "ADD COLUMN IF NOT EXISTS orchestration_instruction TEXT"
+    )
+
+
+def downgrade() -> None:
+    # No-op: leave the columns in place. 025's downgrade owns dropping them,
+    # and dropping here would fight that revision on a normal downgrade path.
+    pass