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

The recipe's example VM name is my-app. This VM's name is the output of `hostname`: use it wherever the recipe writes my-app. 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 Railway services, variables, and data running on the VM, with the same `*.railway.internal` names, at https://my-app.exe.xyz/.
- `git push exe main` deploying like Railway: build, pre-deploy command, health check, and the old build kept if anything fails.
- A list of the API keys that can move into exe.dev integrations, where the VM can't read them.
- A report in `~/railway/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. Change compose.yaml only
where this project needs it, and list the changes in the report.
You need the owner once, early: show them the commands in "Hand over the
project" with this VM's name, and wait until ~/railway/handed-over exists
and each repository in ~/git has a commit. Install the rest meanwhile.
Never run railway commands yourself, never ask for a Railway token, and
never connect to Railway's databases: the addresses in ~/railway are live
production ones. Never run railway/move or handover --move, change DNS,
or run share set-public: the move is the owner's call. Keep the cron
jobs 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; sealed variables the owner sets with
railway/import set over SSH.
If the project needs something exe.dev can't do (public TCP ports other
than HTTP, several regions, MySQL or MongoDB data), put it in the report
and ask.
Finish with the report's summary, https://<vm>.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 project's domains.

Finish with the URLs I should open.