Clear a fixed number of violations of an already-suppressed rule
A ratchet: a fixed number of existing suppressions removed per ticket so the count only moves one way.
The ticket
Remove a stated number of existing suppressions for one rule and fix the underlying code.
Acceptance criteria
- The stated number of suppressions is removed
- Each underlying violation is fixed rather than moved
- The ratchet count is lowered so it cannot climb back
- The remaining count is recorded in the description
What lands as proof
A lowered ratchet threshold, which is what makes the progress irreversible rather than merely done once.
Why teams defer it
- An unbounded cleanup has no definition of done, so it needs a number before it can be a ticket.
- Without lowering the ratchet, the count creeps back up and the work is wasted.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: remove a stated number of existing suppressions for one rule and fix the underlying code. 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 ratchet count drops and cannot climb back, 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.