Set up Executor on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/executor.md from top to bottom.

The recipe's example VM name is my-executor. This VM's name is the output of `hostname`: use it wherever the recipe writes my-executor. Skip the step that creates the VM; you are on it.

You are done when all of these are true. Check each one yourself:
- Executor 2 at `https://my-executor.exe.xyz`, in Docker, restarted on failure and after a reboot.
- Its database, generated keys and your apps' code in `~/executor/data`.
- An owner account that only you can create, because the setup page is behind your exe.dev login.
- One MCP endpoint, `/mcp`, that Claude Code, Codex, Shelley and other agents share.
- A backup and update procedure for the data directory.

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. Use the pinned image tag as written. Never make the VM public:
the first person to finish Executor's setup page becomes its owner, and
that must be the owner. Don't set EXECUTOR_APPS_ALLOW_PRIVATE_FETCH unless
the owner asks. On an existing VM, ask before replacing anything on port
8000. The VM can't reach its own https://<vm>.exe.xyz, so checks use
localhost. Finish by sending the owner to https://<vm>.exe.xyz/ to create
their account, then to "Add your tools" and "Connect your agents", with the
`ssh-key generate-api-key` command to run on their computer.

Finish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them):
  ssh exe.dev ssh-key generate-api-key --vm=my-executor --label=executor-agents --exp=90d