[majesticwizardcat]

Follows https://code.pod.network/pod/pod/pulls/170 (merged): GET /clob/activity/{account} and pod_activity serve one account's activity as one entry list per batch, {"<batch>": [{k, …}]}, with a type filter, newest-first whole-batch paging and next passed back as to. The SDK reads that shape and keeps client.activity(account, query) as the one feed of everything that happened to an account.

Public API

• One feed per account: client.activity(account) holds the one pod_activity subscription and the one paging state; activity.view({ types, from, to }) is a filtered view over its rows (client.activity(account, query) returns one), so the activity page, the chart and any other reader share a single subscription.
• ActivityEntry rows keep activityType and timeMs (the batch) and gain the kinds the node now stores: fill (this fill with its own fee, running totals, closedAs, positionAfter), modify (new and old terms), termination (how the order left the book), modify_reject and cancel_reject (the refusal's reason text, stored by the node like a rejected placement's invalid_reason). The order row is the order as /clob/orders serves it, with its current state on REST and the admission state on the stream; live entries update the held order.
• Order.fills is gone, on /clob/orders too: fills are the activity fill rows and /clob/fills. OrderEvent.fill keeps the live fill's payload.
• A transfer row carries counterparty: the receiver when amount is negative, the sender otherwise. On the wire the money kinds use short names (tok, amt, err, cp, sz, eq); the public rows keep their names.
• ActivityType is the nine kinds, usable as the filter; ActivityQuery.from/to are inclusive batch bounds in ms, limit counts entries per REST page.
• OrderStatus/TerminalStatus gain self_trade_canceled; OrderEvent gains cancel_reject with cancelRejection, so onEvent reports a refused cancel instead of dropping it.
• PodRestClient.activity takes {types, fromUs, toUs, limit} and returns the page as batches newest first with nextUs.

Behaviour

• ActivityHistory seeds from the newest page, subscribes from solution_now, folds every batch in order into the orders it holds, and loadOlder passes next back as to. One batch map is the dedupe point for both sources; a reconnect re-seed fills the gap from the stream cursor and keeps the paging position.
• pnlHistoryStream reads money flows with activity_types=backstop,bridge_transfer,transfer again.
• Version 0.13.0: the public types changed.

Docs

The API reference for the new shape is its own PR, #323; this one carries the SDK code and its README.

🤖 Generated with Claude Code

[0zzy-o]

Looks good!