@marketrix.ai/widget 4.0.114 → 4.0.116

package/dist/src/components/chat/MessageItem.d.ts

@@ -5,6 +5,15 @@
  * the allow/deny controls of a screen-access request, and a done/failed/stopped glyph in the tenant
  * accent at a per-status opacity. The last message fades in.
  *
+ * **Memoized, and `isTaskRunning` arrives as a prop rather than through `useWidget()`.** `MessageList`
+ * commits a whole new `messages` array on every `chat/delta` token (`ChatContext`'s reducer keeps
+ * reference equality for every message except the one being streamed into), so a `useWidget()`/
+ * `useChatContext()` call anywhere inside a list row re-subscribes that row to the token stream directly
+ * and defeats `React.memo` regardless of props — measured at ~21 `MessageItem`/`MessageBody` renders per
+ * token in a 20-message transcript before this change (one per row), ~1 after (only the streaming row).
+ * `onScreenAccessAllow`/`onScreenAccessDeny` must stay referentially stable (`ChatView`'s `useScreenShare`
+ * wraps them for exactly this) or the memo comparison never bails.
+ *
  * `MessageBody` renders the message's `parts` — text and progress lines — and `Thinking` is the
  * spinner-and-caption row shown while a reply is pending, its caption switching to name the visitor's
  * action when the agent is blocked on them. Thinking shows while a placeholder carries no text yet, and
@@ -16,8 +25,9 @@ import type { ChatMessage } from '../../types';
 interface MessageItemProps {
     message: ChatMessage;
     isLastMessage: boolean;
+    isTaskRunning: boolean;
     onScreenAccessAllow?: () => void;
     onScreenAccessDeny?: () => void;
 }
-export declare const MessageItem: React.FC<MessageItemProps>;
+export declare const MessageItem: React.NamedExoticComponent<MessageItemProps>;
 export {};

package/dist/src/components/views/ChatView.d.ts

@@ -21,8 +21,11 @@
  * `useScreenShare` (this file's only other consumer) owns the screen-share lifecycle: the in-transcript
  * permission card, the browser picker, the live share message, and ending a share. `useLatest` keeps a
  * value readable from a callback that must not be re-created (the polling interval below, mounted once);
-its refs are listed in that effect's deps for the linter, but since `useRef` identity never changes,
-listing them cannot re-arm the interval.
+ * its refs are listed in that effect's deps for the linter, but since `useRef` identity never changes,
+ * listing them cannot re-arm the interval. The same idiom stabilizes `handleScreenAccessRequestAllow`/
+ * `handleScreenAccessRequestDeny`: both are handed to every `MessageItem` through `MessageList`, and a
+ * fresh closure each render (the naive `beginScreenShare`/inline-arrow form) defeats `MessageItem`'s
+ * `React.memo` for the whole transcript on every SSE token, not just the streaming row.
  * The hook returns `requestScreenAccess` — posting a request card carrying the queued turn, no-oping if
  * one is already open — plus that card's Allow/Deny handlers, the toolbar dialog's Allow/Dismiss
  * handlers, and `toggleScreenShareRef`, a toggle stopping a live share or opening that dialog.

package/dist/src/design-system/component-tokens.d.ts

@@ -8,7 +8,10 @@
  *
  * `LAYER_TOKENS` is the z-index ladder (screen-edge glow < panel < dialog < toast), based just above the
  * 2^31-ish ceiling most host pages use so the widget sits over everything without the values overflowing a
- * 32-bit int.
+ * 32-bit int. `showHighlight`/`showPopup` are a separate, much higher pair near the int32 ceiling: Show
+ * mode's coaching overlay (`ShowModeService`) mounts to the HOST page, outside the shadow root, to point at
+ * the widget's OWN chrome — it must outrank every value in this ladder by a wide margin, not sit one step
+ * above `toast`.
  */
 import type { CSSProperties } from 'react';
 export type RadiusToken = 'none' | 'sm' | 'md' | 'lg' | 'xl' | 'pill';
@@ -33,6 +36,8 @@ export declare const LAYER_TOKENS: {
     panel: number;
     dialog: number;
     toast: number;
+    showHighlight: number;
+    showPopup: number;
 };
 export declare const notificationToneStyles: Record<NotificationTone, {
     background: string;

package/dist/src/services/ShowModeService.d.ts

@@ -17,6 +17,9 @@
  * highlight is sized and placed over its element, so the first paint and every reposition run through it;
  * placement takes the first of right/left/above/below that fits then clamps, its 120px height an assumption,
  * and the watchdog tests `document.body.contains` first, covering removal as well as occlusion.
+ * `ACCENT_COLOR`/`TEXT_COLOR` are raw literals rather than design-system tokens: the highlight and popup
+ * mount to `document.body` on the HOST page, outside the shadow root, so `index.css`'s `:host`-scoped
+ * CSS custom properties never reach them.
  */
 interface ShowModeOptions {
     element: HTMLElement;