[R44VC0RP]

Replaces drizzle-kit push to production with a normal workflow of plain SQL change files, starting from a baseline verified against production.

Why

A read-only audit on 2026-10-21 found:

• The drizzle history couldn't be replayed.
  • There were 81 SQL files but only 75 journal entries.
  • Six numbers were duplicated (0044, 0048, 0050, 0054, 0059, 0060), and orphan hand-written files weren't in the journal.
  • One journal entry had no file (0047_thin_wind_dancer), and snapshots were missing.
  • Production's drizzle.__drizzle_migrations was empty.
• bun run db-prepare (generate + drizzle-kit push) was dangerous. Run against a copy of production, it wanted to:
  • drop the four *_merge_backup_20260929 tables (about 730 MB);
  • drop two hand-made indexes the IMAP gateway relies on;
  • drop and re-add three unique constraints that are identical (a drizzle-kit bug), one of them on structured_emails.
• drizzle-kit generate on main was stale. It emitted imap_mailbox_removals, which already exists in production.
• Local and e2e databases differed from production. They were built with drizzle-kit export, so they had no IMAP notify triggers and no hand-made indexes.

Production itself matches lib/db/schema.ts exactly, apart from those indexes, triggers and backup tables.

What changed

• History restarted (d05b5322):

  • The old files moved to drizzle/archive/, with a README. They're for reference only and are never applied.
  • The two hand-made indexes are now modelled in schema.ts.
  • New drizzle/migrations/0000_baseline.sql, plus 0001_imap_notify_triggers.sql with production's current function and trigger definitions (safe to re-run).

• Scripts (6b022153, 30c5291f), in scripts/db/:

  Script	What it does
  db:generate	Creates a migration file
  db:check	Fails if schema.ts changed without a migration; runs in CI with no database
  db:migrate:local	Applies migrations to the local database
  db:migrate:preview <branch>	Applies to that branch's Neon preview database. Refuses the production host, and refuses the shared Preview fallback
  db:migrate:prod	Requires an explicit PROD_DATABASE_URL and --yes=<host> or typing the host
  db:baseline:{prod,preview,local}	One-time marker for the baseline. Dry run by default, checks the target's tables, columns, indexes, constraints and triggers first, refuses a non-empty history table

  Other changes in these commits:

  • Every run takes an advisory lock, and db:migrate fails before any prompt if an already-applied migration was edited.
  • drizzle.config.ts no longer has database credentials, so an accidental drizzle-kit push/studio fails instead of connecting.
  • db-prepare is removed.
  • Local dev and e2e now build their databases from the migrations, so they get the triggers and indexes too.

• Rules (5bd68e45): a new "Database Changes" section in AGENTS.md:

  • every change is a reviewed migration file;
  • never edit an applied migration;
  • never push;
  • apply to preview, then to production before merging;
  • ship additive changes first;
  • the one-transaction limits (no CREATE INDEX CONCURRENTLY, and a new enum value can't be used in the same run);
  • agents apply to local and preview only, and the user applies to production.

  CI runs bun run db:check.

Verification

• Baseline vs production: I applied the baseline to a fresh Postgres 17 and compared pg_dump --schema-only with a read-only dump of production. The only difference is the 4 backup tables, left out on purpose. After that, drizzle-kit generate reports no changes.
• Baseline marker: it writes the same hashes and created_at values that drizzle-orm 0.43.1's migrator writes. After it, migrate reports nothing pending, and a dummy 0002 is the only pending migration.
• Refusals tested: a missing constraint, an edited applied migration, a non-empty history table, the production host through a pooled vs unpooled hostname or a port, a bare --yes, and the shared preview fallback.
• Tests: bun run test:e2e 23/23 and bun run test:unit 185/185, before and after. db:check passes, and fails when schema.ts changes without a migration.
• Reviews: two separate review passes, all findings fixed.

After merging (run by the user, once)

PROD_DATABASE_URL='<prod unpooled>' bun run db:baseline:prod            # dry run
PROD_DATABASE_URL='<prod unpooled>' bun run db:baseline:prod --apply    # records 0000
PROD_DATABASE_URL='<prod unpooled>' bun run db:migrate:prod             # applies 0001 (re-creates the IMAP triggers, re-runnable)

Existing local databases: run bun run db:baseline:local, or reset with bun run dev:local reset.

Effect on #214

#214 adds drizzle/0075_jev_classification.sql on the old history. Once this merges:

1. Merge main into that branch and drop its old-history files.
2. Regenerate with bun run db:generate --name jev_classification; it should produce 0002.
3. Apply it to the PR's preview database, then to production, before merging.

Not in this PR

The four *_merge_backup_20260929 tables stay in production. Drop them separately once the Sept 29 merge is confirmed final.

---

Note

High Risk
This changes how production and preview databases are updated; a mistaken migrate/baseline on the wrong host or skipping the one-time prod baseline could break IMAP or leave migration history inconsistent.

Overview
Replaces drizzle-kit push and the broken pre-October migration tree with a replayable workflow: lib/db/schema.ts stays the source of truth, and every change ships as numbered SQL under drizzle/migrations/.

Migration history is restarted: prior files move to drizzle/archive/ (reference only). Live chain is 0000_baseline.sql (production schema as of 2026-10-21) and 0001_imap_notify_triggers.sql (idempotent IMAP pg_notify triggers). drizzle.config.ts writes to drizzle/migrations and drops DB credentials so accidental push/studio cannot connect.

Tooling: removes db-prepare; adds db:generate, db:check (CI unit job), db:migrate:{local,preview,prod}, and db:baseline:{local,preview,prod} via scripts/db/ (journal validation, advisory locks, prod host confirmation, preview vs production guards). Local dev and e2e apply pending migrations instead of drizzle-kit export.

Schema: documents two production-only indexes in schema.ts (structured_emails_lower_recipient_idx, imap_mailbox_messages_mailbox_modseq_idx). AGENTS.md documents the new rules; a few scripts import @/lib/db/schema instead of the old drizzle/schema path.

^{Reviewed by Cursor Bugbot for commit 30c5291. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
inbound.new	Ready	Preview	Oct 21, 2026 11:36pm UTC