gat-godot-gatelisted

# gat-godot-gate — no runtime write without engine evidence Request: $ARGUMENTS This is the mandatory runtime boundary around `/gat-implement`. Read `docs/godot-gate.md` for provider capability profiles and save-isolation contracts. Hastur/editor-control may supplement this gate; it does not replace the MCP lifecycle evidence. ## Before the first edit 1. Confirm the session exposes the configured Godot MCP provider. The baseline capability set is: engine version, project information, run project, read debug output, and stop owned project. 2. Call the version and project-information tools. Confirm the intended `project.godot`, engine version, and current main scene. If the tools are unavailable, stop runtime writes and perform read-only diagnosis only; request a new MCP-bound session. 3. Inspect `git status` and preserve all unrelated changes. 4. Verify save isolation from `gat.config.yaml`: - manual/player slots are read-only to agents; - debug writes go only to an isolated agent slot/root; - a configured pre-debug snapshot hook succeeds before **every** engine launch; - the append-only vault is outside the repo and Godot `user://`; - restore requires the user to name the exact snapshot and destination. If the project has persistence but cannot prove this contract, do not launch it. 5. Run `/gat-reference-first` and validate the slice's reference map. ## Modify and check 1. Patch the smallest scope. Prefer text patches for code/data and edito