Harden health endpoint: typed responses, timeouts, and readiness vs liveness split

[Wilfred007]

What

Improve backend/src/controllers/healthController.ts: remove the any types on the redis client and statusReport, add per-dependency timeouts, and split into a lightweight liveness probe and a dependency-checking readiness probe.

Why

The current handler builds an untyped statusReport: any and checks Postgres, Redis, and Horizon inline. Without timeouts, a slow dependency can hang the health check; without a liveness/readiness split, orchestrators can't distinguish 'process alive' from 'ready to serve traffic', causing unnecessary restarts or routing to a not-ready instance.

Scope

In scope:

• Define typed interfaces for the health report and each dependency status.
• Wrap each dependency check in a bounded timeout.
• Add GET /health/live (process up, no deps) and keep GET /health (or /health/ready) for full dependency checks.
• Return 503 when a critical dependency is down.

Out of scope:

• Adding new monitored dependencies.

Acceptance criteria

• No any types remain in the health controller.
• A hung dependency causes the check to fail fast within the timeout, not hang.
• Liveness and readiness are separately reachable.
• Tests cover healthy, degraded, and timeout paths.

Technical context

• File: backend/src/controllers/healthController.ts (redis: any, statusReport: any).
• Existing tests: backend/src/controllers/__tests__/healthController.test.ts.

[OpensrcLord]

Hello @maintainer, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me. And I will deliver at the shortest possible time.

[Psalmuel01]

I'd like to work on this.

I'll implement a clear liveness/readiness split, introduce typed response models, ensure dependency checks are bounded by timeouts, and add tests covering healthy, degraded, and timeout scenarios. I'll share a PR for review once it's ready.

[grantfox-oss]

🦊 GrantFox — @Psalmuel01 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #402)
2. Your PR will be reviewed by the Protocol-Guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Psalmuel01's PR #436 was approved and merged by @Wilfred007.

🏆 @Psalmuel01: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (166 total points). Track your full progress on GrantFox.

👏 Great work, @Psalmuel01! Keep contributing to Protocol-Guild.