Summary

• register for remote notifications in iOS app lifecycle
• add APNs entitlements/signing/plist wiring across iOS targets
• align bundle-id placeholders for watch/extension targets for signing consistency

Testing

• not run in this PR prep flow

Greptile Summary

This PR adds APNs (Apple Push Notification service) registration to the iOS app, along with signing/entitlements configuration and bundle ID variable alignment for watch targets.

• APNs registration: Adds OpenClawAppDelegate that registers for remote notifications on launch, forwards device tokens to NodeAppModel, which persists them in UserDefaults and sends a push.apns.register event to the gateway on connect. Includes sandbox/production environment detection.
• Entitlements: New OpenClaw.entitlements file with aps-environment capability, wired in project.yml.
• Signing config: Adds default bundle ID variables for watch app/extension targets in Config/Signing.xcconfig, with corresponding overrides in LocalSigning.xcconfig.example.
• Bundle ID alignment: Replaces hardcoded bundle IDs in watch Info.plist files and project.yml with xcconfig variables for signing consistency across all targets.
• WatchConnectivity fix: Moves replyHandler call outside of Task { @MainActor } in WatchConnectivityReceiver, fixing a potential crash where the reply handler could be called after the system timeout.
• Share extension: Adds movie support (NSExtensionActivationSupportsMovieWithMaxCount) and adds info.properties in project.yml for XcodeGen.
• SwiftLint: Raises type_body_length limits to accommodate NodeAppModel growth.
• Version bump: All targets updated to 2026.2.18.

Confidence Score: 4/5

• This PR is generally safe to merge with one timing concern to consider in the app delegate wiring.
• The changes are well-structured: APNs registration follows standard iOS patterns, bundle ID variables improve maintainability, and the WatchConnectivity replyHandler fix addresses a real correctness issue. The one concern is a potential race condition where the APNs device token callback could fire before appModel is wired to the delegate (since it's set in a .task modifier), which could silently drop the token on first launch or warm re-registration. This is mitigated by the token usually arriving after view appearance and by the best-effort nature of push registration, but it would be more robust to wire the model in didFinishLaunchingWithOptions or buffer the token in the delegate.
• apps/ios/Sources/OpenClawApp.swift - potential race between APNs token delivery and appModel wiring

_{Last reviewed commit: 0c6ba66}