#412 feat(settings): show Messenger's account settings

[Anonymous]

Originally created by: kristofferR

Messenger's own account settings, Active Status, message sounds and Do Not Disturb, are hard to reach in Carrier because Facebook's settings chrome is hidden.

Settings has a new Account tab with a "Messenger account" section. It reads and changes these settings through Messenger's own modules, the same ones its Preferences dialog uses, so changes reach the account and sync to the phone:

• Active Status: UpdatePresenceSettingsMutation through CometRelay, with the input Messenger's own switch sends (off hides it from everyone; on shows it again and keeps the existing hidden-from list).
• Message sounds: MWChatChangeSoundsSettingMutation.
• Do Not Disturb: off, 1 hour, 8 hours, 24 hours or until turned off, through LSOptimisticallyUpdateGlobalMuteUntilStoredProcedure (which also queues the server task) and MessengerNotificationsWriter. Carrier's own notifications honor it at once (#378).

The tab explains that these belong to the Facebook account and are separate from Carrier's notification settings. Native asks the page through window.__carrierAccount, and the page answers on carrier:account-result (the remote page can't call app commands). The page applies the change, reads the setting back (retrying briefly) and reports what Messenger has. A failure, including a missing module, shows Messenger's error instead of doing nothing. A dev-only __carrier_mcp_account__:<action> MCP probe and a content-free result log line make it testable without the Settings window.

Live-tested on Linux with a test account in an isolated profile: all three settings changed and read back correctly, and Facebook's own Preferences agreed in both directions (a change made there showed up in Carrier, and changes made in Carrier showed up there). Everything was restored to the account's original values afterwards. Not checked on a phone.

Ref [#358]

[Anonymous]

Originally posted by: kristofferR

[!NOTE]
🤖 Claude Opus 5.5 responding on behalf of Kristoffer

@codex review

[Anonymous]

Originally posted by: chatgpt-codex-connector[bot]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request. | Review | Status | Commit | Review trigger | | --- | --- | --- | --- | | 📝 **Code Review** | ✅ **Completed** <relative-time datetime="2026-11-08T02:54:08.250458Z">2026-11-08T02:54:08.250458Z</relative-time> | `6a4a973` | Manual request |

ℹ️ About Codex in GitHub

[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review" or "@codex security review". Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Anonymous]

Originally posted by: chatgpt-codex-connector[bot]

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 6a4a973731

ℹ️ About Codex in GitHub

[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you - Open a pull request for review - Mark a draft as ready - Comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Anonymous]

Ticket changed by: kristofferR

• status: open --> closed