REPO=<fill-this-in>

Set up Apps from Lovable on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/migrate-lovable.md from top to bottom.

The values at the top of this message are mine:
- REPO: the GitHub repository Lovable syncs your project to, as owner/name (Lovable shows it under Project settings → Git → GitHub)
Ask me for any that still say <fill-this-in> before you need them.

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

You are done when all of these are true. Check each one yourself:
- Supabase running in Docker in `~/supabase` with keys of its own, restarting after a reboot, and Caddy on port 8000 serving its APIs and the app at https://my-lovable.exe.xyz/.
- `~/app.git` cloned through the GitHub integration, and `~/bin/app-deploy` building the newest commit as a Node.js server, applying new files in `supabase/migrations`, switching over, and keeping the previous release if anything fails; `app-deploy.timer` runs it every minute.
- The app answering on port 8000 as `app.service`, on a database with the app's tables and no data yet.
- `~/bin/app-restore`, as published with the recipe, ready to load a Lovable Cloud export; `~/bin/app-backup` with `app-backup.timer` enabled, and a first backup in `~/backups`.
- The output of `~/bin/app-check`, saying what in this app still depends on Lovable.

Read the whole recipe, including the closed details. Follow "Set up by
hand" from "Install Node.js, Bun, Caddy, and PostgreSQL's tools" to the
end of it, as exedev; the walkthrough above it is for the owner
afterwards. Do not run "Move to a new VM" or "Update", do not reboot,
and leave public sharing off. The scripts and units were tested as
written: use them unchanged, check that yours match the recipe, and
leave no test files behind.
REPO is a GitHub repository; turn a URL into owner/name. Clone it
through the GitHub integration. If that fails with "not found" or a 403,
and https://github.com/OWNER/NAME is public, clone that instead;
otherwise give the owner the integration command from "Get the code",
with this VM's name, and wait for them. Install everything else meanwhile.
Never commit or push to the repository: Lovable writes to it.
If the first deploy stops because this isn't a TanStack Start app, say
so and point the owner to the FAQ on older apps; leave the rest set up.
Don't wait for the Lovable export: the owner downloads it. Don't run
app-restore until they ask you to.
Keep keys and passwords out of your replies; say which file holds them.
In your report, say what ~/bin/app-check found, in plain words, with the
section of this recipe that deals with each item. Then give the owner
the next step: export from Lovable as "Bring your data over" says, the
scp command with this VM's name, and to ask you to restore it.

Finish with the URLs I should open.