Readiness probe

GET 
/api/v1/health/ready

Readiness probe — can we serve traffic?

Pings the database and the cache; returns 503 with a descriptive status string when either check fails.

• Public endpoint (no auth required).
• Intended for the container orchestrator / the load balancer readiness checks that must gate traffic until the process can actually serve.

Responses

200

All required dependencies reachable.

400

Bad request — malformed input or failed validation.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.

503

A required dependency (the database or the cache) is unavailable.