Test Audit

• Authoring gates every new/changed test.
• Audits: remove low-value proof in coherent owner batches; never chase deletion counts.
• Whole-subsystem campaign: read CAMPAIGN.md first.

Authoring gate

Before adding test, answer:

1. Protected observable behavior, invariant, or independent contract?
2. Credible regression that makes it fail?
3. Why existing proof misses it? Each contract: one primary owner at strongest boundary. Another layer needs distinct transport/lifecycle risk. Extend tables/shared fixtures; consolidate repeated setup.
4. Export, flag, wrapper, injection hook with no production caller needed? Move proof to real boundary instead.