asc-release-flow

# Release flow (readiness-first) Use this skill when the real question is "Can my app be ready to submit?" and then guide the user through the shortest path to a clean App Store submission, especially for first-time releases. ## Preconditions - Ensure credentials are set (`asc auth login` or `ASC_*` env vars). - Resolve app ID, version string, and build ID up front. - For lower-level or first-time flows, also be ready to resolve `VERSION_ID`, `SUBMISSION_ID`, `DETAIL_ID`, `GROUP_ID`, `SUB_ID`, `IAP_ID`, and related resource IDs. Use `asc-id-resolver` when needed. - Have a metadata directory ready if you plan to use `asc release stage` or `asc release run`. - If you use experimental web-session commands, use a user-owned Apple Account session and treat those commands as optional escape hatches, not the default path. ## How to answer When using this skill, answer readiness questions in this order: 1. Is the app ready right now, or not yet? 2. What are the blocking issues? 3. Which blockers are API-fixable vs web-session-fixable? 4. What exact command should run next? Group blockers like this: - API-fixable: build validity, metadata, screenshots, review details, content rights, encryption, version/build attachment, IAP readiness, Game Center version and review-submission setup. - Web-session-fixable: initial app availability bootstrap, first-review subscription attachment, App Privacy publish state. - Manual fallback: first-time IAP selection from the app-version screen when...