verify

<constants> ```yaml HARD_CUTOFF: 900 # seconds — advisory; Agent() calls are synchronous and cannot be interrupted mid-flight ``` </constants> <objective> Paper-vs-code consistency audit. After `research:scientist` implements method from paper, verify implementation matches paper claims. Audits five dimensions — formula matching, hyperparameter parity, eval protocol, notation consistency, citation chain. Emits verification table with match status and severity. NOT for: running experiments (use `/research:run`); judging experimental methodology (use `/research:judge`); literature search (use `/research:topic`); general code review (use `/develop:review` (requires `develop` plugin)). Verify audits implementation-vs-paper fidelity only — does not evaluate whether paper's claims are valid. </objective> <workflow> ## Agent Resolution `research:scientist` same plugin as this skill — no fallback needed if research plugin installed. Scientist handles all five audit dimensions in single spawn to preserve cross-dimension context (e.g., notation inconsistency explaining formula mismatch needs holistic paper understanding). ## Verify Mode (Steps V1–V6) Triggered by `verify <paper>` where `<paper>` is PDF path, arXiv URL, or multi-line quoted text. **Task tracking**: create tasks for V1, V2, V3, V4, V5, V6 at start — before any tool calls. ### Step V1: Parse paper input **Input resolution** (priority order): 1. Path ending `.pdf` — read via Read tool (use `pages: "1-20"` f...