fix: isolate minimax m3 backend migration

src/mgr/postgres-store.ts

@@ -119,7 +119,17 @@ ON CONFLICT (profile) DO UPDATE SET
 
 const backendProfilesMigrationSql = `
 INSERT INTO agentrun_backends (profile, capabilities, capacity, health, updated_at)
-VALUES ${backendCapabilitiesSqlValues()}
+VALUES ${backendCapabilitiesSqlValues(["codex", "deepseek"])}
+ON CONFLICT (profile) DO UPDATE SET
+  capabilities = EXCLUDED.capabilities,
+  capacity = EXCLUDED.capacity,
+  health = EXCLUDED.health,
+  updated_at = EXCLUDED.updated_at;
+`;
+
+const minimaxM3BackendProfileMigrationSql = `
+INSERT INTO agentrun_backends (profile, capabilities, capacity, health, updated_at)
+VALUES ${backendCapabilitiesSqlValues(["minimax-m3"])}
 ON CONFLICT (profile) DO UPDATE SET
   capabilities = EXCLUDED.capabilities,
   capacity = EXCLUDED.capacity,
@@ -239,6 +249,11 @@ const postgresMigrations: MigrationDefinition[] = [
     checksum: checksumSql(queueQ1MigrationSql),
     sql: queueQ1MigrationSql,
   },
+  {
+    id: "005_v01_minimax_m3_backend_profile",
+    checksum: checksumSql(minimaxM3BackendProfileMigrationSql),
+    sql: minimaxM3BackendProfileMigrationSql,
+  },
 ];
 
 export function postgresMigrationContract(): JsonRecord {