Add health and readiness endpoints with tests
A service the platform cannot ask whether it is ready, given endpoints that answer honestly.
The ticket
Add health and readiness endpoints that reflect real dependency state.
Acceptance criteria
- Readiness reflects real dependency state, not a constant
- Health distinguishes alive from ready
- The unhealthy path is covered by a test, not only the happy one
- The endpoints are cheap enough to poll frequently
What lands as proof
A test forcing a dependency down and asserting readiness reports unready, which is the case that matters.
Why teams defer it
- An endpoint that always returns success passes every review and tells nobody anything.
- Deciding what ready means needs agreement about which dependencies are essential, which is a conversation not a code change.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add health and readiness endpoints that reflect real dependency state. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means endpoints respond, the unhealthy path is covered too, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.