@retrivora-ai/rag-engine 1.6.7 → 1.6.8

package/dist/{chunk-5K7EU4KW.mjs → chunk-J7BCIPO2.mjs}

@@ -2259,7 +2259,7 @@ var Pipeline = class {
   async initialize() {
     var _a, _b;
     if (this.initialised) return;
-    const CHART_MARKER = "<!-- UI_PROTOCOL_V5 -->";
+    const CHART_MARKER = "<!-- UI_PROTOCOL_V6 -->";
     const chartInstruction = `
 
 ${CHART_MARKER}
@@ -2267,16 +2267,16 @@ ${CHART_MARKER}
 When the user asks for a visual representation, comparison, distribution, breakdown, table, list, catalog, products, carousel, stock view, or category summary, you MUST include exactly one \`\`\`ui\`\`\` block.
 
 1. VIEW SELECTION
-   - Use "chart" for distributions, percentages, counts, comparisons, trends, or "show me in a chart".
-   - Use "carousel" for browseable product recommendations or when the user asks to see products/items/cards.
-   - Use "table" for tabular/raw detail, explicit table/list requests, or when there are many attributes to compare.
+   - Use "carousel" for browsing specific products, items, or a catalog. This is the DEFAULT for "show me", "what are", or "find me" requests for a specific category (e.g. "beauty").
+   - Use "chart" ONLY for numerical aggregations: distributions, percentages, counts, comparisons over time, or trends (e.g. "how many beauty products?").
+   - Use "table" for detailed technical specifications, row-heavy comparisons, or when the user explicitly asks for a list/table format.
 
 2. REQUIRED JSON SHAPE
    {
      "view": "chart" | "carousel" | "table",
      "title": "Short heading",
      "description": "One sentence describing the view",
-     "chartType": "pie" | "bar" | "line",
+     "chartType": "pie" | "bar" | "line", // Required if view is "chart"
      "xAxisKey": "label",
      "dataKeys": ["value"],
      "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
@@ -2285,41 +2285,42 @@ When the user asks for a visual representation, comparison, distribution, breakd
    }
 
 3. DATA RULES
-   - Build the UI payload from retrieved context only. Do not invent products, categories, or stock values.
-   - Aggregate raw product rows when the user asks for a chart.
-   - For charts, every row in "data" must be flat JSON with primitive values only.
-   - Prefer { "label": "...", "value": number } for pie charts.
-   - If stock information exists, preserve it in each row with fields like "inStock", "inStockCount", "outOfStockCount", or "stockStatus".
-   - If the user asks to highlight what is in stock, include those stock-related fields in the chart data and mention the pattern in "insights".
-   - For carousel rows, include product-friendly fields such as id, name, brand, price, image, link, category, stockStatus.
-   - For tables, keep "data" row-oriented and include "columns" only as dynamic field keys/order hints from the fetched data, never as hardcoded UI labels.
+   - Build the UI payload from retrieved context only. Do not invent products or values.
+   - For CAROUSEL: "data" must be a list of product objects (id, name, brand, price, image, link).
+   - For CHART: "data" must be aggregated counts or sums. Never put raw product lists in a chart view.
+   - If the user asks for "products in beauty", do NOT return a pie chart of categories; return a carousel of the beauty products themselves.
 
 4. FORMAT RULES
-   - Never use ASCII art, markdown tables as the primary answer, or text-only fake charts when a UI block is requested.
-   - Put any short natural-language explanation before or after the \`\`\`ui\`\`\` block, but keep it concise.
    - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - If the user explicitly asks for a pie chart, return "view": "chart" with "chartType": "pie", not a table fallback.
-   - Do not prefix the JSON with labels like "Table View", "Alternative", or explanatory text inside the code block.
+   - Put natural language explanation before or after the block, not inside.
 
-5. EXAMPLE
-User: "provide me the distribution of products across categories and highlight which ones are in stock in a pie chart"
+5. EXAMPLES
+User: "show me beauty products"
+Assistant:
+\`\`\`ui
+{
+  "view": "carousel",
+  "title": "Beauty Products",
+  "description": "Browse our latest skincare and makeup collection.",
+  "data": [
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
+    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+  ]
+}
+\`\`\`
+
+User: "breakdown of products by category"
 Assistant:
 \`\`\`ui
 {
   "view": "chart",
-  "title": "Product Distribution Across Categories",
-  "description": "Pie chart showing product count by category with stock signals preserved per slice.",
+  "title": "Category Breakdown",
   "chartType": "pie",
   "xAxisKey": "label",
   "dataKeys": ["value"],
-  "insights": [
-    "Beauty has the highest product count.",
-    "Electronics has the largest number of in-stock products."
-  ],
   "data": [
-    { "label": "Beauty", "value": 12, "inStockCount": 9, "outOfStockCount": 3 },
-    { "label": "Electronics", "value": 8, "inStockCount": 7, "outOfStockCount": 1 },
-    { "label": "Home", "value": 5, "inStockCount": 2, "outOfStockCount": 3 }
+    { "label": "Beauty", "value": 15 },
+    { "label": "Fragrances", "value": 8 }
   ]
 }
 \`\`\``;

package/dist/handlers/index.js

@@ -3822,7 +3822,7 @@ var Pipeline = class {
   async initialize() {
     var _a, _b;
     if (this.initialised) return;
-    const CHART_MARKER = "<!-- UI_PROTOCOL_V5 -->";
+    const CHART_MARKER = "<!-- UI_PROTOCOL_V6 -->";
     const chartInstruction = `
 
 ${CHART_MARKER}
@@ -3830,16 +3830,16 @@ ${CHART_MARKER}
 When the user asks for a visual representation, comparison, distribution, breakdown, table, list, catalog, products, carousel, stock view, or category summary, you MUST include exactly one \`\`\`ui\`\`\` block.
 
 1. VIEW SELECTION
-   - Use "chart" for distributions, percentages, counts, comparisons, trends, or "show me in a chart".
-   - Use "carousel" for browseable product recommendations or when the user asks to see products/items/cards.
-   - Use "table" for tabular/raw detail, explicit table/list requests, or when there are many attributes to compare.
+   - Use "carousel" for browsing specific products, items, or a catalog. This is the DEFAULT for "show me", "what are", or "find me" requests for a specific category (e.g. "beauty").
+   - Use "chart" ONLY for numerical aggregations: distributions, percentages, counts, comparisons over time, or trends (e.g. "how many beauty products?").
+   - Use "table" for detailed technical specifications, row-heavy comparisons, or when the user explicitly asks for a list/table format.
 
 2. REQUIRED JSON SHAPE
    {
      "view": "chart" | "carousel" | "table",
      "title": "Short heading",
      "description": "One sentence describing the view",
-     "chartType": "pie" | "bar" | "line",
+     "chartType": "pie" | "bar" | "line", // Required if view is "chart"
      "xAxisKey": "label",
      "dataKeys": ["value"],
      "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
@@ -3848,41 +3848,42 @@ When the user asks for a visual representation, comparison, distribution, breakd
    }
 
 3. DATA RULES
-   - Build the UI payload from retrieved context only. Do not invent products, categories, or stock values.
-   - Aggregate raw product rows when the user asks for a chart.
-   - For charts, every row in "data" must be flat JSON with primitive values only.
-   - Prefer { "label": "...", "value": number } for pie charts.
-   - If stock information exists, preserve it in each row with fields like "inStock", "inStockCount", "outOfStockCount", or "stockStatus".
-   - If the user asks to highlight what is in stock, include those stock-related fields in the chart data and mention the pattern in "insights".
-   - For carousel rows, include product-friendly fields such as id, name, brand, price, image, link, category, stockStatus.
-   - For tables, keep "data" row-oriented and include "columns" only as dynamic field keys/order hints from the fetched data, never as hardcoded UI labels.
+   - Build the UI payload from retrieved context only. Do not invent products or values.
+   - For CAROUSEL: "data" must be a list of product objects (id, name, brand, price, image, link).
+   - For CHART: "data" must be aggregated counts or sums. Never put raw product lists in a chart view.
+   - If the user asks for "products in beauty", do NOT return a pie chart of categories; return a carousel of the beauty products themselves.
 
 4. FORMAT RULES
-   - Never use ASCII art, markdown tables as the primary answer, or text-only fake charts when a UI block is requested.
-   - Put any short natural-language explanation before or after the \`\`\`ui\`\`\` block, but keep it concise.
    - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - If the user explicitly asks for a pie chart, return "view": "chart" with "chartType": "pie", not a table fallback.
-   - Do not prefix the JSON with labels like "Table View", "Alternative", or explanatory text inside the code block.
+   - Put natural language explanation before or after the block, not inside.
 
-5. EXAMPLE
-User: "provide me the distribution of products across categories and highlight which ones are in stock in a pie chart"
+5. EXAMPLES
+User: "show me beauty products"
+Assistant:
+\`\`\`ui
+{
+  "view": "carousel",
+  "title": "Beauty Products",
+  "description": "Browse our latest skincare and makeup collection.",
+  "data": [
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
+    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+  ]
+}
+\`\`\`
+
+User: "breakdown of products by category"
 Assistant:
 \`\`\`ui
 {
   "view": "chart",
-  "title": "Product Distribution Across Categories",
-  "description": "Pie chart showing product count by category with stock signals preserved per slice.",
+  "title": "Category Breakdown",
   "chartType": "pie",
   "xAxisKey": "label",
   "dataKeys": ["value"],
-  "insights": [
-    "Beauty has the highest product count.",
-    "Electronics has the largest number of in-stock products."
-  ],
   "data": [
-    { "label": "Beauty", "value": 12, "inStockCount": 9, "outOfStockCount": 3 },
-    { "label": "Electronics", "value": 8, "inStockCount": 7, "outOfStockCount": 1 },
-    { "label": "Home", "value": 5, "inStockCount": 2, "outOfStockCount": 3 }
+    { "label": "Beauty", "value": 15 },
+    { "label": "Fragrances", "value": 8 }
   ]
 }
 \`\`\``;

package/dist/handlers/index.mjs

@@ -9,7 +9,7 @@ import {
   sseFrame,
   sseMetaFrame,
   sseTextFrame
-} from "../chunk-5K7EU4KW.mjs";
+} from "../chunk-J7BCIPO2.mjs";
 import "../chunk-YLTMFW4M.mjs";
 import "../chunk-X4TOT24V.mjs";
 export {

package/dist/index.js

@@ -651,23 +651,25 @@ function UIDispatcher({ rawContent, primaryColor, accentColor, isStreaming, onAd
       const clean = rawContent.replace(/^```[a-z]*\s*/i, "").replace(/```\s*$/, "").trim();
       const parsed = JSON.parse(sanitizeJson(extractLikelyJsonBlock(clean)));
       const config2 = __spreadValues({}, parsed);
+      const resolvedRows = resolveStructuredRows(config2);
+      const hasProductLikeData = resolvedRows.length > 0 && typeof resolvedRows[0] === "object" && resolvedRows[0] !== null && !Array.isArray(resolvedRows[0]) && (["price", "brand", "image", "link", "thumbnail"].some((key) => key in resolvedRows[0]) || Object.keys(resolvedRows[0]).length >= 4);
+      const hasAggregationLikeData = resolvedRows.length > 0 && typeof resolvedRows[0] === "object" && resolvedRows[0] !== null && !Array.isArray(resolvedRows[0]) && (["value", "count", "total", "percentage"].some((key) => key in resolvedRows[0]) || Object.keys(resolvedRows[0]).length <= 3 && Object.values(resolvedRows[0]).some((v) => typeof v === "number"));
+      if (config2.view === "chart" && hasProductLikeData && !hasAggregationLikeData) {
+        config2.view = "carousel";
+      } else if (config2.view === "carousel" && hasAggregationLikeData && !hasProductLikeData) {
+        config2.view = "chart";
+        config2.chartType = config2.chartType || "bar";
+      }
       if (!config2.view) {
-        const resolvedRows2 = resolveStructuredRows(config2);
-        const hasProductLikeData = resolvedRows2.length > 0 && typeof resolvedRows2[0] === "object" && resolvedRows2[0] !== null && ("price" in resolvedRows2[0] || "brand" in resolvedRows2[0] || "image" in resolvedRows2[0]);
-        if (config2.type === "products" || Array.isArray(config2.items) || Array.isArray(config2.data) && hasProductLikeData) {
+        if (config2.type === "products" || Array.isArray(config2.items) || hasProductLikeData) {
           config2.view = "carousel";
-          config2.data = resolvedRows2;
-        } else if (typeof config2.type === "string" && ["pie", "bar", "line"].includes(config2.type) || typeof config2.chartType === "string" && ["pie", "bar", "line"].includes(config2.chartType)) {
-          const resolvedChartType = config2.chartType === "pie" || config2.chartType === "bar" || config2.chartType === "line" ? config2.chartType : config2.type === "pie" || config2.type === "bar" || config2.type === "line" ? config2.type : "bar";
+        } else if (hasAggregationLikeData || typeof config2.type === "string" && ["pie", "bar", "line"].includes(config2.type) || typeof config2.chartType === "string" && ["pie", "bar", "line"].includes(config2.chartType)) {
           config2.view = "chart";
-          config2.chartType = resolvedChartType;
-          config2.data = resolvedRows2;
+          config2.chartType = config2.chartType || config2.type || "bar";
         } else {
           config2.view = "table";
-          config2.data = Array.isArray(config2.data) ? config2.data : Array.isArray(config2) ? config2 : [];
         }
       }
-      const resolvedRows = resolveStructuredRows(config2);
       const normalizedConfig = __spreadProps(__spreadValues({}, config2), {
         data: normalizeTabularRows(resolvedRows, config2.columns)
       });

package/dist/index.mjs

@@ -614,23 +614,25 @@ function UIDispatcher({ rawContent, primaryColor, accentColor, isStreaming, onAd
       const clean = rawContent.replace(/^```[a-z]*\s*/i, "").replace(/```\s*$/, "").trim();
       const parsed = JSON.parse(sanitizeJson(extractLikelyJsonBlock(clean)));
       const config2 = __spreadValues({}, parsed);
+      const resolvedRows = resolveStructuredRows(config2);
+      const hasProductLikeData = resolvedRows.length > 0 && typeof resolvedRows[0] === "object" && resolvedRows[0] !== null && !Array.isArray(resolvedRows[0]) && (["price", "brand", "image", "link", "thumbnail"].some((key) => key in resolvedRows[0]) || Object.keys(resolvedRows[0]).length >= 4);
+      const hasAggregationLikeData = resolvedRows.length > 0 && typeof resolvedRows[0] === "object" && resolvedRows[0] !== null && !Array.isArray(resolvedRows[0]) && (["value", "count", "total", "percentage"].some((key) => key in resolvedRows[0]) || Object.keys(resolvedRows[0]).length <= 3 && Object.values(resolvedRows[0]).some((v) => typeof v === "number"));
+      if (config2.view === "chart" && hasProductLikeData && !hasAggregationLikeData) {
+        config2.view = "carousel";
+      } else if (config2.view === "carousel" && hasAggregationLikeData && !hasProductLikeData) {
+        config2.view = "chart";
+        config2.chartType = config2.chartType || "bar";
+      }
       if (!config2.view) {
-        const resolvedRows2 = resolveStructuredRows(config2);
-        const hasProductLikeData = resolvedRows2.length > 0 && typeof resolvedRows2[0] === "object" && resolvedRows2[0] !== null && ("price" in resolvedRows2[0] || "brand" in resolvedRows2[0] || "image" in resolvedRows2[0]);
-        if (config2.type === "products" || Array.isArray(config2.items) || Array.isArray(config2.data) && hasProductLikeData) {
+        if (config2.type === "products" || Array.isArray(config2.items) || hasProductLikeData) {
           config2.view = "carousel";
-          config2.data = resolvedRows2;
-        } else if (typeof config2.type === "string" && ["pie", "bar", "line"].includes(config2.type) || typeof config2.chartType === "string" && ["pie", "bar", "line"].includes(config2.chartType)) {
-          const resolvedChartType = config2.chartType === "pie" || config2.chartType === "bar" || config2.chartType === "line" ? config2.chartType : config2.type === "pie" || config2.type === "bar" || config2.type === "line" ? config2.type : "bar";
+        } else if (hasAggregationLikeData || typeof config2.type === "string" && ["pie", "bar", "line"].includes(config2.type) || typeof config2.chartType === "string" && ["pie", "bar", "line"].includes(config2.chartType)) {
           config2.view = "chart";
-          config2.chartType = resolvedChartType;
-          config2.data = resolvedRows2;
+          config2.chartType = config2.chartType || config2.type || "bar";
         } else {
           config2.view = "table";
-          config2.data = Array.isArray(config2.data) ? config2.data : Array.isArray(config2) ? config2 : [];
         }
       }
-      const resolvedRows = resolveStructuredRows(config2);
       const normalizedConfig = __spreadProps(__spreadValues({}, config2), {
         data: normalizeTabularRows(resolvedRows, config2.columns)
       });

package/dist/server.js

@@ -3913,7 +3913,7 @@ var Pipeline = class {
   async initialize() {
     var _a, _b;
     if (this.initialised) return;
-    const CHART_MARKER = "<!-- UI_PROTOCOL_V5 -->";
+    const CHART_MARKER = "<!-- UI_PROTOCOL_V6 -->";
     const chartInstruction = `
 
 ${CHART_MARKER}
@@ -3921,16 +3921,16 @@ ${CHART_MARKER}
 When the user asks for a visual representation, comparison, distribution, breakdown, table, list, catalog, products, carousel, stock view, or category summary, you MUST include exactly one \`\`\`ui\`\`\` block.
 
 1. VIEW SELECTION
-   - Use "chart" for distributions, percentages, counts, comparisons, trends, or "show me in a chart".
-   - Use "carousel" for browseable product recommendations or when the user asks to see products/items/cards.
-   - Use "table" for tabular/raw detail, explicit table/list requests, or when there are many attributes to compare.
+   - Use "carousel" for browsing specific products, items, or a catalog. This is the DEFAULT for "show me", "what are", or "find me" requests for a specific category (e.g. "beauty").
+   - Use "chart" ONLY for numerical aggregations: distributions, percentages, counts, comparisons over time, or trends (e.g. "how many beauty products?").
+   - Use "table" for detailed technical specifications, row-heavy comparisons, or when the user explicitly asks for a list/table format.
 
 2. REQUIRED JSON SHAPE
    {
      "view": "chart" | "carousel" | "table",
      "title": "Short heading",
      "description": "One sentence describing the view",
-     "chartType": "pie" | "bar" | "line",
+     "chartType": "pie" | "bar" | "line", // Required if view is "chart"
      "xAxisKey": "label",
      "dataKeys": ["value"],
      "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
@@ -3939,41 +3939,42 @@ When the user asks for a visual representation, comparison, distribution, breakd
    }
 
 3. DATA RULES
-   - Build the UI payload from retrieved context only. Do not invent products, categories, or stock values.
-   - Aggregate raw product rows when the user asks for a chart.
-   - For charts, every row in "data" must be flat JSON with primitive values only.
-   - Prefer { "label": "...", "value": number } for pie charts.
-   - If stock information exists, preserve it in each row with fields like "inStock", "inStockCount", "outOfStockCount", or "stockStatus".
-   - If the user asks to highlight what is in stock, include those stock-related fields in the chart data and mention the pattern in "insights".
-   - For carousel rows, include product-friendly fields such as id, name, brand, price, image, link, category, stockStatus.
-   - For tables, keep "data" row-oriented and include "columns" only as dynamic field keys/order hints from the fetched data, never as hardcoded UI labels.
+   - Build the UI payload from retrieved context only. Do not invent products or values.
+   - For CAROUSEL: "data" must be a list of product objects (id, name, brand, price, image, link).
+   - For CHART: "data" must be aggregated counts or sums. Never put raw product lists in a chart view.
+   - If the user asks for "products in beauty", do NOT return a pie chart of categories; return a carousel of the beauty products themselves.
 
 4. FORMAT RULES
-   - Never use ASCII art, markdown tables as the primary answer, or text-only fake charts when a UI block is requested.
-   - Put any short natural-language explanation before or after the \`\`\`ui\`\`\` block, but keep it concise.
    - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - If the user explicitly asks for a pie chart, return "view": "chart" with "chartType": "pie", not a table fallback.
-   - Do not prefix the JSON with labels like "Table View", "Alternative", or explanatory text inside the code block.
+   - Put natural language explanation before or after the block, not inside.
 
-5. EXAMPLE
-User: "provide me the distribution of products across categories and highlight which ones are in stock in a pie chart"
+5. EXAMPLES
+User: "show me beauty products"
+Assistant:
+\`\`\`ui
+{
+  "view": "carousel",
+  "title": "Beauty Products",
+  "description": "Browse our latest skincare and makeup collection.",
+  "data": [
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
+    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+  ]
+}
+\`\`\`
+
+User: "breakdown of products by category"
 Assistant:
 \`\`\`ui
 {
   "view": "chart",
-  "title": "Product Distribution Across Categories",
-  "description": "Pie chart showing product count by category with stock signals preserved per slice.",
+  "title": "Category Breakdown",
   "chartType": "pie",
   "xAxisKey": "label",
   "dataKeys": ["value"],
-  "insights": [
-    "Beauty has the highest product count.",
-    "Electronics has the largest number of in-stock products."
-  ],
   "data": [
-    { "label": "Beauty", "value": 12, "inStockCount": 9, "outOfStockCount": 3 },
-    { "label": "Electronics", "value": 8, "inStockCount": 7, "outOfStockCount": 1 },
-    { "label": "Home", "value": 5, "inStockCount": 2, "outOfStockCount": 3 }
+    { "label": "Beauty", "value": 15 },
+    { "label": "Fragrances", "value": 8 }
   ]
 }
 \`\`\``;

package/dist/server.mjs

@@ -39,7 +39,7 @@ import {
   sseFrame,
   sseMetaFrame,
   sseTextFrame
-} from "./chunk-5K7EU4KW.mjs";
+} from "./chunk-J7BCIPO2.mjs";
 import "./chunk-YLTMFW4M.mjs";
 import {
   PineconeProvider

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@retrivora-ai/rag-engine",
-  "version": "1.6.7",
+  "version": "1.6.8",
   "description": "Retrivora AI is a plug-and-play AI engine for RAG chat experiences — generic vector DB + LLM provider, embeddable or standalone.",
   "author": "Abhinav Alkuchi",
   "license": "MIT",

package/src/components/MessageBubble.tsx

@@ -442,36 +442,47 @@ function UIDispatcher({ rawContent, primaryColor, accentColor, isStreaming, onAd
         .trim();
       const parsed = JSON.parse(sanitizeJson(extractLikelyJsonBlock(clean)));
       const config = { ...parsed } as Partial<RawUIConfig> & Record<string, unknown>;
+      const resolvedRows = resolveStructuredRows(config);
 
-      // Smart Auto-Detection for legacy or simpler formats
-      if (!config.view) {
-        const resolvedRows = resolveStructuredRows(config);
-        const hasProductLikeData = resolvedRows.length > 0 && typeof resolvedRows[0] === 'object' && resolvedRows[0] !== null && 
-          ('price' in resolvedRows[0] || 'brand' in resolvedRows[0] || 'image' in resolvedRows[0]);
+      // ─── Intent Healing & Auto-Detection ───────────────────────────────────
+      
+      const hasProductLikeData = resolvedRows.length > 0 && 
+        typeof resolvedRows[0] === 'object' && resolvedRows[0] !== null && 
+        !Array.isArray(resolvedRows[0]) &&
+        (['price', 'brand', 'image', 'link', 'thumbnail'].some(key => key in resolvedRows[0]) || 
+         Object.keys(resolvedRows[0]).length >= 4);
+
+      const hasAggregationLikeData = resolvedRows.length > 0 && 
+        typeof resolvedRows[0] === 'object' && resolvedRows[0] !== null && 
+        !Array.isArray(resolvedRows[0]) &&
+        (['value', 'count', 'total', 'percentage'].some(key => key in resolvedRows[0]) || 
+         (Object.keys(resolvedRows[0]).length <= 3 && Object.values(resolvedRows[0]).some(v => typeof v === 'number')));
+
+      // 1. Healing: Override explicit view if it contradicts the data shape
+      if (config.view === 'chart' && hasProductLikeData && !hasAggregationLikeData) {
+        config.view = 'carousel';
+      } else if (config.view === 'carousel' && hasAggregationLikeData && !hasProductLikeData) {
+        config.view = 'chart';
+        config.chartType = (config.chartType as 'pie' | 'bar' | 'line') || 'bar';
+      }
 
-        if (config.type === 'products' || Array.isArray(config.items) || (Array.isArray(config.data) && hasProductLikeData)) {
+      // 2. Auto-Detection: Fill in missing view
+      if (!config.view) {
+        if (config.type === 'products' || Array.isArray(config.items) || hasProductLikeData) {
           config.view = 'carousel';
-          config.data = resolvedRows;
         } else if (
+          hasAggregationLikeData ||
           (typeof config.type === 'string' && ['pie', 'bar', 'line'].includes(config.type)) ||
           (typeof config.chartType === 'string' && ['pie', 'bar', 'line'].includes(config.chartType))
         ) {
-          const resolvedChartType =
-            config.chartType === 'pie' || config.chartType === 'bar' || config.chartType === 'line'
-              ? config.chartType
-              : config.type === 'pie' || config.type === 'bar' || config.type === 'line'
-                ? config.type
-                : 'bar';
           config.view = 'chart';
-          config.chartType = resolvedChartType;
-          config.data = resolvedRows;
+          config.chartType = (config.chartType as 'pie' | 'bar' | 'line') || 
+                             (config.type as 'pie' | 'bar' | 'line') || 'bar';
         } else {
           config.view = 'table';
-          config.data = Array.isArray(config.data) ? config.data : (Array.isArray(config) ? config : []);
         }
       }
 
-      const resolvedRows = resolveStructuredRows(config);
       const normalizedConfig: UIConfig = {
         ...(config as Omit<UIConfig, 'data'>),
         data: normalizeTabularRows(resolvedRows, config.columns),

package/src/core/Pipeline.ts

@@ -101,22 +101,22 @@ export class Pipeline {
 
     // Augment system prompt with a Universal Visualization Protocol
     // We use a unique marker to ensure this is only injected once but is ALWAYS present.
-    const CHART_MARKER = '<!-- UI_PROTOCOL_V5 -->';
+    const CHART_MARKER = '<!-- UI_PROTOCOL_V6 -->';
     const chartInstruction = `\n\n${CHART_MARKER}
 ### UNIVERSAL UI PROTOCOL
 When the user asks for a visual representation, comparison, distribution, breakdown, table, list, catalog, products, carousel, stock view, or category summary, you MUST include exactly one \`\`\`ui\`\`\` block.
 
 1. VIEW SELECTION
-   - Use "chart" for distributions, percentages, counts, comparisons, trends, or "show me in a chart".
-   - Use "carousel" for browseable product recommendations or when the user asks to see products/items/cards.
-   - Use "table" for tabular/raw detail, explicit table/list requests, or when there are many attributes to compare.
+   - Use "carousel" for browsing specific products, items, or a catalog. This is the DEFAULT for "show me", "what are", or "find me" requests for a specific category (e.g. "beauty").
+   - Use "chart" ONLY for numerical aggregations: distributions, percentages, counts, comparisons over time, or trends (e.g. "how many beauty products?").
+   - Use "table" for detailed technical specifications, row-heavy comparisons, or when the user explicitly asks for a list/table format.
 
 2. REQUIRED JSON SHAPE
    {
      "view": "chart" | "carousel" | "table",
      "title": "Short heading",
      "description": "One sentence describing the view",
-     "chartType": "pie" | "bar" | "line",
+     "chartType": "pie" | "bar" | "line", // Required if view is "chart"
      "xAxisKey": "label",
      "dataKeys": ["value"],
      "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
@@ -125,41 +125,42 @@ When the user asks for a visual representation, comparison, distribution, breakd
    }
 
 3. DATA RULES
-   - Build the UI payload from retrieved context only. Do not invent products, categories, or stock values.
-   - Aggregate raw product rows when the user asks for a chart.
-   - For charts, every row in "data" must be flat JSON with primitive values only.
-   - Prefer { "label": "...", "value": number } for pie charts.
-   - If stock information exists, preserve it in each row with fields like "inStock", "inStockCount", "outOfStockCount", or "stockStatus".
-   - If the user asks to highlight what is in stock, include those stock-related fields in the chart data and mention the pattern in "insights".
-   - For carousel rows, include product-friendly fields such as id, name, brand, price, image, link, category, stockStatus.
-   - For tables, keep "data" row-oriented and include "columns" only as dynamic field keys/order hints from the fetched data, never as hardcoded UI labels.
+   - Build the UI payload from retrieved context only. Do not invent products or values.
+   - For CAROUSEL: "data" must be a list of product objects (id, name, brand, price, image, link).
+   - For CHART: "data" must be aggregated counts or sums. Never put raw product lists in a chart view.
+   - If the user asks for "products in beauty", do NOT return a pie chart of categories; return a carousel of the beauty products themselves.
 
 4. FORMAT RULES
-   - Never use ASCII art, markdown tables as the primary answer, or text-only fake charts when a UI block is requested.
-   - Put any short natural-language explanation before or after the \`\`\`ui\`\`\` block, but keep it concise.
    - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - If the user explicitly asks for a pie chart, return "view": "chart" with "chartType": "pie", not a table fallback.
-   - Do not prefix the JSON with labels like "Table View", "Alternative", or explanatory text inside the code block.
+   - Put natural language explanation before or after the block, not inside.
 
-5. EXAMPLE
-User: "provide me the distribution of products across categories and highlight which ones are in stock in a pie chart"
+5. EXAMPLES
+User: "show me beauty products"
+Assistant:
+\`\`\`ui
+{
+  "view": "carousel",
+  "title": "Beauty Products",
+  "description": "Browse our latest skincare and makeup collection.",
+  "data": [
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
+    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+  ]
+}
+\`\`\`
+
+User: "breakdown of products by category"
 Assistant:
 \`\`\`ui
 {
   "view": "chart",
-  "title": "Product Distribution Across Categories",
-  "description": "Pie chart showing product count by category with stock signals preserved per slice.",
+  "title": "Category Breakdown",
   "chartType": "pie",
   "xAxisKey": "label",
   "dataKeys": ["value"],
-  "insights": [
-    "Beauty has the highest product count.",
-    "Electronics has the largest number of in-stock products."
-  ],
   "data": [
-    { "label": "Beauty", "value": 12, "inStockCount": 9, "outOfStockCount": 3 },
-    { "label": "Electronics", "value": 8, "inStockCount": 7, "outOfStockCount": 1 },
-    { "label": "Home", "value": 5, "inStockCount": 2, "outOfStockCount": 3 }
+    { "label": "Beauty", "value": 15 },
+    { "label": "Fragrances", "value": 8 }
   ]
 }
 \`\`\``;