Health readiness can conflate database failure with local query-pool starvation
Read-only Shield incident code trace: `GET /api/health/ready` runs `select 1 as ready` through the same postgres-js pooled client used by normal application reads (max 10 connections per process), warns after 1s, and returns 503 after a 2s JS deadline. Therefore readiness failure…