Store the registry in PostgreSQL in production

[ralyodio]

Summary

• The registry store is now async and picks PostgreSQL when DATABASE_URL is set, SQLite otherwise (local dev and tests).
• Every caller awaits the store: HTTP routes, site renderer, operations dispatch, conformance script, CLI/integration tests.
• /healthz reports "storage": "postgres" | "sqlite".
• Registry contract tests run against both backends when W3BS_TEST_DATABASE_URL is set; CI adds a postgres:18-alpine service.
• Deployment docs and .env.example describe the self-hosted Railway Postgres service. No app volume is needed anymore.

Test plan

• npm test on SQLite: 14 pass
• node --test test/core.test.mjs with a local Postgres 18 container: 12 pass, including the 3 [postgres] cases
• Server booted with DATABASE_URL: health shows storage: postgres, 10 seeded resources, /prompts 200, resolve returns the canonical manifest
• npm run check, npm run conformance (evidence regenerated), npm run test:browser (8 pass)

🤖 Generated with Claude Code

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	pg@​8.23.0

View full report