@aigentyc/chat-sdk 0.2.5 → 0.3.1

package/dist/llms-full.txt

@@ -431,9 +431,33 @@ Peer deps required: `react>=19`, `react-dom>=19`. The CSS import is required for
 
 ## Slots
 
-Replace any UI piece via the `slots` prop:
+Replace any UI piece via the `slots` prop. Every slot receives `DefaultComponent` as a prop so you can compose with — or fully replace — the built-in UI.
 
-`header`, `welcome`, `message`, `input`, `footer`, `loader`, `suggestions`, `tools` (keyed per tool name).
+**Available slot names:**
+
+- `header`, `footer`, `input`, `welcomePage`, `loader` — layout chrome
+- `assistantMessage`, `userMessage`, `systemMessage` — per-role message rendering
+- `feedback` — thumbs-up/down + copy row under assistant messages
+- `emptyState` — shown when no messages and no welcome
+- `tools` — `Record<toolName, Component>` (keyed by **tool name**, e.g. `searchProducts`)
+- `toolRenderers` — `Record<renderMode, Component>` (keyed by **render mode**, e.g. `visualization`)
+- `liveChatPanel`, `satisfactionRating`, `visitorIdentityForm`, `floatingButton` — live-chat + widget chrome
+
+**Common confusion:** `tools` is by **tool name**, `toolRenderers` is by **render mode**. If you want to override a specific tool's display, use `tools`. In dev mode the SDK emits a console warning if a tool name leaks into `toolRenderers`.
+
+```tsx
+import type { AssistantMessageSlotProps } from "@aigentyc/chat-sdk";
+
+function MyAssistantMsg({ text, DefaultComponent, ...rest }: AssistantMessageSlotProps & { DefaultComponent: any }) {
+  return (
+    <div className="my-wrapper">
+      <DefaultComponent text={text} {...rest} />
+    </div>
+  );
+}
+
+<Chat slots={{ assistantMessage: MyAssistantMsg }} projectId="..." apiEndpoint="..." />
+```
 
 ## Tool rendering
 
@@ -648,17 +672,163 @@ import { useAigentycChat } from "@aigentyc/chat-sdk/hooks";
 
 const { newConversation, clearMessages } = useAigentycChat({ projectId: "...", apiEndpoint: "..." });
 
-<button onClick={newConversation}>New conversation</button>  // new sessionId + clears
-<button onClick={clearMessages}>Clear messages</button>      // clears, keeps session
+<button onClick={newConversation}>New conversation</button>  // new sessionId + clears + returns to welcome
+<button onClick={clearMessages}>Clear messages</button>      // clears, keeps session, returns to welcome
+```
+
+### Recipe: headless — full control with every event
+
+```tsx
+"use client";
+import { useAigentycChat } from "@aigentyc/chat-sdk/hooks";
+
+export default function MyCustomChat() {
+  const {
+    messages,
+    status,
+    sendMessage,
+    stopGeneration,
+    newConversation,
+    clearMessages,
+    activeTools,
+    liveChat,
+    sessionId,
+  } = useAigentycChat({
+    projectId: "proj_...",
+    apiEndpoint: "https://app.aigentyc.ai",
+    apiKey: "tyco_pk_...",
+    onMessageSent: (m) => console.log("sent", m),
+    onMessageReceived: (m) => console.log("received", m),
+    onStreamStart: () => console.log("stream started"),
+    onStreamEnd: () => console.log("stream ended"),
+    onToolCall: (name, args) => console.log("tool", name, args),
+    onToolResult: (name, result) => console.log("tool result", name, result),
+    onNewConversation: (newSessionId) => console.log("new session", newSessionId),
+    onStopGeneration: () => console.log("stopped"),
+    onClearMessages: () => console.log("cleared"),
+    onError: (err) => console.error(err),
+  });
+
+  return (
+    <div>
+      <div className="history">
+        {messages.map((m) => (
+          <div key={m.id}>
+            <b>{m.role}:</b> {m.content}
+          </div>
+        ))}
+      </div>
+      {status === "streaming" && <button onClick={stopGeneration}>Stop</button>}
+      <button onClick={newConversation}>New</button>
+    </div>
+  );
+}
+```
+
+### Recipe: control message part order (tools-first vs text-first)
+
+```tsx
+// Text parts render before tool cards (default, best for Q&A/RAG)
+<Chat messagePartOrder="text-first" projectId="..." apiEndpoint="..." />
+
+// Tool cards render before text (best for tool-heavy apps — product cards, forms, etc.)
+<Chat messagePartOrder="tools-first" projectId="..." apiEndpoint="..." />
+
+// Render parts in the stream order (whatever the API returns)
+<Chat messagePartOrder="stream-order" projectId="..." apiEndpoint="..." />
+```
+
+### Recipe: customize MessageFeedback (thumbs up/down) styling
+
+```tsx
+import { MessageFeedback } from "@aigentyc/chat-sdk/ai-elements";
+
+// Option 1: strip defaults and style from scratch
+<Chat
+  slots={{
+    feedback: (props) => (
+      <MessageFeedback {...props} unstyled classNames={{
+        root: "my-feedback-row",
+        thumbsUp: "my-thumb-btn",
+        thumbsDown: "my-thumb-btn",
+      }} />
+    ),
+  }}
+/>
+
+// Option 2: full render override
+<Chat
+  slots={{
+    feedback: (props) => (
+      <MessageFeedback
+        {...props}
+        renderActions={({ onPositive, onNegative, onCopy, feedback }) => (
+          <div className="flex gap-2">
+            <button onClick={onPositive} className={feedback === "positive" ? "active" : ""}>👍</button>
+            <button onClick={onNegative} className={feedback === "negative" ? "active" : ""}>👎</button>
+            <button onClick={onCopy}>Copy</button>
+          </div>
+        )}
+      />
+    ),
+  }}
+/>
 ```
 
+### Recipe: normalize messy tool data shapes
+
+Custom tools (especially `data_store`) can return rows in a few shapes. Use the helper so renderers don't care:
+
+```tsx
+import { normalizeToolRows } from "@aigentyc/chat-sdk";
+
+function ProductGrid({ result }: ToolRendererProps) {
+  // Handles: flat array, { rows: [...] } wrapper, raw DB rows { id, data: {...} }
+  const rows = normalizeToolRows(result?.data);
+  return (
+    <div className="grid grid-cols-2 gap-2">
+      {rows.map((row, i) => <div key={i}>{row.name as string} — ${row.price as number}</div>)}
+    </div>
+  );
+}
+```
+
+### Recipe: catch tool-renderer crashes without killing the chat
+
+Wrap a risky slot in `ChatErrorBoundary`:
+
+```tsx
+import { ChatErrorBoundary } from "@aigentyc/chat-sdk";
+
+<Chat
+  slots={{
+    tools: {
+      myRiskyTool: (props) => (
+        <ChatErrorBoundary
+          label="product grid"
+          onError={(e) => Sentry.captureException(e)}
+          fallback={(err, retry) => <div>Failed. <button onClick={retry}>Retry</button></div>}
+        >
+          <MyProductGrid {...props} />
+        </ChatErrorBoundary>
+      ),
+    },
+  }}
+/>
+```
+The built-in tool dispatcher already wraps each tool in a boundary, so a single broken renderer never takes down the rest of the chat. Use `ChatErrorBoundary` manually only around custom slots you haven't tested in production.
+
 ## Troubleshooting
 
 | Symptom | Likely cause | Fix |
 | --- | --- | --- |
 | Unstyled / broken layout | Missing CSS import | `import "@aigentyc/chat-sdk/theme/styles.css"` |
-| 401 / 403 from API | `apiKey` missing or wrong scope | Create key with `Chat: Full` permission |
+| 401 / "Missing Authorization" on embed | No `apiKey` passed — required for all third-party domain embeds | Pass `apiKey` prop (or `NEXT_PUBLIC_AIGENTYC_API_KEY` / `VITE_AIGENTYC_API_KEY` env var). The "no apiKey needed" path only works inside `app.aigentyc.com` itself (session cookie). |
+| 403 / invalid origin | API key's Allowed Origins list doesn't include your embed domain | Dashboard → Settings → API Keys → edit → add domain |
 | CORS error in browser | Allowed Origins on API key doesn't include current URL | Add `http://localhost:5173` (Vite) or `http://localhost:3000` (Next) to the key's Allowed Origins |
+| Slot override doesn't render | Using `toolRenderers` keyed by tool name | Use `tools` for per-tool overrides; `toolRenderers` is per render mode. Dev console warns automatically. |
+| Welcome doesn't reappear after "new conversation" | Old SDK version (pre-0.2) | Upgrade — `newConversation()` now triggers a bidirectional welcome toggle |
+| Dark mode leaks white backgrounds | Custom CSS / old SDK | As of 0.2, internal components use `bg-background`/`bg-card` vars — upgrade if you see white leaks |
 | `Cannot find module @ai-sdk/react` | Stale install from old SDK version | `rm -rf node_modules package-lock.json && npm install` (peers are bundled now) |
 | Hebrew text shows LTR | Forgot `language="he"` | Pass `language="he"` to `<Chat>` |
 | Tool result shows raw JSON | Custom tool with no renderer | Add `slots.tools[toolName]` or set `uiRenderMode: "hidden"` server-side |
@@ -695,22 +865,28 @@ Each entry below shows the typed exports for one subpath of the package. Use the
 ### `@aigentyc/chat-sdk` — Main exports — Chat, ChatWidget, ChatProvider, useAigentycChat
 
 ```ts
-export { a as ChatConfig, b as ChatEventCallbacks, c as ChatMessage, d as ComponentAction, L as Language, e as LiveChatMessage, f as LiveChatState, Q as QuestionConfig, S as SlotMap, T as ThemeConfig, g as ToolRendererProps, h as ToolResult } from './types-DKJ_-nbG.js';
+export { a as ChatConfig, b as ChatEventCallbacks, c as ChatMessage, d as ComponentAction, L as Language, e as LiveChatMessage, f as LiveChatState, Q as QuestionConfig, S as SlotMap, T as ThemeConfig, g as ToolRendererProps, h as ToolResult } from './types-DlNwk-bG.js';
 
-export { L as LiveChatReturn, U as UseAigentycChatOptions, a as UseAigentycChatReturn, u as useAigentycChat, b as useChatContext, c as useLiveChat, d as useSlot, e as useSlots } from './SlotsContext-CBtt36al.js';
+export { L as LiveChatReturn, S as SlotComponent, a as SlotName, U as UseAigentycChatOptions, b as UseAigentycChatReturn, r as renderSlot, u as useAigentycChat, c as useChatContext, d as useLiveChat, e as useSlot, f as useSlots } from './SlotsContext-BjiX1mRx.js';
 
 export { useTheme } from './theme.js';
 
 export { useI18n } from './i18n.js';
 
-export { Chat, ChatProvider, ChatProviderProps, ChatWidget };
+export { A as AssistantMessageSlotProps, C as ChatInterfaceProps, U as UserMessageSlotProps } from './ChatInterface-f8ftS56n.js';
+
+export { g as getToolDisplayData, n as normalizeToolRows } from './normalize-KzCLLqpU.js';
+
+export { F as FeedbackData, M as MessageFeedbackActionsState } from './message-feedback-cWR0NVok.js';
+
+export { Chat, ChatErrorBoundary, type ChatProps, ChatProvider, ChatProviderProps, ChatWidget };
 ```
 
 
 ### `@aigentyc/chat-sdk/hooks` — Hooks — useAigentycChat, useChatContext, useTheme, useI18n, useLiveChat, useSlots
 
 ```ts
-export { L as LiveChatReturn, U as UseAigentycChatOptions, a as UseAigentycChatReturn, u as useAigentycChat, b as useChatContext, c as useLiveChat, d as useSlot, e as useSlots } from './SlotsContext-CBtt36al.js';
+export { L as LiveChatReturn, U as UseAigentycChatOptions, b as UseAigentycChatReturn, u as useAigentycChat, c as useChatContext, d as useLiveChat, e as useSlot, f as useSlots } from './SlotsContext-BjiX1mRx.js';
 
 export { useTheme } from './theme.js';
 
@@ -725,16 +901,20 @@ export { useImageLoader, useIsMobile, useMultiImageLoader, useMultiOrderTracking
 ### `@aigentyc/chat-sdk/components` — Granular components — ChatInterface, ChatInput, ChatHeader, etc.
 
 ```ts
-export { CartDrawer, ChatDrawer, ChatFooter, ChatHeader, ChatInput, ChatInputWithAttachments, ChatInterface, FloatingButton, LiveChatHeader, LiveChatPanel, LiveChatQueueBanner, PreviewEmbedPanel, QuickQuestions, SatisfactionRating, SystemMessage, VisitorIdentityForm, WelcomePage };
+export { a as ChatInterface } from './ChatInterface-f8ftS56n.js';
+
+export { CartDrawer, ChatDrawer, ChatFooter, ChatHeader, ChatInput, ChatInputWithAttachments, FloatingButton, LiveChatHeader, LiveChatPanel, LiveChatQueueBanner, PreviewEmbedPanel, QuickQuestions, SatisfactionRating, SystemMessage, VisitorIdentityForm, WelcomePage };
 ```
 
 
 ### `@aigentyc/chat-sdk/tools` — Tool rendering — ToolRenderer, SearchKnowledgeBaseRenderer
 
 ```ts
-export { d as ComponentAction, h as ToolResult } from './types-DKJ_-nbG.js';
+export { d as ComponentAction, h as ToolResult } from './types-DlNwk-bG.js';
+
+export { J as JsonRenderResult } from './JsonRenderResult-D6ogds0_.js';
 
-export { J as JsonRenderResult } from './JsonRenderResult-Ftw4AKwb.js';
+export { g as getToolDisplayData, n as normalizeToolRows } from './normalize-KzCLLqpU.js';
 
 export { ComponentRenderer, SearchKnowledgeBaseRenderer, ToolRenderer, ToolRendererProps, VisualizationRenderer };
 ```
@@ -743,7 +923,7 @@ export { ComponentRenderer, SearchKnowledgeBaseRenderer, ToolRenderer, ToolRende
 ### `@aigentyc/chat-sdk/theme` — Theming — ThemeProvider
 
 ```ts
-export { T as ThemeConfig } from './types-DKJ_-nbG.js';
+export { T as ThemeConfig } from './types-DlNwk-bG.js';
 
 export { ThemeProvider, useTheme };
 ```
@@ -752,7 +932,7 @@ export { ThemeProvider, useTheme };
 ### `@aigentyc/chat-sdk/i18n` — Internationalization — addLanguage
 
 ```ts
-export { L as Language } from './types-DKJ_-nbG.js';
+export { L as Language } from './types-DlNwk-bG.js';
 
 export { I18nProvider, type I18nProviderProps, type TranslationKeys, type TranslationMap, addLanguage, isRTL, useI18n };
 ```
@@ -761,7 +941,7 @@ export { I18nProvider, type I18nProviderProps, type TranslationKeys, type Transl
 ### `@aigentyc/chat-sdk/core` — Core types and utilities
 
 ```ts
-export { b as ChatEventCallbacks, c as ChatMessage, C as ChatProviderProps, d as ComponentAction, L as Language, e as LiveChatMessage, f as LiveChatState, Q as QuestionConfig, S as SlotMap, i as SlotProps, T as ThemeConfig, g as ToolRendererProps, h as ToolResult } from './types-DKJ_-nbG.js';
+export { b as ChatEventCallbacks, c as ChatMessage, C as ChatProviderProps, d as ComponentAction, L as Language, e as LiveChatMessage, f as LiveChatState, Q as QuestionConfig, S as SlotMap, i as SlotProps, T as ThemeConfig, g as ToolRendererProps, h as ToolResult } from './types-DlNwk-bG.js';
 
 export { I as InteractionMetadata, a as InteractionType, T as TrackInteractionParams, U as UseInteractionTrackerOptions, g as generateSessionId, u as useInteractionTracker } from './interaction-tracker-D9P1Oq4j.js';
 

package/dist/message-feedback-BFh3-qym.d.cts

@@ -0,0 +1,92 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { ReactNode } from 'react';
+import { T as TrackInteractionParams } from './interaction-tracker-D9P1Oq4j.cjs';
+
+declare const REVIEW_TYPES: readonly [{
+    readonly value: "wrong_answer";
+    readonly labelKey: "wrongAnswer";
+}, {
+    readonly value: "partial_answer";
+    readonly labelKey: "partialAnswer";
+}, {
+    readonly value: "hallucination";
+    readonly labelKey: "hallucination";
+}, {
+    readonly value: "inappropriate_tone";
+    readonly labelKey: "inappropriateTone";
+}];
+type ReviewType = (typeof REVIEW_TYPES)[number]["value"];
+interface FeedbackData {
+    isPositive: boolean;
+    reviewType?: ReviewType;
+    reviewText?: string;
+}
+/**
+ * Render-prop state passed to `renderActions`, letting consumers build
+ * a fully custom action row while keeping all behaviour (submit, copy,
+ * analytics) intact.
+ */
+interface MessageFeedbackActionsState {
+    /** Current feedback selection (if any) */
+    feedback: "positive" | "negative" | null;
+    /** True while a feedback submit is in-flight */
+    isSubmitting: boolean;
+    /** True briefly after the copy button is used */
+    copied: boolean;
+    /** Submit positive feedback and fire analytics */
+    onPositive: () => void;
+    /** Submit negative feedback — opens the review form */
+    onNegative: () => void;
+    /** Copy the assistant's text content to clipboard */
+    onCopy: () => void;
+}
+interface MessageFeedbackProps {
+    messageId: string;
+    projectId: string;
+    sessionId?: string;
+    apiKey?: string;
+    apiEndpoint?: string;
+    textContent: string;
+    trackInteraction?: (params: TrackInteractionParams) => void;
+    /** Optional className merged onto the root wrapper. */
+    className?: string;
+    /**
+     * When true, strip the default Tailwind bubble styling and only render
+     * the semantic structure. Ideal if you want to style from scratch with
+     * your own design system.
+     */
+    unstyled?: boolean;
+    /**
+     * Per-element className overrides. Merged with defaults via `cn()` so
+     * Tailwind utilities can override (e.g. `bg-red-500`).
+     */
+    classNames?: {
+        root?: string;
+        actions?: string;
+        thumbsUp?: string;
+        thumbsDown?: string;
+        copy?: string;
+        reviewForm?: string;
+    };
+    /**
+     * Full override of the action button row. Receives the submit handlers
+     * + current state. Return any ReactNode. The built-in review form still
+     * appears below when the user clicks thumbs-down (unless you handle
+     * `onNegative` yourself and never trigger it).
+     *
+     * @example
+     * ```tsx
+     * renderActions={({ onPositive, onNegative, onCopy }) => (
+     *   <div className="my-custom-row">
+     *     <MyButton onClick={onPositive}>👍</MyButton>
+     *     <MyButton onClick={onNegative}>👎</MyButton>
+     *     <MyButton onClick={onCopy}>Copy</MyButton>
+     *   </div>
+     * )}
+     * ```
+     */
+    renderActions?: (state: MessageFeedbackActionsState) => ReactNode;
+}
+declare function MessageFeedback({ messageId, projectId, sessionId, apiKey, apiEndpoint, textContent, trackInteraction, className, unstyled, classNames, renderActions, }: MessageFeedbackProps): react_jsx_runtime.JSX.Element;
+
+export { type FeedbackData as F, type MessageFeedbackActionsState as M, MessageFeedback as a };

package/dist/message-feedback-cWR0NVok.d.ts

@@ -0,0 +1,92 @@
+import * as react_jsx_runtime from 'react/jsx-runtime';
+import { ReactNode } from 'react';
+import { T as TrackInteractionParams } from './interaction-tracker-D9P1Oq4j.js';
+
+declare const REVIEW_TYPES: readonly [{
+    readonly value: "wrong_answer";
+    readonly labelKey: "wrongAnswer";
+}, {
+    readonly value: "partial_answer";
+    readonly labelKey: "partialAnswer";
+}, {
+    readonly value: "hallucination";
+    readonly labelKey: "hallucination";
+}, {
+    readonly value: "inappropriate_tone";
+    readonly labelKey: "inappropriateTone";
+}];
+type ReviewType = (typeof REVIEW_TYPES)[number]["value"];
+interface FeedbackData {
+    isPositive: boolean;
+    reviewType?: ReviewType;
+    reviewText?: string;
+}
+/**
+ * Render-prop state passed to `renderActions`, letting consumers build
+ * a fully custom action row while keeping all behaviour (submit, copy,
+ * analytics) intact.
+ */
+interface MessageFeedbackActionsState {
+    /** Current feedback selection (if any) */
+    feedback: "positive" | "negative" | null;
+    /** True while a feedback submit is in-flight */
+    isSubmitting: boolean;
+    /** True briefly after the copy button is used */
+    copied: boolean;
+    /** Submit positive feedback and fire analytics */
+    onPositive: () => void;
+    /** Submit negative feedback — opens the review form */
+    onNegative: () => void;
+    /** Copy the assistant's text content to clipboard */
+    onCopy: () => void;
+}
+interface MessageFeedbackProps {
+    messageId: string;
+    projectId: string;
+    sessionId?: string;
+    apiKey?: string;
+    apiEndpoint?: string;
+    textContent: string;
+    trackInteraction?: (params: TrackInteractionParams) => void;
+    /** Optional className merged onto the root wrapper. */
+    className?: string;
+    /**
+     * When true, strip the default Tailwind bubble styling and only render
+     * the semantic structure. Ideal if you want to style from scratch with
+     * your own design system.
+     */
+    unstyled?: boolean;
+    /**
+     * Per-element className overrides. Merged with defaults via `cn()` so
+     * Tailwind utilities can override (e.g. `bg-red-500`).
+     */
+    classNames?: {
+        root?: string;
+        actions?: string;
+        thumbsUp?: string;
+        thumbsDown?: string;
+        copy?: string;
+        reviewForm?: string;
+    };
+    /**
+     * Full override of the action button row. Receives the submit handlers
+     * + current state. Return any ReactNode. The built-in review form still
+     * appears below when the user clicks thumbs-down (unless you handle
+     * `onNegative` yourself and never trigger it).
+     *
+     * @example
+     * ```tsx
+     * renderActions={({ onPositive, onNegative, onCopy }) => (
+     *   <div className="my-custom-row">
+     *     <MyButton onClick={onPositive}>👍</MyButton>
+     *     <MyButton onClick={onNegative}>👎</MyButton>
+     *     <MyButton onClick={onCopy}>Copy</MyButton>
+     *   </div>
+     * )}
+     * ```
+     */
+    renderActions?: (state: MessageFeedbackActionsState) => ReactNode;
+}
+declare function MessageFeedback({ messageId, projectId, sessionId, apiKey, apiEndpoint, textContent, trackInteraction, className, unstyled, classNames, renderActions, }: MessageFeedbackProps): react_jsx_runtime.JSX.Element;
+
+export { type FeedbackData as F, type MessageFeedbackActionsState as M, MessageFeedback as a };

package/dist/normalize-KzCLLqpU.d.cts

@@ -0,0 +1,42 @@
+/**
+ * Tool result normalization helpers.
+ *
+ * Tools (especially `data_store`) can return data in a handful of shapes:
+ *
+ *   1. Projected flat rows (default `rows_only` mode):
+ *      `[{ name: "alice", city: "haifa" }, ...]`
+ *
+ *   2. Full-format wrapper (`responseMode: "full"`):
+ *      `{ storeName, columns, rows: [...], totalMatches, returned }`
+ *
+ *   3. Raw DB rows (from custom_execute that echoes the DB layer):
+ *      `[{ id, dataStoreId, data: { name, city }, sortOrder }]`
+ *
+ * Custom renderers that want to work with any of these shapes can use
+ * `normalizeToolRows()` to get a consistent `Array<Record<string, unknown>>`
+ * regardless of upstream shape.
+ */
+/**
+ * Normalize a tool result (or `result.data`) into a flat array of row
+ * objects, regardless of which shape the backend returned.
+ *
+ * @example
+ * ```tsx
+ * function MyRenderer({ result }: ToolRendererProps) {
+ *   const rows = normalizeToolRows(result?.data);
+ *   return <Table rows={rows} />;
+ * }
+ * ```
+ */
+declare function normalizeToolRows(input: unknown): Array<Record<string, unknown>>;
+/**
+ * Extract the display payload from a tool result, preferring `_displayData`
+ * over `data` (matches the ToolRenderer resolution). Useful when you're
+ * rendering from outside the built-in dispatcher.
+ */
+declare function getToolDisplayData(result: {
+    data?: unknown;
+    _displayData?: unknown;
+} | undefined): unknown;
+
+export { getToolDisplayData as g, normalizeToolRows as n };

package/dist/normalize-KzCLLqpU.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Tool result normalization helpers.
+ *
+ * Tools (especially `data_store`) can return data in a handful of shapes:
+ *
+ *   1. Projected flat rows (default `rows_only` mode):
+ *      `[{ name: "alice", city: "haifa" }, ...]`
+ *
+ *   2. Full-format wrapper (`responseMode: "full"`):
+ *      `{ storeName, columns, rows: [...], totalMatches, returned }`
+ *
+ *   3. Raw DB rows (from custom_execute that echoes the DB layer):
+ *      `[{ id, dataStoreId, data: { name, city }, sortOrder }]`
+ *
+ * Custom renderers that want to work with any of these shapes can use
+ * `normalizeToolRows()` to get a consistent `Array<Record<string, unknown>>`
+ * regardless of upstream shape.
+ */
+/**
+ * Normalize a tool result (or `result.data`) into a flat array of row
+ * objects, regardless of which shape the backend returned.
+ *
+ * @example
+ * ```tsx
+ * function MyRenderer({ result }: ToolRendererProps) {
+ *   const rows = normalizeToolRows(result?.data);
+ *   return <Table rows={rows} />;
+ * }
+ * ```
+ */
+declare function normalizeToolRows(input: unknown): Array<Record<string, unknown>>;
+/**
+ * Extract the display payload from a tool result, preferring `_displayData`
+ * over `data` (matches the ToolRenderer resolution). Useful when you're
+ * rendering from outside the built-in dispatcher.
+ */
+declare function getToolDisplayData(result: {
+    data?: unknown;
+    _displayData?: unknown;
+} | undefined): unknown;
+
+export { getToolDisplayData as g, normalizeToolRows as n };