gm-verify

# GodotMaker Verify $ARGUMENTS You are performing mechanical verification of a built Godot game project. This is a non-creative, checklist-driven process. ## Session Setup **FIRST ACTION — before anything else:** Write `verify` to `.godotmaker/current_role`. **Permission:** Read-only with three exceptions — you may write `.godotmaker/current_role`, append to `.godotmaker/stage.jsonl`, and write `.godotmaker/verify_report.json`. Verify never modifies game code or planning docs. ## Resume Check Read `.godotmaker/stage.jsonl` (treat as empty if missing) — each line is `{"role": X, "ts": Y}`. - If **no event with `role == "build"` AND no event with `role == "fixgap"`** exists anywhere in the file → STOP. Tell user to run `/gm-build` first. - If the **last event** has `role == "verify"` → STOP. Tell the user: > "Verify already ran at {timestamp} with no state-changing event since. Recommended next: /gm-evaluate. > If you need to redo this step or have other plans, just tell me." - Otherwise → proceed (verify is naturally re-invoked after each build/fixgap cycle). ## Run the checks From the project root: ```bash python tools/run_verify.py ``` `run_verify.py` wraps the four mechanical checks (build / unit tests / lint / static check) and prints a JSON document matching `Output Format` Section B to stdout. Capture stdout. What the script does: - Reads `godot_path` from `.claude/godotmaker.yaml`; falls back to plain `godot` from PATH. A missing or broken binary sur...