@ai4b-team/fsaos-gateway-sdk 3.31.0 → 3.31.1

package/README.md

@@ -157,6 +157,25 @@ The SDK does not decide when AI should respond, spawn agents, or infer agent ide
 | `useComponent(path)` | Dynamically load a component from the edge |
 | `useTheme()` | Read theme CSS custom properties |
 
+`useInfiniteItems(filter, { realtime: true })` uses the existing WebSocket event
+dispatch and reconnect recovery. As with the other realtime hooks, the host
+must hold an SDK account or path subscription (directly or via SDK bootstrap).
+It does not open a separate socket or subscribe once per component. The shared
+query cache stays fresh until a relevant item change or transport reconnect.
+Events with a different direct `parent_id` do not refresh a parent-filtered list;
+loaded items moving out still refresh their former list. Closed lists are marked
+stale without fetching, and unchanged lists reopen from cache. All consumers of
+the same filtered query should use the same realtime setting.
+
+A relevant burst refreshes the loaded pages once, using the existing
+`refreshQuery` protection against overlapping loads. Multiple pages are read
+again together so offset pagination stays consistent after inserts/deletes.
+Current VFS notifications do not include arbitrary `type_data` fields, so a
+direct-child change may still require a listing read to evaluate a field filter
+(for example `role=user`). Missing old-parent information can only identify a
+move out when the changed item is already cached; reconnect or the next fetch
+reconciles the remaining count. No background polling is used.
+
 **Channel / notification hooks:**
 
 | Hook | Description |