Add docs for server health check endpoint response fields and what each indicates

[Chucks1093]

Summary

The health check endpoint is used by deployment infrastructure to determine if the server is ready to receive traffic. Its response fields are undocumented so operators do not know what each field means or what values indicate a healthy vs degraded state.

Scope

• Document all fields in the health check response: database connectivity, indexer lag, cache status, uptime
• Define what values indicate healthy, degraded, and unhealthy for each field
• Explain the difference between the liveness and readiness checks if both exist
• Add a note on which field causes a non-200 response

Acceptance Criteria

• All response fields documented with possible values
• Healthy vs degraded vs unhealthy states defined per field
• Liveness vs readiness distinction explained
• Non-200 trigger condition documented

ETA: 12 hours

---

Coordinate on Telegram

[heymide]

I can take this on. I've gone through the details and will provide a well-tested solution aligned with the project standards.

[heymide]

I can take this on. I've gone through the details and will provide a well-tested solution aligned with the project standards.

[Ajibose]

can i work on thsi

[grantfox-oss]

🦊 GrantFox — @Ajibose 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 #571)
2. Your PR will be reviewed by the accesslayerorg 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!

@Ajibose's PR #575 was approved and merged by @Chucks1093.

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

👏 Great work, @Ajibose! Keep contributing to accesslayerorg.