Testing

Select the smallest real proof that exercises the changed behavior, then widen only as the repo contract and risk surface require.

When To Use

• Choosing validation for code, docs, config, workflow, skill, or eval changes.
• Fixing failing tests or classifying validation failure ownership.
• Designing test coverage for a behavior, workflow, skill, or harness change.
• Proving completion before a handoff, PR, merge, release, or closeout claim.

Philosophy

• Testing is proof selection, not command volume.
• Repo-native contracts beat guessed defaults.
• Artifacts, schemas, and deterministic checks decide required gates; reviewers and LLM judges advise unless calibrated.

Avoid