Description

This PR builds on perps/fix-avail-balance-order-entry by fixing the remaining live-update gap for HyperLiquid availableToTradeBalance.

The parent branch corrected the balance math and UI usage, but after a successful trade or margin mutation the Perps home screen could still briefly show the right value and then get overwritten by stale streamed account data, because the live HyperLiquid account stream was still using cached spot state.

The solution is to refresh the existing streamed account path after successful trade mutations instead of adding new UI side refresh logic.

An optional refreshLiveAccountState() hook was added to the provider interface, implemented for HyperLiquid, and invoked by TradingService after successful order placement, close, flip, batch close, and margin updates.

On HyperLiquid, that forces a fresh spotClearinghouseState fetch and reuses the existing account aggregation/notification path, so subscribers receive an updated availableToTradeBalance from the live stream itself rather than a temporary one-off refresh.

Changelog

CHANGELOG entry:

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.

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.