chore: merge 8.5.0 into next

[andredestro]

What

Ports the 8.5 line into the Capacitor 9 branch so the two lines don't diverge. This brings next up to date with main as of the 8.5.0 release:

• feat(ios): UIScene Support (feat(ios): UIScene Support #8536)
• feat(cli): add migrator functionality for adopting UIScene (feat(cli): add migrator functionality for adopting UIScene #8544)
• fix(cli): support TypeScript 7 when loading capacitor.config.ts (fix(cli): support TypeScript 7 when loading capacitor.config.ts #8534)
• fix(cli): use POSIX paths in CapApp-SPM Package.swift (fix(cli): use POSIX paths in CapApp-SPM Package.swift #8549)

Conflict resolutions

Most conflicts were version bookkeeping. The interesting ones are where 8.5's UIScene work overlapped with Capacitor 9 refactors:

• Version files (lerna.json, package.json x4, CHANGELOGs): kept 9.0.0-alpha.6, with the 8.5.0 changelog entries interleaved below the alpha.6 sections.
• cli/src/tasks/migrate.ts: kept the v9 updateAppDelegate task and added the 8.5 migrateToUIScene step after it. The UIScene migrator self-detects already-migrated or partial projects and skips them, so running both is safe for apps coming from any 8.x version.
• CapacitorBridge.swift: kept the v9 setupListeners structure (Cordova decoupled, cordovaIsPresent guard) and adopted the 8.5 scene-filtered UIScene resume/pause observers in place of the UIApplication ones.
• project.pbxproj: kept the v9 removals of CAPFile.swift and CAPBridge.swift (refactor(ios)!: remove deprecated Swift and Obj-C APIs for Capacitor 9 #8551) and added CAPSceneDelegateProxy.swift to the Sources build phase.
• CAPSceneDelegateProxy.swift (semantic conflict, not textual): dropped the CDVPluginHandleOpenURL post. Cordova is decoupled from the Capacitor framework on the v9 line, and CAPApplicationDelegateProxy on next already dropped the same post, so the scene proxy now matches that behavior. Everything else from 8.5 is carried over unchanged, including the .capacitorOpenURL back-compat payload and the new scene-aware notifications.

Verification

• CLI: npm run build passes, all 84 tests pass (including the new migrate-uiscene and xcode specs)
• iOS: Capacitor scheme builds and all 81 unit tests pass (iPhone 17 simulator, iOS 26.5)
• iOS: Cordova scheme builds

[OS-pedrogustavobilro]

@andredestro the problem with this being a PR is that it will squash all previous commits. Ideally we'd do a straight merge to next locally and push. Is the PR because the merge from main had conflicts and you want some validation that everything's okay?

[markemer]

@andredestro the problem with this being a PR is that it will squash all previous commits. Ideally we'd do a straight merge to next locally and push. Is the PR because the merge from main had conflicts and you want some validation that everything's okay?

I just turned on merge commits for a hot second here.

[andredestro]

@andredestro the problem with this being a PR is that it will squash all previous commits. Ideally we'd do a straight merge to next locally and push. Is the PR because the merge from main had conflicts and you want some validation that everything's okay?

Yes, exactly. The merge had conflicts in a few areas where 8.5 overlapped with Capacitor 9 refactors, and one of them was semantic rather than textual, so I wanted a second pair of eyes before this lands on next.