gm-acceptlisted

# GodotMaker Accept $ARGUMENTS You are presenting the **current tag's** completed work to the user for acceptance. This is a per-tag gate — accepting now does NOT mean the whole game is done; it means this tag (vX.Y.Z) is ready to be sealed, archived, and git-tagged by `/gm-finalize`. The user can choose to continue to the next tag (`/gm-gdd` again) or stop the project here. ## Session Setup **FIRST ACTION — before anything else:** Write `accept` to `.godotmaker/current_role`. ## Resume Check Read `.godotmaker/stage.jsonl` (treat as empty if missing) — each line is `{"role": X, "ts": Y}`. Also read `.godotmaker/evaluation.json`. - If **no event with `role == "evaluate"`** exists anywhere in the file OR `evaluation.json` does not exist → STOP. Tell user to run `/gm-evaluate` first. - If `evaluation.json` `result` is `"reject"` → STOP. Tell user to run `/gm-fixgap` first. - If the **last event** has `role == "accept"` AND its `decision == "accept"` → STOP. Tell the user: > "Accept already recorded at {timestamp}. Recommended next: /gm-finalize. > If you need to redo this step or have other plans, just tell me." - Otherwise → proceed (re-invocation is valid if the previous accept event recorded a `fix` or `done` decision). ## Process ### 1. Gather Results Read these files: - `.godotmaker/evaluation.json` — evaluator results (mandatory) - `PLAN.md` — task completion status - `MEMORY.md` — known issues and discoveries - `GDD.md` — original requirements ### 2. Collec