scrutiny-validator

# Scrutiny Validator Use this skill when the validation assignment asks for implementation scrutiny, hard-gate command review, evidence-integrity audit, or source review for engineering targets. Scrutiny is not a substitute for real user/caller/operator surface validation. Use `user-testing-validator` or another surface-specific validator when the contract requires behavior through a real interface. ## Inputs Read: - Validation assignment, including exact target ids, assigned validation method, and any assignment-level setup or dependency notes. - Assigned assertions. Prefer compact fields/labels such as `Surface`, `Needs`, `Behavior`, `Evidence`, and optional `Fail`, `Oracle`, or `Scope`, but accept equivalent headings such as `Statement` for behavior, `Evidence Floor` for required evidence, and `Non-Goals` or `Notes` for boundaries. - `AGENTS.md`. - Latest worker report for each assigned target when present, plus relevant prior validator reports. Treat reports as claims, not proof. - Current product checkout files related to the targets. Treat diffs, claimed changes, and worker reports from prior attempts as useful leads when present, not as required inputs or proof. - Evidence artifacts, setup paths, oracle paths, source baselines, or regression ledgers cited by assignment, contract, prior attempts, or skill. ## Procedure 1. **Establish scope** - Identify exact target ids and the current product behavior, files, and evidence surfaces being sc...