Replace ad-hoc prints with the project logger
Debug prints left in production code, replaced with structured logging a query can reach.
The ticket
Replace ad-hoc print statements across one service with the project's structured logger.
Acceptance criteria
- No print statements remain in the service
- Each replacement carries a level and structured fields rather than an interpolated string
- A lint rule blocks the old call from returning
- Tests assert the structured output where the message matters
What lands as proof
A lint rule failing on a seeded print, which is what stops this being undone next week.
Why teams defer it
- A print works locally, which is where the person adding it is standing.
- Nobody notices the cost until an incident needs a query and the logs are unstructured text.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: replace ad-hoc print statements across one service with the project's structured logger. 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 a rule blocks the old call, tests assert the new one, 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.