test adequacy Shipped
What this lens looks for
Flag NEW risk-bearing code paths this diff introduces that no test in the diff (or named existing test) exercises: retry/backoff loops, network or subprocess I/O and its failure handling, new exception handlers or error-recovery branches, concurrency primitives (locks, async tasks, shared mutable state), and boundary parsing of external input. Each finding names the specific untested path and the failure mode a test would have to provoke. This is NOT a coverage lane: if the diff adds no such path — or every risky path it adds is exercised — report zero findings; never file blanket "add more tests" advice, never flag pre-existing untested code the diff merely touches, and never re-argue the design of the path itself (that belongs to the owning lane — cross-reference it instead).
What its verifier checks
The flagged path is genuinely new in this diff (not pre-existing code); no test added or changed in the diff exercises it and the finding does not misname an existing test that does; the named failure mode is concrete and provocable (a test could actually assert it); the finding is not disguised design criticism or generic coverage advice