chore(runway): cherry-pick fix: cp-7.58.0 close position disabled when receiveAmount <0

[runway-github]

• fix: cp-7.58.0 close position disabled when receiveAmount <0 (fix: cp-7.58.0 close position disabled when receiveAmount <0 #21622)

Description

Problem

Users were blocked from closing positions when fees exceeded recoverable
value (receiveAmount <= 0), creating a financial trap where they
couldn't exit losing positions. This particularly affected accounts that
lost all available margin in the position after price movement.

Solution

Changed negative receive amount validation from a blocking error to a
non-blocking warning, allowing users to always close positions while
still informing them of the cost.

Changes

usePerpsClosePositionValidation.ts: Moved receiveAmount < 0 check from
errors to warnings array
PerpsClosePositionView.tsx: Removed receiveAmount <= 0 from button
disable logic
en.json: Added negative_receive_warning locale string
usePerpsClosePositionValidation.test.ts: Updated test to expect warning
instead of error

Impact

✅ Users can now always exit positions (critical for risk management)
✅ Clear warning can be shown when closing will cost money (we are not
currently showing warnings)

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/TAT-1887
Fixes: #21624

Manual testing steps

*** You may need to mock receiveAmount to simulate less than 0 on main
and then compare with this branch

Feature: close position disabled when receiveAmount <0

  Scenario: user creates a btc position at the min amount
    Given user loses all of the margin in their position to the point of have nothing left to get back
    When user attempts to close their position at total loss <0 
    Then user should be able to close that position

Screenshots/Recordings

Before

Message from Matthieu Saint Olive in
#tmp-beta-bip44-mobile

After

n/a position can close

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

Converts negative receive amount from blocking error to non-blocking warning so users can close positions; updates validation, button disable logic, tests, and locale strings.

• Perps Close Position UI:
  • Remove receiveAmount <= 0 from confirm button isDisabled logic in PerpsClosePositionView.tsx.
• Validation Hook (usePerpsClosePositionValidation):
  • Change negative receiveAmount check from error to warning (negative_receive_warning with formatted amount).
  • Update validation docs and numbering; keep other validations unchanged.
• Tests:
  • Adjust test to expect a warning (and still valid) for negative receiveAmount in usePerpsClosePositionValidation.test.ts.
• Localization:
  • Add perps.close_position.negative_receive_warning string in en.json.

^{Written by Cursor Bugbot for commit 727e0de. This will update automatically on new commits. Configure here.}

cfb4d79

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[Cal-L]

LGTM

[metamaskbot]

No release label on PR. Adding release label release-7.58.0 on PR, as PR was cherry-picked in branch 7.58.0.