Report the exceptions a silent catch is swallowing
Catch blocks that discard the error, changed to report or rethrow.
The ticket
Make every silent catch in one module either report the error or rethrow it.
Acceptance criteria
- No catch block discards its error
- Each catch either reports with context or rethrows
- A seeded failure on each path produces a reported event
- Expected control-flow catches are marked explicitly with a reason
What lands as proof
A seeded failure per catch path, each producing a visible event, so the silence is proven gone.
Why teams defer it
- An empty catch was usually added to stop a noisy log, so removing it brings the noise back and the noise needs handling too.
- Nothing fails when it is wrong, which is the whole problem.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: make every silent catch in one module either report the error or rethrow it. 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 every catch reports or rethrows, proven by a seeded failure per path, 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.