AMP_ORB_PROVIDER_TOKEN=<fill-this-in>

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

The values at the top of this message are mine:
- AMP_ORB_PROVIDER_TOKEN: the `aop_live_…` token Amp showed once when you added the provider in Settings → Orbs
Ask me for any that still say <fill-this-in> before you need them.

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

You are done when all of these are true. Check each one yourself:
- The Amp CLI, and the dispatch program at `~/amp-orbs/dispatch.sh`
- The provider token in `~/amp-orbs/provider.env`, readable only by `exedev`
- The amp-orb-provider systemd service, enabled so it comes back after a reboot, with `Orb provider started` in its log

Run "Set up the provider by hand", skipping VM creation and SSH.
AMP_ORB_PROVIDER_TOKEN is a secret: write it to ~/amp-orbs/provider.env
with `printf 'AMP_ORB_PROVIDER_TOKEN=%s\n' "$value"` under `umask 077`
instead of the interactive read, and never print it. If the log says
`Amp rejected the orb provider token`, tell the owner the token is wrong
or revoked. Never ask for an exe.dev API key: the integration in "Let
the provider make VMs" is created by the owner, on their own computer.
Don't start a thread. Finish by giving the owner that integration
command with this VM's name, then pointing them to "Start a thread on
your VMs".

Finish with the URLs I should open.