limn-review 0.1.123

package/dist/db/migrations-pg/0046_merge_queue_state.sql

@@ -0,0 +1,18 @@
+-- GitHub's native merge queue as a SYNCED, STORED fact — the Postgres twin of sqlite
+-- 0059_merge_queue_state.sql. HAND-WRITTEN ADDITIVE, like every pg migration since 0023: never
+-- regenerate the baseline with `pnpm db:generate:pg`, which squashes it.
+--
+-- Read the sqlite twin for the full argument. The two things that will otherwise be re-litigated:
+--   • it is stored because MergeStateStatus has NO QUEUED member — a queued PR reports `blocked`,
+--     indistinguishable from a protection-blocked one — and the Pending board may not fetch on
+--     mount to find out (fifty cards would be ~150 GitHub calls to paint a screen);
+--   • ⚠ NEITHER COLUMN TAKES A DEFAULT: null means "not observed", not "not queued". A DEFAULT
+--     false would assert about every already-synced PR that GitHub had said it is out of the
+--     queue, which it never did.
+-- Position and estimatedTimeToMerge stay live-only in GET /api/prs/:id/merge-options — genuinely
+-- volatile, and rendered only by the click-gated merge control.
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "in_merge_queue" boolean;--> statement-breakpoint
+-- GitHub's MergeQueueEntryState, lowercased (awaiting_checks | locked | mergeable | queued |
+-- unmergeable). Kept as `text` with a drizzle `enum:`, matching every other stored enum on this
+-- table — no native pg enum, so there is nothing to CREATE TYPE here.
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "merge_queue_entry_state" text;

package/dist/db/migrations-pg/0047_drop_my_turn_dismissals.sql

@@ -0,0 +1,21 @@
+-- DROP `my_turn_dismissals` — the Postgres twin of sqlite 0060_drop_my_turn_dismissals.sql.
+-- HAND-WRITTEN ADDITIVE, like every pg migration since 0023: never regenerate the baseline with
+-- `pnpm db:generate:pg`, which squashes it.
+--
+-- ⚠ DESTRUCTIVE AND ONE-WAY. No down migration, no archive — the rows go when this runs. The
+-- table has already been inert for a release (the ball rule landed in `getMyTurn` first), so
+-- nothing breaks, but a restore is the only way back.
+--
+-- Read the sqlite twin for the full argument. In short: each row was a hand-written "I have seen
+-- this", needed only because My Turn had no predicate for "you already acted on this PR". The ball
+-- rule is that predicate — state-derived, recomputed on every read — so a card now leaves the
+-- board when the user does the work rather than when they tell the app they did. And a dismissal
+-- never expired, which made it a ticket queue kept true by grooming: exactly the thing this
+-- product claims not to be.
+--
+-- IF-EXISTS because a fresh cloud database may or may not have replayed the 0000 baseline that
+-- created it. The FK to `accounts` and both indexes (`mtd_kind_ref_ux`, `mtd_account_idx`) are
+-- dropped with the table; nothing else references it, so no CASCADE is needed and none is given —
+-- a CASCADE here could only ever mean something unexpected depends on this table, which is a
+-- failure worth seeing rather than swallowing.
+DROP TABLE IF EXISTS "my_turn_dismissals";

package/dist/db/migrations-pg/0048_auto_merge_durable_anchors.sql

@@ -0,0 +1,27 @@
+-- Two anchors the auto-merge watcher DISARMS on, moved out of process memory onto the row.
+-- The SQLite twin is migrations/0061_auto_merge_durable_anchors.sql.
+--
+-- WHY. Both facts lived in module-level Maps in `merge/auto-merge-runner.ts` (`pendingUpdates`,
+-- and the retarget guard's implicit reliance on a synced column read at run time). A Map is fine
+-- for a hint. It is not fine for a fact the watcher ends an intent on, because losing it does not
+-- read as "I forgot" — it reads as "something unexplained happened to this branch", and the safe
+-- response to an unexplained head move is to disarm. Under `pnpm dev` that is every file save;
+-- in cloud it is every deploy. Measured on the author's own account, 3 of 21 intents died and a
+-- further 2 were at risk from exactly this class of bookkeeping loss.
+--
+-- ⚠ BOTH ARE NULLABLE WITH NO DEFAULT, AND NULL MEANS "NOT RECORDED", NEVER A VALUE.
+-- "expected_base_ref" is null on every row armed before this migration; the retarget guard falls
+-- back to the synced base ref for those, which is exactly what it did before, so no already-armed
+-- intent changes behaviour. A DEFAULT here would assert the user consented to a branch nobody
+-- asked them about.
+
+-- The base branch the SPA was showing when the user armed. The head pin cannot see a retarget
+-- (PATCH pulls/{n} with a new `base` leaves head.sha alone), so consent to "merge into main"
+-- needs its own anchor. It was being approximated by reading `pull_requests.base_ref_name` at RUN
+-- time — a value the sync owns and may correct at any moment, at which point the watcher reports
+-- a retarget that never happened.
+ALTER TABLE "auto_merge_requests" ADD COLUMN IF NOT EXISTS "expected_base_ref" text;--> statement-breakpoint
+-- The head SHA an in-flight update-branch was issued AGAINST. GitHub's update-branch returns 202
+-- with no handle to poll, so the head move it causes arrives on a later tick; without this the
+-- watcher cannot tell its OWN merge commit from a human push and disarms with "the branch moved".
+ALTER TABLE "auto_merge_requests" ADD COLUMN IF NOT EXISTS "update_issued_against_oid" text;

package/dist/db/migrations-pg/0049_blast_radius_config.sql

@@ -0,0 +1,8 @@
+-- Postgres twin of migrations/0062_blast_radius_config.sql — the blast-radius reading settings
+-- (CORE, free, no AI), one nullable JSON blob per account. See the sqlite original for why this
+-- is account-grained, why it is one JSON column rather than six integers, and why it is nullable
+-- with no backfill.
+--
+-- `jsonb` here against sqlite's `text` json mode: the standard divergence in this schema pair
+-- (the header of schema.pg.ts records the mapping), and both read back as the same object.
+ALTER TABLE "accounts" ADD COLUMN "blast_radius_config" jsonb;

package/dist/db/migrations-pg/0050_repo_file_coupling.sql

@@ -0,0 +1,13 @@
+-- Postgres twin of migrations/0063_repo_file_coupling.sql — the per-repo co-change index behind
+-- the blast-radius hub arm. See the sqlite original for what it stores, why it stores only the
+-- hubs, and why `hub_bar` is max(repo p90, an absolute floor) rather than either alone.
+CREATE TABLE IF NOT EXISTS "repo_file_coupling" (
+	"id" serial PRIMARY KEY NOT NULL,
+	"account_id" integer NOT NULL REFERENCES "accounts"("id"),
+	"repo_id" integer NOT NULL REFERENCES "repos"("id"),
+	"hub_bar" integer NOT NULL,
+	"pr_count" integer NOT NULL,
+	"hubs" jsonb NOT NULL,
+	"built_at" timestamp with time zone DEFAULT now() NOT NULL
+);
+CREATE UNIQUE INDEX IF NOT EXISTS "rfc_account_repo" ON "repo_file_coupling" ("account_id","repo_id");

package/dist/db/migrations-pg/0051_pr_content_kind.sql

@@ -0,0 +1,6 @@
+-- Postgres twin of migrations/0064_pr_content_kind.sql — what a pull request's code churn
+-- consists of ('comments' | 'formatting' | 'code'), plus the head sha it was read at. See the
+-- sqlite original for why NULL is the common case, why there is no backfill, and why the sha
+-- column is load-bearing rather than bookkeeping.
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "content_kind" text;
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "content_kind_sha" text;

package/dist/db/migrations-pg/0052_workspace_flow_settings.sql

@@ -0,0 +1,4 @@
+-- Postgres twin of migrations/0065_workspace_flow_settings.sql — a workspace's working hours,
+-- time zone and wait budgets for Chronology, stored as OVERRIDES ONLY (NULL = every default).
+-- See the sqlite original for why it is per workspace and why there is no backfill.
+ALTER TABLE "workspaces" ADD COLUMN IF NOT EXISTS "flow_settings" jsonb;

package/dist/db/migrations-pg/0053_review_request_events.sql

@@ -0,0 +1,18 @@
+-- Postgres twin of migrations/0066_review_request_events.sql — the review-request HISTORY (every
+-- requested / removed event from a PR's timeline) plus the per-PR "history received" stamp. See
+-- the sqlite original for why the table carries no account_id, why it is immutable, and why NULL
+-- in the stamp means "not known" rather than "never requested".
+CREATE TABLE IF NOT EXISTS "review_request_events" (
+	"id" serial PRIMARY KEY NOT NULL,
+	"pr_id" integer NOT NULL,
+	"github_node_id" text NOT NULL,
+	"kind" text NOT NULL,
+	"occurred_at" timestamp with time zone NOT NULL,
+	"reviewer_kind" text NOT NULL,
+	"reviewer_user_id" integer,
+	"team_slug" text,
+	CONSTRAINT "review_request_events_pr_id_pull_requests_id_fk" FOREIGN KEY ("pr_id") REFERENCES "pull_requests"("id"),
+	CONSTRAINT "review_request_events_reviewer_user_id_users_id_fk" FOREIGN KEY ("reviewer_user_id") REFERENCES "users"("id")
+);
+CREATE UNIQUE INDEX IF NOT EXISTS "review_request_events_pr_node" ON "review_request_events" ("pr_id","github_node_id");
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "review_requests_synced_at" timestamp with time zone;

package/dist/db/migrations-pg/0054_pr_security_signals.sql

@@ -0,0 +1,59 @@
+-- Postgres twin of migrations/0067_pr_security_signals.sql. Read that file for the reasoning:
+-- four small DERIVED columns on `pull_requests` (`dependency_vendor`, `security_fix`,
+-- `advisory_ids`, `security_checked_at`) read at sync from the PR's title, branch, labels and FULL
+-- `bodyText` — no bodies stored, a three-state write (a body that was not received writes
+-- nothing), never `search_index` (its 4,000-character cap cuts Dependabot's footer off), and
+-- `security_checked_at` NULL is the backfill's worklist.
+--
+-- The `workspace_reviewers` UPDATEs upgrade six newly-known automation logins (plus Semgrep's
+-- per-org App) whose stored role/kind would otherwise beat the new login seed forever — the
+-- 0040/0041 precedent, with the same three conditions.
+--
+-- Only spelling difference from the sqlite file: `regexp_replace(…, '\[bot\]$', '')` rather
+-- than `replace(…, '[bot]', '')` (the documented divergence; each is idiomatic for its dialect).
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "dependency_vendor" text;
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "security_fix" text;
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "advisory_ids" jsonb;
+ALTER TABLE "pull_requests" ADD COLUMN IF NOT EXISTS "security_checked_at" timestamp with time zone;
+UPDATE "workspace_reviewers"
+SET "role" = 'dependency'
+WHERE "source" <> 'manual'
+  AND "author_user_id" IN (
+    SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN
+      ('snyk-io', 'aikido-autofix', 'mend-for-github-com')
+  );
+UPDATE "workspace_reviewers"
+SET "role" = 'quality_check'
+WHERE "source" <> 'manual'
+  AND "author_user_id" IN (
+    SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('endor-labs-pro')
+       OR lower("github_login") LIKE 'semgrep-code-%' OR lower("github_login") LIKE 'semgrepcode-%'
+  );
+UPDATE "workspace_reviewers"
+SET "role" = 'code_agent'
+WHERE "source" <> 'manual'
+  AND "author_user_id" IN (
+    SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN
+      ('step-security-bot', 'orbisai0security')
+  );
+UPDATE "workspace_reviewers" SET "kind" = 'snyk', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('snyk-io'));
+UPDATE "workspace_reviewers" SET "kind" = 'aikido', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('aikido-autofix'));
+UPDATE "workspace_reviewers" SET "kind" = 'mend', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('mend-for-github-com'));
+UPDATE "workspace_reviewers" SET "kind" = 'endor', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('endor-labs-pro'));
+UPDATE "workspace_reviewers" SET "kind" = 'semgrep', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE lower("github_login") LIKE 'semgrep-code-%' OR lower("github_login") LIKE 'semgrepcode-%');
+UPDATE "workspace_reviewers" SET "kind" = 'step_security', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('step-security-bot'));
+UPDATE "workspace_reviewers" SET "kind" = 'orbisai', "label" = NULL
+WHERE "identity_source" <> 'manual' AND "kind" IN ('in_house', 'vendor')
+  AND "author_user_id" IN (SELECT "id" FROM "users" WHERE regexp_replace(lower("github_login"), '\[bot\]$', '') IN ('orbisai0security'));

package/dist/db/migrations-pg/0055_my_turn_settings.sql

@@ -0,0 +1,6 @@
+-- Postgres twin of migrations/0068_my_turn_settings.sql. See the sqlite original for why the
+-- settings are overrides-only with no backfill, and why mentioned_at starts NULL. jsonb against
+-- sqlite's text json mode is the standard divergence (schema.pg.ts header).
+ALTER TABLE "accounts" ADD COLUMN IF NOT EXISTS "my_turn_settings" jsonb;
+ALTER TABLE "pr_mentions" ADD COLUMN IF NOT EXISTS "mentioned_at" timestamp with time zone;
+ALTER TABLE "pr_mentions" ADD COLUMN IF NOT EXISTS "mentioned_by_user_id" integer;

package/dist/db/migrations-pg/0056_my_turn_dismissals.sql

@@ -0,0 +1,21 @@
+-- MY TURN DISMISSALS — the Postgres twin of migrations/0069_my_turn_dismissals.sql. Read that
+-- header for the contract (and 0047/0060 for why the previous table of this name was dropped).
+--
+-- `pull_requests_id_account` is the parent key of the composite tenancy FK below, the
+-- `repos_id_account` trick; Postgres accepts a plain unique index there.
+CREATE UNIQUE INDEX IF NOT EXISTS "pull_requests_id_account" ON "pull_requests" USING btree ("id","account_id");
+--> statement-breakpoint
+CREATE TABLE IF NOT EXISTS "my_turn_dismissals" (
+	"id" serial PRIMARY KEY NOT NULL,
+	"account_id" integer NOT NULL,
+	"pr_id" integer,
+	"repo_id" integer,
+	"dismissed_at" timestamp with time zone NOT NULL,
+	CONSTRAINT "my_turn_dismissals_account_id_accounts_id_fk" FOREIGN KEY ("account_id") REFERENCES "accounts"("id") ON DELETE cascade,
+	CONSTRAINT "my_turn_dismissals_pr_account_fk" FOREIGN KEY ("pr_id","account_id") REFERENCES "pull_requests"("id","account_id") ON DELETE cascade,
+	CONSTRAINT "my_turn_dismissals_repo_account_fk" FOREIGN KEY ("repo_id","account_id") REFERENCES "repos"("id","account_id") ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX IF NOT EXISTS "my_turn_dismissals_account_pr" ON "my_turn_dismissals" USING btree ("account_id","pr_id");
+--> statement-breakpoint
+CREATE UNIQUE INDEX IF NOT EXISTS "my_turn_dismissals_account_repo" ON "my_turn_dismissals" USING btree ("account_id","repo_id");

package/dist/db/migrations-pg/0057_claude_review_follow_up_ticket.sql

@@ -0,0 +1,8 @@
+-- Postgres twin of migrations/0070_claude_review_follow_up_ticket.sql. See the sqlite original for
+-- the contracts and why prior_finding_id is a soft reference with no FK. Claude Review is
+-- local-only, so these columns exist in Postgres for schema parity. jsonb against sqlite's text
+-- json mode is the standard divergence (schema.pg.ts header).
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "ticket" jsonb;
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "ticket_assessment" jsonb;
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "follow_up" jsonb;
+ALTER TABLE "claude_review_findings" ADD COLUMN IF NOT EXISTS "prior_finding_id" integer;

package/dist/db/migrations-pg/0058_claude_review_trigger.sql

@@ -0,0 +1,4 @@
+-- Postgres twin of migrations/0071_claude_review_trigger.sql, where the contract lives.
+-- 'manual' | 'auto'; existing rows read 'manual'. Claude Review is local-only, so the column exists
+-- in Postgres for schema parity.
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "trigger" text DEFAULT 'manual' NOT NULL;

package/dist/db/migrations-pg/0059_commit_message_headline.sql

@@ -0,0 +1,3 @@
+-- Postgres twin of migrations/0072_commit_message_headline.sql, where the contract lives.
+-- Nullable: NULL is "not synced yet", never an empty headline.
+ALTER TABLE "commits" ADD COLUMN IF NOT EXISTS "message_headline" text;

package/dist/db/migrations-pg/0060_claude_review_chat.sql

@@ -0,0 +1,24 @@
+-- Postgres twin of migrations/0073_claude_review_chat.sql, where the contract lives. Claude Review
+-- is local-only, so the table exists in Postgres for schema parity.
+CREATE UNIQUE INDEX IF NOT EXISTS "claude_reviews_id_account" ON "claude_reviews" USING btree ("id","account_id");
+--> statement-breakpoint
+CREATE TABLE IF NOT EXISTS "claude_review_chat_messages" (
+	"id" serial PRIMARY KEY NOT NULL,
+	"account_id" integer NOT NULL,
+	"review_id" integer NOT NULL,
+	"finding_id" integer,
+	"role" text NOT NULL,
+	"content" text NOT NULL,
+	"model" text,
+	"cost_usd" double precision,
+	"input_tokens" integer,
+	"output_tokens" integer,
+	"created_at" timestamp with time zone DEFAULT now() NOT NULL,
+	CONSTRAINT "claude_review_chat_messages_account_id_accounts_id_fk" FOREIGN KEY ("account_id") REFERENCES "accounts"("id") ON DELETE cascade,
+	CONSTRAINT "claude_review_chat_messages_finding_id_claude_review_findings_id_fk" FOREIGN KEY ("finding_id") REFERENCES "claude_review_findings"("id") ON DELETE cascade,
+	CONSTRAINT "crcm_review_account_fk" FOREIGN KEY ("review_id","account_id") REFERENCES "claude_reviews"("id","account_id") ON DELETE cascade
+);
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "crcm_thread_idx" ON "claude_review_chat_messages" USING btree ("review_id","finding_id","id");
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "crcm_account_idx" ON "claude_review_chat_messages" USING btree ("account_id");

package/dist/db/migrations-pg/0061_adopt_agentic_tables.sql

@@ -0,0 +1,79 @@
+-- ADOPT THE AGENTIC TABLES INTO CORE — the Postgres twin of
+-- migrations/0074_adopt_agentic_tables.sql, where the contract lives. Every statement is
+-- replay-safe (IF NOT EXISTS), so an install where the plugin already created the tables adopts
+-- them in place. Unlike SQLite, Postgres can add the comments-seed columns idempotently, so an
+-- adopted ai_fixes that predates plugin 0024 is brought up to shape here too.
+CREATE TABLE IF NOT EXISTS "review_learnings" (
+	"id" serial PRIMARY KEY,
+	"account_id" integer NOT NULL,
+	"repo_id" integer NOT NULL,
+	"pr_id" integer NOT NULL,
+	"source_review_id" integer NOT NULL,
+	"finding_id" integer,
+	"head_sha" text NOT NULL,
+	"kind" text NOT NULL,
+	"path" text,
+	"dir_path" text,
+	"ext" text,
+	"category" text,
+	"claude_verdict" text,
+	"user_verdict" text,
+	"claude_title" text,
+	"claude_text" text,
+	"user_text" text,
+	"posted_comment_kind" text,
+	"dedupe_key" text NOT NULL,
+	"created_at" timestamp with time zone DEFAULT now() NOT NULL
+);
+--> statement-breakpoint
+CREATE UNIQUE INDEX IF NOT EXISTS "rl_account_dedupe" ON "review_learnings" ("account_id","dedupe_key");
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "rl_account_repo_category" ON "review_learnings" ("account_id","repo_id","category");
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "rl_account_repo_dir" ON "review_learnings" ("account_id","repo_id","dir_path");
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "rl_account_source_review" ON "review_learnings" ("account_id","source_review_id");
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "rl_account_repo_created" ON "review_learnings" ("account_id","repo_id","created_at");
+--> statement-breakpoint
+CREATE TABLE IF NOT EXISTS "ai_fixes" (
+	"id" serial PRIMARY KEY,
+	"account_id" integer NOT NULL,
+	"repo_id" integer NOT NULL,
+	"pr_id" integer NOT NULL,
+	"source_review_id" integer,
+	"base_sha" text NOT NULL,
+	"status" text NOT NULL,
+	"model" text NOT NULL,
+	"seed" text NOT NULL,
+	"prompt" text,
+	"summary" text,
+	"commit_message" text,
+	"patch" text,
+	"files_changed" text,
+	"cost_usd" double precision,
+	"input_tokens" integer,
+	"output_tokens" integer,
+	"num_turns" integer,
+	"error" text,
+	"pushed_branch" text,
+	"pushed_pr_number" integer,
+	"pushed_pr_url" text,
+	"pushed_at" timestamp with time zone,
+	"created_at" timestamp with time zone DEFAULT now() NOT NULL,
+	"finished_at" timestamp with time zone,
+	"comment_targets" text,
+	"comment_verdicts" text
+);
+--> statement-breakpoint
+ALTER TABLE "ai_fixes" ADD COLUMN IF NOT EXISTS "comment_targets" text;
+--> statement-breakpoint
+ALTER TABLE "ai_fixes" ADD COLUMN IF NOT EXISTS "comment_verdicts" text;
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "af_account_pr_created" ON "ai_fixes" ("account_id","pr_id","created_at");
+--> statement-breakpoint
+CREATE INDEX IF NOT EXISTS "af_account_status" ON "ai_fixes" ("account_id","status");
+--> statement-breakpoint
+ALTER TABLE "workspaces" ADD COLUMN IF NOT EXISTS "auto_review_enabled" boolean;
+--> statement-breakpoint
+ALTER TABLE "workspaces" ADD COLUMN IF NOT EXISTS "auto_review_enabled_at" timestamp with time zone;

package/dist/db/migrations-pg/0062_review_lens_drop_learnings.sql

@@ -0,0 +1,5 @@
+-- Postgres twin of migrations/0075_review_lens_drop_learnings.sql, where the contract lives:
+-- claude_review_findings.lens (nullable, no backfill) and review memory's table dropped.
+ALTER TABLE "claude_review_findings" ADD COLUMN IF NOT EXISTS "lens" text;
+--> statement-breakpoint
+DROP TABLE IF EXISTS "review_learnings";

package/dist/db/migrations-pg/0063_claude_review_threads.sql

@@ -0,0 +1,7 @@
+-- Postgres twin of migrations/0076_claude_review_threads.sql, where the contract lives:
+-- claude_reviews.thread_assessments (other reviewers' open threads, judged) and
+-- claude_reviews.comments_through (the comment half of the auto re-review key). Both nullable, no
+-- backfill.
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "thread_assessments" jsonb;
+--> statement-breakpoint
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "comments_through" timestamp with time zone;

package/dist/db/migrations-pg/0064_claude_review_ci_failures.sql

@@ -0,0 +1,4 @@
+-- Postgres twin of migrations/0077_claude_review_ci_failures.sql, where the contract lives:
+-- claude_reviews.ci_failures (the head's CI state at review time and Claude's diagnosis of each
+-- failing check). Nullable, no backfill.
+ALTER TABLE "claude_reviews" ADD COLUMN IF NOT EXISTS "ci_failures" jsonb;

package/dist/db/migrations-pg/0065_ai_fix_change_report.sql

@@ -0,0 +1,9 @@
+-- Postgres twin of migrations/0078_ai_fix_change_report.sql, where the contract lives:
+-- ai_fixes.trigger ('manual' | 'auto'), ai_fixes.review_items (the review items a 'review' run was
+-- given, with refs) and ai_fixes.change_report (the validated per-change report). Text JSON like
+-- the table's other JSON columns. All nullable, no backfill.
+ALTER TABLE "ai_fixes" ADD COLUMN IF NOT EXISTS "trigger" text;
+--> statement-breakpoint
+ALTER TABLE "ai_fixes" ADD COLUMN IF NOT EXISTS "review_items" text;
+--> statement-breakpoint
+ALTER TABLE "ai_fixes" ADD COLUMN IF NOT EXISTS "change_report" text;

package/dist/db/migrations-pg/0066_claude_finding_story.sql

@@ -0,0 +1,7 @@
+-- Postgres twin of migrations/0079_claude_finding_story.sql, where the contract lives:
+-- claude_review_findings.story_index (the ticket's 0-based position on the run) and
+-- claude_review_findings.story_ref ('AC2' / 'M1') mark a finding the server made from the run's
+-- user-story assessment. Both NULL on an ordinary finding. Nullable, no backfill.
+ALTER TABLE "claude_review_findings" ADD COLUMN IF NOT EXISTS "story_index" integer;
+--> statement-breakpoint
+ALTER TABLE "claude_review_findings" ADD COLUMN IF NOT EXISTS "story_ref" text;