Delete mocks for endpoints that no longer exist
Mock handlers still answering for routes the real API removed, deleted so the two surfaces match.
The ticket
Delete mock handlers for endpoints the real API no longer serves.
Acceptance criteria
- Every removed handler is confirmed absent from the API contract first
- No test depends on the removed handlers
- A conformance run passes after the deletion
- The removed routes are listed in the description
What lands as proof
A conformance run showing the mock and the contract now describe the same set of routes.
Why teams defer it
- A stale handler never fails, so nothing draws attention to it.
- Removing one means proving nothing depends on it, and that check is more work than leaving it in place.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: delete mock handlers for endpoints the real API no longer serves. 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 the mock surface matches the live surface, proven by the conformance run, 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.