@waniwani/sdk 0.20.1 → 0.20.3

package/dist/chat/index.d.ts

@@ -258,9 +258,20 @@ interface Messages {
     promptInput: {
         placeholder: string;
         uploadFiles: string;
+        uploadFilesUpTo: string;
+        uploadFilesUpToWithPages: string;
         stop: string;
         submit: string;
         removeAttachments: string;
+        removeAttachment: string;
+        uploading: string;
+        retry: string;
+        retryUpload: string;
+        uploadFailed: string;
+        dropToAttach: string;
+        errorAccept: string;
+        errorTooLarge: string;
+        errorTooMany: string;
     };
     workingIndicator: {
         default: string;
@@ -284,6 +295,9 @@ interface Messages {
     };
     attachments: {
         attachmentFallback: string;
+        kindPdf: string;
+        kindImage: string;
+        kindFile: string;
         fileFallback: string;
     };
     threadMenu: {
@@ -559,6 +573,18 @@ interface ChatClassNames {
     /** The input bar container. */
     input?: string;
 }
+/** What the platform reports about the documents module for this project. */
+interface DocumentUploadConfig {
+    enabled: boolean;
+    /** Refused before the upload starts. */
+    maxBytes: number;
+    /** Stated to the visitor; the OCR vendor is what enforces it. */
+    maxPdfPages: number;
+    /** The chat request refuses more than this, so the composer must not take more. */
+    maxFiles: number;
+    /** MIME types the platform accepts. */
+    accept: string[];
+}
 interface ChatBaseProps {
     /** Waniwani project API key */
     apiKey?: string;
@@ -603,6 +629,12 @@ interface ChatBaseProps {
     body?: Record<string, unknown>;
     /** Enable file attachments in the input. Defaults to false. */
     allowAttachments?: boolean;
+    /**
+     * Document upload, as the platform reports it on `GET /api/mcp/chat/config`.
+     * The composer offers a paperclip, a drop target and paste only while
+     * `enabled` is true, and the upload endpoint enforces the same flag.
+     */
+    documentUpload?: DocumentUploadConfig;
     /** Placeholder text shown in the input field. Defaults to "Ask me anything...". Animates with a typing effect. */
     placeholder?: string;
     /**
@@ -900,6 +932,100 @@ interface McpAppFrameProps {
 }
 declare function McpAppFrame({ resourceUri, toolInput, toolResult, resourceEndpoint, chatSessionId, isDark, className, autoHeight, onOpenLink, onFollowUp, onCallTool, onDisplayModeChange, isFullscreen, toolDefinitions, }: McpAppFrameProps): react_jsx_runtime.JSX.Element;
 
+/**
+ * The shapes crossing the WebMCP boundary.
+ *
+ * Structural rather than imported from `@modelcontextprotocol/sdk`, because
+ * everything here is also read by the browser bridge, and the MCP SDK is an
+ * optional peer dependency that has no business in a page bundle. What the
+ * server sends and what the page reads is JSON either way.
+ */
+/**
+ * One MCP content block. `type` is the discriminator every block carries; the
+ * index signature keeps the rest of whichever block it is, since nothing on
+ * this path reads them and re-deriving the union would only restate a schema
+ * the server already validated on the way out.
+ */
+type WebMcpContentBlock = {
+    type: string;
+    text?: string;
+    [key: string]: unknown;
+};
+/**
+ * Everything the page needs to mount a widget itself.
+ *
+ * Assembled server-side because none of it is derivable on the page: the view
+ * URI carries a content hash that moves every deploy, and the display tool's
+ * result is what the view reads its own configuration from.
+ */
+type WebMcpWidgetPayload = {
+    /**
+     * The `ui://` the view was resolved from.
+     *
+     * Carries a content hash that moves on every deploy, which is why this is
+     * resolved server-side per call and why nothing on the page can cache it.
+     *
+     * The only half of the view the page is told. Where to fetch it from is the
+     * resource endpoint the page already derived from its token, the same one
+     * the chat's own widget iframes use.
+     */
+    viewUri: string;
+    /** Display tool the view belongs to. */
+    tool: string;
+    /** Props, delivered to the view as `ui/notifications/tool-input`. */
+    data: Record<string, unknown>;
+    /** The display tool's own result, delivered as `ui/notifications/tool-result`. */
+    result: {
+        content: WebMcpContentBlock[];
+        structuredContent?: Record<string, unknown>;
+        _meta?: Record<string, unknown>;
+    };
+    /** Whether the flow is waiting on the visitor before it can advance. */
+    interactive: boolean;
+    /**
+     * Set by the preview endpoint. A real widget step is a flow waiting on the
+     * visitor and has no way out; a preview is something someone opened to look
+     * at, so the host can give it one.
+     */
+    preview?: boolean;
+};
+
+/**
+ * `McpAppFrame` is used exactly as the chat uses it, with no new props.
+ *
+ * Three things would be worth telling it on this surface, and none of them are
+ * worth touching a component every customer's chat renders:
+ *
+ * - It advertises a `message` capability in its handshake, which is how a view
+ *   pushes a follow-up into the conversation. There is no channel back to a
+ *   browsing agent, so a view that uses it is ignored. The panel's own content
+ *   still works; only the agent's narration is lost.
+ * - Its `hostInfo` says "Waniwani Chat". A view reading it is told the wrong
+ *   host, and nothing in ours reads it.
+ * - It clamps its own height. The panel below sets `maxHeight` and scrolls, so
+ *   an oversized view is contained here rather than there.
+ *
+ * Each becomes worth doing once this surface has run in front of real traffic
+ * and one of them has actually cost something.
+ */
+type WebMcpOverlayProps = {
+    /** The step to show, or `null` for nothing. */
+    widget: WebMcpWidgetPayload | null;
+    /** The tools endpoint, so a view's own `tools/call` can be proxied. */
+    toolsEndpoint: string;
+    /** Auth for that endpoint, matching what the bridge sends. */
+    headers?: Record<string, string>;
+    /**
+     * Where view HTML is fetched from, resolved from the token the same way the
+     * chat's own widget iframes resolve theirs.
+     */
+    resourceEndpoint: string;
+    /** Raised when the view says it is finished, and on Escape for a preview. */
+    onClose: () => void;
+    isDark?: boolean;
+};
+declare function WebMcpOverlay({ widget, toolsEndpoint, resourceEndpoint, headers, onClose, isDark, }: WebMcpOverlayProps): react_jsx_runtime.JSX.Element | null;
+
 /**
  * **Bare-bones, bring-your-own-backend chat primitive.** Most apps want
  * `WaniwaniChat` (the hosted version) — `ChatEmbed` is the unmanaged
@@ -1085,4 +1211,4 @@ declare function mergeTheme(userTheme?: ChatTheme): Required<ChatTheme>;
  */
 declare function themeToCSSProperties(theme: ChatTheme): Record<string, string>;
 
-export { type ChatAppearance, type ChatBaseProps, ChatEmbed, type ChatEmbedMcpConfig, type ChatEmbedProps, type ChatHandle, type ChatTheme, DARK_THEME, DEFAULT_THEME, type McpAppDisplayMode, McpAppFrame, type McpAppFrameProps, type ShowToolCalls, type SuggestionsConfig, type ThemePreset, WaniwaniChat, type WaniwaniChatOverrides, type WaniwaniChatProps, type WelcomeConfig, type WidgetEvent, type WidgetEventName, type WidgetMode, mergeTheme, themeToCSSProperties };
+export { type ChatAppearance, type ChatBaseProps, ChatEmbed, type ChatEmbedMcpConfig, type ChatEmbedProps, type ChatHandle, type ChatTheme, DARK_THEME, DEFAULT_THEME, type McpAppDisplayMode, McpAppFrame, type McpAppFrameProps, type ShowToolCalls, type SuggestionsConfig, type ThemePreset, WaniwaniChat, type WaniwaniChatOverrides, type WaniwaniChatProps, WebMcpOverlay, type WebMcpOverlayProps, type WelcomeConfig, type WidgetEvent, type WidgetEventName, type WidgetMode, mergeTheme, themeToCSSProperties };