@bongos/core 1.17.0

package/migrations/021_v3_renumber_and_deps.sql

@@ -0,0 +1,224 @@
+-- 021_v3_renumber_and_deps.sql
+-- GDS-V3 / task 309 / V3.R01b — Renumber the V3.R## prefix on every non-shipped
+-- task to match topological dependency order, and write the dependency edges
+-- into task_dependencies.
+--
+-- Idempotent: title rename is guarded by checking against the new prefix;
+-- dep inserts use ON CONFLICT DO NOTHING.
+--
+-- After this migration applies, the auto-promotion trigger created in 020
+-- is fully wired — when a task ships, its non-spike dependents auto-promote.
+BEGIN;
+
+-- ============================================================================
+-- 1. Renumber V3.R## title prefix (topologically sorted)
+--    Pattern: 'V3.R<old> — <rest>' becomes 'V3.R<new> — <rest>'
+--    Idempotent: only updates if the prefix doesn't already match the new value.
+-- ============================================================================
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R01b ', 'V3.R02 ') WHERE id = 309 AND title LIKE 'V3.R01b %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R02 ', 'V3.R03 ') WHERE id = 229 AND title LIKE 'V3.R02 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R03 ', 'V3.R04 ') WHERE id = 230 AND title LIKE 'V3.R03 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R04 ', 'V3.R05 ') WHERE id = 106 AND title LIKE 'V3.R04 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R05 ', 'V3.R06 ') WHERE id = 231 AND title LIKE 'V3.R05 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R06 ', 'V3.R07 ') WHERE id = 232 AND title LIKE 'V3.R06 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R07 ', 'V3.R08 ') WHERE id = 233 AND title LIKE 'V3.R07 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R08 ', 'V3.R09 ') WHERE id = 234 AND title LIKE 'V3.R08 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R09 ', 'V3.R10 ') WHERE id = 235 AND title LIKE 'V3.R09 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R10 ', 'V3.R11 ') WHERE id = 91 AND title LIKE 'V3.R10 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R11 ', 'V3.R12 ') WHERE id = 236 AND title LIKE 'V3.R11 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R12 ', 'V3.R13 ') WHERE id = 237 AND title LIKE 'V3.R12 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R13 ', 'V3.R14 ') WHERE id = 238 AND title LIKE 'V3.R13 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R14 ', 'V3.R15 ') WHERE id = 239 AND title LIKE 'V3.R14 %';
+-- R16 → R16: no change (task id=240)
+-- R17 → R17: no change (task id=241)
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R15 ', 'V3.R18 ') WHERE id = 222 AND title LIKE 'V3.R15 %';
+-- R19 → R19: no change (task id=201)
+-- R20 → R20: no change (task id=202)
+-- R21 → R21: no change (task id=98)
+-- R22 → R22: no change (task id=242)
+-- R23 → R23: no change (task id=243)
+-- R24 → R24: no change (task id=244)
+-- R25 → R25: no change (task id=245)
+-- R26 → R26: no change (task id=246)
+-- R27 → R27: no change (task id=247)
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R29 ', 'V3.R28 ') WHERE id = 249 AND title LIKE 'V3.R29 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R30 ', 'V3.R29 ') WHERE id = 250 AND title LIKE 'V3.R30 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R31 ', 'V3.R30 ') WHERE id = 251 AND title LIKE 'V3.R31 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R32 ', 'V3.R31 ') WHERE id = 252 AND title LIKE 'V3.R32 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R28 ', 'V3.R32 ') WHERE id = 248 AND title LIKE 'V3.R28 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R34 ', 'V3.R33 ') WHERE id = 254 AND title LIKE 'V3.R34 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R35 ', 'V3.R34 ') WHERE id = 255 AND title LIKE 'V3.R35 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R36 ', 'V3.R35 ') WHERE id = 256 AND title LIKE 'V3.R36 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R37 ', 'V3.R36 ') WHERE id = 257 AND title LIKE 'V3.R37 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R38 ', 'V3.R37 ') WHERE id = 258 AND title LIKE 'V3.R38 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R39 ', 'V3.R38 ') WHERE id = 259 AND title LIKE 'V3.R39 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R40 ', 'V3.R39 ') WHERE id = 260 AND title LIKE 'V3.R40 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R41 ', 'V3.R40 ') WHERE id = 261 AND title LIKE 'V3.R41 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R42 ', 'V3.R41 ') WHERE id = 262 AND title LIKE 'V3.R42 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R43 ', 'V3.R42 ') WHERE id = 263 AND title LIKE 'V3.R43 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R44 ', 'V3.R43 ') WHERE id = 264 AND title LIKE 'V3.R44 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R33 ', 'V3.R44 ') WHERE id = 253 AND title LIKE 'V3.R33 %';
+-- R45 → R45: no change (task id=265)
+-- R46 → R46: no change (task id=224)
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R48 ', 'V3.R47 ') WHERE id = 266 AND title LIKE 'V3.R48 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R49 ', 'V3.R48 ') WHERE id = 267 AND title LIKE 'V3.R49 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R50 ', 'V3.R49 ') WHERE id = 268 AND title LIKE 'V3.R50 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R51 ', 'V3.R50 ') WHERE id = 269 AND title LIKE 'V3.R51 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R52 ', 'V3.R51 ') WHERE id = 270 AND title LIKE 'V3.R52 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R53 ', 'V3.R52 ') WHERE id = 271 AND title LIKE 'V3.R53 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R54 ', 'V3.R53 ') WHERE id = 272 AND title LIKE 'V3.R54 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R55 ', 'V3.R54 ') WHERE id = 273 AND title LIKE 'V3.R55 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R56 ', 'V3.R55 ') WHERE id = 274 AND title LIKE 'V3.R56 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R57 ', 'V3.R56 ') WHERE id = 275 AND title LIKE 'V3.R57 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R58 ', 'V3.R57 ') WHERE id = 276 AND title LIKE 'V3.R58 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R59 ', 'V3.R58 ') WHERE id = 277 AND title LIKE 'V3.R59 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R60 ', 'V3.R59 ') WHERE id = 278 AND title LIKE 'V3.R60 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R61 ', 'V3.R60 ') WHERE id = 279 AND title LIKE 'V3.R61 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R62 ', 'V3.R61 ') WHERE id = 280 AND title LIKE 'V3.R62 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R63 ', 'V3.R62 ') WHERE id = 281 AND title LIKE 'V3.R63 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R64 ', 'V3.R63 ') WHERE id = 282 AND title LIKE 'V3.R64 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R65 ', 'V3.R64 ') WHERE id = 283 AND title LIKE 'V3.R65 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R66 ', 'V3.R65 ') WHERE id = 284 AND title LIKE 'V3.R66 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R67 ', 'V3.R66 ') WHERE id = 285 AND title LIKE 'V3.R67 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R68 ', 'V3.R67 ') WHERE id = 286 AND title LIKE 'V3.R68 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R69 ', 'V3.R68 ') WHERE id = 287 AND title LIKE 'V3.R69 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R70 ', 'V3.R69 ') WHERE id = 288 AND title LIKE 'V3.R70 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R71 ', 'V3.R70 ') WHERE id = 289 AND title LIKE 'V3.R71 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R72 ', 'V3.R71 ') WHERE id = 290 AND title LIKE 'V3.R72 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R73 ', 'V3.R72 ') WHERE id = 291 AND title LIKE 'V3.R73 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R74 ', 'V3.R73 ') WHERE id = 292 AND title LIKE 'V3.R74 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R75 ', 'V3.R74 ') WHERE id = 293 AND title LIKE 'V3.R75 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R76 ', 'V3.R75 ') WHERE id = 294 AND title LIKE 'V3.R76 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R77 ', 'V3.R76 ') WHERE id = 295 AND title LIKE 'V3.R77 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R78 ', 'V3.R77 ') WHERE id = 296 AND title LIKE 'V3.R78 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R79 ', 'V3.R78 ') WHERE id = 297 AND title LIKE 'V3.R79 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R80 ', 'V3.R79 ') WHERE id = 298 AND title LIKE 'V3.R80 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R82 ', 'V3.R80 ') WHERE id = 300 AND title LIKE 'V3.R82 %';
+-- R81 → R81: no change (task id=299)
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R83 ', 'V3.R82 ') WHERE id = 301 AND title LIKE 'V3.R83 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R85 ', 'V3.R83 ') WHERE id = 303 AND title LIKE 'V3.R85 %';
+-- R84 → R84: no change (task id=302)
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R86 ', 'V3.R85 ') WHERE id = 304 AND title LIKE 'V3.R86 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R87 ', 'V3.R86 ') WHERE id = 305 AND title LIKE 'V3.R87 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R88 ', 'V3.R87 ') WHERE id = 306 AND title LIKE 'V3.R88 %';
+UPDATE tasks SET title = regexp_replace(title, '^V3\.R89 ', 'V3.R88 ') WHERE id = 307 AND title LIKE 'V3.R89 %';
+
+-- ============================================================================
+-- 2. Insert task_dependencies rows
+--    Each task gets one INSERT per dep edge. ON CONFLICT DO NOTHING makes the
+--    migration safe to re-run.
+--
+--    FRESH-DB GUARD (task 1238 / ADR 0062 §5 + §8): the 86 edges below reference
+--    THIS instance's V3 task rows, which are seeded by scripts/pms/seed-v3-tasks.js
+--    (a JS seed run on prod AFTER migration 018) — NOT by any SQL migration. On a
+--    fresh / empty instance DB those task rows don't exist, so the INSERTs would
+--    violate task_dependencies' FK to tasks(id) — and ON CONFLICT does NOT suppress
+--    an FK violation. This block is OTB-instance prod data, so skip it wholesale when
+--    `tasks` is empty; the core migration history then replays cleanly on an empty DB
+--    (the C8 customer-0 bringup). On prod the rows exist AND this migration is already
+--    recorded in schema_migrations, so it never re-runs there regardless.
+-- ============================================================================
+DO $$
+BEGIN
+  IF NOT EXISTS (SELECT 1 FROM tasks) THEN
+    RAISE NOTICE 'task 1238: tasks table empty — skipping the V3 dependency seed (fresh-DB replay)';
+    RETURN;
+  END IF;
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (106, 229) ON CONFLICT DO NOTHING; -- R04->R02
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (231, 229) ON CONFLICT DO NOTHING; -- R05->R02
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (231, 106) ON CONFLICT DO NOTHING; -- R05->R04
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (232, 106) ON CONFLICT DO NOTHING; -- R06->R04
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (232, 231) ON CONFLICT DO NOTHING; -- R06->R05
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (234, 233) ON CONFLICT DO NOTHING; -- R08->R07
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (235, 234) ON CONFLICT DO NOTHING; -- R09->R08
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (91, 234) ON CONFLICT DO NOTHING; -- R10->R08
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (238, 231) ON CONFLICT DO NOTHING; -- R13->R05
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (238, 232) ON CONFLICT DO NOTHING; -- R13->R06
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (239, 106) ON CONFLICT DO NOTHING; -- R14->R04
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (240, 106) ON CONFLICT DO NOTHING; -- R16->R04
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (241, 233) ON CONFLICT DO NOTHING; -- R17->R07
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (241, 234) ON CONFLICT DO NOTHING; -- R17->R08
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (241, 237) ON CONFLICT DO NOTHING; -- R17->R12
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (241, 238) ON CONFLICT DO NOTHING; -- R17->R13
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (241, 239) ON CONFLICT DO NOTHING; -- R17->R14
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (241, 240) ON CONFLICT DO NOTHING; -- R17->R16
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (222, 241) ON CONFLICT DO NOTHING; -- R15->R17
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (202, 201) ON CONFLICT DO NOTHING; -- R20->R19
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (98, 201) ON CONFLICT DO NOTHING; -- R21->R19
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (98, 202) ON CONFLICT DO NOTHING; -- R21->R20
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (242, 201) ON CONFLICT DO NOTHING; -- R22->R19
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (242, 202) ON CONFLICT DO NOTHING; -- R22->R20
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (245, 244) ON CONFLICT DO NOTHING; -- R25->R24
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (246, 244) ON CONFLICT DO NOTHING; -- R26->R24
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (249, 232) ON CONFLICT DO NOTHING; -- R29->R06
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (250, 231) ON CONFLICT DO NOTHING; -- R30->R05
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (251, 231) ON CONFLICT DO NOTHING; -- R31->R05
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (252, 229) ON CONFLICT DO NOTHING; -- R32->R02
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (248, 244) ON CONFLICT DO NOTHING; -- R28->R24
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (248, 252) ON CONFLICT DO NOTHING; -- R28->R32
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (255, 254) ON CONFLICT DO NOTHING; -- R35->R34
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (261, 260) ON CONFLICT DO NOTHING; -- R41->R40
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (262, 260) ON CONFLICT DO NOTHING; -- R42->R40
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (262, 261) ON CONFLICT DO NOTHING; -- R42->R41
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (263, 256) ON CONFLICT DO NOTHING; -- R43->R36
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (264, 229) ON CONFLICT DO NOTHING; -- R44->R02
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (264, 231) ON CONFLICT DO NOTHING; -- R44->R05
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (253, 254) ON CONFLICT DO NOTHING; -- R33->R34
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (253, 264) ON CONFLICT DO NOTHING; -- R33->R44
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (265, 264) ON CONFLICT DO NOTHING; -- R45->R44
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (271, 256) ON CONFLICT DO NOTHING; -- R53->R36
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (272, 260) ON CONFLICT DO NOTHING; -- R54->R40
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (272, 262) ON CONFLICT DO NOTHING; -- R54->R42
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (273, 230) ON CONFLICT DO NOTHING; -- R55->R03
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (274, 273) ON CONFLICT DO NOTHING; -- R56->R55
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (275, 273) ON CONFLICT DO NOTHING; -- R57->R55
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (275, 274) ON CONFLICT DO NOTHING; -- R57->R56
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (276, 273) ON CONFLICT DO NOTHING; -- R58->R55
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (277, 230) ON CONFLICT DO NOTHING; -- R59->R03
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (279, 257) ON CONFLICT DO NOTHING; -- R61->R37
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (280, 273) ON CONFLICT DO NOTHING; -- R62->R55
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (280, 275) ON CONFLICT DO NOTHING; -- R62->R57
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (281, 273) ON CONFLICT DO NOTHING; -- R63->R55
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (283, 254) ON CONFLICT DO NOTHING; -- R65->R34
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (283, 282) ON CONFLICT DO NOTHING; -- R65->R64
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (285, 256) ON CONFLICT DO NOTHING; -- R67->R36
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (285, 258) ON CONFLICT DO NOTHING; -- R67->R38
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (285, 282) ON CONFLICT DO NOTHING; -- R67->R64
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (286, 260) ON CONFLICT DO NOTHING; -- R68->R40
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (286, 262) ON CONFLICT DO NOTHING; -- R68->R42
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (286, 282) ON CONFLICT DO NOTHING; -- R68->R64
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (286, 284) ON CONFLICT DO NOTHING; -- R68->R66
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (286, 285) ON CONFLICT DO NOTHING; -- R68->R67
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (288, 282) ON CONFLICT DO NOTHING; -- R70->R64
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (288, 285) ON CONFLICT DO NOTHING; -- R70->R67
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (291, 202) ON CONFLICT DO NOTHING; -- R73->R20
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (292, 202) ON CONFLICT DO NOTHING; -- R74->R20
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (292, 242) ON CONFLICT DO NOTHING; -- R74->R22
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (292, 263) ON CONFLICT DO NOTHING; -- R74->R43
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (293, 285) ON CONFLICT DO NOTHING; -- R75->R67
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (294, 106) ON CONFLICT DO NOTHING; -- R76->R04
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (294, 238) ON CONFLICT DO NOTHING; -- R76->R13
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (296, 238) ON CONFLICT DO NOTHING; -- R78->R13
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (296, 294) ON CONFLICT DO NOTHING; -- R78->R76
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (297, 239) ON CONFLICT DO NOTHING; -- R79->R14
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (299, 300) ON CONFLICT DO NOTHING; -- R81->R82
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (301, 106) ON CONFLICT DO NOTHING; -- R83->R04
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (301, 239) ON CONFLICT DO NOTHING; -- R83->R14
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (303, 236) ON CONFLICT DO NOTHING; -- R85->R11
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (302, 303) ON CONFLICT DO NOTHING; -- R84->R85
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (305, 229) ON CONFLICT DO NOTHING; -- R87->R02
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (306, 231) ON CONFLICT DO NOTHING; -- R88->R05
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (306, 250) ON CONFLICT DO NOTHING; -- R88->R30
+INSERT INTO task_dependencies (task_id, depends_on_task_id) VALUES (306, 251) ON CONFLICT DO NOTHING; -- R88->R31
+END $$;
+
+-- Total dependency edges inserted: 86
+
+-- ============================================================================
+-- 3. Bump migration counter + register migration
+-- ============================================================================
+UPDATE migration_counter SET next_number = GREATEST(next_number, 22) WHERE id = 1;
+INSERT INTO schema_migrations (version) VALUES ('021_v3_renumber_and_deps')
+  ON CONFLICT (version) DO NOTHING;
+
+COMMIT;

package/migrations/022_v3_reconcile_dep_gated_status.sql

@@ -0,0 +1,41 @@
+-- 022_v3_reconcile_dep_gated_status.sql
+-- GDS-V3 / task 347 / V3.R02-followup — Reconcile dep-gated task status.
+--
+-- Migration 021 wired dependency edges onto existing GDS-V3 tasks
+-- retroactively, but did not demote tasks that were ALREADY 'ready' and now
+-- carry an unshipped dependency. Result: ~51 tasks displayed as 'ready' in
+-- /builder-start yet returned 409 DEPS_NOT_SHIPPED on claim (the claim-time
+-- guard in src/bongos/db.js caught them). The queue lied about what was
+-- actually claimable.
+--
+-- Fix: demote every 'ready' task that has at least one unshipped dependency
+-- back to 'backlog'. The auto-promotion trigger from migration 020 then
+-- re-promotes each one to 'ready' the moment its last dependency ships.
+--
+-- Invariant restored: a task is 'ready' only if all of its dependencies are
+-- 'shipped'. Spikes are unaffected (they already live in backlog by policy).
+--
+-- Idempotent: the demotion is conditioned on the presence of an unshipped
+-- dependency, so re-running after deps ship is a no-op. Tasks already in
+-- backlog are not in scope (WHERE status = 'ready').
+BEGIN;
+
+UPDATE tasks t
+   SET status = 'backlog',
+       updated_at = now()
+ WHERE t.version_id = 'GDS-V3'
+   AND t.status = 'ready'
+   AND EXISTS (
+     SELECT 1
+       FROM task_dependencies d
+       JOIN tasks dep ON dep.id = d.depends_on_task_id
+      WHERE d.task_id = t.id
+        AND dep.status <> 'shipped'
+   );
+
+-- Bump migration counter (021 left it at 22, which this file consumes) + register.
+UPDATE migration_counter SET next_number = GREATEST(next_number, 23) WHERE id = 1;
+INSERT INTO schema_migrations (version) VALUES ('022_v3_reconcile_dep_gated_status')
+  ON CONFLICT (version) DO NOTHING;
+
+COMMIT;

package/migrations/023_pms_rank.sql

@@ -0,0 +1,30 @@
+-- V3.R05 (#106): Builder rank system — ancient-Greek hierarchy.
+--
+-- Authority lives in ONE place: builders.rank, on the production DB, checked
+-- server-side per request with no caching (see ADR 0016). This migration adds
+-- the rank column; the FOUNDING admin is no longer hard-coded here. It is seated
+-- at first enrollment from instance config (the configured firstAdmin), idempotent
+-- and only while no Archon exists yet — see src/bongos/auth.js maybeSeatFirstAdmin
+-- (ADR 0062 R62 / task 1201). This keeps the build-system core free of any one
+-- instance's owner identity; the live instance was already seated by the original
+-- form of this migration, so prod is unaffected.
+--
+-- Live ranks for V3: Archon + Thetes. The full enum is reserved up front so
+-- future ranks (the reserved ladder in task #106) don't need a schema change —
+-- adding a rank to the live set later is a code-only change (route grants),
+-- never a migration.
+
+ALTER TABLE builders
+  ADD COLUMN IF NOT EXISTS rank text NOT NULL DEFAULT 'thetes'
+    CHECK (rank IN (
+      -- Divine — above-the-system
+      'olympian', 'hermes', 'oracle', 'demigod',
+      -- Citizen — the working ladder (archon + thetes LIVE in V3)
+      'archon', 'strategos', 'boule', 'aristoi', 'hippeis', 'zeugitai', 'thetes',
+      -- Outsider / sub-citizen — sandboxed
+      'metic', 'xenos', 'periokoi', 'doulos', 'helot'
+    ));
+
+-- No founding-admin literal here (R62 / task 1201): a fresh install seats its
+-- configured firstAdmin in code, at that account's first enrollment, only while
+-- no Archon exists. Every builder defaults to 'thetes' via the column default.

package/migrations/025_builder_exit_status.sql

@@ -0,0 +1,15 @@
+-- V3.R88 (#307): Graceful builder exit.
+--
+-- A builder can be deactivated (they quit / are offboarded) without losing any
+-- history. status gates whether they can claim new work; their drachmae
+-- (credits) and credit_log stay untouched (preserved indefinitely), their
+-- shipped tasks and session_logs stay attributed to them, and an Archon can
+-- reactivate them later. On exit their rank drops to the sandboxed 'xenos'
+-- tier and their active claims are released cleanly (handled in app code).
+
+ALTER TABLE builders
+  ADD COLUMN IF NOT EXISTS status text NOT NULL DEFAULT 'active'
+    CHECK (status IN ('active', 'inactive')),
+  ADD COLUMN IF NOT EXISTS deactivated_at     timestamptz,
+  ADD COLUMN IF NOT EXISTS reactivated_at     timestamptz,
+  ADD COLUMN IF NOT EXISTS deactivated_reason text;

package/migrations/027_builders_preferred_disciplines.sql

@@ -0,0 +1,46 @@
+-- 027_builders_preferred_disciplines.sql — adds builders.preferred_disciplines.
+--
+-- A builder's preferred_disciplines is the set of interest areas they want
+-- the work queue tilted toward — the builder-side mirror of tasks.discipline
+-- (migration 014). Valid elements are the *real* interest areas only:
+--
+--   creative      — map/world, quests, narrative, visual art, pixel pipeline
+--   engineering   — gameplay mechanics, infra, the GDS itself, perf, bugs
+--
+-- Encoding:
+--   {}                          — no preference stated (default)
+--   {creative}                  — creative only
+--   {engineering}               — engineering only
+--   {creative,engineering}      — "both"
+--
+-- Note the enum here is intentionally narrower than tasks.discipline, which
+-- also carries 'unclassified' for un-triaged work. A builder never *prefers*
+-- unclassified — that's a state of a task, not an interest area — so it is
+-- excluded from the CHECK. Empty array is the builder equivalent of "no
+-- preference yet".
+--
+-- Pairs with V3.R81 (#299), which consumes this column to gate the queue and
+-- surface cross-discipline recommendations.
+--
+-- Idempotent: safe to re-run.
+
+ALTER TABLE builders
+  ADD COLUMN IF NOT EXISTS preferred_disciplines text[] NOT NULL DEFAULT '{}';
+
+-- Validate every element against the discipline enum (creative|engineering).
+-- Postgres forbids subqueries in CHECK constraints, so we use the array
+-- containment operator `<@` ("is contained by"): the constraint holds iff
+-- every element of preferred_disciplines is in the allowed set. The empty
+-- array `<@` anything is true, so the default {} passes.
+DO $$
+BEGIN
+  IF NOT EXISTS (
+    SELECT 1 FROM pg_constraint WHERE conname = 'builders_preferred_disciplines_check'
+  ) THEN
+    ALTER TABLE builders ADD CONSTRAINT builders_preferred_disciplines_check
+      CHECK (preferred_disciplines <@ ARRAY['creative', 'engineering']::text[]);
+  END IF;
+END$$;
+
+INSERT INTO schema_migrations (version) VALUES ('027_builders_preferred_disciplines')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/028_tasks_parallel_safe.sql

@@ -0,0 +1,71 @@
+-- 028_tasks_parallel_safe.sql — adds tasks.parallel_safe.
+--
+-- The autonomous overnight session-runner (task #358) can run several tasks at
+-- once in separate sub-agents when the operator opts into parallel mode
+-- (--parallel N). `touches[]` disjointness already prevents *file* collisions
+-- mechanically (claimable_tasks + the unique active-claim index), but some
+-- tasks are unsafe to run concurrently for non-file reasons: they restart the
+-- server, mutate shared infra/DB, or run long deploys. parallel_safe is the
+-- human/planning judgment layered on top of the mechanical touches check.
+--
+-- Encoding (deliberately conservative — unset means "do NOT fan out"):
+--   NULL   — not yet judged (default). Treated as serial-only by the runner.
+--   false  — explicitly unsafe to run alongside other tasks.
+--   true   — safe to run concurrently (subject to touches[] disjointness too).
+--
+-- A task is eligible for a parallel slot iff it is autonomous-fit
+-- (tasks_session_fit → 'autonomous' ∈ fits_session_modes, i.e.
+-- automation_tag='overnight-safe' AND manual_degree<=2 AND no blocker) AND
+-- parallel_safe = true. See src/bongos/db.js listClaimableTasks({ fit: 'parallel' }).
+--
+-- Idempotent: safe to re-run.
+
+ALTER TABLE tasks
+  ADD COLUMN IF NOT EXISTS parallel_safe boolean;
+
+-- Rebuild the two SELECT t.* views so the new column flows through. Same
+-- bodies as migration 015 — only the implicit t.* column list changes (it now
+-- includes parallel_safe). DROP+CREATE rather than OR REPLACE because the
+-- column-list changes; mirrors how migration 014 added `discipline`. Neither
+-- view has dependents (verified against pg_depend at migration-write time).
+
+DROP VIEW IF EXISTS claimable_tasks;
+CREATE VIEW claimable_tasks AS
+SELECT t.*,
+       pms_calibrated_minutes(t.est_minutes, t.kind) AS est_minutes_calibrated
+  FROM tasks t
+ WHERE t.status = 'ready'
+   AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+   AND NOT EXISTS (
+     SELECT 1 FROM task_blockers tb WHERE tb.task_id = t.id
+   )
+   AND NOT EXISTS (
+     SELECT 1 FROM claims c
+       JOIN tasks t2 ON t2.id = c.task_id
+      WHERE c.released_at IS NULL
+        AND t2.touches && t.touches
+   );
+
+DROP VIEW IF EXISTS tasks_session_fit;
+CREATE VIEW tasks_session_fit AS
+SELECT t.*,
+  CASE
+    WHEN t.automation_tag = 'overnight-safe' AND COALESCE(t.manual_degree, 5) <= 2
+         AND NOT EXISTS (SELECT 1 FROM task_blockers tb WHERE tb.task_id = t.id)
+      THEN ARRAY['autonomous','check-in','active']
+    WHEN t.automation_tag = 'live-only' OR COALESCE(t.manual_degree, 5) >= 4
+      THEN ARRAY['active']
+    ELSE ARRAY['check-in','active']
+  END AS fits_session_modes,
+  pms_calibrated_minutes(t.est_minutes, t.kind) AS est_minutes_calibrated,
+  CASE
+    WHEN t.credits_reward > 0
+     AND pms_calibrated_minutes(t.est_minutes, t.kind) IS NOT NULL
+     AND pms_calibrated_minutes(t.est_minutes, t.kind) > 0
+    THEN ROUND(t.credits_reward::numeric / pms_calibrated_minutes(t.est_minutes, t.kind), 3)
+    ELSE NULL
+  END AS credits_per_minute
+FROM tasks t;
+
+INSERT INTO schema_migrations (version) VALUES ('028_tasks_parallel_safe')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/029_rank_three_live.sql

@@ -0,0 +1,32 @@
+-- 029_rank_three_live.sql — the three-rank model goes live (Xenos / Metic / Archon).
+--
+-- Context: task #360, follow-up to the V3.R86 (#305) CLAUDE.md audit, which
+-- surfaced that the ENFORCED model (archon + thetes default, xenos = exit tier)
+-- conflicted with the PLANNED model in V3 criterion C2 + the skills (xenos
+-- default sandbox -> metic working rank -> archon). Lars chose to wire the
+-- three-rank model for real. See ADR 0018.
+--
+-- This migration does the two SCHEMA pieces; the route-grant + claim-gate
+-- pieces are code (src/bongos/*), not schema. Adding 'metic' to the live set is a
+-- code change (it was already a reserved value in the migration 023 CHECK enum)
+-- — no enum change is needed here.
+--
+-- Blast radius is zero: at the time this ran only the founding Archon existed. No thetes/metic/xenos
+-- builders are live, so flipping the default affects only builders created from
+-- now on. Existing rows are untouched (ALTER ... SET DEFAULT is not retroactive).
+--
+-- Idempotent: safe to re-run.
+
+-- 1. New GitHub-authed builders now default to the sandboxed entry rank.
+--    (Was 'thetes' in migration 023.) Metic is the Archon-approved working rank
+--    a builder is deliberately promoted to; thetes joins the reserved ladder.
+ALTER TABLE builders ALTER COLUMN rank SET DEFAULT 'xenos';
+
+-- 2. The "explicitly-tagged-open" mechanism for the Xenos sandbox. A Xenos can
+--    only claim tasks flagged open to them; everything else needs Metic+.
+--    Default false = closed; an Archon opens a task by setting it true via
+--    PATCH /api/gds/tasks/:id.
+ALTER TABLE tasks ADD COLUMN IF NOT EXISTS xenos_claimable boolean NOT NULL DEFAULT false;
+
+INSERT INTO schema_migrations (version) VALUES ('029_rank_three_live')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/030_vulnerability_reports.sql

@@ -0,0 +1,61 @@
+-- 030_vulnerability_reports.sql — the red-team bounty intake table (V3.R63 / #282).
+--
+-- A builder who finds a security flaw files a vulnerability_report here. This is
+-- the durable record of what was found, by whom, against what target, and how
+-- the report was adjudicated (open → repro_attempted → confirmed/disputed →
+-- fixed/wontfix). It is the foundation for:
+--   R65 (#284, shipped) — the bounty payout table in src/bongos/security.js. The
+--        `severity` CHECK below uses the SAME four tiers the bounty table keys
+--        on (low/medium/high/critical) so a confirmed report maps cleanly to a
+--        drachmae amount.
+--   R67 — the Archon adjudication path (read ALL reports, change status).
+--   R68 — auto-confirmation awards `drachmae_awarded` from the bounty table and
+--        links a `fix_task_id` once the fix ships.
+--
+-- Unit convention: drachmae_awarded is the in-world currency (see credit_log in
+-- 003_pms.sql) — a plain numeric count of drachmae, NULL until a report is
+-- confirmed and paid out by R68. Stored numeric (not integer) to match the
+-- task spec; the bounty defaults themselves are integers.
+--
+-- Idempotent: safe to re-run.
+
+CREATE TABLE IF NOT EXISTS vulnerability_reports (
+  id                   bigserial PRIMARY KEY,
+  -- Who filed it. FK to builders, like every other ownership column in the GDS.
+  reporter_builder_id  bigint NOT NULL REFERENCES builders(id),
+  -- What it's against (a component / route / surface). Free text, not an enum:
+  -- the attack surface isn't a closed set.
+  target               text NOT NULL,
+  -- Severity tiers MUST match the bounty table keys in src/bongos/security.js
+  -- (SEVERITIES = ['low','medium','high','critical']). Keep these in sync — a
+  -- new tier is a coordinated change to both this CHECK and that module.
+  severity             text NOT NULL CHECK (severity IN ('low', 'medium', 'high', 'critical')),
+  title                text NOT NULL,
+  description          text,
+  -- Reproduction steps as markdown (the report's evidence).
+  repro_steps_md       text,
+  -- Adjudication lifecycle. open is the filing default; an Archon (R67) drives
+  -- it forward. confirmed/fixed are the payout-eligible terminal-ish states.
+  status               text NOT NULL DEFAULT 'open'
+                         CHECK (status IN ('open', 'repro_attempted', 'confirmed', 'disputed', 'fixed', 'wontfix')),
+  -- Adjudication timestamps — NULL until the corresponding transition happens.
+  confirmed_at         timestamptz,
+  fixed_at             timestamptz,
+  -- The task that fixes this vuln, once one exists (R68 links it).
+  fix_task_id          bigint REFERENCES tasks(id),
+  -- Drachmae paid out on confirmation (R68 fills this from the bounty table).
+  -- NULL = not yet paid. numeric per the task spec.
+  drachmae_awarded     numeric,
+  reported_at          timestamptz NOT NULL DEFAULT now()
+);
+
+CREATE INDEX IF NOT EXISTS idx_vuln_reports_reporter ON vulnerability_reports (reporter_builder_id, reported_at DESC);
+CREATE INDEX IF NOT EXISTS idx_vuln_reports_status ON vulnerability_reports (status, reported_at DESC);
+CREATE INDEX IF NOT EXISTS idx_vuln_reports_severity ON vulnerability_reports (severity);
+
+-- Bump the migration counter past 030 so the next claim that includes
+-- 'migrations/' allocates 031.
+UPDATE migration_counter SET next_number = GREATEST(next_number, 31) WHERE id = 1;
+
+INSERT INTO schema_migrations (version) VALUES ('030_vulnerability_reports')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/031_reward_simplification.sql

@@ -0,0 +1,57 @@
+-- 031_reward_simplification.sql — flip the simplification incentive (V3.R93 / #354).
+--
+-- Layer 2 (REWARD) of the code-simplification plan. Three coordinated changes,
+-- all schema/seed (the streak un-exclusion + the net-negative credit path are
+-- code changes in src/bongos/streak.js + src/bongos/db.js, not SQL):
+--
+--   1. credit_log gains a nullable `description` column so the net-negative
+--      ship bonus (db.js awardNetNegativeBonus) can record the raw
+--      removed/added line counts and the reason inline, instead of cramming
+--      everything into the short `reason` enum-ish string. Existing inserts use
+--      explicit column lists and never touch `description`, so this is additive
+--      and safe; old rows read back NULL.
+--
+--   2. A new "Subtractor" achievement is seeded into the fixed catalog. It is
+--      awarded via the EXISTING builder_achievements mechanism (see
+--      src/bongos/achievements.js evaluateAfterShip) when a builder has earned the
+--      net-negative ship bonus on >= 3 ships — i.e. they have, across multiple
+--      ships, deleted more than they added. icon 🪓, credit_bonus 2 (same tier
+--      as the other "ship a class of work" achievements).
+--
+--   3. The streak-3 / streak-7 achievement descriptions are corrected: they
+--      previously read "(>=15min, kind != cleanup)", but as of this task
+--      cleanup/refactor ships DO count toward streaks (streak.js exclusion
+--      removed). Keep the catalog text honest.
+--
+-- Idempotent: ADD COLUMN IF NOT EXISTS; achievement seed is upsert-on-id.
+
+-- 1. credit_log.description ------------------------------------------------
+ALTER TABLE credit_log ADD COLUMN IF NOT EXISTS description text;
+
+-- 2. + 3. Achievement catalog ----------------------------------------------
+-- New "Subtractor"; corrected streak descriptions. Upsert so re-running this
+-- migration (or a later catalog edit) converges. credit_bonus / sort_order on
+-- Subtractor mirror the other touches[]-class achievements (art/gds shippers).
+INSERT INTO achievements (id, name, description, icon, credit_bonus, sort_order) VALUES
+  ('subtractor', 'Subtractor',
+   'Earn the net-negative ship bonus on 3 ships — across your work you have deleted more than you have added.',
+   '🪓', 2, 65),
+  ('streak-3', 'Streak: 3 Nights',
+   'Ship a task in 3 consecutive local-time nights (>=15min; cleanup/refactor now counts).',
+   '🔥', 2, 40),
+  ('streak-7', 'Streak: 7 Nights',
+   'Ship a task in 7 consecutive local-time nights (>=15min; cleanup/refactor now counts).',
+   '🌋', 5, 50)
+ON CONFLICT (id) DO UPDATE
+  SET name         = EXCLUDED.name,
+      description  = EXCLUDED.description,
+      icon         = EXCLUDED.icon,
+      credit_bonus = EXCLUDED.credit_bonus,
+      sort_order   = EXCLUDED.sort_order;
+
+-- Bump the migration counter past 031 so the next claim that includes
+-- 'migrations/' allocates 032.
+UPDATE migration_counter SET next_number = GREATEST(next_number, 32) WHERE id = 1;
+
+INSERT INTO schema_migrations (version) VALUES ('031_reward_simplification')
+  ON CONFLICT (version) DO NOTHING;