saasco-sdk 0.2.3 → 0.2.4

package/dist/{support-chat.d.cts → support.d.cts}

@@ -1,6 +1,6 @@
 /**
  * Iframe-side half of the cross-origin bridge. Runs inside the Saasco
- * `/embed/support-chat` page and talks to the host page's loader over
+ * `/embed/support` page and talks to the host page's loader over
  * `postMessage`:
  *
  * - inbound host messages (boot/identify/updateJwt/setStateSnapshot/viewport/
@@ -29,7 +29,7 @@ declare function initEmbedBridge(options: {
 declare function setStateSnapshot(snapshot: unknown): void;
 
 /**
- * Public types for the embeddable support chat widget. These restate the
+ * Public types for the embeddable support widget. These restate the
  * server wire contracts (`libs/support/shared` / `libs/chat/shared`) locally
  * so the published package carries zero workspace dependencies.
  */
@@ -49,17 +49,16 @@ type JSONSchema7Object = {
 /**
  * The runtime shape of a tool the support widget can run in the browser. Tools
  * are authored in the dashboard (stored in `Meta`) and served by the public
- * settings endpoint as a `PublicChatTool`, which the widget rebuilds into this
+ * settings endpoint as a `PublicSupportTool`, which the widget rebuilds into this
  * shape via `reconstructDashboardTool`.
  *
  * `execute` runs in the host app's browser when the agent calls a host tool
  * and may touch in-page state, mutations, or SDKs. Server tools (dashboard
- * `execution: "server"`) are proxied by the agent instead and never reach the
- * widget; the reconstructed `execute` is only a same-origin `credentials:
- * "include"` fallback. Tools marked `destructive` pause for an explicit
- * Approve/Reject before running.
+ * `execution: "server"`) are proxied by the agent instead — the widget must
+ * not browser-fetch their absolute endpoints (that causes CORS noise). Tools
+ * marked `destructive` pause for an explicit Approve/Reject before running.
  */
-type SupportChatTool = {
+type SupportTool = {
     /** Shown to the model; 1–2000 chars. */
     description: string;
     /** Pauses for an explicit Approve/Reject before running. */
@@ -91,7 +90,7 @@ type SupportChatTool = {
     contextParameters?: string[];
 };
 /** A canned prompt offered in the empty state; clicking it fills the input. */
-type SupportChatSuggestion = {
+type SupportSuggestion = {
     /** Optional second line shown under the label. */
     description?: string;
     label: string;
@@ -99,7 +98,7 @@ type SupportChatSuggestion = {
     prompt: string;
 };
 type WidgetConfig = {
-    /** Origin of the saasco app hosting the support-chat API, e.g. https://app.example.com */
+    /** Origin of the saasco app hosting the support API, e.g. https://app.example.com */
     baseUrl: string;
     /** Read at submit time and appended to the agent's system prompt. */
     getStateSnapshot?: () => unknown;
@@ -107,16 +106,16 @@ type WidgetConfig = {
     placeholder?: string;
     projectId: string;
     /** Canned prompts offered before the first message. */
-    suggestions?: SupportChatSuggestion[];
+    suggestions?: SupportSuggestion[];
 };
 
 /**
- * Plain-fetch transport for the public support-chat REST endpoints. The
+ * Plain-fetch transport for the public support REST endpoints. The
  * embedding origin must be on the project's allowlist (configured in the
  * support widget settings) for cross-origin calls to pass CORS.
  */
 
-type ChatSession = {
+type SupportSession = {
     attachments?: ConversationImageAttachment[];
     conversationId: string;
     sessionToken: string;
@@ -126,7 +125,7 @@ type ConversationImageAttachment = {
     fileName?: string;
     url: string;
 };
-type ChatThreadMessage = {
+type SupportConversationMessage = {
     attachments?: ConversationImageAttachment[];
     /** Replier's first name — present for `role: "team"` (human) messages only. */
     authorName?: string;
@@ -144,16 +143,16 @@ type ChatThreadMessage = {
     plainBody: string | null;
     role: "user" | "team" | "bot";
 };
-type ChatThread = {
+type SupportConversation = {
     /** False while a human has taken over — the widget goes persist-only. */
     agentEnabled: boolean;
     conversationId: string;
-    messages: ChatThreadMessage[];
+    messages: SupportConversationMessage[];
     state: "open" | "closed" | "snoozed";
 };
 
 /**
- * Embeddable customer-facing support chat for third-party apps — an
+ * Embeddable customer-facing support for third-party apps — an
  * Intercom-style messenger (Home + Messages tabs, branded workspace rows, a
  * restyled chat with a workspace header and per-message meta lines) on top of the
  * persisted support channel:
@@ -164,7 +163,7 @@ type ChatThread = {
  * - an email gate captures a reply-to address before the first message when the
  *   host app hasn't already identified the visitor; every message is persisted
  *   into the saasco support inbox under `projectId`, with human replies merged
- *   into the open chat by polling the thread endpoint, and
+ *   into the open chat by polling the conversation endpoint, and
  * - once a human takes the conversation over the agent stream is muted, the
  *   customer sees a handoff acknowledgment, a "Waiting for a teammate" indicator
  *   until someone replies, then "{name} has joined the conversation" above the
@@ -174,11 +173,11 @@ type ChatThread = {
  * the Saasco iframe-origin `localStorage` so anonymous threads survive reloads
  * (best-effort — Safari/strict-Firefox partition third-party storage; identified
  * users resume server-side via the JWT instead). This component is the iframe
- * app entry: it renders directly into the `/embed/support-chat` page (no host-
+ * app entry: it renders directly into the `/embed/support` page (no host-
  * realm blank-iframe wrapper), and the host integrates over the postMessage
  * bridge — identity, JWT, state snapshots, viewport and open/close all arrive
  * through {@link initEmbedBridge} and are read here from the registry.
  */
-declare function SupportChatWidgetInner({ baseUrl, getStateSnapshot, placeholder, projectId, suggestions, }: WidgetConfig): React.ReactElement;
+declare function SupportWidgetInner({ baseUrl, getStateSnapshot, placeholder, projectId, suggestions, }: WidgetConfig): React.ReactElement;
 
-export { type ChatSession, type ChatThread, type ChatThreadMessage, type JSONSchema7Object, type SupportChatSuggestion, type SupportChatTool, SupportChatWidgetInner, type WidgetConfig, initEmbedBridge, setStateSnapshot };
+export { type JSONSchema7Object, type SupportConversation, type SupportConversationMessage, type SupportSession, type SupportSuggestion, type SupportTool, SupportWidgetInner, type WidgetConfig, initEmbedBridge, setStateSnapshot };

package/dist/{support-chat.d.ts → support.d.ts}

@@ -1,6 +1,6 @@
 /**
  * Iframe-side half of the cross-origin bridge. Runs inside the Saasco
- * `/embed/support-chat` page and talks to the host page's loader over
+ * `/embed/support` page and talks to the host page's loader over
  * `postMessage`:
  *
  * - inbound host messages (boot/identify/updateJwt/setStateSnapshot/viewport/
@@ -29,7 +29,7 @@ declare function initEmbedBridge(options: {
 declare function setStateSnapshot(snapshot: unknown): void;
 
 /**
- * Public types for the embeddable support chat widget. These restate the
+ * Public types for the embeddable support widget. These restate the
  * server wire contracts (`libs/support/shared` / `libs/chat/shared`) locally
  * so the published package carries zero workspace dependencies.
  */
@@ -49,17 +49,16 @@ type JSONSchema7Object = {
 /**
  * The runtime shape of a tool the support widget can run in the browser. Tools
  * are authored in the dashboard (stored in `Meta`) and served by the public
- * settings endpoint as a `PublicChatTool`, which the widget rebuilds into this
+ * settings endpoint as a `PublicSupportTool`, which the widget rebuilds into this
  * shape via `reconstructDashboardTool`.
  *
  * `execute` runs in the host app's browser when the agent calls a host tool
  * and may touch in-page state, mutations, or SDKs. Server tools (dashboard
- * `execution: "server"`) are proxied by the agent instead and never reach the
- * widget; the reconstructed `execute` is only a same-origin `credentials:
- * "include"` fallback. Tools marked `destructive` pause for an explicit
- * Approve/Reject before running.
+ * `execution: "server"`) are proxied by the agent instead — the widget must
+ * not browser-fetch their absolute endpoints (that causes CORS noise). Tools
+ * marked `destructive` pause for an explicit Approve/Reject before running.
  */
-type SupportChatTool = {
+type SupportTool = {
     /** Shown to the model; 1–2000 chars. */
     description: string;
     /** Pauses for an explicit Approve/Reject before running. */
@@ -91,7 +90,7 @@ type SupportChatTool = {
     contextParameters?: string[];
 };
 /** A canned prompt offered in the empty state; clicking it fills the input. */
-type SupportChatSuggestion = {
+type SupportSuggestion = {
     /** Optional second line shown under the label. */
     description?: string;
     label: string;
@@ -99,7 +98,7 @@ type SupportChatSuggestion = {
     prompt: string;
 };
 type WidgetConfig = {
-    /** Origin of the saasco app hosting the support-chat API, e.g. https://app.example.com */
+    /** Origin of the saasco app hosting the support API, e.g. https://app.example.com */
     baseUrl: string;
     /** Read at submit time and appended to the agent's system prompt. */
     getStateSnapshot?: () => unknown;
@@ -107,16 +106,16 @@ type WidgetConfig = {
     placeholder?: string;
     projectId: string;
     /** Canned prompts offered before the first message. */
-    suggestions?: SupportChatSuggestion[];
+    suggestions?: SupportSuggestion[];
 };
 
 /**
- * Plain-fetch transport for the public support-chat REST endpoints. The
+ * Plain-fetch transport for the public support REST endpoints. The
  * embedding origin must be on the project's allowlist (configured in the
  * support widget settings) for cross-origin calls to pass CORS.
  */
 
-type ChatSession = {
+type SupportSession = {
     attachments?: ConversationImageAttachment[];
     conversationId: string;
     sessionToken: string;
@@ -126,7 +125,7 @@ type ConversationImageAttachment = {
     fileName?: string;
     url: string;
 };
-type ChatThreadMessage = {
+type SupportConversationMessage = {
     attachments?: ConversationImageAttachment[];
     /** Replier's first name — present for `role: "team"` (human) messages only. */
     authorName?: string;
@@ -144,16 +143,16 @@ type ChatThreadMessage = {
     plainBody: string | null;
     role: "user" | "team" | "bot";
 };
-type ChatThread = {
+type SupportConversation = {
     /** False while a human has taken over — the widget goes persist-only. */
     agentEnabled: boolean;
     conversationId: string;
-    messages: ChatThreadMessage[];
+    messages: SupportConversationMessage[];
     state: "open" | "closed" | "snoozed";
 };
 
 /**
- * Embeddable customer-facing support chat for third-party apps — an
+ * Embeddable customer-facing support for third-party apps — an
  * Intercom-style messenger (Home + Messages tabs, branded workspace rows, a
  * restyled chat with a workspace header and per-message meta lines) on top of the
  * persisted support channel:
@@ -164,7 +163,7 @@ type ChatThread = {
  * - an email gate captures a reply-to address before the first message when the
  *   host app hasn't already identified the visitor; every message is persisted
  *   into the saasco support inbox under `projectId`, with human replies merged
- *   into the open chat by polling the thread endpoint, and
+ *   into the open chat by polling the conversation endpoint, and
  * - once a human takes the conversation over the agent stream is muted, the
  *   customer sees a handoff acknowledgment, a "Waiting for a teammate" indicator
  *   until someone replies, then "{name} has joined the conversation" above the
@@ -174,11 +173,11 @@ type ChatThread = {
  * the Saasco iframe-origin `localStorage` so anonymous threads survive reloads
  * (best-effort — Safari/strict-Firefox partition third-party storage; identified
  * users resume server-side via the JWT instead). This component is the iframe
- * app entry: it renders directly into the `/embed/support-chat` page (no host-
+ * app entry: it renders directly into the `/embed/support` page (no host-
  * realm blank-iframe wrapper), and the host integrates over the postMessage
  * bridge — identity, JWT, state snapshots, viewport and open/close all arrive
  * through {@link initEmbedBridge} and are read here from the registry.
  */
-declare function SupportChatWidgetInner({ baseUrl, getStateSnapshot, placeholder, projectId, suggestions, }: WidgetConfig): React.ReactElement;
+declare function SupportWidgetInner({ baseUrl, getStateSnapshot, placeholder, projectId, suggestions, }: WidgetConfig): React.ReactElement;
 
-export { type ChatSession, type ChatThread, type ChatThreadMessage, type JSONSchema7Object, type SupportChatSuggestion, type SupportChatTool, SupportChatWidgetInner, type WidgetConfig, initEmbedBridge, setStateSnapshot };
+export { type JSONSchema7Object, type SupportConversation, type SupportConversationMessage, type SupportSession, type SupportSuggestion, type SupportTool, SupportWidgetInner, type WidgetConfig, initEmbedBridge, setStateSnapshot };