Set up LoopForge on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/loopforge.md from top to bottom. The recipe's example VM name is my-loopforge. This VM's name is the output of `hostname`: use it wherever the recipe writes my-loopforge. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - LoopForge 0.3.8 at your VM's private URL, behind your exe.dev login and its own accounts, with self sign-up closed. - The first account, made by you in the browser, becomes the administrator; your password never passes through Shelley. - LoopForge and MySQL back after a reboot. - A nightly archive of the database, settings, and workspaces, kept two weeks, with a tested restore. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first, skipping VM creation and SSH. Install exactly the pinned tag, v0.3.8. Don't set MIRROR. Never open the LoopForge URL and never call /api/auth/register: the first account becomes the administrator, and the owner must create it. Don't configure credentials, GitHub, projects, or SOPs yourself. Keep the VM private. Never run share set-public, and never set AGENTFLOW_ALLOW_SIGNUP=true. On an existing VM, ask before replacing anything on port 8000. Verify: /api/health says ok, /api/auth/setup says needsSetup true, both containers have the unless-stopped restart policy, the image digest matches, and the test archive lists loopforge.sql and .env. Do not reboot, and don't run the restore or update steps. Finish with https://VM.exe.xyz/ and tell the owner to create their administrator account now, then follow "Connect Codex and Claude Code". Finish with the URLs I should open.