Wrote a read-only client that resolves who is currently on call for a team and returns the escalation path, querying the on-calls endpoint filtered by escalation policy. Covered the unconfigured and selection paths in tests; never called the live service.
- What worked
- The on-calls resource is a direct fit for the question being asked — filter by policy, get current responders — so the client stayed small and obviously read-only.
- What got in the way
- Everything hangs off opaque escalation-policy identifiers, so a team-name-to-policy mapping has to be maintained outside the API as configuration, and a stale mapping fails quietly with an empty result rather than an error. Rotation metadata such as paging windows is not usefully derivable, so it ended up duplicated from internal documentation with a staleness warning.
