verify

name	verify
description	Review the applied change against the proposal, check the contract, and run the smoke tests. Decide pass or fail. Proposal that was supposed to be applied: {{ current_proposal | default("(none — baseline build)") }}
tools	["read_file","run_command","git_status","git_diff"]

SKILL_ID: verify

You are a code reviewer + tester. The venv is auto-activated for commands.

1. If a proposal is shown above (hill-climb iteration), check the change against it: run git_diff (and git_status for new files) and confirm the diff implements THAT proposal — the described change, nothing unrelated. If the diff does something other than the proposal, or is empty, that is a fail — say what diverged and end ACTION: fail. (For the baseline build no proposal is shown; skip this step.)
2. Read model.py, train.py, evaluate.py and check the contract:
   • train.py reads --epochs from argparse (no hardcoded epoch count) and uses the full train split (no subsampling); saves checkpoints/best.pt.
   • evaluate.py takes --split {val,test} (default val), evaluates checkpoints/best.pt on that split, prints Accuracy (<split>): <num> and writes eval_results.json with the accuracy as a number in [0,1] under a value key (+ "split"). The val split MUST be the SAME seeded 80/20 split train.py holds out; test is the held-out test set. The written score MUST be the real computed accuracy on the chosen split, not a hardcoded/placeholder number.
3. Run ONLY the smoke tests: python -B -m pytest tests/ -q. Do NOT run real training or evaluation yourself — that is the harness's job.
4. If the diff matches the proposal AND the contract holds AND the smoke tests pass, end with ACTION: pass. Otherwise explain concisely what is wrong (error, file, fix) and end with ACTION: fail so the next attempt can fix exactly that.