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

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

You are done when all of these are true. Check each one yourself:
- OpenChamber 2.6.1 running as a service on port 3000, back after a reboot
- OpenCode connected to Claude, GPT and open models through exe.dev's LLM integration, with no API key to paste
- A random UI password in `~/.config/openchamber/ui-password`, readable only by you
- A Git project at `~/project` and a setup-check session that answered `OK`
- OpenChamber's web app at port 3000, behind exe.dev login and the password

Run the VM-side commands in "Install by hand" only, from "Install
OpenChamber" on. If `~/.config/opencode/opencode.json` holds more than
exe.dev's placeholder (`$schema` and `autoupdate`), add the `model` and
`providers` settings to it instead of replacing it. Verify that
`systemctl --user is-active openchamber` says active, that `ss -ltn`
shows `0.0.0.0:3000`, that `curl -s -o /dev/null -w '%{http_code}'
localhost:3000/api/config` prints `401` (the password is on), and that
the setup check prints `OK`. Never print the UI 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 .config/openchamber/ui-password` command from "Open
OpenChamber", with this VM's name, and tell them to add `~/project` as
a project and then follow "Add your phone".

Finish with the URLs I should open.