Recover Payne’s database

In local-live, PostgreSQL owns Shutdown Gates, immutable evidence, jobs, approvals, monitoring, invalidations, and delivery history. Diagnose service availability before running a migration. Do not edit evidence or events directly.

1. Open Health and read the database and migration status. This check does not mutate durable records.
2. Confirm the local PostgreSQL container is running and that the server-only runtime and migration URLs point to the Payne database. Do not paste either URL into the browser or an issue report.
3. If Health reports committed migrations are missing, run the migration command below. It creates only missing Payne schema objects and migration records; it does not erase gate history.

pnpm db:migrate

4. Restart the unavailable web or worker process, then reopen Health.

The migration role owns schema changes. The runtime application role has narrower permissions. A database reset is not a recovery step for records you need to preserve.