Set up Omnara on this VM by following the exe.dev recipe at https://exe.dev/deploy/omnara.md from top to bottom.

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

You are done when all of these are true. Check each one yourself:
- Omnara 0.2.15's whole Compose stack at your VM's private URL, started at boot by omnara.service
- A relay to exe.dev's LLM gateway that lists its models, so agents need no model API key on the VM
- Signup, password reset, and invitation emails sent through exe.dev, with no mail account
- A user, omnara-agent, ready to be your agents' machine, without sudo and cut off from the stack's databases
- Omnara's encryption keys in ~/omnara/.env, mode 600
- Nightly backups of the database, artifacts, and memory, with the first one taken and checked

Read the whole recipe, including the closed details. Follow "Install by
hand" from "On the VM", skipping VM creation and SSH: Docker, Omnara,
.env, the stack, omnara.service, the omnara-agent user, and backups.
Work as exedev in ~/omnara. Never overwrite an existing .env, and never
print its contents. Don't sign up, create organizations, or connect a
machine: the owner does those in the browser with their own password,
and the machine token comes from their dashboard. Don't send test
emails. Don't share the VM or make it public. Verify that /healthz says
ok, that the relay lists models, and that api-mail's log says it is
listening, then point the owner to "Sign up".

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 share add my-omnara teammate@example.com