ship-ios

One way from branch to TestFlight, for every iOS app. The lifecycle below is Thames's ship flow; the build stages are the studio's shared pipeline (the ship-ios.sh pipeline script in this skill — same stages, same rules, each repo supplying only its build and upload). The cost policy is Omiro's: everything builds locally, so there is no EAS cloud-build spend. App-specific commands live in the adapter rows; app runbooks stay in the app repos.

Authorization boundary

Checks and preflight are read-only or local and may run on a readiness question. Committing, pushing, uploading, merging, publishing an OTA, and deleting branches require authorization within the current task. A requested release can authorize its documented build and upload stages; local builds are local validation and are not themselves publication. Never turn a readiness request into a release, and never merge or deploy on your own judgment: report ready and wait for the word. A submitted build cannot be un-submitted.