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

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

You are done when all of these are true. Check each one yourself:
- The Paseo daemon running as a systemd service on port 6767 with its web app on, back after a reboot
- A random Paseo password in `~/.paseo/paseo.env`, readable only by its owner
- Claude Code and Codex ready in Paseo through exe.dev's LLM integration, with no API key to paste
- A Git project at `~/project`, added to Paseo
- Paseo's web app at port 6767, behind exe.dev login and Paseo's password

Run the VM-side commands in "Install by hand" only, from "Install Paseo"
on. If `exeuntu configure` reports an existing user config, leave it
alone. Do not run `paseo daemon pair`: it turns on Paseo's relay, which
is the owner's choice. Verify that `systemctl is-active paseo` says
active, that `ss -ltn` shows `0.0.0.0:6767`, that the health check
prints `"status":"ok"`, and that the setup check prints `OK`. Never
print the password in your messages. Skip the backup, update and
troubleshooting sections and the FAQ. Finish by giving the owner the
browser URL and the `ssh ... cat .paseo/paseo.env` command from "Open
Paseo", with this VM's name, and tell them to follow "Add your phone"
next.

Finish with the URLs I should open.