Set up Plane on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/plane.md?via=terminal from top to bottom. The recipe's example VM name is my-plane. This VM's name is the output of `hostname`: use it wherever the recipe writes my-plane. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Plane Community Edition 1.x at `https://my-plane.exe.xyz/`, behind your exe.dev login, restarted after a reboot. - Sign-in with exe.dev: no Plane passwords; the people you share the VM with and invite are signed in as themselves, with accounts created on their first visit. - Open sign-up off from the start: you claim god mode, and everyone else joins by invitation. - Secrets generated on the VM in `~/plane/.env` (mode 600), which also holds the agents' Plane token. - `plane-api`, `plane-mcp` and a Shelley MCP bridge on the VM, ready for Claude Code and Shelley once there's a token. - Nightly backups of the database, uploads and settings in `~/plane-backups`, with a restore checked in a scratch container. Read the whole recipe, closed details included, and follow "Set up by hand" in order, skipping VM creation; the walkthrough above it is for the owner. Don't create the god-mode admin or any Plane account: the first admin must be the owner, with their exe.dev email. Don't make the VM public. The VM can't reach its own https://.exe.xyz, so check with http://localhost:8000 as written. The first start runs database migrations for several minutes; wait for them. Don't enable plane-mcp.service or register MCP servers yet: there's no token until the owner makes one. Don't run Restore or Update, and don't reboot. Finish with the god-mode URL, tell the owner to follow "Claim your instance", and point them to "Connect your agents" for the token. Finish with the URLs I should open.