chore(predict): adds initial logic to handle a resolved market

[kevinbluer]

Description

• Adds logic to market details to handle a closed market
• Not full parity with the designs / flow yet, but leaning towards more incremental PRs to mitigate merge conflicts, etc

Changelog

CHANGELOG entry: null

Related issues

Fixes: PRED-189

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

^{Cursor Bugbot is generating a summary for commit 8e1bb29. Configure here.}

[cursor]

Bug: Market Outcome Prop Mismatch Causes Display Inconsistency

For closed markets, the PredictMarketOutcome component incorrectly uses market?.outcomes[0] for its outcome prop, even though the outcomeToken prop correctly identifies the winning token. This mismatch can cause inconsistent details to display, like the title from the winning token but the image or volume from a different outcome.

 

[sonarqubecloud]

Quality Gate failed

Failed conditions
68.4% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud