v0.0.2 — zero-config sandbox via MCP roots

No more --project-dir. The server now resolves its sandbox from the connected client's MCP roots, so Claude Code setup is just:

claude mcp add tiled -- npx -y tiled-mcp-server

Open Claude Code inside your Tiled project and the server sandboxes itself to that folder automatically.

Resolution order: --project-dir → TILED_PROJECT_DIR → the client's first file:// root. If none yields a directory, startup fails closed — the server never guesses. Clients without a working-directory concept (Claude Desktop and other JSON-config hosts) keep passing --project-dir explicitly.

Under the hood, a gated transport answers the MCP handshake before the sandbox exists, buffers all other traffic while the client's roots are fetched and the tools wire up, then replays it — so an early tools/list always sees the full 50-tool surface. The root is fixed for the session; later roots/list_changed notifications do not move it.

Upgrade: nothing to do — npx -y tiled-mcp-server picks up 0.0.2 automatically. Existing --project-dir configurations behave exactly as before.