feat(ts-sdk): account value on the PnL history

[majesticwizardcat]

What

Every point of pnlHistory and pnlHistoryStream now carries the absolute accountValue, next to pnl, when the node serves the activity feed (ADR 0057 on the node). Builds on the merged activity resource (#310) and PnL history.

How

Account value is PnL plus every movement that is not PnL:

accountValue(t) = accountValue(ref) + [PnL(t) − PnL(ref)] − Σ_{flows in (t, ref]} value(flow)

The backward walk keeps one more running sum over money events, fetched per window next to the fills and cached with them:

Row	Event	Value that moved
bridge_transfer with a positive amount, native token	cash	the amount
bridge_transfer with a positive amount, spot token	deposit, a size event	quantity × that tick's clearing price, which is also the cost the engine marks it at
transfer, either sign	cash or a size event by token	as above; a token leaving goes at the average cost, like a withdrawal
backstop without orderbook_id	cash of −cash	the balance moved to the backstop
native withdrawals from the bridge feed already read	cash	the amount
any row with error	skipped

Negative bridge_transfer rows and backstop legs are skipped because withdrawals and sweep legs already come from the existing feeds. Within a tick, events are undone as withdrawals, cash, fills, deposits, then sweeps.

On a node without /clob/activity the points omit accountValue and a warning says so; PnL is unchanged.

Also on this branch: two loading fixes

• Empty tick lookups are remembered. A lookup for the newest solutions row at or before t that comes back empty proves the market has no rows before t, so the cache keeps that bound per market and skips every older point. A yearly window on a canary account went from about 4,800 lookups cold and 4,300 again warm to about 600 cold and none warm: 6.7 s to 3.4 s cold, 5.7 s to 1.6 s warm.
• Smaller first chunks, shorter preamble. Chunks start at 10 points and grow 20, 40, 50; backstop and withdrawals ride with the snapshot round; the first windows are fetched while the watermark is checked, with a refetch of the newest window in the rare case the indexer was behind. Staging maker, 30 min: first chunk 1.7 s to 1.0 s. Canary account, 1 year: warm 1.3 s, which is now two round trips to Singapore plus the newest window.

The frontend's chart branch calls the one-shot pnlHistory and waits for every point; it needs pnlHistoryStream to see the chunks arrive.

Also on this branch: fills and solutions over REST

The node's /clob/fills/{account} and /clob/solutions routes (backend #129, same JSON as the ob_* reads, microsecond _us params) replace ob_getFills and ob_getSolutions in the walk. pod_getSolverState is the one JSON-RPC read left. Nodes that predate the routes answer 404 and get the ob_* twins behind the same calls; that fallback goes once every network has the routes.

What REST changes in cost: JSON-RPC let the walk batch 200 tick lookups into one request, REST has no batch, so each lookup is its own request, at most 24 in flight. Quiet accounts hardly notice; a yearly window is a few hundred requests. For a market maker, where the funding index of every fill batch is a lookup, the request count is in the thousands per hour of history. Two things on the node would remove that: a times= or until_us= list on /clob/solutions to answer several lookups in one response, and Cache-Control: immutable on past windows instead of today's no-store, which would let the browser cache do what the SDK cache does across reloads.

No deployed network has the routes yet, so the REST path is exercised by the unit tests and the fallback by the live checks until one does.

Verification

Unit tests only so far. The forward engine simulation tracks cash and account value through a cash deposit, a token deposit in the same tick as a fill, and a cash withdrawal, and the fold matches it at every tick; a stub node pushes a deposit, an outgoing transfer, a refused deposit and a cash sweep through the stream. No network serves the activity feed yet, so there is no live comparison against the positions endpoint's account value.

🤖 Generated with Claude Code

[0zzy-o]

Looks good, just a couple of things raised by the agent that seems worth checking on.