Test Audit

Use the authoring gate when writing or changing tests. For a requested audit, inspect the selected scope before proposing edits; keep each batch coherent. Read repository test integrity rules first. Use fixture and scenario conventions when extracting reusable setup, builders, or contract suites. Keep expected outcomes independent of the implementation and resource ownership explicit.

Authoring gate

Before adding a test, answer all four questions:

1. What observable behavior, invariant, or independent contract does it protect?
2. What credible regression makes it fail?
3. Why does existing coverage not already catch that failure? Prefer extending an existing case or fixture over duplicating the same proof.
4. Does it need an export, flag, wrapper, or injection hook that no production caller needs? If so, test at the real owning boundary instead.