v0.2.0 — Self-healing installs, and a Godot it can find

First tagged release of Foundry for Godot / Godot Vibe OS, carrying the same round of work as its Unity sibling.

godot_verify works on a normal macOS install

The tooling shelled out to a bare godot, which is the Linux/package-manager assumption. On macOS most people install Godot by dragging Godot.app to /Applications, and on Windows by unzipping Godot.exe — so the call that decides whether a change actually works failed with ENOENT on machines that plainly had Godot installed. It now resolves GODOT_BIN → PATH → the platform's standard install location, and treats a bare name or a stale path as a hint rather than a hard requirement.

This also turned a long-red test green.

The install keeps itself current

gvibe update re-syncs a project with the running build: it re-installs the editor addon when the copy in the project has drifted from this version, re-renders the AGENTS.md / CLAUDE.md block (the standing brief the agent actually follows there — a project set up months ago was still running on months-old rules), and reports a .mcp.json whose absolute paths stopped resolving after the checkout moved. Studio runs it in the background whenever you open a project, and toasts only what it actually changed.

The project map is finally used

It was built, refreshed and queryable, but nothing told the agent on the turn it was answering that a valid map existed — so it re-scanned. Every prompt now carries a header with the map's real state: counts and coverage when fresh, an explicit "stale — call godot_orient first" when writes have dirtied it, "no usable map yet" when there is none.

Studio

• Your own messages are selectable and copyable. user-select: none on the shell meant assistant text opted back in and user bubbles never did. Both roles also get a hover copy button.
• Model and effort are per message. Change them whenever, including mid-run: the running turn keeps what it started with, the next message uses the new choice. The backend stays pinned per conversation — a CLI session id is only meaningful to the backend that created it.

The addon moves to 0.2.0 alongside the server; projects carrying 0.1.0 are refreshed when they are next opened.