@ai4b-team/fsaos-gateway-sdk 3.38.0 → 3.39.0

package/README.md

@@ -174,7 +174,7 @@ loaded page whenever a reply changes. It supports one item `type`, an explicit
 `scope`, `sort_by: 'created_at'`, and optional `parent_id`, `fields`, or
 `field_in`. It returns the same list and pagination fields as
 `useInfiniteItems`. Inserts cost one item read; updates are ignored unless
-`shouldReadUpdate(change, loadedItems)` selects them; deletes and reconnects
+`shouldReadUpdate(change, loadedItems)` selects them; moves, deletes, and reconnects
 reconcile the pages. More complex filters fall back to the ordinary realtime
 listing. The host still needs its normal account or path WebSocket subscription.
 
@@ -348,3 +348,22 @@ coalesced item-change events and reconnects, with no polling.
 
 Requires the `personal-sections` kernel method from migration `0793523446ad`.
 Projects are protocol-ready; a consumer must supply its Project UI separately.
+
+### Bound browser read traffic
+
+Hosts sharing the SDK's QueryClient can opt into transport scheduling before mounting readers:
+
+```ts
+configureGatewayReads({ concurrency: 6, timeoutMs: 15_000, onTiming: recordTiming });
+useInfiniteItems(filter, { priority: 'foreground' });
+gatewayCall('query', params, { signal, priority: 'background' });
+```
+
+Equivalent in-flight reads share one transport request, scoped by credentials,
+session generation, hostname, and effective parameters. Each observer receives its
+own result object and may cancel independently. The last cancellation aborts the
+fetch; identity reset cancels queued and active reads. The deadline includes queue
+time. `onTiming` reports only method, priority, queue/request duration and outcome.
+Commands, writes, materializing queries and subscriptions bypass the queue. The
+scheduler never retries a request; retry/cooldown policy remains with the host's
+existing QueryClient. Without configuration, transport behavior is unchanged.