Move one consumer off a deprecated internal library
One consumer migrated off an internal library everybody agreed to retire.
The ticket
Migrate one consumer off a deprecated internal library.
Acceptance criteria
- The consumer no longer imports the old library
- Its tests pass unchanged in what they assert
- Behaviour the replacement does not cover is raised rather than worked around
- The remaining consumers are counted in the description
What lands as proof
A passing suite with the old import gone, plus a count of what is left so the next ticket is obvious.
Why teams defer it
- The library still works, so each migration is optional until the day it is urgent for everybody at once.
- The replacement usually covers ninety percent, and the last ten percent is a design conversation.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: migrate one consumer off a deprecated internal library. 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 consumer migrated, the old import no longer resolves anywhere, 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.