fix(wallet): remove account menu feature flag

[cursor]

Description

Removes the mobileUxAccountMenu remote feature flag and makes the account menu permanently enabled in mobile. This eliminates runtime gating for the hamburger/account-menu experience and prevents future remote flag toggles from changing behavior.

Changelog

CHANGELOG entry: Removed the hamburger menu feature flag and permanently enabled the account menu.

Related issues

Fixes:
Refs: TMCU-456

Manual testing steps

Feature: Account menu is always enabled

  Scenario: Open account menu from settings navigation
    Given the wallet is unlocked on the main home view
    When I tap the Settings tab in bottom navigation
    Then the Accounts Menu view is displayed

  Scenario: Open account menu from wallet header
    Given the wallet is unlocked on the main home view
    When I tap the hamburger menu button in the wallet header
    Then the Accounts Menu view is displayed

Screenshots/Recordings

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

  

---

Note

Medium Risk
Removes runtime gating for the Settings/Account Menu entry points and changes Wallet header actions (QR scanner/notifications), which can impact core navigation and user access paths. Main risk is regressions in navigation stack behavior and missing/relocated actions across platforms.

Overview
Makes the Account Menu permanently enabled by removing the mobileUxAccountMenu remote flag, its selector/hook, and its registry entry.

Updates navigation so the Settings tab and SettingsFlow always start at Routes.ACCOUNTS_MENU_VIEW, and removes conditional Settings-page entries that were previously hidden/shown based on the flag (snapshots/tests updated accordingly).

Simplifies Wallet header actions by removing the QR-scan entry point and routing notifications access through the hamburger/account menu, with e2e/page-object tests updated to navigate via AccountMenu.

^{Written by Cursor Bugbot for commit 4bce482. This will update automatically on new commits. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[github-actions]

🔍 Smart E2E Test Selection

⏭️ Smart E2E selection skipped - draft PR

All E2E tests pre-selected.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
80.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

✅ E2E Fixture Validation — Schema is up to date
17 value mismatches detected (expected — fixture represents an existing user).
View details

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[cursor]

View test is a render-only scenario with no interaction

Low Severity

The test 'scan button is not rendered when account menu is enabled' is a pure render scenario — it only calls queryByTestId and asserts absence with toBeNull(). It has no fireEvent, waitFor/findBy, store.dispatch/act, or Engine spy. The component view test rules (Golden Rule #7 and the Self-Review Checklist item #1) explicitly prohibit render-only scenarios: "every test must have at least one of: fireEvent, waitFor/findBy, store.dispatch/act, or an Engine spy. Static visibility checks are not tests."

 

^{Triggered by project rule: Component View Test Agent}