@alxxsck/ai-assistant 1.2.0 → 1.4.0

package/README.md

@@ -268,8 +268,15 @@ The widget consumes Lola Backend `command.created` envelopes from the AnyCable
 deduplicates `commandId` during reconnect replay. Updating the interaction session
 now reconnects REST and AnyCable without remounting the widget.
 
-Host-owned pages, modals, and elements are registered explicitly. Backend payloads
-are never evaluated as JavaScript or used as arbitrary selectors:
+The complete frontend integration and rollout guide is available in
+[`docs/ui-actions-sdk.ru.md`](docs/ui-actions-sdk.ru.md).
+
+The previous callback fields (`url`, `target`, `commandType`,
+`targetDefinition`, and `modalId`) remain as deprecated aliases for a
+zero-downtime host migration.
+
+Canonical page routes and modal names arrive in `data.target`; the host only
+provides typed callbacks:
 
 ```ts
 const widget = new ChatWidgetInstance({
@@ -280,6 +287,11 @@ const widget = new ChatWidgetInstance({
     sessionId,
     expiresAt,
   },
+  handlers: {
+    openModal: ({ modalName }) => modalRegistry.open(modalName),
+    openPage: ({ route }) => router.push(route),
+  },
+  // Temporary fallback for legacy commands without data.target.
   uiTargets: {
     deposit_button: {
       kind: "button",
@@ -287,7 +299,7 @@ const widget = new ChatWidgetInstance({
     },
     deposit_modal: {
       kind: "modal",
-      query: { lola_modal: "deposit" },
+      modalName: "deposit",
     },
     account_page: {
       kind: "page",
@@ -295,11 +307,6 @@ const widget = new ChatWidgetInstance({
       query: { source: "lola" },
     },
   },
-  handlers: {
-    openModal: ({ modalCode, payload }) =>
-      modalRegistry.open(modalCode!, payload),
-    openPage: ({ url }) => router.push(url!),
-  },
 });
 ```
 
@@ -315,9 +322,8 @@ by an element's `overflow` or container bounds and follows resize and scroll. A
 URL fallback uses `history.pushState` and emits `popstate`, so an explicitly
 configured query such as `?lola_modal=deposit` can be handled without reloading the
 host SPA. A registered modal selector can also open a native `HTMLDialogElement`.
-Commands are normalized across the current backend payload (`modalId`, `pageId`,
-`target`) and the canonical Lola contract (`data.target.code`, `modalCode`,
-`pageCode`). If no safe handler/fallback exists, the widget sends
+`data.target` is authoritative. Legacy commands without it are resolved through
+`payload.modalId`/`pageId` and `uiTargets`. If no safe handler/fallback exists, the widget sends
 `unsupported` and emits `command_unsupported`; other lifecycle events are
 `command_received`, `command_succeeded`, `command_failed`, and `command_expired`.