Set up DeepSeek Harness on this VM by following the exe.dev recipe at https://exe.dev/deploy/deepseek-harness.md from top to bottom.

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

You are done when all of these are true. Check each one yourself:
- DeepSeek Harness's web app at `https://<vm>.exe.xyz:3080/`, behind your exe.dev login and DeepSeek Harness's own sign-in link.
- DeepSeek V4.1 Flash through exe.dev's LLM integration, with no API key to paste.
- A project folder at `~/project` on persistent disk.
- A service that keeps running when you close the tab and comes back after a reboot.

Run the VM-side commands in "Start DeepSeek Harness" and "Open it in
your browser". If ~/.dsh/profiles/web/cordis.patch.yml already holds
more than `[]`, add the two rows to it instead of replacing it; same for
~/.dsh/.env. Keep `dsh web` on its default 127.0.0.1 address and never
run share set-public. Verify with the `dsh headless` command, check that
`systemctl is-enabled dsh-web` prints enabled and `systemctl is-active
dsh-web` prints active. Skip the optional sections (own DeepSeek key,
superagent) unless the owner asks. Finish with the sign-in link from
the journal command in "Open it in your browser"; this conversation is
private to the owner.

Finish with the URLs I should open.