@noodleseed/assistant 1.9.0 → 1.11.0

package/README.md

@@ -247,6 +247,26 @@ interaction streams a continuation. `principalKey` is browser-local and never se
 whenever the authenticated user or tenant changes so the hook aborts and clears the previous session and
 transcript.
 
+If the product deliberately sends a first turn on mount, make the effect cleanup-aware. React Strict Mode
+discards the provisional effect, so a persistent "already sent" ref can suppress the stable remount:
+
+```tsx
+import { useEffect } from "react";
+
+useEffect(() => {
+  let active = true;
+  queueMicrotask(() => {
+    if (active) settle(client.sendMessage(initialMessage));
+  });
+  return () => {
+    active = false;
+  };
+}, [client, initialMessage]);
+```
+
+`settle` must await or catch the command promise as in the complete example; the same structured failure
+also appears in the hook's `error` state.
+
 When the customer-owned transcript should render the linked MCP App itself, pass the typed `data-view`
 payload and the same client to the supported host component:
 
@@ -259,7 +279,7 @@ if (part.type === "data-view") {
       key={`${part.data.id}:${part.data.resourceUri}`}
       client={client}
       view={part.data}
-      theme="dark"
+      theme={resolvedTheme}
       onError={(failure) => reportAssistantError(failure)}
     />
   );
@@ -269,7 +289,9 @@ if (part.type === "data-view") {
 `NoodleAppView` owns the double iframe and AppBridge. Its lifecycle identity is the supplied client plus
 `view.id` plus `view.resourceUri`: ordinary parent rerenders and fresh view/callback objects retain the
 iframe, while a semantic view replacement or unmount requests standard App teardown and closes the bridge.
-Do not also key an ancestor by the whole view object or a callback.
+Do not also key an ancestor by the whole view object or a callback. Pass the embedding application's
+resolved `"light"` or `"dark"` theme; later changes are published through MCP Apps host context without
+replacing the iframe.
 
 Outside React, subscribe to the DOM-free AI SDK `UIMessage` state without registering a custom element or
 touching browser storage:
@@ -318,6 +340,24 @@ Use the lower-level `subscribe(...)` event stream only for transport and session
 do not belong in the transcript. The package uses the headless `ai` runtime only; React remains an optional
 peer isolated to the `/react` and `/react/client` entries.
 
+For a custom progress surface, raw `tool_started` carries the direct invocation's call `id` and technical
+`tool` name before execution. Map known tools through a finite application-owned label table and use a
+neutral fallback such as "Working"; never turn an internal identifier into customer copy mechanically.
+Keep one reserved region with `role="status"` and `aria-live="polite"` from submitted/thinking through tool
+activity and the linked-view skeleton. `view_available` makes that view ready; a raw `error` event or chat
+`error` state replaces the skeleton with `role="alert"`. Keep the skeleton's dimensions stable, mark its
+decorative shapes `aria-hidden="true"`, and disable shimmer/transition animation under
+`@media (prefers-reduced-motion: reduce)`.
+
+The transport identity of a view is exactly `view.id + view.resourceUri`; different call IDs are distinct
+invocations and must not be collapsed automatically. If the product intentionally owns one current panel
+for a known resource, define an explicit application-owned slot map and replace only that slot:
+
+```ts
+const viewSlots = new Map([["ui://workspace/current", "current-workspace"]]);
+const renderKey = viewSlots.get(view.resourceUri) ?? `${view.id}:${view.resourceUri}`;
+```
+
 `clientContext` contains untrusted locale/timezone presentation hints and is evaluated for every turn.
 The client resolves a turn or interaction only after exactly one valid terminal `done` event followed by
 stream EOF. A truncated or malformed stream, duplicate `done`, or any frame after `done` is
@@ -393,10 +433,19 @@ exact control over assistant-specific roles:
 ```tsx
 <NoodleAssistant
   sessionEndpoint="/api/assistant/session"
+  theme={resolvedTheme}
   appearance={{
     light: {
-      panel: { surface: "#FFFFFF", text: "#101828", border: "#E4E7EC" },
-      composer: { surface: "#F9FAFB", text: "#101828", border: "#D0D5DD" },
+      panel: {
+        surface: "var(--app-surface)",
+        text: "var(--app-text)",
+        border: "var(--app-border)",
+      },
+      composer: {
+        surface: "var(--app-input)",
+        text: "var(--app-text)",
+        border: "var(--app-border)",
+      },
       confirmation: { surface: "#F8FAFC", text: "#101828", border: "#CBD5E1" },
       primaryButton: { surface: "#635BFF", text: "#FFFFFF" },
     },
@@ -405,11 +454,38 @@ exact control over assistant-specific roles:
 />
 ```
 
-The same object is available as `element.appearance`. It covers canvas, panel, header, assistant/user
-messages, composer, suggestions, confirmation, primary/secondary buttons, launcher, code, and MCP App frame
-roles in light and dark modes. Exact colors are preserved; insufficient contrast emits the typed
-`assistant-appearance-warning` event. Stable public CSS variables remain available for stylesheet-based
-integration:
+The same object is available as `element.appearance`. CSS custom properties inherit through the assistant
+host into its shadow tree, so `var(--app-token)` references reuse the embedding application's existing
+tokens without copying literal colors. Exact parseable literal colors are preserved and checked;
+insufficient contrast emits the typed `assistant-appearance-warning` event. Contrast for unresolved CSS
+references remains the host application's responsibility.
+
+The complete typed appearance role map is:
+
+| Appearance role | Public CSS custom properties |
+| --- | --- |
+| `canvas` | `--ns-assistant-canvas` |
+| `text` | `--ns-assistant-text` |
+| `mutedText` | `--ns-assistant-muted-text` |
+| `link` | `--ns-assistant-link` |
+| `focus` | `--ns-assistant-focus` |
+| `success` | `--ns-assistant-success` |
+| `warning` | `--ns-assistant-warning` |
+| `danger` | `--ns-assistant-danger` |
+| `panel` | `--ns-assistant-panel`, `--ns-assistant-panel-text`, `--ns-assistant-panel-border` |
+| `header` | `--ns-assistant-header`, `--ns-assistant-header-text`, `--ns-assistant-header-border` |
+| `assistantMessage` | `--ns-assistant-assistant-message`, `--ns-assistant-assistant-message-text`, `--ns-assistant-assistant-message-border` |
+| `userMessage` | `--ns-assistant-user-message`, `--ns-assistant-user-message-text`, `--ns-assistant-user-message-border` |
+| `composer` | `--ns-assistant-composer`, `--ns-assistant-composer-text`, `--ns-assistant-composer-border` |
+| `suggestion` | `--ns-assistant-suggestion`, `--ns-assistant-suggestion-text`, `--ns-assistant-suggestion-border` |
+| `confirmation` | `--ns-assistant-confirmation`, `--ns-assistant-confirmation-text`, `--ns-assistant-confirmation-border` |
+| `primaryButton` | `--ns-assistant-primary-button`, `--ns-assistant-primary-button-text`, `--ns-assistant-primary-button-border` |
+| `secondaryButton` | `--ns-assistant-secondary-button`, `--ns-assistant-secondary-button-text`, `--ns-assistant-secondary-button-border` |
+| `launcher` | `--ns-assistant-launcher`, `--ns-assistant-launcher-text`, `--ns-assistant-launcher-border` |
+| `code` | `--ns-assistant-code`, `--ns-assistant-code-text`, `--ns-assistant-code-border` |
+| `app` | `--ns-assistant-app`, `--ns-assistant-app-text`, `--ns-assistant-app-border` |
+
+Stable public CSS variables also remain available directly for stylesheet-based integration:
 
 ```css
 noodle-assistant {
@@ -427,6 +503,11 @@ defaults. The public slots are `launcher-icon`,
 embedding-page integration API, not a way to put HTML or callbacks in deployment configuration. Internal
 shadow-DOM selectors and classes are not public API.
 
+`theme="auto"` follows the browser's operating-system color preference. When the embedding application has
+its own theme toggle, pass its resolved `"light"` or `"dark"` value to `NoodleAssistant` and every
+`NoodleAppView`. Updates change the assistant in place and notify mounted MCP Apps through standard host
+context.
+
 Server branding controls customer name, themed logo/mark/avatar assets, semantic light/dark colors, density,
 radius, typography, and automatic theme. `embeddedAssistant(...)` controls floating/inline/drawer layout,
 position and dimensions, mobile and launcher/header/avatar/timestamp behavior, visible labels, suggested

package/dist/{chunk-RYQBXTLR.js → chunk-KRB2SXFD.js}

@@ -8360,6 +8360,11 @@ function toAssistantClientEvent(event) {
         return event;
       }
       break;
+    case "tool_started":
+      if (hasString(value, "id") && hasString(value, "tool") && hasOptionalTurnId(value)) {
+        return event;
+      }
+      break;
     case "tool_proposed":
       if (hasString(value, "id") && hasString(value, "tool") && hasOptionalString(value.title) && hasOptionalString(value.description) && hasOptionalJson(value.arguments) && (value.reviewSchema === void 0 || isRecord2(value.reviewSchema)) && hasOptionalString(value.expiresAt) && (value.requiresConfirmation === void 0 || value.requiresConfirmation === true) && hasOptionalTurnId(value)) {
         return event;
@@ -9086,4 +9091,4 @@ export {
   AssistantClientError,
   createAssistantClient
 };
-//# sourceMappingURL=chunk-RYQBXTLR.js.map
+//# sourceMappingURL=chunk-KRB2SXFD.js.map