Delete code the coverage report and call graph agree is unreachable
Code neither the coverage report nor the call graph can reach, removed on both pieces of evidence.
The ticket
Delete code that both the coverage report and the call graph show is unreachable.
Acceptance criteria
- Both coverage and call-graph evidence are attached
- The suite passes after deletion
- Build output size is recorded before and after
- Anything reachable only through reflection or configuration is excluded
What lands as proof
Two independent sources agreeing the code is unreachable, because either one alone is misleading.
Why teams defer it
- Deleting code feels risky even with evidence, because the evidence is never quite complete.
- Dynamic access defeats both tools, so somebody has to check the exceptions by hand.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: delete code that both the coverage report and the call graph show is unreachable. 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 suite green, build output measurably smaller, 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.