feat: MUSD-673 conditionally render Money hub via feature flag

[Matt561]

Description

Adds new selectMoneyHubEnabledFlag selector to control conditional rendering of the new Money hub screen.

Changelog

CHANGELOG entry: added new selectMoneyHubEnabledFlag selector to control conditional rendering of the new Money hub screen.

Related issues

Fixes: MUSD-673: Create feature flag for Money Hub

Manual testing steps

Feature: Money Hub feature flag

  Scenario: user with Money Hub enabled sees the full view
    Given the MM_MONEY_HUB_ENABLED remote feature flag is enabled

    When user navigates to the Cash Tokens full view
    Then the Money Hub component is rendered

  Scenario: user with Money Hub disabled sees the fallback
    Given the MM_MONEY_HUB_ENABLED remote feature flag is disabled

    When user navigates to the Cash Tokens full view
    Then the Money Hub component is not rendered

Screenshots/Recordings

Before

Money hub always rendered

After

When enabled

When disabled

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.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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

Low Risk
Feature-flag-gated UI rendering changes with no new data handling or critical logic; primary risk is accidentally hiding/showing Money Hub sections due to flag wiring.

Overview
Adds a new selectMoneyHubEnabledFlag selector (remote version-gated flag with MM_MONEY_HUB_ENABLED env fallback) and registers the corresponding remote flag earnMoneyHubEnabled for test defaults.

Updates CashTokensFullView to conditionally render the bonus/convert sections and bottom CTAs (Convert vs Swap/Buy) only when Money Hub is enabled, with expanded unit tests covering the enabled/disabled UI states and CTA behavior.

^{Reviewed by Cursor Bugbot for commit 1434111. Bugbot is set up for automated code reviews on this repo. 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.

[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.}

^{Reviewed by Cursor Bugbot for commit 9047abf. Configure here.}

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 88%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes in this PR are:

1. New feature flag earnMoneyHubEnabled added to the feature flag registry with inProd: false and enabled: false as defaults - this flag is disabled by default in production and in E2E test environments.

2. New Redux selector selectMoneyHubEnabledFlag that reads the new remote feature flag with a local env var fallback (MM_MONEY_HUB_ENABLED=false).

3. CashTokensFullView UI gating: The bonus/convert sections and CTA buttons (Convert/Swap/Buy) are now conditionally rendered based on isMoneyHubEnabled. Since the flag defaults to false, these sections are hidden by default - meaning the component now renders LESS UI than before.

4. .js.env.example and unit test files updated accordingly.

Why no E2E tags are needed:

• The feature flag is disabled by default (inProd: false, enabled: false), so E2E tests running against the app will see the same behavior as before (the bonus/convert sections were already not visible in test environments without the flag)
• No existing E2E tests reference CashTokensFullView or the Money Hub feature
• The changes are purely additive (new flag, new selector, conditional rendering) with no modifications to existing functionality
• No shared components (navigation, modals, confirmations, TabBar) are affected
• The feature flag registry change only adds a new entry without modifying existing flags
• Unit tests provide adequate coverage for the new selector and component behavior

Performance Test Selection:
The changes are purely additive UI gating behind a disabled feature flag. No performance-sensitive code paths (rendering loops, data fetching, state management at scale, app startup) are affected. The CashTokensFullView actually renders LESS UI when the flag is disabled (default), which would only improve performance marginally. No performance tests are warranted.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud