[rinov]

API-key requests currently omit the iOS bundle identifier required by Google when a key is restricted to an iOS app. This adds the host bundle ID while preserving explicit identity headers (case-insensitively), OAuth behavior, request bodies, and the existing public API. Eight regression tests cover these compatibility boundaries.

The second commit prepares 0.14.0: podspec and installation versions, English README and public deprecation guidance, player error diagnostics in the Example, release notes, and a publishing checklist. CocoaPods users upgrading from the previously published 0.9.0 are informed of the iOS 13 requirement.

Validation

• Xcode 26.4.1 / iOS 26.4 Simulator: 28 package tests and 2 hosted Example tests pass in each of Swift 5 and Swift 6 modes.
• CocoaPods 1.16.2: dynamic and static library validation pass. Temporary consumer apps also confirm runtime HTML loading and privacy-manifest packaging in both configurations.
• Live Simulator playback: video playback, advancing time callbacks, fullscreen presentation, rotation, ordinary looping, and return from the background were observed with the bundled Example video.
• Xcode 26/27 × Swift 5/6 CI passed all four configurations for this PR's head commit.
• Diff, documentation links, and the 300-line file limit checked. Existing deprecation warnings remain expected.

Before publishing

No tag or release has been published. Merge this PR, confirm the merged commit's CI, and complete the physical-device and real iOS-restricted-key checks in RELEASING.md. The Example contains a placeholder API key, so live Data API authentication has not been verified.

The notes retain the known limitations in #35 and #111. This relates to #89 without assuming that every reported 403 is resolved; none of these issues is automatically closed.