verifylisted

<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> <constants> HARD_CUTOFF: 900 # 15 min — ADVISORY ONLY, not enforced. # Synchronous Agent() has no escape — the parent cannot interrupt mid-flight call. # If the agent exceeds the expected ~15 min budget, the parent must handle the timeout in the NEXT turn # (e.g., user re-invokes, or orchestrator surfaces partial results from $RUN_DIR/audit-raw.md after Agent returns). # Same limitation as research:topic — documented, not bypassable from within the skill. </constants> <workflow> ## Agent Resolution `research:scientist` in 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 requires holistic paper understanding). ## Verify Mode (Steps