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

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

You are done when all of these are true. Check each one yourself:
- Qwen Code's Web Shell on port 4170, reachable through private HTTPS
- A stable, owner-only daemon token in ~/.qwen/serve.env, not in the service unit
- Qwen3.8 through exe.dev's LLM integration, verified with a short prompt
- qwen-serve.service enabled and healthy, restarted after a crash or reboot
- Project files and saved sessions on persistent disk, plus a checked backup

Follow "Install by hand" first, including the closed details, skipping
VM creation. Do not run optional model-provider setup, restore, or update.
Keep the VM and port 4170 private: never share set-public. Ask before
replacing existing ~/.qwen/settings.json, serve.env, qwen-serve.service,
or a listener on 4170; preserve existing model entries if applicable.
Use the official standalone installer pinned to 0.26.6. Verify qwen's
version, the Qwen model's OK reply, systemd enabled/active, HTTP 401
without the bearer, health OK with it, and a backup containing
.qwen/settings.json and .qwen/serve.env. Do not start an interactive
agent, enable YOLO, or print a secret-bearing QR into logs. Finish with
the private HTTPS URL, the SSH command to read the token, and where
to select the project. Explain the second sign-in, not just exe.dev.

Finish with the URLs I should open.