Set up Payload on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/payload.md?via=terminal from top to bottom. The recipe's example VM name is my-payload. This VM's name is the output of `hostname`: use it wherever the recipe writes my-payload. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - Payload 3.94 with the website template (pages, posts, media, forms, search, SEO) answering on port 8000, restarting after a reboot. - Content in SQLite and uploads in ~/data, backed up every night and before every deploy. - /admin and the login APIs open only to people signed in to exe.dev, who are signed in to Payload by their email. - Payload's email (password resets, form notifications) sent through exe.dev, and an Auto-generate button for meta descriptions that uses the LLM gateway. - ~/payload as the place to change the code, a dev server on port 3000, and ~/bin/payload-deploy to migrate, build, and switch with rollback. Read the whole recipe, including the closed details. For initial setup, follow "Set up by hand" from "Install Node.js" to the end of it, as exedev; the walkthrough sections are for the owner afterwards. Use the exact versions given. Never overwrite an existing ~/payload.env or ~/payload/.env. Don't create Payload users, don't press or call "Seed your database", don't make the VM public, and don't run Restore or Update. Do not reboot. If a build fails, read its output and fix what you can; never commit secrets. Finish with https://.exe.xyz/admin and ask the owner to open it and create the first user with the email of their exe.dev account. Don't paste secrets into the chat; say they are in ~/payload.env. Finish with the URLs I should open.