App Store readiness audit

Audit the exact release candidate that App Review would receive. Treat readiness as an evidence state, not as a successful compile or a generic policy checklist.

Operate read-only. Do not edit the app or metadata, change signing, upload a build, submit for review, or alter external services. Use isolated temporary build output only after checking build phases for side effects. Ask before a check needs credentials, signing changes, device resets, paid resources, or external mutation.

Do not promise approval.

1. Set the evidence boundary

Read applicable repository instructions, then record:

• repository path, branch, commit, and dirty state;
• new app or update, platforms, device families, OS targets, and storefronts;
• project or workspace, scheme, target, and Release configuration;
• bundle ID, marketing version, and build number;
• supplied archive, app bundle, export, or TestFlight build and its SHA-256;
• available App Store Connect and runtime evidence;
• user exclusions.