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

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

You are done when all of these are true. Check each one yourself:
- Gemini CLI on Node.js 24, answering a headless `gemini -p` prompt
- A Gemini API key stored in an exe.dev integration, never on the VM
- A Git repository at `~/project` on persistent disk
- A `gemini` tmux session that survives disconnects

Run the VM-side commands in "Install Gemini CLI" and "Connect it to
Gemini". Only the owner can create the Gemini integration, in their
browser, and the API key must never be on this VM: give them the
integration link from "Connect it to Gemini" with this VM's name in it,
and wait until they say it's done. Never ask for the key. If
`~/.gemini/settings.json` already exists, set `security.auth.selectedType`
in it instead of replacing the file. Create tmux detached
(`tmux new -d -s gemini -c ~/project`) rather than attaching, and reuse
the session if it exists. Do not launch interactive Gemini CLI; leave the
folder-trust question to the owner. Verify with
`curl -fsS https://gemini.int.exe.xyz/v1beta/models >/dev/null` and, from
~/project, `gemini --skip-trust -m flash-lite -p "Reply with exactly: OK"`, and
check `tmux has-session -t gemini`. Skip the later optional sections and
FAQ. Finish with the SSH command from "Take a break", using this VM's
name, and tell the owner to run `gemini` inside it.

Finish with the URLs I should open.