…o-sweep spot→perps on withdraw

AccountState now carries three purpose-built fields:
- totalBalance     — venue equity (display only)
- spendableBalance — max collateral for a new position (order-entry)
- withdrawableBalance — max reachable to user's wallet (withdraw)

Previously `availableBalance` was overloaded between order-entry and withdraw
paths, and the `availableToTradeBalance` hotfix (TAT-3016) carried an optional
fallback that every consumer had to re-derive. This commit retires both,
pushing per-intent semantics into the type with JSDoc per field.

Per-provider mapping is provider-internal:
- HL Unified:  withdrawable + freeSpotUSDC (both new fields fold spot)
- HL Standard: withdrawable (spot.hold = 0, math collapses)
- MYX:         walletBalance (spendable === withdrawable)

HyperLiquidProvider.withdraw() now auto-sweeps spot→perps via
usdClassTransfer when the perps clearinghouse alone can't cover the
requested amount but the user's spendable does. The caller (UI) never
branches on provider — it just reads withdrawableBalance. If the shortfall
exceeds free spot, the withdraw is rejected with a clear error.

Fixes: TAT-3047 — unblocks withdraw for Unified-mode accounts whose
collateral sits entirely in spot USDC (previously showed \$0 max and
refused to submit).

Scope:
- AccountState + SubAccountState types in app/controllers/perps/types
- HL adapter, accountUtils spot-fold, subscription-service aggregation
- HyperLiquidProvider.withdraw() sweep + polling
- MYX adapter
- 30+ consumer files migrated by intent (spendable vs withdrawable vs total)
- Hook params renamed (usePerpsOrderValidation, validateBalance,
  getMaxAllowedAmount)
- Test fixtures + mocks updated across ~40 test files

…tomic

HL's usdClassTransfer is applied at the validator layer and is visible to
the perps clearinghouse immediately on `status === 'ok'`. The 10s poll on
clearinghouseState was defensive paranoia added before SDK semantics were
verified. Removing it eliminates a failure mode where a delayed `ok`
response would throw a misleading "sweep did not confirm before timeout"
error while the funds had already moved.

After-sweep path is now: transfer → check status → withdraw3.

… balance contract

Three fallout spots missed in the prior field rename:

1. hyperLiquidAdapter.test.ts asserted the adapter still returns
   availableToTradeBalance. Removed — the field no longer exists.
2. HyperLiquidSubscriptionService.test.ts expected subAccountBreakdown
   entries without withdrawableBalance. Production code emits it now.
3. tests/framework/fixtures/json/default-fixture.json +
   tests/component-view/renderers/perpsViewRenderer.tsx seed
   accountState directly (bypassing redux-persist migration 133), so
   legacy availableBalance would leave consumers reading 0 on any
   fixture-backed run. Migrated the seed shapes to the new fields.

…State shape

The cold-start disk cache (PERPS_DISK_CACHE_USER_DATA) stores
AccountState snapshots via buildUserDataPayload and is hydrated into
cachedUserDataByProvider by hydrateFromDiskSync before the first WS
tick. Existing installs have legacy-shape accountState
(availableBalance / availableToTradeBalance) sitting in that cache, so
consumers that read spendable/withdrawableBalance via getPreloadedData
see undefined and render $0 / disabled controls until the first live
fetch lands.

The disk payload has no in-payload version field, so the simplest
no-tech-debt path is to bump the storage key. Upgraded installs see an
empty new cache on first run, fall through to skeleton/fallback, then
backfill from WS as normal. The orphan old-key blob stays on disk
(small, eventually cleaned by any reset/logout flow).

…Unified mode

Live probe against the Trading fixture (Unified-mode mainnet) shows HL
rejects usdClassTransfer with 'Action disabled when unified account is
active'. Both sweeps (withdraw + updateMargin) would fail on every
Unified-mode user — the default on app.hyperliquid.xyz and most of our
traffic. That is a worse regression than the original TAT-3047 symptom
(UI showed \$0, didn't submit).

Correct behaviour:
- Unified mode: HL unifies the spot + perps ledger internally. withdraw3
  and updateIsolatedMargin draw from the unified balance directly. No
  sweep needed.
- Standard mode: spot and perps are separate; moving funds requires
  explicit user action on HL web. Our mobile app did not handle this
  pre-refactor and this PR does not introduce it.

This PR therefore reduces to rename-only: the three-field contract
(totalBalance / spendableBalance / withdrawableBalance), the persisted-
state migration, and consumer updates. withdraw() and updateMargin()
bodies revert to their pre-refactor shapes aside from the field name
changes in validation.

Revert-of: 2708b11 (updateMargin sweep), portion of 5f07189 +
a3a1798 (withdraw sweep).

…AT-3047

Three composable flows under scripts/perps/agentic/teams/perps/flows/:

- hl-balance-contract-check: asserts PerpsController.accountState exposes
  the new three-field contract (spendable / withdrawable / total) with no
  legacy keys. Inputs: address, phaseLabel. Runs against any account.

- hl-balance-math-check: asserts the spot-fold math by using the
  controller's subAccountBreakdown as perps-side truth (covers HIP-3
  multi-DEX) plus spotClearinghouseState REST as spot-side truth.
  Expected: spendable/withdrawable = Σ(breakdown.spendable) + freeSpot;
  total = Σ(breakdown.total) + spot.total − spot.hold; spendable ===
  withdrawable. Tolerates a small rounding epsilon.

- hl-empty-state-check: asserts zero-balance accounts surface the
  PerpsEmptyBalance affordance (Add Funds button) on PerpsMarketListView.

These compose cleanly via \`call\` so future balance-field refactors can
reuse them with different fixture accounts.

Recipe usage (local, .task/-gated): see .task/fix/tat-3047-0424-1139/
VALIDATION.md for the multi-account validation matrix and run output.

Previously spot USDC was folded into spendable/withdrawable unconditionally,
which is correct for HL Unified/Portfolio (spot is unified with perps) but
inflates balances on Standard mode where spot is a separate ledger HL's
backend can't auto-draw from. UI approved submissions HL would reject.

Design — clean separation:
- accountUtils.addSpotBalanceToAccountState takes { foldIntoCollateral }
  option; provider-agnostic utility, no HL-specific imports.
- hyperliquid-types.ts owns HyperLiquidAbstractionMode (alias of HL SDK's
  UserAbstractionResponse) and hyperLiquidModeFoldsSpot(mode) helper.
- HyperLiquidProvider.getAccountState fetches userAbstraction in parallel
  with clearinghouse + spot, computes the flag, passes to the util.
- HyperLiquidSubscriptionService caches the mode alongside #cachedSpotState
  (refreshed together, cleared together on cleanup) and gates both fold
  call sites on the helper.

Migration 133 asymmetric mapping: legacy availableBalance maps to
withdrawableBalance (perps-only pre-refactor value);
availableToTradeBalance ?? availableBalance maps to spendableBalance.
Minimises cold-start inflation window for upgraded Standard-mode users.

Live proof on dev2 flipped to Standard:
  spot.free = \$10.01
  standardSemanticExpected.spendable = 0 (perps-only)
  adapterActual.spendable = 0
  observedInflation = 0 — gate works.

Recipe phase 2c passes hl-balance-math-check with foldIntoCollateral=false
and hl-standard-mode-fold-check asserting standardModeCorrect.

Tests: accountUtils.test.ts gains 2 cases; hyperliquid-types.test.ts is
new and covers all 5 modes plus null/undefined. Recipe 36/36 across
Trading + dev1 + dev2 Unified-to-Standard-to-Unified + Account 6.

… fixtures

- HyperLiquidSubscriptionService: throttle constant moved to perpsConfig,
  the doc-comment that documented it stayed behind above an unrelated field
  declaration. Remove the dangling comment.
- useTransactionCustomAmount tests: three perps-withdraw fixtures only
  seeded withdrawableBalance; pair them with spendableBalance to match the
  peer fixture in the same file.

Map was set in two write sites and cleared in cleanUp/clearAll, but
never read. Throttle gate uses #abstractionModeLastWsRefreshAtByUser
exclusively. Removing the dead state so the intent of the remaining
map is unambiguous.

…ance-contract-reshape

# Conflicts:
#	app/components/UI/Perps/Views/PerpsWithdrawView/PerpsWithdrawView.tsx
#	app/components/UI/Perps/hooks/usePerpsBalanceTokenFilter.ts
#	app/components/UI/Perps/hooks/usePerpsPaymentTokens.ts
#	app/components/UI/Perps/hooks/useWithdrawValidation.ts
#	app/components/Views/confirmations/components/perps-confirmations/perps-withdraw-balance/perps-withdraw-balance.tsx
#	app/components/Views/confirmations/hooks/alerts/useInsufficientPerpsBalanceAlert.ts
#	app/components/Views/confirmations/hooks/transactions/useTransactionCustomAmount.ts
#	app/controllers/perps/providers/HyperLiquidProvider.test.ts
#	app/controllers/perps/providers/HyperLiquidProvider.ts
#	app/controllers/perps/services/HyperLiquidSubscriptionService.test.ts
#	app/controllers/perps/services/HyperLiquidSubscriptionService.ts
#	app/controllers/perps/types/hyperliquid-types.test.ts
#	app/controllers/perps/types/hyperliquid-types.ts
#	app/controllers/perps/utils/accountUtils.test.ts
#	app/controllers/perps/utils/accountUtils.ts