Initialize verified-empty application schemas with a frozen v0.12.2 schema
and catalog snapshot, recording historical migration checksums in the same
transaction. Preserve existing histories and reject incomplete, failed or
unknown states without automatic adoption or reset.

Run one Compose migration job before web, ingress and worker. Use shared
readiness locks and an exclusive migrator lock, validate the generated
client's tables and columns, and keep migration output free of secrets.
Custom deployments must replace raw Prisma startup overrides with
sh /usr/local/bin/gitchalerts-start migrate and retain the success gate.
No encryption-key rotation, provider reconnect or new environment setting
is required. Existing historical SQL files remain unchanged.

Add packaged PostgreSQL 17/18 acceptance coverage for the original failure,
the complete historical sequence, fresh OIDC bootstrap and alert SSE,
both existing-history fixtures, data and decryption preservation, repeat
runs, concurrent checks, schema isolation and failed migration gating.

Refs #182. Release publication, the signed Homelab bundle update and dev
deployment acceptance remain follow-up work; preserve the deployment hold.

@@ -0,0 +128,4 @@
+      .filter((field) => field.kind !== 'object')
+      .map((field) => identifier(field.dbName ?? field.name));
+    try {
+      await client.query(

@@ -0,0 +203,4 @@
+  log = (message) => console.info(`[migrations] ${message}`),
+} = {}) {
+  log(checkOnly ? 'Checking database readiness.' : 'Starting database migration.');
+  const { schema, ...connection } = connectionSettings(process.env.DATABASE_URL);