test: verify outcome migrations and worker recovery on PostgreSQL

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0e747-8f27-7242-8df8-8bc44f88c929

workplans/HUB-WP-0012-netkingdom-platform-root-access.md

@@ -389,6 +389,25 @@ suite. Inventory drift, distribution builds, isolated installed-wheel checks
 and current migration/context/store wheel contents pass.
 No database migration or deployment was applied to a live service.
 
+## Real PostgreSQL verification — 2026-09-28
+
+Added a required `make postgres-test` gate to `make ci-check` and therefore the
+existing Forgejo workflow. A digest-pinned, loopback-only disposable PostgreSQL
+container hosts isolated test databases. Operator database URLs are not accepted;
+the fixture removes its own databases and container after the run.
+
+Five integration tests exercise the full Alembic chain to `0006`, guarded
+schema downgrade/re-upgrade, two concurrent `SKIP LOCKED` delivery workers,
+atomic rollback, persisted retry state and replay after an actual child worker
+process exits after a synthetic custody receipt but before local acknowledgement.
+
+Final `make ci-check` passed: **360 ordinary tests** (two optional modules
+skipped in that phase), inventory/build/installed-wheel checks, then **five real
+PostgreSQL tests** with the opt-in enabled. Fixture-container cleanup was verified.
+Production grants, deployment and live receiver acceptance remain open; no live
+database was contacted or migrated.
+See [test details](../docs/conformance.md#disposable-postgresql-gate).
+
 ## Acceptance checkpoints
 
 - [x] Architecture/source/runtime review captured; new implementation owner is hub-core