Set up Sites from Netlify on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/migrate-netlify.md?via=terminal from top to bottom. The recipe's example VM name is my-site. This VM's name is the output of `hostname`: use it wherever the recipe writes my-site. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Your Netlify site running on the VM at https://my-site.exe.xyz/, with its functions, edge functions, server, database, redirects, headers, forms, Blobs, and variables. - `git push exe main` deploying like Netlify: the build, an atomic switch, and the old deploy kept if anything fails; other branches as a branch deploy. - A list of the API keys that can move into exe.dev integrations, where the VM can't read them. - A report in `~/netlify/report.md`, and your steps for the move. Read the whole recipe, including the closed details, and do "Rehearse the move by hand" in order, skipping VM creation; the rest of the page is for the owner. Use the kit's scripts as published. You need the owner once, early: show them the commands in "Hand over the site" with this VM's name, and wait until ~/netlify/handed-over exists and ~/git/site.git has a commit. Install the rest meanwhile. Never call Netlify's API yourself and never ask for a Netlify token. Never run handover --move or netlify/import live, change DNS, or run share set-public: the move is the owner's call. Scheduled functions stay off until then. Keep variable values out of your replies and the report. Never ask the owner to paste an API key into the conversation: API keys go into integrations, which the owner adds; secret values Netlify won't hand over the owner sets with netlify/import set over SSH. If the site renders pages with a framework's Netlify adapter (Next.js, Astro, SvelteKit, Nuxt, Remix), switch the build to the framework's Node adapter, run its server with a systemd unit on port 8000 in place of netlify@production, and list in the report what moved out of netlify.toml. For anything else exe.dev doesn't do (Identity, geolocation, split testing), put it in the report and ask. Finish with the report's summary, https://.exe.xyz/, the keys that could move to integrations, and the owner's steps in "Make the move" with this VM's name and the site's domains. Finish with the URLs I should open.