mobile · cloud · planning17 Nov 2026 · iOS lines: staging, UAT, production

Move the iOS release into the engine.
Mobile keeps EAS; cloud owns the lanes.

A new mobile/ domain in cloud ports the staging, UAT and production release logic and its gates. Mobile pins the engine the way Collections does and keeps only its EAS build files and three thin workflows.

Reviewer gates enforcedGitHub environments, read 17 Nov 2026 09:00 UTCmeasured
0 of 3
lines gated today
3 of 3
declared in policy after the port
Today the staging, uat and stale qa environments carry 0 protection rules and production does not exist, so no build waits for a reviewer. After the port each line's reviewers live in cloud/oc.yml and the engine's release guard refuses a run that skips them.
At a glancebefore → after

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.

Node release code in mobile modelled
1,176→0−100%
lines in scripts/release, six files, 17 Nov 2026
One Go domain with its own tests replaces scripts that only Vitest covers.
Reviewer gates by design
0→3
environments staging, uat and production
A UAT or production build cannot start without its named reviewer.
Workflow YAML in mobile modelled
723→≈120
5 workflows and 2 composite actions today
Each thin workflow provisions the pinned engine and runs one verb.
Lines that have delivered a build measured
2 of 3→3 of 3
staging rc.1 to rc.68, UAT once, production never
Production becomes a dispatch the engine records, not a lane that has never run.
Whytriage of the live release state, 17 Nov 2026

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.

68
release candidates, all on version 0.1.1
GitHub releases v0.1.1-rc.1 to rc.68
1
UAT delivery that succeeded
v0.1.1-uat.61, 12 Nov 2026
0
production builds, tags or environment
EAS build list · GitHub environments
1
unsigned bot commit on main, now blocked
chore(release): prepare v0.1.1, 21 Sep 2026
What moves, and where it landsmobile main 0a0893bcc · cloud main 11e2234cmapped
PieceToday, in mobileAfter, in cloud mobile/Evidence
Version and tag planningscripts/release/plan.mjs, 41 Vitest casesmobile/plan with the same cases as Go table testspnpm release:test, 41 passed, 17 Nov
EAS dispatch and callbackdispatch-eas.mjs, callback.mjs, two composite actionsoc mobile dispatch and oc mobile complete, writing a journal receipt.github/actions, 334 lines
Candidate proofGitHub deployment records uat_release and parsed release bodiesjournal promotion record: run id, build id, delivery statusplan 400 task 4
Approvalnone enforcedreviewers per environment in policy, checked by the release guardenvironments API · release.yml
Version commitunsigned bot push to maindecided in task D2ruleset 1592092 history
Engine pinnonecloud/oc.lock and provision-oc, as Collections pins 0.54.0collections cloud/oc.lock
Build fileseas.json, four EAS workflowsstay in mobile; EAS reads them from the app repository.eas/workflows, 207 lines
Reading: every piece of release logic has a home in the engine; only the files EAS itself reads stay in mobile.
Release cycledata flow after the port, one lane at a time

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.

Lane
Release cycle data flow
Plan

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.

Risks and gapsbusiness impact first

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.