asc-submission-health

1# App Store submission health
2 
3Use this skill to explain why a release cannot proceed and to manage an existing review submission. Hand healthy release execution back to `asc-release-flow`.
4 
5## Ownership boundary
6 
7This skill owns:
8 
9- readiness validation and blocker diagnosis;
10- public-API, web-session, and manual repair routing;
11- review status and history;
12- cancellation and retry decisions.
13 
14Use `asc-release-flow` for staging, upload, publication, and submission. Switching skills continues the current task with its resolved targets, authorization, and verified progress; it does not require the user to restart the workflow. Continue authorized repairs and return to release execution when healthy. Ask for new authority only when a repair exceeds scope.
15 
16## Answer order
17 
181. State whether the version is ready, blocked, or already under review.
192. Name each blocker and the evidence that proves it.
203. Separate public-API repairs from web-session and manual work.
214. Run the read-only checks needed to establish the diagnosis. For diagnosis-only requests, report the evidence and one proposed repair command without executing that repair. For authorized execution, continue the repair queue and report completed work and remaining blockers.
22 
23## Establish the target
24 
25- Resolve `APP_ID`, the version string or `VERSION_ID`, `BUILD_ID`, platform, and any known `SUBMISSION_ID`.
26- Configure auth with `asc auth login` or `ASC_*` environment variables.
27…