chore(perps): use feature flag for referral code

[geositta]

Description

• Gate rewards referral code in Perps PnL hero card behind rewardsReferralCodeEnabled feature flag

  • S1 is over, but code stays for potential S2 - flag defaults to disabled
  • Selector supports both boolean and version-gated JSON flag formats
    https://consensyssoftware.atlassian.net/browse/TAT-2430

  https://app.launchdarkly.com/projects/metamask-client-config-api-mobile/flags/rewards-referral-code-enabled/targeting?env=flask-dev&env=flask-prod&env=production&selected-env=production

Changelog

CHANGELOG entry: Gate rewards referral code in Perps PnL hero card behind rewardsReferralCodeEnabled feature flag

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

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

Low Risk
Low risk: behavior change is limited to hiding/showing the referral code in the Perps PnL hero card and share copy based on a remote flag, with tests covering enabled/disabled cases.

Overview
Referral code display in the Perps PnL hero card is now feature-flagged off by default. PerpsHeroCardView derives an effectiveReferralCode that is only set when selectPerpsRewardsReferralCodeEnabledFlag is true, and uses it to control referral tag rendering, layout styling, and the share message/link.

Adds selectPerpsRewardsReferralCodeEnabledFlag to Perps feature-flag selectors, supporting both boolean and version-gated flag shapes, and expands unit tests to cover flag enabled/disabled and referral-code-present/absent scenarios.

^{Written by Cursor Bugbot for commit c731e97. 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.

[aganglada]

@geositta we are serving Enabled by default, is this ok? I think we need to disable right now, correct?
Also please lets meet the >= 80% threshold on coverage

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokePerps, SmokeRewards
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 90%

click to see 🤖 AI reasoning details

E2E Test Selection:
The changes add a new feature flag selector selectPerpsRewardsReferralCodeEnabledFlag to gate the display of referral codes in the PerpsHeroCardView component. This is a targeted change to the Perps (perpetuals trading) feature that:

1. Adds a new selector in app/components/UI/Perps/selectors/featureFlags/index.ts that reads the rewardsReferralCodeEnabled remote feature flag
2. Modifies PerpsHeroCardView.tsx to use this flag to conditionally show/hide referral codes
3. Updates unit tests to properly test the feature flag gating behavior

The changes are well-scoped to the Perps feature with proper unit test coverage. The referral code functionality is part of the rewards system, so both SmokePerps and SmokeRewards tags are appropriate. The risk is low because:

• Changes are isolated to a specific view component
• Feature flag adds a gate but doesn't change core functionality
• Comprehensive unit tests are included
• No changes to navigation, shared components, or critical paths

Performance Test Selection:
The changes involve adding a simple Redux selector and a conditional check in a component. This has negligible performance impact - no changes to list rendering, data loading patterns, animations, or critical user flows. The selector is a simple read from state with minimal computation. No performance tests are needed.

View GitHub Actions results

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[gambinish]

Tested this by toggling the new flag disabled in the main-dev environment and confirmed that the referral code doesn't render: