fix(next): clean up UI inspector from nonisolated deinit
#24707 introduced the UI inspector's @MainActor cleanup, and the next Release compile exposed Swift 6.2 errors in its deinit. This forward fix makes deinit nonisolated and performs AppKit monitor/notification removal only under MainActor.assumeIsolated on the main thread, matching the existing package pattern. It is required to get a Release compile green at the current tip after Aziz's WebRTC notice fix 83cb35f5b2b.
Validation:
- Release compile failure reproduced on run 40055959790 (UIInspectorController.swift:44-45).
- Nonisolated deinit follows existing
MainActor.assumeIsolatedcleanup pattern. git diff --check.
agent-identity footer
Agent session: huge-blue
![View with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/view-with-codesmith-dark-v3-3x.png)
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the Release compile error in the UI inspector's deinit: cleanup is now nonisolated and only removes AppKit monitors/observers when already on the main thread, matching the existing MainActor.assumeIsolated pattern. The Release build previously failed at UIInspectorController.swift:44-45 under Swift 6.2.
CI
- Adds an advisory warning step that flags missing or unmapped bundled binaries in Release builds; the signed nightly check remains authoritative.