Diff coverage and the tests you did not write
Repo-wide coverage barely moves when you add a file, so it tells you nothing about the change in front of you. agI3R intersects the coverage report with the diff and reports the only number that matters: how much of what you just changed is covered.
How it works
CoverageAgent runs your coverage command in the proposal's sandbox and intersects the lcov report with the changed source lines, reporting percent-of-changed-lines plus the uncovered lines by name.
Under your configured threshold, the gate escalates to a more senior approver rather than blocking — the change still ships if a human says so, but not quietly.
TestGapReviewAgent reads the diff for changed behaviours that no test covers, grounding itself on the uncovered lines when coverage ran, and writes a suggested test for each gap.
A suggested test is text on the gate. Neither agent writes a test into your repo, escalates on its own, or decides the gate.
Both are switched on per tenant with your own coverage command and threshold — agI3R does not guess how your project measures coverage.
The agents behind it
Human control
Proposal gate — coverage can raise the required approver and gaps are annotated, but only a human decision moves the proposal.