fix: in the position card, when user has multiple TP (or SL) orders, Then display TP (or SL) orders count instead of the position TP (or SL) priceof

[abretonc7s]

Explanation

A partial (quantity-scoped) take profit cannot be position-bound — a position-bound
trigger always closes the whole position — so updatePositionTPSL places it with
grouping: 'na' as a standalone reduce-only trigger. The scalar summary fields
Position.takeProfitPrice / stopLossPrice were only ever scanned from
position-bound triggers, so a position whose only take profit was partial reported
takeProfitCount: 1 with no price at all. Clients that render the scalar — the
mobile position card among them — showed nothing where a price belongs.

This adds resolvePositionTriggerSummaryPrice to @metamask/perps-controller/utils
and uses it wherever a position's TP/SL summary is assembled: when a direction has
exactly one trigger order, that order's price is the summary price, partial or not.
Two or more triggers keep the previously scanned value, because no single price
describes them and clients render takeProfitCount instead; zero triggers keep it
too, since it still carries the TP/SL of a pending order on the market, which the
trigger arrays deliberately exclude.

The same summary is computed at three independent sites — the REST getPositions
path, getUserDataSnapshot, and the WebSocket merge in
HyperLiquidSubscriptionService. All three now go through the helper, so the price a
position reports no longer depends on whether the WebSocket cache happens to be warm.

Note for clients: a partial take profit now surfaces on the scalar. A TP/SL editor
that prefills from takeProfitPrice should key off takeProfitOrders /
takeProfitCount instead, so a partial trigger is not silently offered up for
replacement by a whole-position one.

Proved end to end against HyperLiquid testnet: one real partial take profit attached
through the controller's signing path, read back through
PerpsController.getUserDataSnapshot() — takeProfitPrice was null before the
change and carries the trigger's price after, with a whole-position replacement
asserted in the same run to cover the pre-existing path.

References

• Fixes TAT-3791

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

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