What the port changes, in four numbers.
Before is the mobile repository on 17 Nov 2026. After is the shape this plan proposes. The line counts after the port are modelled from the thin-workflow design; the gate and lane counts hold by design once the policy is declared.
The lanes work by hand and stop at production.
Staging ships a candidate every time it is asked and UAT has delivered once. Nothing gates a build, the next version bump cannot reach main, and production has no environment, no App Store Connect id and no build.
| Piece | Today, in mobile | After, in cloud mobile/ | Evidence |
|---|---|---|---|
| Version and tag planning | scripts/release/plan.mjs, 41 Vitest cases | mobile/plan with the same cases as Go table tests | pnpm release:test, 41 passed, 17 Nov |
| EAS dispatch and callback | dispatch-eas.mjs, callback.mjs, two composite actions | oc mobile dispatch and oc mobile complete, writing a journal receipt | .github/actions, 334 lines |
| Candidate proof | GitHub deployment records uat_release and parsed release bodies | journal promotion record: run id, build id, delivery status | plan 400 task 4 |
| Approval | none enforced | reviewers per environment in policy, checked by the release guard | environments API · release.yml |
| Version commit | unsigned bot push to main | decided in task D2 | ruleset 1592092 history |
| Engine pin | none | cloud/oc.lock and provision-oc, as Collections pins 0.54.0 | collections cloud/oc.lock |
| Build files | eas.json, four EAS workflows | stay in mobile; EAS reads them from the app repository | .eas/workflows, 207 lines |
What flows where, from the operator to the journal.
Pick a lane and press play. Each step lights the systems it touches and the list under the diagram names the data that crosses the boundary. Secrets are named by their key, never shown.
Decide, then staging, then UAT, then production.
Pick a phase to see its tasks. Each task names its owner, its time and the condition that closes it. Staging does not wait for plans 398 to 401; UAT and production do.
What can still go wrong.
Ordered by severity. Each risk states the number behind it, what it means for the business, and where the evidence lives. Pick a severity to narrow the list.