gm-buildlisted

# GodotMaker Build $ARGUMENTS You are implementing a Godot game by dispatching Worker subagents. Risk tasks first, then main tasks — both surfaced from PLAN.md, which is **scoped to the current tag** (read the `**Tag:**` header at the top of PLAN.md). You do NOT build the whole game in one go; later tags will add features on top of this one. ## Session Setup **FIRST ACTION — before anything else:** Write `build` to `.godotmaker/current_role`. ## Resume Check Read `.godotmaker/stage.jsonl` (treat as empty if missing) — each line is `{"role": X, "ts": Y}`. - If `project.godot` does not exist → STOP. Tell user to run `/gm-scaffold` first. - If `ROADMAP.md` does not exist → STOP. Tell user to run `/gm-gdd` first. - If **no event with `role == "gdd"`** exists anywhere in the file → STOP. Tell user to run `/gm-gdd` first. - If `PLAN.md` is missing the `**Tag:**` header → STOP. Tell user the file is stale and to re-run `/gm-gdd` to regenerate it for the current tag. Read `.godotmaker/verify_report.json` if it exists. Define **pending verify feedback** as: - `.godotmaker/verify_report.json` exists. - Its top-level `result` is `"fail"`. - Its `ts` is later than the latest `role == "build"` event in `stage.jsonl`, or there is no prior build event. Apply the resume gates in this order: - If pending verify feedback exists → proceed to Step 0, even if the last event is `build` and all PLAN.md tasks are already `verified`. - If the **last event** has `role == "build"` AND all PL