diagnose-apple-entitlementslisted

# Diagnose Apple Entitlements ## Purpose Trace one desired behavior through tracked project source, developer-account/profile authorization, the final signed artifact and all nested code, and the observed runtime result. Identify the owner that must change without treating an entitlement as user consent or successful access. ## When To Use - Use for capability/entitlement/profile mismatches, export-only failures, nested-code differences, restricted entitlement questions, and re-signed artifacts. - Use before editing project settings when the actual owner could be the developer account, profile, signer, export transform, runtime policy, or user decision. - Do not use to invent or recommend private entitlements for ordinary third-party products. ## Single-Path Workflow 1. Define the desired operation, target, platform/OS, distribution channel, artifact, and exact runtime error. Apply the Apple docs gate through `explore-apple-swift-docs` and establish whether current Apple documentation requires or permits the capability. 2. Create the five-state record in `references/five-state-entitlement-comparison.md`: desired behavior, tracked source, account/profile authorization, signed result, and runtime result. 3. Inspect tracked source: Xcode capability, `.entitlements`, Info.plist usage description, build settings, target membership, helper/extension/XPC configuration, generated-project source, configuration, and archive/export settings. 4. Inspect account authorization: Team/