@marketrix.ai/widget 4.0.110 → 4.0.111

package/dist/src/components/base/Surface.d.ts

@@ -1,27 +1,21 @@
 /**
  * `Surface` is the canonical container primitive: a polymorphic `forwardRef` element (`as`, default
  * `div`) that composes the shared layout-token vocabulary with a `background` token, a `SHADOW`
- * `elevation` token and a `paddingPreset`, all emitted as inline style. `SurfaceBackground` and
- * `SurfacePadding` are those token unions, `backgroundStyles` and `paddingPresetStyles` their lookup
- * tables — the `default`/`none` entries are empty, so a bare `Surface` is a plain element — and
- * `SurfaceProps` the prop surface: `LayoutProps` plus the host element's HTML attributes.
+ * `elevation` token and a `paddingPreset`, all emitted as inline style — the `default`/`none` lookup
+ * entries are empty, so a bare `Surface` is a plain element. `className` is dropped from the host
+ * attributes and re-declared because it is INTERNAL to `blocks/`: layout props are the styling API
+ * everywhere else, and the only legitimate classes are the `index.css` hooks the block components key on.
  *
  * `floatingCard` is a `variant` shorthand for the card-background/border/card-elevation/card-padding/xl-
  * rounded/margin bundle both `HomeView`'s recent-conversation card and `ChatView`'s composer card use —
  * the margin lives in `variantStyles` since both call sites want it, while `ChatView`'s extra
  * `marginTop: 'auto'` stays an override on its own `style` prop rather than joining the preset.
  *
- * `className` is dropped from those attributes and re-declared because it is INTERNAL to `blocks/`:
- * layout props are the styling API everywhere else, and the only legitimate classes are the
- * `index.css` hooks the block components key on.
- *
- * Style order is fixed and load-bearing: background → padding preset → elevation → layout props →
- * the caller's own `style` last, so an inline style always wins. `Flex` depends on that tail
- * position, resolving `display` itself because `resolveLayoutStyle` is applied ahead of it.
- *
- * `resolveLayoutStyle` is handed the whole `props` (it reads only layout keys), while the DOM spread
- * goes through `stripLayoutProps` — a layout token left on the props bag reaches the element as an
- * unknown attribute.
+ * Style order is fixed and load-bearing: background → padding preset → elevation → layout props → the
+ * caller's own `style` last, so an inline style always wins; `Flex` depends on that tail position,
+ * resolving `display` itself because `resolveLayoutStyle` is applied ahead of it. `resolveLayoutStyle`
+ * is handed the whole `props` (it reads only layout keys), while the DOM spread goes through
+ * `stripLayoutProps` — a layout token left on the props bag reaches the element as an unknown attribute.
  */
 import { type ElementType } from 'react';
 import { type ShadowToken } from '../../design-system/component-tokens';

package/dist/src/components/base/layoutProps.d.ts

@@ -3,25 +3,23 @@
  * `resolveLayoutStyle` which reduces them to a `CSSProperties` object, and `stripLayoutProps` which
  * removes them from a props bag so the remainder can be spread onto a DOM element. `SPACING_SCALE` is
  * the exported `SpacingToken`→pixel table, declared smallest-first so a token name orders the same way
- * as the pixels it emits (`__tests__/layoutProps.test.ts` pins that); `ALIGN`, `JUSTIFY`, `ANIMATION`
- * and `BORDER_SIDE` are the private lookups for the remaining token families.
+ * as the pixels it emits.
  *
  * Layout props resolve to a style object rather than class names: as classes they were interpolated
- * (`p-${token}`), which no scanner could see, so a build-time safelist emitting the whole 8x7 matrix
- * was the only thing keeping them alive and a missing entry failed silently at runtime.
- * `resolveLayoutStyle` emits a property only for a prop set to a non-default value — `grow: false`,
- * `shrink: true`, `border: false`, `rounded: false` and `animate: 'none'` deliberately emit nothing —
- * and its `ANIMATION` values name `mtx-*` keyframes `index.css` must define
- * (`__tests__/stylesheet-contract.test.ts` pins the pairing).
+ * (`p-${token}`), which no scanner could see, so a build-time safelist emitting the whole 8x7 matrix was
+ * the only thing keeping them alive and a missing entry failed silently at runtime. `resolveLayoutStyle`
+ * emits a property only for a prop set to a non-default value (`grow: false`, `shrink: true`, `border:
+ * false`, `rounded: false` and `animate: 'none'` deliberately emit nothing), and its `ANIMATION` values
+ * name `mtx-*` keyframes `index.css` must define.
  *
  * `LAYOUT_KEYS` must list every key of `LayoutProps`: `stripLayoutProps` filters by that set, so a
  * layout prop missing from it reaches the DOM as an unknown attribute. `as` and `style` are in it
  * because the consuming component (`Surface`) applies them itself rather than forwarding them.
  *
- * `withClass(base, extra)` appends an optional caller `className` to a component's fixed base class
- * (`Button`, `Icon`, `Avatar`). It is NOT the banned `cn()`: there is no variant list to merge or
- * dedup, just a plain conditional concat of one fixed string and one optional string — variants stay
- * on `data-*` attributes per the styling rule in `../../../CLAUDE.md`.
+ * `withClass(base, extra)` appends an optional caller `className` to a component's fixed base class. It
+ * is NOT the banned `cn()`: there is no variant list to merge or dedup, just a plain conditional concat
+ * of one fixed string and one optional string — variants stay on `data-*` attributes per the styling
+ * rule in `../../../CLAUDE.md`.
  */
 import type { CSSProperties, ElementType } from 'react';
 import { type RadiusToken } from '../../design-system/component-tokens';

package/dist/src/hooks/useFocusTrap.d.ts

@@ -1,23 +1,20 @@
 /**
  * Focus trap for the messenger panel: while `isActive`, focus starts inside `containerRef`, Tab cycles
  * within it, Escape calls `onEscape`, and on deactivation focus returns to whatever held it before.
- *
- * The tabbable candidates come from `utils/dom`'s shared `focusablesIn` (built on `TABBABLE_SELECTOR`,
- * visibility and `aria-hidden` ancestry — the same filter `keySimulation`'s Tab simulation uses, so the
- * widget's own tab order and the host page's can't re-diverge); `activeElementIn` reads the focused
- * element as seen from a container's own root; and `useFocusTrap(containerRef, isActive, {onEscape,
- * focusTargetRef})` focuses `focusTargetRef` (else the first focusable), installs one capture-phase
- * `keydown` listener on `document`, and restores focus on the active→inactive edge.
+ * `useFocusTrap(containerRef, isActive, {onEscape, focusTargetRef})` focuses `focusTargetRef` (else the
+ * first focusable), installs one capture-phase `keydown` listener on `document`, and restores focus on
+ * the active→inactive edge. The tabbable candidates come from `utils/dom`'s shared `focusablesIn`, the
+ * same filter `keySimulation`'s Tab simulation uses, so the widget's own tab order and the host page's
+ * can't re-diverge.
  *
  * Inside the widget's closed shadow root `document.activeElement` retargets to the HOST, never naming
  * an element of the widget's own tree; `activeElementIn` reads through `container.getRootNode()`
  * instead and is the ONE home for that retargeting — eslint's `no-restricted-properties` bans the bare
- * read everywhere else. Hand-rolled on purpose: `MessengerShell` is a NON-modal panel, not a Dialog,
- * and Base UI exposes no standalone focus trap; reaching it by making the panel a Dialog would inert
- * the customer's page. Both key arms bail unless focus is currently inside the container, since the
+ * read everywhere else. Hand-rolled on purpose: `MessengerShell` is a NON-modal panel, not a Dialog, and
+ * Base UI exposes no standalone focus trap; reaching it by making the panel a Dialog would inert the
+ * customer's page. Both key arms bail unless focus is currently inside the container, since the
  * listener sits on `document` ahead of host-page handlers and an unguarded Escape would close the
- * widget mid-typing. Tab `preventDefault`s only at the two ends; `previousActiveRef` edge-triggers the
- * restore once on close.
+ * widget mid-typing.
  */
 export declare function useFocusTrap(containerRef: React.RefObject<HTMLElement | null>, isActive: boolean, options?: {
     onEscape?: () => void;

package/dist/src/utils/dom.d.ts

@@ -1,29 +1,27 @@
 /**
  * Predicates the agent's element index runs against the HOST page's DOM — what counts as a control and
- * whether it is reachable — plus `WIDGET_SHADOW_HOST_CLASS`, set by `bootstrap` on the shadow host so
- * `DomService` can recognise its own overlay chrome instead of reporting it as obscuring the host page, and
- * `TABBABLE_SELECTOR`, the one tab-order candidate query: `send_keys`' Tab simulation walks the host page
- * with it and `useFocusTrap` the widget's own tree, and they must agree on what the browser would focus next.
+ * whether it is reachable. `TABBABLE_SELECTOR` is the one tab-order candidate query: `send_keys`'s Tab
+ * simulation walks the host page with it and `useFocusTrap` the widget's own tree, and they must agree
+ * on what the browser would focus next. `WIDGET_SHADOW_HOST_CLASS`, set by `bootstrap` on the shadow
+ * host, lets `DomService` recognise its own overlay chrome instead of reporting it as obscuring the host
+ * page.
  *
- * `ancestry` walks element → `parentElement`, crossing each shadow boundary at its host; a bare
- * `parentElement` walk stops dead at a `ShadowRoot`, so a control inside a host-page web component
- * would read as top-level. `disabledReason` names why an element cannot be operated (disabled control,
- * `aria-disabled`, or an `inert` ancestor) as a sentence fragment completing `DomService`'s
- * `Element <n> …` message — reword both together; `disabled` is read duck-typed since it sits on
- * several unrelated control interfaces. `isIndexable`, checked against `INTERACTIVE_ROLES`, is
- * `DomService`'s geometry-aware fallback after its cheap selector/handler checks. Visibility there is more
- * than computed style: an element scrolled out of an `overflow: hidden|clip` ancestor is unreachable despite
- * a non-zero rect (that walk stops at `document.body`), and a zero-size shadow host hides its whole tree, so
- * both chains are climbed. Its one `try` is deliberate — the host page owns this DOM and may have patched
- * anything on it, so a poisoned element is logged with the real error and skipped rather than aborting the
- * whole indexing pass.
+ * `ancestry` walks element → `parentElement`, crossing each shadow boundary at its host, since a bare
+ * `parentElement` walk stops dead at a `ShadowRoot` and a control inside a host-page web component would
+ * read as top-level. `disabledReason` names why an element cannot be operated (disabled control,
+ * `aria-disabled`, or an `inert` ancestor) as a sentence fragment completing `DomService`'s `Element
+ * <n> …` message — reword both together. `isIndexable` is `DomService`'s geometry-aware fallback after
+ * its cheap selector/handler checks; visibility there climbs both the `overflow: hidden|clip` chain
+ * (that walk stops at `document.body`) and the shadow-host size, since either can hide an element
+ * despite a non-zero rect. Its one `try` is deliberate — the host page owns this DOM and may have
+ * patched anything on it, so a poisoned element is logged with the real error and skipped rather than
+ * aborting the whole indexing pass.
  *
  * `focusablesIn` is the one home for "which `TABBABLE_SELECTOR` matches are actually reachable" —
- * `useFocusTrap` (the widget's own tree) and `keySimulation`'s Tab simulation (the host page) both call
- * it so they can't re-diverge. Per WAI-ARIA, `aria-hidden="true"` removes an element (and its whole
- * subtree) from the accessibility tree, so it must not receive focus — `isAriaHidden` walks ancestors,
- * not just the element itself, since a hidden container hides everything under it even though none of
- * those descendants carry the attribute.
+ * `useFocusTrap` and `keySimulation`'s Tab simulation both call it so they can't re-diverge.
+ * `isAriaHidden` walks ancestors, not just the element itself, since a hidden container hides everything
+ * under it (per WAI-ARIA, `aria-hidden="true"` removes an element and its whole subtree from the
+ * accessibility tree) even though none of those descendants carry the attribute.
  */
 export declare const WIDGET_SHADOW_HOST_CLASS = "marketrix-widget-container";
 export declare const TABBABLE_SELECTOR = "a[href], button:not([disabled]), input:not([disabled]), select:not([disabled]), textarea:not([disabled]), [tabindex]:not([tabindex=\"-1\"])";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@marketrix.ai/widget",
-  "version": "4.0.110",
+  "version": "4.0.111",
   "type": "module",
   "packageManager": "bun@1.4.2",
   "sideEffects": false,