feat(cli): make pg-delta the only and the default diff engine

[avallete]

Summary

Two changes that finish the pg-delta migration, tracked as CLI-2211 and CLI-1588:

1. The in-process pg-delta engine is now the only pg-delta implementation (CLI-2211)

The SUPABASE_USE_PG_DELTA_NEXT escape hatch shipped in v2.115.0 as a temporary opt-out back to the legacy edge-runtime engine; its release notes announced removal after ~a month. Setting it now has no effect. Deleted with the legacy engine (net −4,300 lines):

• the flag module and the engine selector layer; LegacyPgDeltaEngine loses its implementation discriminator and every handler branch keyed on it
• the edge-runtime pg-delta Deno script templates, the supabase/.temp/pgdelta-version npm pin, and the PGDELTA_NPM_REGISTRY / PGDELTA_{SOURCE,TARGET}_SSLROOTCERT plumbing (all legacy-engine-only; the edge-runtime service itself stays — migra still runs through it)
• the migrations-catalog cache warmups after db push / db reset / start / db start / bootstrap, and the whole catalog snapshot machinery (legacy-pgdelta.cache.ts); the shared migration lister moves to legacy-migration-list.ts
• the legacy declarative catalog seam (LegacyDeclarativeSeam.exportCatalog), the declarative-apply engine (legacy-pgdelta.apply.ts), and db pull's legacy empty-diff debug bundle
• the "--strict-coverage has no effect with the legacy pg-delta engine" warning — the flag is now always effective

2. pg-delta is the default diff engine for all projects (CLI-1588)

An absent [experimental.pgdelta] section — or a section that omits enabled — now resolves to pg-delta for db diff, db pull, and db remote commit, in the TypeScript CLI, @supabase/config (and the published JSON schema), and the Go binary backing the delegated db remote changes|commit / db pull --experimental commands.

The Go zero-value tri-state called out in CLI-1588 needed no *bool: the ejected config template now defaults enabled = true, and since mergeDefaultValues feeds that template to viper as the default config, viper's key-level merge resolves both the absent-section and omitted-key cases to true while an explicit enabled = false still wins.

Rollback stays one line: [experimental.pgdelta] enabled = false in config.toml, or per-invocation --use-migra (db diff) / --diff-engine migra (db pull). Migra is unchanged. The explicit config rollback is authoritative: the historical SUPABASE_EXPERIMENTAL_PG_DELTA opt-in env var is no longer consulted (with pg-delta on by default it added nothing, and a stale opt-in would have silently defeated enabled = false); --use-pg-delta remains the per-run opt-in that overrides the rollback.

Knock-on behavior changes to note in release notes:

• the db schema declarative commands' gate (--experimental || pgdelta enabled) is now open by default
• a versionless db reset --experimental only takes the [db.migrations].schema_paths schema-files path when pg-delta is explicitly disabled; otherwise it replays migrations
• SUPABASE_EXPERIMENTAL_PG_DELTA is ignored (see Rollback above)

SIDE_EFFECTS.md files, db diff/db pull docs, and the Go CONTRIBUTING pg-delta section were updated to match. Tests pin the new default (absent config → pg-delta), the explicit-false → migra rollback (including with a stale env opt-in present), and the per-invocation flag overrides; migra-subject tests opt out explicitly.

Linked issue

Linear: CLI-2211, CLI-1588

• The linked issue is open and carries the open-for-contribution label (or I'm a Supabase maintainer).

Checklist

• The PR title follows Conventional Commits (e.g. fix(cli): …).
• Tests added or updated for the change.
• From the repository root, pnpm check:all passes; relevant package tests pass for every touched workspace, and pnpm types:check passes for each touched TypeScript workspace (or workspace declaring it).

🤖 Generated with Claude Code

https://claude.ai/code/session_01BQAoY9JF4uiZRvKVkSd9Wy

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:2f97b70424

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

Supabase CLI preview

npx --yes https://pkg.pr.new/supabase/cli/supabase@1b603b7b25976ebadecb403f7a06ff66c58b5e53

Preview package for commit 1b603b7.

[avallete]

CI status note — Run end-to-end tests (shard 2/3) failure is not this PR's.

The failing test is packages/stack tests/createStack.e2e.test.ts: its beforeAll times out after 45s inside createStack({...}) (before stack.start()), followed by the afterAll 30s timeout. It failed identically on this PR's last two heads — and also on the unrelated #6371 (workers push, run 33230852020, where all three e2e shards failed with the exact same createStack.e2e.test.ts:24 / :44 hook timeouts).

Why it's not this PR's:

• This diff touches apps/cli, apps/cli-go, and packages/config. packages/stack depends only on @effect/* and @supabase/process-compose — not @supabase/config — and neither stack nor process-compose is touched here.
• The last green e2e run was Aug 28 17:28 UTC (run 4834); every test.yml run since then shows failures across unrelated branches, and nothing touching packages/stack merged to develop in that window (only CI-workflow commits).

No fix PR exists yet that I can port. A fresh run (33239773281) is already in progress on the current head 64831cd and serves as the re-run; I'll keep watching it. All other failures from the previous run are resolved: the 14 Go test failures were fixed in 4234d36, and the "Run unit and integration tests" red on the old head was unit=success, integration=cancelled — cancellation from the superseding push, not a test failure.

---

Generated by Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:64831cdca5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[avallete]

CI status note (2/2) — Run end-to-end tests (shard 3/3) failure is also not this PR's.

The failing test is apps/cli src/next/commands/start/start.e2e.test.ts:67 ("keeps an HTTP service dormant until its first proxied request"): supabase start exits 1 with stdout ending at postgres: Initializing.... The unrelated #6371 failed with the identical test and assertion (start.e2e.test.ts:67, expected 1 to be +0) in run 33230852020. src/next/ has no pg-delta code paths, so this diff cannot reach it.

Together with the shard 2/3 createStack hook timeout (see previous note), both point at the same underlying repo-wide breakage: local Docker stack provisioning failing in CI since Aug 28 ~18:00 UTC, on every branch. No fix exists yet to port. Everything within this PR's control is green-bound; these two e2e checks will stay red until the base breakage is fixed.

---

Generated by Claude Code