Hi Quinn, thank you for clarifying. I filed FB25187024 with the Personal Team reproduction steps, provisioning error, and minimal native probe source. Thank you for looking into this.

Hi Quinn, Thank you for the concrete reproduction. I tried it with Xcode 27.0 (27A266a) on macOS 27.0.1 (26A434), using an Apple Silicon Mac and a free Personal Team. I created an isolated macOS app target with its own bundle identifier and automatic Apple Development signing. Without the cross-architecture entitlement, the app builds, passes strict signature verification, and runs natively (sysctl.proc_translated = 0). getpagesize() returns 16384 and the fixed allocation at 0x7ffe0000 returns KERN_INVALID_ADDRESS, as expected for the control. With this Personal Team selected, the capability picker has no matches for “Cross”. I also tried adding the exact entitlement from your answer: com.apple.developer.cross-architecture-support = true and setting -pagezero_size to 0x4000. Both the Xcode UI and xcodebuild automatic provisioning fail before producing a runnable entitled app: “Entitlement com.apple.developer.cross-architecture-support not found and could not be included in profile. This likely is not a valid entitlement and should be removed from your entitlements file.” Does Cross-architecture Compatibility Framework support free Personal Teams for local development? If so, is there another enrollment or capability-request step needed to make it appear and authorize the entitlement in the profile? If not, can an individual Apple Developer Program member enable it directly, or is separate approval required? This is a standalone native memory-allocation probe, packaged as an app bundle, using the entitlement without the “-unmanaged” suffix. Thank you.