Public: anyone can read this; the crew can change it.
gretchy-stretchy moves to the forge and keeps working: its data, its domain and its payments #11857
Check · Review · Land · Live done — Landed and live in production.
Nothing is new on #11687: it has no comments, and the branch matches `origin`, so I pushed nothing this run. I changed no code and ran no tests, `tsc` or gate this run. The branch holds only documentation from earlier runs.
shipped production is serving it deploy cc205a8
Nothing is new on #11687: it has no comments, and the branch matches origin, so I pushed nothing this run. I changed no code and ran no tests, tsc or gate this run. The branch holds only documentation from earlier runs.
What the branch holds
- A runbook for moving a platform app (gretchy-stretchy) onto the forge. It lists what the forge lacks for that.
- Each gap in the runbook names its own issue (#11697–#11705), linked to #11687.
- A note that the owner wants the app to survive its node going away, and that the runbook is the first step, ahead of pipeline items.
What I chose not to do
- No migration tooling, and no step that touches gretchy-stretchy or its production data, DNS or payments. Those need the owner's secrets and the owner's go before the domain moves, and my sandbox cannot reach the app or its database.
- No new gap issues, since the map shows no new blocker.
What to look at
- Whether the runbook's order of work matches the owner's wish, and whether #11697–#11705 are the right next issues to pick up.
git diff origin/mainon this branch looks large only becausemainhas moved on since the branch was cut. The branch's own changes are the runbook and direction commits.
I merged main into the branch and pushed it; the only conflict was docs/features/platform-app-move.md. bun x tsc --noEmit and bun scripts/gate.ts both ran clean. I did not run any tests: the change touches only that doc, and the test selector would have picked 75 files (about 6 minutes), so I left the full check to the forge's run on the push.
What I did with the conflict
- Both sides had added the same file.
main's version is a superset of mine: it adds the database import, file copy, rehearsal and webhooks, the read-only old side, customer accounts, and marks gaps built or decided. I tookmain's file whole. main's gap list had dropped the custom-domain item (#11700), so I added it back with a pointer todocs/features/app-own-domain.md.
Nothing else on the branch changed.
One-line docs change: restores the custom-domain gap (#11700) to the move runbook with a pointer to docs/features/app-own-domain.md, which exists. No code, no README change, no dependency, so the security, tests and both-doors items do not apply. Next two things: (1) mark the item struck-through as built if app-own-domain.md describes a finished feature, matching the neighbouring items; (2) the rehearsal guard (#11702) is still the riskiest open gap before a payment name can leak into production.
Nothing is new on #11687: it has no comments, and the branch matches
origin, so I pushed nothing this run. I changed no code and ran no tests,tscor gate this run. The branch holds only documentation from earlier runs.What the branch holds
What I chose not to do
What to look at
git diff origin/mainon this branch looks large only becausemainhas moved on since the branch was cut. The branch's own changes are the runbook and direction commits.Closes #11687