test-audit

原文涵盖的主题

• Test Audit
• Choose the scope
• Decision gate
• Prevent new duplication
• Focused workflow
• Completion and reporting

Reduce execution and maintenance cost while preserving meaningful failure detection. Investigate aggressively; delete only with evidence. Retaining an area after review is a valid result. This skill is self-contained; upstream attribution is in NOTICE.md. Focused cleanup: follow this entry point and read the candidate evidence guide before editing. Multiple owners, agents, or PRs: also read CAMPAIGN.md. Declare whether the work is a targeted sweep or an exhaustive subsystem audit. Validation and cost claims: read references/validation.md. Paperclip commands, invariants, and delivery: read references/paperclip.md alongside repository instructions. For every proposed removal, answer: 1. Which observable contract and plausible regression do the assertions cover? 2. Which retained file/case detects that regression through the responsible production code? Otherwise, why is the assertion vacuous or contract retired? 3. Does this candidate uniquely cover a transport, permission, lifecycle, storage boundary, platform, default, or other independent failure mode? 4. What improves: executions, fixtures, processes, maintenance, or runtime? Prefer the smallest test that reaches the code respons

这里只展示节选，请以完整原文和当前要求为准。