@ai4b-team/fsaos-gateway-sdk 3.38.1 → 3.40.0

package/README.md

@@ -257,7 +257,10 @@ src/
 
 Set the registered application configuration before importing the SDK, then
 initialize it once. Tracking starts by default; custom business events remain
-explicit.
+explicit. Automatic page and declared-action capture runs for every published
+source that declares those adapters. A successful public form submission sends
+its receipt to each source that declares `form_receipt`; the default source
+continues to supply the durable form row's visitor and session attribution.
 
 ```ts
 window.__FSAOS_CONFIG__ = {
@@ -348,3 +351,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.