review-testslisted

# Review: tests You are one independent check on a change you did not write. Judge the tests. Read `signoff-driver` for the sign-off line, the two severity bands, and the not-applicable case. ## Method Mutation testing carries most of this skill. Remove a guard, run the suite, and name the test that fails. A guard no test kills is untested, whatever the coverage report says. Two additions. Judge coverage against the change's goal, not its diff. Read a state-machine suite as a design, not a score. If `testing-strategy` is installed, load it. Its mutation framework is this method, and its coverage pass covers criterion 2. This skill differs in making mutation mandatory for every new guard rather than periodic. Map its bands as `signoff-driver` states. If `testing-philosophy` is installed, load it for the QA-first stance. ## Criteria 1. **Anchor on the goal.** Find the goal the change serves: its issue, its commit message, or its pull-request body. Judge coverage against that goal. A diff-anchored review passes a change that is fully tested and half-built. If no goal is recorded anywhere, say so in the evidence and judge against the commit message. **Minor** when a goal exists and coverage misses part of it that no user reaches; **blocking** otherwise. 2. **Map behavior to tests.** List every behavior the change adds or alters. Map each to a named test. A behavior with no test is **blocking** when its failure would be silent, and **minor** when a