macOS Tahoe (26): "Allow browser integration" checkbox missing and desktop never opens the browser-integration IPC socket (2026.6.1, Mac App Store)

## Steps To Reproduce 1. On macOS 26.5.1 (Tahoe), install the Bitwarden desktop app from the Mac App Store (2026.6.1). Clean install — no prior container/data. 2. Sign in and unlock the vault (Touch ID working, "Unlock with Touch ID" enabled). 3. Open Settings and look for the "Allow browser integration" option (App Settings, near "Allow DuckDuckGo browser integration"). 4. In Firefox, open the Bitwarden extension and try to use biometric/desktop unlock. ## Expected Result The "Allow browser integration" checkbox is present in Settings; enabling it makes the desktop app open its app-group IPC socket so `desktop_proxy` can connect, and the browser extension unlocks via the desktop app. ## Actual Result - The "Allow browser integration" checkbox is **completely absent** from Settings. Only "Allow DuckDuckGo browser integration" is shown. - The desktop app **never creates the `s.bw` socket** in `~/Library/Group Containers/LTZ2PFU5D6.com.bitwarden.desktop/`. Only `s.af` is created. - The extension loops forever: `Connecting to Bitwarden Desktop app… -> Retrieving application id -> native port disconnecting`, with `TypeError: can't access property "message", e.error is null` (`nativeMessaging.background.ts:260`), and the lock screen hangs on a spinner before falling back to master password. ## Additional Context Reproducible from a fully clean state (deleted `~/Library/Containers/com.bitwarden.desktop`, `~/Library/Group Containers/LTZ2PFU5D6.com.bitwarden.desktop`, keychain items; reinstalled; fresh login). Detailed findings: - The `enableBrowserIntegration` checkbox is **unconditional** (no `@if` guard) in `apps/desktop/src/app/accounts/settings-dialog.component.html` at tag `desktop-v2026.6.1`, yet it does not render on macOS 26.5.1. - Forcing the backing state true directly — `global_desktopSettings_browserIntegrationEnabled: true` in `data.json` (the key state-migration #66 relocates it to), app quit, vault unlocked on relaunch — does **not** start the server; `s.bw` is still never created. So the main process is not honoring the stored enabled-state at startup on this build/OS. - It worked **once**, on 2026-06-30, immediately after the in-place App Store update to 2026.6.1 — because migration #66 carried a `true` flag over from a pre-2026.6 version and the server started that one time (`desktop_core::ipc::client: Connected path=…/s.bw`). A clean install cannot reach that state because the only UI to enable it (the checkbox) is missing. - The Chromium native-messaging manifest the app writes points correctly to `…/Contents/MacOS/desktop_proxy`; the manifest/proxy side is fine. The break is entirely that the desktop app does not open `s.bw`. - Likely related: #21562 (closed not-planned; identical MAS 2026.6.0 case), #21339, #20929. ## Operating System macOS ## Operating System Version 26.5.1 (25F80) ## Installation method Mac App Store ## Build Version 2026.6.1 ## Issue Tracking Info - [x] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.