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

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

You are done when all of these are true. Check each one yourself:
- herdr-core (`hc`) and Herdr TUI installed on the VM, so Herdr on your computer can add it as a machine
- Claude Code, Codex, Pi and OpenCode using exe.dev's LLM integration, with no API key to paste
- Herdr's status integrations for those four agents
- A Git project at `~/project`
- A Claude Code run through `hc` that answers `OK`

Run the VM-side commands in "Set up the VM" only; skip creating the VM.
If `exeuntu configure` reports an existing user config, leave it alone.
If `~/.config/opencode/opencode.json` already exists, add the `model`
and `providers` settings to it instead of replacing it. Do not start
interactive agents or `herdr`. Verify with the checks at the end of that
section: both versions print, `herdr integration status` lists claude,
codex, pi and opencode as `current`, and the `hc run` check prints `OK`.
Skip the later sections and the FAQ. Finish by telling the owner to add
`<this VM's name>.exe.xyz` in the Herdr app ("Add it to Herdr"), or to run
`ssh -t <this VM's name>.exe.xyz herdr` for Herdr TUI.

Finish with the URLs I should open.