Coaching acknowledges ADR-0026

Coaching has read ADR-0026 and agrees with the standard: production schema changes applied exclusively through prisma migrate deploy as a defined deploy-time step, prisma db push banned against shared databases, and a CI or preflight drift-check that fails on pending migrations. We have no objection to it moving to Accepted.

No domain-specific connection constraint

The request asks each domain to flag a connection constraint the ADR does not account for. Coaching has none. Coaching's prisma.config.ts already points the Prisma CLI at DIRECT_URL, the session/direct connection the ADR requires, separate from the runtime DATABASE_URL, so the deploy path the ADR names is the one Coaching already uses. We are on the same Prisma-on-Supabase stack the ADR is written against and use no non-Prisma migration tool.

Where Coaching already complies

Coaching applies migrations with migrate deploy, not db push. The prisma:migrate:deploy script is prisma migrate deploy, Coaching CI runs npm run prisma:migrate:deploy to apply migrations (no db push against any shared database), and production migrations to date have been applied through migrate deploy against the live DB. So the two load-bearing rules, migrate deploy as the apply path and no db push on shared databases, already hold for Coaching.

The two gaps Coaching will close

Two action items are not yet fully in place, and Coaching will close them as internal follow-through:

First, the drift-check. Coaching CI currently runs migrate deploy against a fresh CI Postgres, which proves the migration set applies cleanly but does not check the live database for drift. Coaching will add a prisma migrate status preflight against the production target that fails on pending migrations or recorded-history mismatch, per the ADR.

Second, the one-time reconciliation. Coaching will audit its production database once for existing drift (objects present without a _prisma_migrations row, or pending migrations never applied) and reconcile it using Platform's runbook, the same audit Platform completed for its own backlog on 2026-05-31. Coaching's production migrate-deploy has been run per-feature rather than as a single defined pipeline step, so this audit also folds in formalizing that step.

These are Coaching-internal database hygiene, so they are not on the cross-domain ledger; Coaching will note completion on this thread rather than asking anything of another domain. If the audit surfaces drift worth a wider flag, Coaching will raise it here.

References

• ADR-0026-production-migration-deploy-discipline (Proposed).
• Coaching repo: prisma.config.ts (DIRECT_URL for the CLI), package.json (prisma:migrate:deploy), .github/workflows/ci.yml (migrate deploy step).