[Reliability] Separate liveness and readiness checks for deployment-safe health monitoring

[doctorlight0]

🚀 Feature Overview

[Reliability] Separate liveness and readiness checks for deployment-safe health monitoring

🛠️ Implementation Requirements

• Improve the current health endpoint so orchestrators can distinguish a running process from one ready to serve dependent services.
• Add a lightweight liveness endpoint with no dependency calls.
• Add a readiness endpoint that checks required database and Redis capabilities with timeouts.
• Return meaningful non-2xx readiness status when essential dependencies are unavailable.
• Document probe configuration for Docker and hosting providers.

🔧 Technical Specifications

TypeScript, React/Next.js, Node.js/Express, PostgreSQL/Redis, GitHub Actions — as applicable to the scoped implementation.

✅ Acceptance Criteria

• Liveness remains fast and succeeds while the process is alive.
• Readiness fails when required dependencies are unavailable or unhealthy.
• Responses avoid credentials, connection strings, and internal stack traces.
• Health routes have automated success and dependency-failure tests.
• Deployment documentation includes probe examples.

🎓 Difficulty Level

Intermediate to Advanced — requires careful production-quality implementation.

⏱️ Timeline

ETA: 2 days

[vercel]

@doctorlight0 is attempting to deploy a commit to the Ayomide Adeniran's projects Team on Vercel.

A member of the Team first needs to authorize it.

[ayomideadeniran]

pr under review