[Backend] Add a health-check and readiness endpoint covering Redis, RPC, and indexer lag

[grantfox-oss]

Problem

The microservices architecture introduces real distributed-systems failure modes (Redis down, indexer worker crashed, RPC unreachable) but the README only mentions /metrics for Prometheus scraping — there's no lightweight /healthz//readyz for orchestrators (Docker Compose healthchecks, PM2, k8s if ever adopted) to use for restart/alerting decisions.
Proposed work

Add /api/health (liveness: is the process up) and /api/ready (readiness: can Redis be reached, is the indexer's last-seen ledger within an acceptable lag window) endpoints to server-decoupled.ts.
Wire the existing docker-compose.microservices.yml services to use these for their healthcheck blocks instead of (presumably) no healthcheck or a naive TCP check.
Document expected response shapes and status codes in MICROSERVICES_ARCHITECTURE.md.

Acceptance criteria

Killing the Redis container causes /api/ready to report unhealthy within one polling interval, verified manually or via test.
Docker Compose correctly restarts/holds back dependent services based on these healthchecks.
Endpoints return structured JSON (not just 200/500) so monitoring tools can distinguish which dependency failed.

[jordansilly77-stack]

I can take this one. I’ll keep it focused: add lightweight /api/health and /api/ready, check Redis/RPC/indexer lag using the existing service wiring, add compose healthchecks, and document the JSON/status-code behavior. I’ll open a PR after checking the current structure.

[yunus-dev-codecrafter]

Hi! I've carefully reviewed the entire task description and fully understand the requirements and expected outcome.
I have experience working on similar tasks and I'm confident I can complete this within about an hour. I'd be happy to take ownership of this issue and submit a clean, well-tested solution promptly.
If it's available, please assign it to me. Thank you!

[rahimatonize]

hi maintainer, i would love to work on this issue, please assign

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[anidroid1184]

Hi! I would like to apply for this issue to implement the /api/health and /api/ready endpoints in the decoupled server. This will be one of my first open-source contributions, and I am excited to help enhance the microservices architecture telemetry!

I have carefully reviewed the CONTRIBUTING.md file and the architecture of server-decoupled.ts. My technical approach will be:

1. Create a dedicated feature branch following your standards: feat/health-readiness-endpoints.
2. Intercept the incoming requests inside the createServer HTTP lifecycle before they are handed off to Next.js, inspecting parsedUrl.pathname.
3. Implement /api/health (Liveness) to return a lightweight JSON {"status": "healthy"} with a 200 OK status code.
4. Implement /api/ready (Readiness) by consuming the internal subscriber.getStatus() method to check the Redis connection state, returning a structured JSON response.
5. Update docker-compose.microservices.yml to integrate these endpoints into the container healthchecks and update microservices_architecture.md.
6. Run the complete quality suite (npm test, npx tsc --noEmit, and npm run lint) as required by the contribution guidelines before opening the PR.

I am ready to start as soon as I get the green light!