Health and Readiness Endpoints

[charlieroth]

Why

Enable safe rollouts and reliable orchestration.

Definition of Done

• Liveness route returns success when the process is up.
• Readiness route returns success only when database connection is healthy, index directory is available, and workers are ready.
• Both routes avoid heavy work and allocate minimally.
• Documentation explains expected behaviors.

Tasks

• Implement /healthz/live and /healthz/ready.
• Add checks for database, index path access, and worker state.
• Add timing and result logs with low verbosity.
• Document usage in the runbook.