Filter out error noise you have already judged harmless
Bot traffic and cancelled requests filtered with written rules, instead of turning off the whole inbox.
The ticket
Add targeted ignore rules for benign error classes rather than muting the inbox.
Acceptance criteria
- Each rule is as narrow as possible and documented with a reason
- Nothing is muted at project level
- Inbox volume before and after is recorded
- Rules are reviewed on a stated date rather than left forever
What lands as proof
A per-rule justification plus the volume difference, so the reduction can be checked rather than assumed.
Why teams defer it
- A broad mute is one click and a narrow rule is an afternoon of pattern matching.
- Once muted, a real error hiding in the same class becomes invisible, and nobody finds out for months.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add targeted ignore rules for benign error classes rather than muting the inbox. 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 documented rule per pattern, inbox volume before and after, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.