Contributor Focus: [Operational Clarity] Make backend health reporting more informative than a binary status
ETA: 2 days
Context
Real backend health often degrades gradually rather than failing all at once.
Problem
A simple healthy or unhealthy signal hides useful information about partial outages or slow performance.
Task Breakdown
- Define meaningful degraded states such as stale polling, partial RPC failure, or retry backlog pressure.
- Extend health endpoints to expose these states.
- Keep status outputs machine-readable and human-readable.
- Document recommended operator interpretation for each state.
- Add tests covering state transitions.
Acceptance Criteria
- Health output distinguishes degraded modes from total failure.
- Operators can identify the nature of the problem faster.
- Status transitions are predictable and documented.
- Existing health behavior is not broken for simple consumers.
Contributor Focus: [Operational Clarity] Make backend health reporting more informative than a binary status
ETA: 2 days
Context
Real backend health often degrades gradually rather than failing all at once.
Problem
A simple healthy or unhealthy signal hides useful information about partial outages or slow performance.
Task Breakdown
Acceptance Criteria