Description

Adds the new Predict-specific empty state experience for wallet home users with no Predict positions. The treatment replaces the generic/trending-only empty state with a sports discovery layout featuring World Cup/NBA championship discovery rows, bracket/stage CTAs, and feature-flagged BTC up/down row scaffolding that is hidden for now.

This PR also implements Segment/MetaMetrics tracking for the Predict Empty State A/B test:

• Tracks Empty State Viewed exposure for zero-position Predict users.
• Tracks treatment CTA engagement with cta_name and optional category_name.
• Threads active_ab_tests through market entry and bet placement paths for downstream attribution.
• Preserves trending experiment attribution when the trending-only section renders the treatment/list layout.
• Normalizes championship CTA category tracking so the FIFA World Cup winner row reports category_name: "world_cup" instead of the internal row kind.
• Adds remote feature flags for the Predict discovery NBA champion row and empty-state experiment handling.

The BTC 5m up/down row is intentionally left hidden and its data/navigation wiring is commented for now because the shared live-market hook work lives on predict/crypto-updown-feed-card and has not merged into main yet. The current branch keeps the row scaffold in place behind SHOW_BTC_UP_DOWN_5M_ROW = false so the later integration should be a small, low-risk follow-up instead of rebuilding the row wiring from scratch.

When predict/crypto-updown-feed-card is merged, enable the BTC row by:

• Removing the temporary SHOW_BTC_UP_DOWN_5M_ROW guard, or setting it to true if the team still wants a short-lived rollout switch.
• Uncommenting the shared hook imports and hook call in HomepagePredictWorldCupDiscovery.
• Replacing the temporary BTC placeholder values with the hook values for spot price, price-to-beat, countdown, market id, and market metadata.
• Uncommenting the navigateToMarketDetails branch in handleBtcRow so the row opens the current 5m up/down market directly when available.
• Keeping the fallback Predict crypto market-list navigation for cases where no current 5m market is available.

Changelog

CHANGELOG entry: Added a new Predict discovery empty state for users with no Predict positions

Related issues

Refs: https://consensyssoftware.atlassian.net/browse/TMCU-749
https://consensyssoftware.atlassian.net/browse/TMCU-750
https://consensyssoftware.atlassian.net/browse/TMCU-754

Manual testing steps

Feature: Predict empty state discovery

  Scenario: user with no Predict positions views the Predict section
    Given Predict is enabled
    And the user has zero active or claimable Predict positions

    When the user lands on the wallet home Predict section
    Then the Predict empty state is displayed
    And the Empty State Viewed event is emitted with surface "predict", the assigned variant, and active_ab_tests

  Scenario: user taps a treatment CTA
    Given the user is assigned to the treatment variant
    And the Predict empty state sports discovery layout is visible

    When the user taps a World Cup, NBA, category, or explore CTA
    Then the Empty State CTA Clicked event is emitted with the correct cta_name
    And category_name is included for category-specific CTAs
    And the World Cup winner row reports category_name "world_cup"
    And downstream Market Viewed and Bet Placed attribution includes active_ab_tests

  Scenario: trending-only treatment list preserves attribution
    Given the homepage Predict section is rendered in trending-only mode
    And the discovery experiment assigns the list treatment

    When the user opens a market from the sports discovery list
    Then the Predict market navigation params include the trending experiment transactionActiveAbTests

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.

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.