test-audit

# Test Audit Tests earn their place by catching a credible regression that nothing else catches. Agents write a test for every small change, and most of those re-assert the source, replay a stronger test through a mock, or pin a private call shape. Coverage barely moves when they go; maintenance cost and suite time do. - **IS:** gating a new or changed test before it lands, sweeping a directory for low-value tests, and campaign-pruning a whole subsystem to a measured target with coverage held, plus deleting the test-only production seams those tests kept alive. - **IS NOT:** making CI faster by splitting or sharding (`ci-speedup`), reviewing a feature diff (`tidy`), or writing tests for untested code (though any test that work adds should pass the gate). ## Pick a mode | Mode | When | Done means | |------|------|------------| | **Gate** | About to add or change a test, or asked "should this test exist" | Each test passes the four questions and no junk pattern, or is rewritten at the owning boundary, or is not added | | **Audit** | A focused sweep of named files or a directory | A handful of high-confidence candidates with full evidence, deleted in one coherent batch with validation green | | **Campaign** | A subsystem's whole test surface, or any request with a target ("remove 20%") | The target is met or the ledger shows why it cannot be, coverage held within tolerance, and the preservation review passed. Read `references/campaign.md` first | ## Set a target before star...