gat-verifylisted

# gat-verify — prove the slice works before claiming it Request: $ARGUMENTS GAT's honesty gate. A milestone is not "done" because the code compiles — it is done when the flow runs, the numbers hold, the assets exist and match the style, and the design is covered. Report with evidence; if something failed, say so with the output. ## Four checks ### 1. Runtime smoke (behavior, not tests) Drive the actual feature end-to-end: - With Hastur up: `skills/godot-editor-control/scripts/gop.py` → `play`, exercise the flow, read `get_debug_output`. Respect an open editor (smoke only; don't run headless `--import`). - Logic-only: `godot --headless` a smoke scene that calls the new system. Confirm: no errors, the feature does what the milestone's acceptance criteria say. ### 2. Balance / data simulation (for systems with numbers) Do not tune by feel. Use the two-headed method (from `skill-design`): - **Static audit** — compute a power/cost index for each skill/item/foe from `data/*.json`. - **Combat/economy sim** — run staged benchmark characters through simulated fights/loops and measure survival / pressure %. Calibrate difficulty bands (easy 10–50 / mid 50–100 / hard 100–200, or the game's own bands). Flag outliers (a skill 3× the band, a resource that never binds). Numbers, not vibes. ### 3. Asset & style audit For every asset the milestone references (`data/*.json` `art:`/`vfx:` keys): - Assert the file exists on disk. - Gate it: `python tools/art_audit.py <file> --contract