@bongos/core 1.17.0

package/migrations/013_claim_locking.sql

@@ -0,0 +1,22 @@
+-- Claim session lock — closes the cross-session claim-interference hole
+-- described 2026-05-11.
+--
+-- The bug: builder has claim A active in session-A (terminal 1). Session-B
+-- (terminal 2) calls /builder-release — same builder_id passes the existing
+-- NOT_YOUR_CLAIM check — drops claim A, then claims a conflicting task.
+-- Session-A has no idea its claim was released and keeps working. Both
+-- sessions advance changes to the same files; only one wins at ship time.
+--
+-- Fix: record which session created each claim. The resolve endpoint
+-- enforces that only the creator session can ship or release it. A different
+-- terminal (different session token) gets CLAIM_SESSION_MISMATCH (403).
+-- Use --force on /builder-release as an emergency escape hatch when the
+-- original terminal is gone.
+--
+-- Parallel non-conflicting claims (different touches[]) are still allowed —
+-- this change only prevents cross-session resolve, not cross-session claiming.
+ALTER TABLE claims
+  ADD COLUMN IF NOT EXISTS creator_session_id bigint REFERENCES builder_sessions(id);
+
+INSERT INTO schema_migrations (version) VALUES ('013_claim_locking')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/014_pms_task_discipline.sql

@@ -0,0 +1,86 @@
+-- 014_pms_task_discipline.sql — adds tasks.discipline.
+--
+-- tasks.kind classifies the TYPE of change (feature / bug / refactor / ...).
+-- tasks.discipline classifies the BUILDER INTEREST AREA — orthogonal axis
+-- so a builder can filter the work queue to what they actually want to do:
+--
+--   creative      — map/world recommendations, quests, narrative, visual art,
+--                   level design, pixel-art pipeline work
+--   engineering   — gameplay mechanics, infra, the PMS itself, performance,
+--                   data plumbing, bug fixes that aren't visual
+--   unclassified  — default for existing rows + new captures; gets triaged later
+--
+-- Applies to both tracks (product + internal). Existing rows stay
+-- 'unclassified'; retroactive classification is a separate task.
+--
+-- The two existing tasks views that expose `SELECT t.*` (claimable_tasks,
+-- tasks_session_fit) are rebuilt below so the new column flows through to
+-- API consumers without a follow-up migration. version_progress and
+-- version_lifecycle_breakdown project specific columns and don't need
+-- rebuilding.
+--
+-- Idempotent: safe to re-run.
+
+-- =========================================================================
+-- 1. Column + CHECK constraint
+-- =========================================================================
+
+ALTER TABLE tasks
+  ADD COLUMN IF NOT EXISTS discipline text NOT NULL DEFAULT 'unclassified';
+
+DO $$
+BEGIN
+  IF NOT EXISTS (
+    SELECT 1 FROM pg_constraint WHERE conname = 'tasks_discipline_check'
+  ) THEN
+    ALTER TABLE tasks ADD CONSTRAINT tasks_discipline_check
+      CHECK (discipline IN ('creative', 'engineering', 'unclassified'));
+  END IF;
+END$$;
+
+-- =========================================================================
+-- 2. Rebuild views that use SELECT t.* so the new column is exposed
+-- =========================================================================
+
+-- claimable_tasks — body identical to migration 006's definition. Rebuilt
+-- only so SELECT t.* re-expands and picks up tasks.discipline.
+DROP VIEW IF EXISTS claimable_tasks;
+CREATE VIEW claimable_tasks AS
+SELECT t.*
+  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
+   );
+
+-- tasks_session_fit — body identical to migration 006's definition.
+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,
+  CASE WHEN t.credits_reward > 0 AND t.est_minutes IS NOT NULL AND t.est_minutes > 0
+    THEN ROUND(t.credits_reward::numeric / t.est_minutes, 3)
+    ELSE NULL
+  END AS credits_per_minute
+FROM tasks t;
+
+-- =========================================================================
+-- 3. Record migration
+-- =========================================================================
+
+INSERT INTO schema_migrations (version) VALUES ('014_pms_task_discipline')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/015_pms_estimation_calibration.sql

@@ -0,0 +1,140 @@
+-- 015_pms_estimation_calibration.sql — per-kind estimate calibration.
+--
+-- Problem (investigated 2026-05-11, idea #25, task #198):
+--   Across 109 shipped tasks with actuals, median actual/est ratio is 0.03
+--   (mean 0.14, p90 0.10). Estimates are sized for humans but the work is
+--   Claude-executed — they run ~30× faster than the prior assumes. The
+--   optimizer's `est_minutes <= timeBudgetMin` filter rejects tasks that
+--   would actually fit; displayed estimates create false expectations.
+--
+-- Fix:
+--   `pms_calibrated_minutes(est, kind)` returns est × per-kind median ratio
+--   computed live from shipped+confirmed tasks (the smoke-filter row
+--   pattern from view 006 is preserved). Three-tier fallback:
+--     1. ≥5 same-kind samples → use kind-specific median.
+--     2. ≥10 total samples    → use overall median (kind has too little data).
+--     3. <10 total samples    → return raw est (cold-start; trust the human).
+--   Returning NULL for NULL/zero est. Result is GREATEST(1, …) so we never
+--   tell a builder "0 minutes".
+--
+--   `claimable_tasks` and `tasks_session_fit` are rebuilt to expose
+--   `est_minutes_calibrated` and to compute `credits_per_minute` from
+--   the calibrated number rather than the raw input.
+--
+-- Selection follow-on (src/pms/optimizer.js):
+--   `est_minutes <= timeBudgetMin` becomes
+--   `COALESCE(est_minutes_calibrated, est_minutes) <= timeBudgetMin`.
+--
+-- Idempotent: CREATE OR REPLACE for function + views.
+
+CREATE OR REPLACE FUNCTION pms_calibrated_minutes(est integer, in_kind text)
+RETURNS integer
+LANGUAGE sql
+STABLE
+AS $$
+  WITH ratios AS (
+    SELECT t.kind,
+           t.actual_minutes::numeric / t.est_minutes AS r
+      FROM tasks t
+     WHERE t.status IN ('shipped', 'confirmed')
+       AND t.actual_minutes IS NOT NULL
+       AND t.est_minutes IS NOT NULL
+       AND t.est_minutes > 0
+       AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+  ),
+  kind_stats AS (
+    SELECT percentile_cont(0.5) WITHIN GROUP (ORDER BY r)::numeric AS median,
+           COUNT(*)::integer AS n
+      FROM ratios
+     WHERE kind = in_kind
+  ),
+  overall_stats AS (
+    SELECT percentile_cont(0.5) WITHIN GROUP (ORDER BY r)::numeric AS median,
+           COUNT(*)::integer AS n
+      FROM ratios
+  )
+  SELECT CASE
+    WHEN est IS NULL OR est <= 0 THEN NULL
+    WHEN (SELECT n FROM kind_stats) >= 5 THEN
+      GREATEST(1, ROUND(est * (SELECT median FROM kind_stats))::integer)
+    WHEN (SELECT n FROM overall_stats) >= 10 THEN
+      GREATEST(1, ROUND(est * (SELECT median FROM overall_stats))::integer)
+    ELSE est
+  END;
+$$;
+
+-- Companion summary function for transparency / debugging. Returns the
+-- ratios table used by pms_calibrated_minutes. Not used in production
+-- selection — only by smoke tests, /builder-start --debug, and any future
+-- status-page transparency row (deferred follow-up).
+CREATE OR REPLACE FUNCTION pms_calibration_summary()
+RETURNS TABLE (kind text, median_ratio numeric, sample_size integer)
+LANGUAGE sql
+STABLE
+AS $$
+  WITH ratios AS (
+    SELECT t.kind,
+           t.actual_minutes::numeric / t.est_minutes AS r
+      FROM tasks t
+     WHERE t.status IN ('shipped', 'confirmed')
+       AND t.actual_minutes IS NOT NULL
+       AND t.est_minutes IS NOT NULL
+       AND t.est_minutes > 0
+       AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+  )
+  SELECT kind,
+         ROUND(percentile_cont(0.5) WITHIN GROUP (ORDER BY r)::numeric, 4) AS median_ratio,
+         COUNT(*)::integer AS sample_size
+    FROM ratios
+   GROUP BY kind
+   ORDER BY sample_size DESC, kind;
+$$;
+
+-- Rebuild claimable_tasks to expose est_minutes_calibrated. Same WHERE
+-- clauses as 006 — only the SELECT list changes.
+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
+   );
+
+-- Rebuild tasks_session_fit to compute credits_per_minute against the
+-- calibrated estimate (was: raw est_minutes). Also exposes
+-- est_minutes_calibrated so consumers can display it. Uses DROP+CREATE
+-- rather than OR REPLACE because adding a column mid-SELECT-list isn't
+-- supported by CREATE OR REPLACE VIEW. No dependent views (verified
+-- against pg_depend at migration-write time).
+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 ('015_pms_estimation_calibration')
+  ON CONFLICT (version) DO NOTHING;

package/migrations/016_pms_task_grades.sql

@@ -0,0 +1,60 @@
+-- PMS-V2 task 197: quality grader for task output.
+--
+-- One row per task. Inserted when a task transitions completed → confirmed
+-- (or when verification passes and the grade fails — see grader.js).
+-- The grade gates the lifecycle transition: passed=true → confirmed +
+-- credits, passed=false → task stays at completed, no credits.
+--
+-- The threshold + grader_version are captured PER ROW so historical grades
+-- stay interpretable when either moves. V2 ships with threshold=5.0 and
+-- grader_version='v1'; rubric weights live in src/pms/grader-rubric.json.
+
+CREATE TABLE IF NOT EXISTS task_grades (
+  id              BIGSERIAL PRIMARY KEY,
+  task_id         BIGINT NOT NULL UNIQUE REFERENCES tasks(id) ON DELETE CASCADE,
+  score           NUMERIC(3,1) NOT NULL CHECK (score >= 0 AND score <= 10),
+  passed          BOOLEAN NOT NULL,
+  threshold       NUMERIC(3,1) NOT NULL,
+  grader_kind     TEXT NOT NULL CHECK (grader_kind IN ('auto', 'subagent', 'lars')),
+  grader_version  TEXT NOT NULL,
+  rubric_scores   JSONB NOT NULL DEFAULT '{}'::jsonb,
+  signals         JSONB NOT NULL DEFAULT '{}'::jsonb,
+  notes_md        TEXT,
+  graded_at       TIMESTAMPTZ NOT NULL DEFAULT now()
+);
+
+CREATE INDEX IF NOT EXISTS idx_task_grades_graded_at ON task_grades(graded_at DESC);
+CREATE INDEX IF NOT EXISTS idx_task_grades_passed_grade ON task_grades(passed, graded_at DESC);
+
+-- View: grades joined with task + claim + cost. Powers the V4 optimizer
+-- (quality-per-dollar) and the public dashboard tile.
+CREATE OR REPLACE VIEW task_grades_with_context AS
+SELECT
+  g.id              AS grade_id,
+  g.task_id,
+  g.score,
+  g.passed,
+  g.threshold,
+  g.grader_kind,
+  g.grader_version,
+  g.rubric_scores,
+  g.signals,
+  g.graded_at,
+  t.title           AS task_title,
+  t.kind            AS task_kind,
+  t.discipline      AS task_discipline,
+  t.version_id,
+  t.est_minutes,
+  t.actual_minutes,
+  t.shipped_by      AS builder_id,
+  b.github_login,
+  b.display_name,
+  (SELECT COALESCE(SUM(amount_usd), 0)
+     FROM cost_log cl WHERE cl.task_id = g.task_id)  AS total_cost_usd
+FROM task_grades g
+JOIN tasks t      ON t.id = g.task_id
+LEFT JOIN builders b ON b.id = t.shipped_by;
+
+-- Bump the migration counter past 016 so the next claim that includes
+-- 'migrations/' allocates 017.
+UPDATE migration_counter SET next_number = GREATEST(next_number, 17) WHERE id = 1;

package/migrations/017_version_progress_exclude_abandoned.sql

@@ -0,0 +1,49 @@
+-- PMS task #218 — version_progress should not count abandoned tasks.
+--
+-- Background: migration 012 rebuilt version_progress to treat completed +
+-- confirmed + shipped as "done" but kept abandoned tasks in the denominator.
+-- That's wrong: abandoned is a terminal state (deliberately cut), not pending
+-- work. It should be filtered out just like __smoke__ and parent tasks.
+--
+-- Effect: closing versions surface their true completion ratio. PMS-V2 (which
+-- abandoned 5 tasks during build, mostly debris + redundant rows) jumps from
+-- 92% to 100% once its last in-flight task lands. The progress-bar metric now
+-- matches "of the work this version actually scoped, what shipped?"
+--
+-- DROP+CREATE rather than CREATE OR REPLACE because Postgres rejects the
+-- latter when the column list/order would change. Here the columns are
+-- identical to migration 012 — the only diff is one extra clause in each
+-- FILTER — but DROP+CREATE is the safe pattern for view edits (see PMS
+-- learnings).
+
+DROP VIEW IF EXISTS version_progress;
+CREATE VIEW version_progress AS
+SELECT v.id AS version_id,
+       v.name,
+       v.track,
+       v.status,
+       count(*) FILTER (
+         WHERE t.status IN ('completed', 'confirmed', 'shipped')
+           AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+           AND NOT EXISTS (SELECT 1 FROM tasks c WHERE c.parent_task_id = t.id)
+       ) AS shipped_count,
+       count(*) FILTER (
+         WHERE t.status <> 'abandoned'
+           AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+           AND NOT EXISTS (SELECT 1 FROM tasks c WHERE c.parent_task_id = t.id)
+       ) AS total_count,
+       COALESCE(SUM(CASE
+         WHEN t.status IN ('completed', 'confirmed', 'shipped')
+              AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+              AND NOT EXISTS (SELECT 1 FROM tasks c WHERE c.parent_task_id = t.id)
+         THEN (6 - COALESCE(t.priority, 5))
+         ELSE 0 END), 0) AS shipped_weight,
+       COALESCE(SUM(CASE
+         WHEN t.status <> 'abandoned'
+              AND t.title NOT LIKE '\_\_smoke\_\_%' ESCAPE '\'
+              AND NOT EXISTS (SELECT 1 FROM tasks c WHERE c.parent_task_id = t.id)
+         THEN (6 - COALESCE(t.priority, 5))
+         ELSE 0 END), 0) AS total_weight
+  FROM versions v
+  LEFT JOIN tasks t ON t.version_id = v.id
+ GROUP BY v.id, v.name, v.track, v.status;

package/migrations/019_rename_pms_v3_to_gds_v3.sql

@@ -0,0 +1,65 @@
+-- 019_rename_pms_v3_to_gds_v3.sql
+--
+-- V3.R01: rename the in-flight version's ID from `PMS-V3` to `GDS-V3`, and
+-- rename the related `pms-shipper` achievement to `gds-shipper`.
+--
+-- PMS-V1 and PMS-V2 are intentionally NOT renamed — those versions shipped
+-- under those names and their archives in `limitations/pms-v*-shipped.md`
+-- are immutable historical records. Going forward (V3 onward), the system
+-- is the Game Development System (GDS); future versions are GDS-V4, GDS-V5,
+-- etc.
+--
+-- The version id `versions(id)` is a TEXT primary key referenced by FK from
+-- `tasks`, `done_when_criteria`, and `idea_inbox`. The `achievements(id)`
+-- primary key is referenced by FK from `builder_achievements`. Neither FK
+-- was declared with `ON UPDATE CASCADE`, so we drop them, rewrite all the
+-- relevant tables in one transaction, and re-add them at the end.
+--
+-- `source_ref` strings that were seeded as `pms-v3-r##` are rewritten to
+-- `gds-v3-r##` for consistency (these are internal audit identifiers — no
+-- user-visible surface).
+
+BEGIN;
+
+-- ─────────────────────────────────────────────────────────────────────────
+-- 1. Versions rename: PMS-V3 → GDS-V3
+-- ─────────────────────────────────────────────────────────────────────────
+
+ALTER TABLE tasks DROP CONSTRAINT IF EXISTS tasks_version_id_fkey;
+ALTER TABLE done_when_criteria DROP CONSTRAINT IF EXISTS done_when_criteria_version_id_fkey;
+ALTER TABLE idea_inbox DROP CONSTRAINT IF EXISTS idea_inbox_suggested_version_fkey;
+
+UPDATE versions SET id = 'GDS-V3' WHERE id = 'PMS-V3';
+
+UPDATE tasks SET version_id = 'GDS-V3' WHERE version_id = 'PMS-V3';
+UPDATE done_when_criteria SET version_id = 'GDS-V3' WHERE version_id = 'PMS-V3';
+UPDATE idea_inbox SET suggested_version = 'GDS-V3' WHERE suggested_version = 'PMS-V3';
+
+-- Rewrite V3 planning-seed source_refs (pms-v3-r## → gds-v3-r##)
+UPDATE tasks SET source_ref = REPLACE(source_ref, 'pms-v3-', 'gds-v3-') WHERE source_ref LIKE 'pms-v3-%';
+
+ALTER TABLE tasks ADD CONSTRAINT tasks_version_id_fkey FOREIGN KEY (version_id) REFERENCES versions(id);
+ALTER TABLE done_when_criteria ADD CONSTRAINT done_when_criteria_version_id_fkey FOREIGN KEY (version_id) REFERENCES versions(id);
+ALTER TABLE idea_inbox ADD CONSTRAINT idea_inbox_suggested_version_fkey FOREIGN KEY (suggested_version) REFERENCES versions(id);
+
+-- ─────────────────────────────────────────────────────────────────────────
+-- 2. Achievement rename: pms-shipper → gds-shipper
+--    Display name also updates ("PMS Shipper" → "GDS Shipper") for the UI.
+-- ─────────────────────────────────────────────────────────────────────────
+
+ALTER TABLE builder_achievements DROP CONSTRAINT IF EXISTS builder_achievements_achievement_id_fkey;
+
+UPDATE achievements
+   SET id = 'gds-shipper',
+       name = 'GDS Shipper'
+ WHERE id = 'pms-shipper';
+
+UPDATE builder_achievements
+   SET achievement_id = 'gds-shipper'
+ WHERE achievement_id = 'pms-shipper';
+
+ALTER TABLE builder_achievements
+  ADD CONSTRAINT builder_achievements_achievement_id_fkey
+  FOREIGN KEY (achievement_id) REFERENCES achievements(id);
+
+COMMIT;

package/migrations/020_task_dependencies.sql

@@ -0,0 +1,99 @@
+-- 020_task_dependencies.sql
+-- GDS-V3 / task 309 / V3.R01b — Task dependencies + auto-promotion system.
+--
+-- Adds a many-to-many task-dependency table and a trigger that auto-promotes
+-- non-spike tasks from 'backlog' → 'ready' when their last dependency ships.
+--
+-- Operating rules (see ADR 0015):
+--   * task_dependencies(task_id, depends_on_task_id) is the canonical edge list.
+--   * A task is "satisfied" iff every row pointing at it from task_dependencies
+--     has the referenced task in status='shipped'.
+--   * The trigger fires when a task transitions INTO status='shipped'.
+--     It scans every dependent of the just-shipped task. If a dependent is
+--     in 'backlog', is NOT a spike, and all its other deps are also shipped,
+--     it auto-promotes to 'ready'. Spikes stay in backlog by convention —
+--     they're the architectural gates that humans open manually.
+--   * Claim-time enforcement (refusing to claim while a dep is unshipped) is
+--     handled in the application layer (src/bongos/db.js createClaim).
+
+BEGIN;
+
+-- ============================================================================
+-- 1. task_dependencies table
+-- ============================================================================
+CREATE TABLE IF NOT EXISTS task_dependencies (
+  task_id            bigint NOT NULL REFERENCES tasks(id) ON DELETE CASCADE,
+  depends_on_task_id bigint NOT NULL REFERENCES tasks(id) ON DELETE CASCADE,
+  created_at         timestamptz NOT NULL DEFAULT now(),
+  PRIMARY KEY (task_id, depends_on_task_id),
+  CONSTRAINT no_self_dep CHECK (task_id <> depends_on_task_id)
+);
+
+-- "What does X depend on?" (forward edge)
+CREATE INDEX IF NOT EXISTS idx_task_deps_task
+  ON task_dependencies (task_id);
+
+-- "What depends on Y?" (reverse edge — used by the auto-promotion trigger)
+CREATE INDEX IF NOT EXISTS idx_task_deps_depends_on
+  ON task_dependencies (depends_on_task_id);
+
+-- ============================================================================
+-- 2. Auto-promotion trigger
+-- ============================================================================
+-- Fires AFTER UPDATE OF status when the new status is 'shipped'. Looks for
+-- backlog tasks that depend on the just-shipped one, AND whose remaining
+-- deps are also all shipped, AND that are not kind='spike'. Promotes them
+-- to 'ready'.
+--
+-- We deliberately do NOT touch tasks in any other status (active, blocked,
+-- completed, etc.) — auto-promotion only kicks in from 'backlog'. If a task
+-- was manually promoted earlier and is mid-flight, the trigger leaves it
+-- alone.
+
+CREATE OR REPLACE FUNCTION promote_dependents_on_ship()
+RETURNS TRIGGER AS $$
+BEGIN
+  -- Only fire on transition INTO 'shipped'
+  IF NEW.status = 'shipped' AND (OLD.status IS DISTINCT FROM 'shipped') THEN
+    UPDATE tasks t
+       SET status = 'ready',
+           promoted_at = COALESCE(t.promoted_at, now()),
+           updated_at = now()
+     WHERE t.status = 'backlog'
+       AND t.kind <> 'spike'
+       AND EXISTS (
+         SELECT 1 FROM task_dependencies td
+          WHERE td.task_id = t.id
+            AND td.depends_on_task_id = NEW.id
+       )
+       AND NOT EXISTS (
+         -- still has at least one unshipped dep
+         SELECT 1 FROM task_dependencies td2
+           JOIN tasks dep ON dep.id = td2.depends_on_task_id
+          WHERE td2.task_id = t.id
+            AND dep.status <> 'shipped'
+            AND dep.id <> NEW.id  -- the one we just shipped counts as shipped
+       );
+  END IF;
+  RETURN NEW;
+END;
+$$ LANGUAGE plpgsql;
+
+DROP TRIGGER IF EXISTS trg_promote_dependents_on_ship ON tasks;
+CREATE TRIGGER trg_promote_dependents_on_ship
+  AFTER UPDATE OF status ON tasks
+  FOR EACH ROW
+  EXECUTE FUNCTION promote_dependents_on_ship();
+
+-- ============================================================================
+-- 3. Bump migration counter
+-- ============================================================================
+UPDATE migration_counter SET next_number = GREATEST(next_number, 21) WHERE id = 1;
+
+-- ============================================================================
+-- 4. Record migration
+-- ============================================================================
+INSERT INTO schema_migrations (version) VALUES ('020_task_dependencies')
+  ON CONFLICT (version) DO NOTHING;
+
+COMMIT;