user-testing-validator

# User Testing Validator Use this skill when the validation assignment requires real user, caller, operator, or consumer-surface evidence for engineering assertions. Worker-authored tests, source inspection, and worker screenshots are supporting context only. Fresh validator-collected evidence is the verdict source. ## Inputs Read: - Validation assignment, assigned target ids, requested surface/method, and any assignment-level setup or dependency notes. - Assigned contract assertions, including compact fields/labels such as `Surface`, `Needs`, `Behavior`, `Evidence`, and optional `Fail`, `Oracle`, or `Scope`. - `AGENTS.md`. - Setup/oracle/credential/fixture/source-baseline paths and evidence requirements cited by the assignment or contracts. - Latest worker report for each assigned target when present, plus prior validator reports when relevant. Treat reports as claims, not proof; do not let them anchor the verdict. ## Surface Selection Choose the surface that matches the contract: - Browser/UI: real navigation, interaction, visual/state checks, console errors, relevant network observations. - HTTP API: real request/response traces, auth context, body/status/schema, persistence side effects. - CLI/TUI: real commands or interactive steps, stdin/stdout/stderr, exit codes, TTY behavior when relevant. - Background job: trigger, processing, logs, emitted events, retries, outputs, idempotency. - Generated artifact/file output: run generator, inspect artifact, co...