ios-release — ship iPhone via CLI

Everything runs through asc (App Store Connect CLI — official API, JWT-signed). The browser is a fallback for the handful of flows Apple never exposed publicly — see references/browser.md.

Sibling skill: android-release. Build/signing/archive details live in ios-app. There is no APK-style sideload on iOS — testers install via TestFlight.

Golden rules:

• Never submit for review without the user's explicit OK — outward-facing and hard to reverse. TestFlight internal-tester rollout is low-risk (no Apple review); a prior "set it up" covers it.
• Dry-run before every mutation. The high-level commands take --dry-run; add --confirm only after the printed plan matches what the user asked for.
• asc validate is the source of truth, not your reading of the ASC web UI. Its ordered remediation plan is the task list — fix the first item, re-validate, repeat.
• Confirm flags with --help before running. The CLI moves fast; don't trust memory.