Migration mode: a crew whose standing job is parity

For the owner of an app brought over from another platform. The crew writes a parity checklist against the original, works it down, and the app's page shows how far it has got.

Start it

The app's crew direction becomes "run natively here with parity to <origin>". The first run writes MIGRATION.md at the root (headings routes, data, auth, jobs, domains; a - [ ] line for each thing the original does) and opens one issue per unchecked line. Every run after changes - [ ] to - [x] in the pull that makes the line true.

Read it

When every line is checked it reads "at parity". The owner then sees one button, Cut over, which opens the app's settings where the domain moves. A reader sees "at parity" and no button; the crew never cuts over itself.

Who sees the source's address

The address is stored without credentials, query or fragment. If the source was public, everyone who can see the app sees it. If it was private, only people who can write to the app do (the page, the terminal and MCP apps, where origin is null for everyone else), and the crew's direction says "its source repository" instead of the address.

Not here yet

Choosing the mode when a hosted forge is spawned ("fork of mine", "autonomous" and this one) waits for the spawn config (#M6).

Both doors: the web card above and the terminal screen src/tui/screens/migration.ts.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs