Set up Multica on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/multica.md?via=terminal from top to bottom. The recipe's example VM name is my-multica. This VM's name is the output of `hostname`: use it wherever the recipe writes my-multica. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Multica 0.10.0 at your VM's private URL, signing you and your teammates in with your exe.dev logins, back after a reboot. - The VM connected as Multica's agent runtime, with Claude Code and Codex on exe.dev's LLM gateway and no API keys on the VM. - The `multica` CLI signed in on the VM, so you, Shelley, and scripts can create, assign, and close issues. - Generated secrets in one private file, and a nightly backup of the database, uploads, and secrets, with a tested restore. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" in order, skipping VM creation and SSH. The walkthrough at the top is for the owner afterwards: don't create a workspace, agents, or issues yourself. "Connect this VM as the agent runtime" signs in to Multica as the VM owner only to mint the daemon's token. Install exactly the pinned versions. Keep the VM private: never run share set-public. On an existing VM, ask before replacing anything on port 8000. Do not reboot, restore, or update. Verify: /readyz says ok, `multica daemon status` says running, the multica-daemon user service is enabled and active, Linger=yes, the backup timer is scheduled, and the test backup holds multica.dump. Never send a made-up X-ExeDev-Email header: Multica creates an account for every address the bridge signs in. Finish with https://.exe.xyz/: opening it signs the owner in with their exe.dev login. Finish with the URLs I should open.