feat(db): support transaction-pooling poolers (pgbouncer / RDS Proxy / Supabase)

[modernitconsultants]

Running HAIP against Postgres through pgbouncer in transaction mode, the API dies on its second concurrent query. Two causes, both in how postgres.js is initialised.

1. Named prepared statements. postgres.js prepares by default. Under transaction pooling the statement is prepared on one backend connection and executed on another, which fails. The driver supports prepare: false for exactly this case, but there's no way to reach it from configuration today.

2. TLS. Poolers commonly terminate TLS with a private or self-signed certificate, and sslmode in the connection URL is not honoured consistently across postgres.js versions — so a URL parameter looks like it works and doesn't.

The change

Two environment switches, both defaulting to current behaviour so nothing changes for direct connections:

• DATABASE_POOLER_MODE=transaction → prepare: false
• DATABASE_SSL=no-verify → ssl: { rejectUnauthorized: false }

Applied at all three connection sites (apps/api database module, seed, push-schema), since the init containers reach the database through the same pooler. Documented in .env.example and .env.production.example.

Direct connections keep prepared statements, which are a real win when you own the connection — the switch only opts out where the pooler makes them impossible.

Testing

Verified against pgbouncer in transaction mode with a self-signed certificate: without these, push-schema exits on PostgresError: SSL required and the API fails on concurrent queries; with them, schema push and normal operation both succeed. pnpm build && pnpm -r test green.

Happy to split the TLS half into its own PR if you'd prefer them separate.

[telivity-otaip]

This is a solid fix — thank you, Charles. postgres.js named prepares under transaction pooling and unreliable URL sslmode were exactly the failure mode.

Merging with full credit to you. Small maintainer polish on top of your PR (not changing the design):

• shared postgresOptionsFromEnv so api / seed / push-schema can’t drift
• louder DATABASE_SSL=no-verify warning in .env.example and .env.production.example

(tools/haip-connect-gpt left alone — different package / TOOL_LOG_DATABASE_URL, no clean shared dep.)

Appreciate you running HAIP through a real pooler and sending this back.