APP STORE PREFLIGHT
A repeatable release check, not another AI answer.
Run the same bounded repository checks every release and review file-level evidence before App Store Connect upload. Use AI to help fix findings if you want; use AccessVerdict to rerun the gate.
CHECK 01
Required-reason APIs
Detect app-owned native calls in Apple's required-reason API categories and compare them with PrivacyInfo.xcprivacy declarations.
The result points to repository evidence. It does not claim to predict every App Review decision.
CHECK 02
Privacy manifest
Look for PrivacyInfo.xcprivacy and obvious category/reason structure gaps around detected required-reason API use.
The same rule set can be rerun after a fix instead of relying on a fresh prompt and a different answer.
CHECK 03
Common SDK review
Inventory common Apple-listed SDK dependencies and flag versions that need privacy-manifest/signature review before the final build is uploaded.
WHY IT EXISTS
Use AI for explanation. Use a preflight for repeatability.
A coding assistant can explain Apple documentation and suggest changes. AccessVerdict is for the release moment: scan the granted repository, produce file-level findings, fix locally, and rerun the same gate.