Apply committed migrations on boot instead of db push --accept-data-loss #192

Background

src/index.ts:18 runs execSync("npx prisma db push --accept-data-loss") on every startup, while prisma/migrations/ holds seven committed migrations that are never applied. db push diffs the schema and drops whatever does not match; --accept-data-loss makes that non-interactive. Commit 1acb9dd ("let db push add the network primary key to populated tables") is the scar tissue from exactly this.

tests/integration/migrations.test.ts already tests migration idempotency, so the migrations are verified and simply unused.

Acceptance criteria

• Startup runs prisma migrate deploy; db push survives only behind an explicit dev/test flag
• A migration failure is fatal with a clear message — a half-migrated database serving traffic is worse than a crash
• docs/ documents the drift-recovery path for a database that was previously db pushed
• A fresh database reaches the current schema via migrate deploy alone
• --accept-data-loss appears on no production path

Drips Wave · Complexity: Intermediate · 150 points

How this repo is laid out

Wraith is a Soroban incoming-transfer indexer: it fills the gap Horizon leaves for SAC/SEP-41 token events by recipient address. Roughly 14k lines under src/, REST + GraphQL + WebSocket, Postgres via Prisma, deployed on Render.

• Unit tests are jest (src/**/__tests__, tests/*.test.ts), with a coverage gate.
• Integration tests are vitest (tests/integration/, vitest.integration.config.ts, Docker).
• Don't mix the two runners in one file.

Known state of main before you start

tsc --noEmit and the unit suite are green. The Integration tests CI job is red, and so is Load test — both predate this batch. Open PRs #177 and #178 address them. If the integration job is red when you open a PR, that is not your fault; say so in the PR and carry on.

Four modules are shipped, closed as done, and imported by nothing: src/indexer/checkpoint.ts, src/ingest/reorg.ts, src/middleware/opa.ts, and src/api/candles.ts + src/workers/ohlc-refresh.ts. So the live indexer today has no reorg handling and no atomic checkpointing, despite both features being closed. Two issues below start unpicking that — don't assume a closed issue means a wired feature.

Ground rules

• Every PR needs a test that fails before the change and passes after, unless the issue says otherwise.
• Don't widen a Prometheus label to something unbounded — addresses and contract ids must never become label values.
• Nothing may log or return a raw database error, a connection string, or a provider URL.
• Don't reformat a file you're changing. A diff that is 90% whitespace hides the 10% that matters.

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk