Store / Platform Ship-Readiness Gate — refactor-chain · review/ship

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: review → ship · Prerequisite: the review gate ran (refactor-review-gate); there is a diff and a build target · Next: ship (only once no Blocker rejection risk remains). Adaptivity / conditional: conditional — activates only when a store-publishable target is detected (iOS App Store, Android/Play, web/PWA, or a notarized desktop app). On a library, a service, or a non-published app it stays dormant. Advisory by default; blocks ship only on a Blocker.

Purpose

A refactor that moves files, renames bundles, edits manifests, or bumps dependencies can quietly break the things a store reviewer checks — even when the code is correct, safe, and fast. This skill is the platform/store lens the other reviewers don't have. It reads the changed manifest and config surface for the target platform and answers: would Apple, Google, the browser install prompt, or notarization reject this? For iOS that means Info.plist usage-description strings, entitlements, the privacy manifest (PrivacyInfo.xcprivacy) and required-reason APIs, App Tracking Transparency, and background modes. For Android it means the manifest permissions, targetSdkVersion, and data-safety alignment. For web/PWA it means the web app manifest, icons, HTTPS/installability. For desktop it means code signing and notarization/entitlements. It hands back a ranked list of rejection risks with the exact fix. It changes nothing by default and only blocks the ship when a risk is a genuine Blocker-severity rejection.

When to use

• A refactor touched a publishable app and you want a pre-submission check. Triggers: "will this pass App Store review", "store readiness check", "will Apple/Google reject this".
• A manifest, entitlements file, privacy manifest, or bundle id was moved or edited by the refactor. Triggers: "did we break our entitlements", "is the privacy manifest still right".
• A dependency bump may have pulled in a required-reason API or a new permission. Triggers: "did this dependency add a permission", "new SDK — is it store-safe".
• Precondition / conditional gate: a store-publishable target is detected (see Method step 1). If none is, this skill reports "not applicable — no publishable target" and stays out of the way.