@retrivora-ai/rag-engine 1.6.8 → 1.6.9

package/dist/{chunk-J7BCIPO2.mjs → chunk-Q7FLITXB.mjs}

@@ -2259,17 +2259,18 @@ var Pipeline = class {
   async initialize() {
     var _a, _b;
     if (this.initialised) return;
-    const CHART_MARKER = "<!-- UI_PROTOCOL_V6 -->";
+    const CHART_MARKER = "<!-- UI_PROTOCOL_V7 -->";
     const chartInstruction = `
 
 ${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.
+### UNIVERSAL UI PROTOCOL (MANDATORY)
+CRITICAL: When providing visual data (carousels, charts, tables), you MUST wrap the JSON payload in a \`\`\`ui\`\`\` code block. 
+NEVER output naked JSON. If you provide a visualization, do not also provide a markdown table of the same data unless explicitly asked.
 
 1. VIEW SELECTION
-   - 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.
+   - Use "carousel" for browsing products, items, or catalogs. (e.g., "show me beauty products").
+   - Use "chart" ONLY for numerical aggregations (counts, sums, percentages).
+   - Use "table" for technical specs or row-heavy comparisons.
 
 2. REQUIRED JSON SHAPE
    {
@@ -2277,52 +2278,31 @@ When the user asks for a visual representation, comparison, distribution, breakd
      "title": "Short heading",
      "description": "One sentence describing the view",
      "chartType": "pie" | "bar" | "line", // Required if view is "chart"
-     "xAxisKey": "label",
-     "dataKeys": ["value"],
-     "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
-     "insights": ["Short takeaway 1", "Short takeaway 2"],
-     "data": []
+     "data": [] // Array of objects
    }
 
 3. DATA RULES
-   - 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.
+   - Build the UI payload from retrieved context only.
+   - For CAROUSEL: "data" items MUST have { id, name, brand, price, image, link }.
+   - For CHART: "data" items MUST have { label, value }.
 
 4. FORMAT RULES
-   - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - Put natural language explanation before or after the block, not inside.
+   - Wrap the JSON in \`\`\`ui ... \`\`\` blocks.
+   - Place natural language text OUTSIDE the block.
 
-5. EXAMPLES
-User: "show me beauty products"
-Assistant:
+5. EXAMPLE
+User: "find me beauty products"
+Assistant: "I found several beauty products in our catalog:"
 \`\`\`ui
 {
   "view": "carousel",
   "title": "Beauty Products",
-  "description": "Browse our latest skincare and makeup collection.",
+  "description": "Latest skincare and makeup items.",
   "data": [
-    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
-    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." }
   ]
 }
 \`\`\`
-
-User: "breakdown of products by category"
-Assistant:
-\`\`\`ui
-{
-  "view": "chart",
-  "title": "Category Breakdown",
-  "chartType": "pie",
-  "xAxisKey": "label",
-  "dataKeys": ["value"],
-  "data": [
-    { "label": "Beauty", "value": 15 },
-    { "label": "Fragrances", "value": 8 }
-  ]
-}
 \`\`\``;
     if (!((_a = this.config.llm.systemPrompt) == null ? void 0 : _a.includes(CHART_MARKER))) {
       this.config.llm.systemPrompt = (this.config.llm.systemPrompt || "") + chartInstruction;

package/dist/handlers/index.js

@@ -3822,17 +3822,18 @@ var Pipeline = class {
   async initialize() {
     var _a, _b;
     if (this.initialised) return;
-    const CHART_MARKER = "<!-- UI_PROTOCOL_V6 -->";
+    const CHART_MARKER = "<!-- UI_PROTOCOL_V7 -->";
     const chartInstruction = `
 
 ${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.
+### UNIVERSAL UI PROTOCOL (MANDATORY)
+CRITICAL: When providing visual data (carousels, charts, tables), you MUST wrap the JSON payload in a \`\`\`ui\`\`\` code block. 
+NEVER output naked JSON. If you provide a visualization, do not also provide a markdown table of the same data unless explicitly asked.
 
 1. VIEW SELECTION
-   - 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.
+   - Use "carousel" for browsing products, items, or catalogs. (e.g., "show me beauty products").
+   - Use "chart" ONLY for numerical aggregations (counts, sums, percentages).
+   - Use "table" for technical specs or row-heavy comparisons.
 
 2. REQUIRED JSON SHAPE
    {
@@ -3840,52 +3841,31 @@ When the user asks for a visual representation, comparison, distribution, breakd
      "title": "Short heading",
      "description": "One sentence describing the view",
      "chartType": "pie" | "bar" | "line", // Required if view is "chart"
-     "xAxisKey": "label",
-     "dataKeys": ["value"],
-     "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
-     "insights": ["Short takeaway 1", "Short takeaway 2"],
-     "data": []
+     "data": [] // Array of objects
    }
 
 3. DATA RULES
-   - 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.
+   - Build the UI payload from retrieved context only.
+   - For CAROUSEL: "data" items MUST have { id, name, brand, price, image, link }.
+   - For CHART: "data" items MUST have { label, value }.
 
 4. FORMAT RULES
-   - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - Put natural language explanation before or after the block, not inside.
+   - Wrap the JSON in \`\`\`ui ... \`\`\` blocks.
+   - Place natural language text OUTSIDE the block.
 
-5. EXAMPLES
-User: "show me beauty products"
-Assistant:
+5. EXAMPLE
+User: "find me beauty products"
+Assistant: "I found several beauty products in our catalog:"
 \`\`\`ui
 {
   "view": "carousel",
   "title": "Beauty Products",
-  "description": "Browse our latest skincare and makeup collection.",
+  "description": "Latest skincare and makeup items.",
   "data": [
-    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
-    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." }
   ]
 }
 \`\`\`
-
-User: "breakdown of products by category"
-Assistant:
-\`\`\`ui
-{
-  "view": "chart",
-  "title": "Category Breakdown",
-  "chartType": "pie",
-  "xAxisKey": "label",
-  "dataKeys": ["value"],
-  "data": [
-    { "label": "Beauty", "value": 15 },
-    { "label": "Fragrances", "value": 8 }
-  ]
-}
 \`\`\``;
     if (!((_a = this.config.llm.systemPrompt) == null ? void 0 : _a.includes(CHART_MARKER))) {
       this.config.llm.systemPrompt = (this.config.llm.systemPrompt || "") + chartInstruction;

package/dist/handlers/index.mjs

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

package/dist/index.js

@@ -405,7 +405,7 @@ function sanitizeJson(raw) {
       return `: ${result}`;
     }
   );
-  s = s.replace(/\/\/[^\n]*/g, "");
+  s = s.replace(/(^|[^\:])\/\/[^\n]*/g, "$1");
   s = s.replace(/([{,]\s*)([A-Za-z_$][A-Za-z0-9_$]*)\s*:/g, '$1"$2":');
   s = s.replace(/'([^'\\]*(?:\\.[^'\\]*)*)'/g, '"$1"');
   s = s.replace(/,\s*([}\]])/g, "$1");
@@ -456,7 +456,7 @@ function extractLikelyJsonBlock(raw) {
   return trimmed.slice(Math.min(...starts));
 }
 function looksLikeStructuredPayload(raw) {
-  return /"?(view|chartType|type|data|items|rows|products|results)"?\s*:/.test(raw);
+  return /"?(view|chartType|type|data|items|rows|products|results|columns|xAxisKey)"?\s*:/.test(raw);
 }
 function stripMarkdownTables(raw) {
   return raw.replace(
@@ -841,15 +841,16 @@ function MessageBubble({
     let raw = structuredContent.payload ? structuredContent.text : cleanContent || message.content;
     const hasStructuredUiBlock = Boolean(structuredContent.payload) || /```(?:ui|json|chart)\s*[\s\S]*?"(?:view|chartType|type|data|items|rows|products|results)"\s*:/i.test(raw);
     raw = raw.replace(/([^\n])\n\|/g, "$1\n\n|").replace(/(\|[^\n]*\|)\n\n+(?=\|)/g, "$1\n");
-    if (!isStreaming) {
-      raw = raw.replace(/(?:^|\n)\s*\{[\s\S]*\}\s*(?:\n|$)/g, (match) => {
+    if (!isStreaming && !hasStructuredUiBlock) {
+      raw = raw.replace(/(?:^|\n)\s*(\{[\s\S]+?\})(?:\s*\n|$)/g, (match, body) => {
         if (match.includes("```")) return match;
-        if (!looksLikeStructuredPayload(match)) return match;
-        const type = match.includes('"view"') || match.includes('"chartType"') || match.includes('"type": "pie"') || match.includes('"type":"pie"') || match.includes('"type": "bar"') || match.includes('"type":"bar"') || match.includes('"type": "line"') || match.includes('"type":"line"') ? "ui" : "json";
+        const trimmedBody = body.trim();
+        if (!looksLikeStructuredPayload(trimmedBody)) return match;
+        const type = trimmedBody.includes('"view"') || trimmedBody.includes('"chartType"') || trimmedBody.includes('"type"') || trimmedBody.includes('"xAxisKey"') ? "ui" : "json";
         return `
 
 \`\`\`${type}
-${match.trim()}
+${trimmedBody}
 \`\`\`
 
 `;

package/dist/index.mjs

@@ -368,7 +368,7 @@ function sanitizeJson(raw) {
       return `: ${result}`;
     }
   );
-  s = s.replace(/\/\/[^\n]*/g, "");
+  s = s.replace(/(^|[^\:])\/\/[^\n]*/g, "$1");
   s = s.replace(/([{,]\s*)([A-Za-z_$][A-Za-z0-9_$]*)\s*:/g, '$1"$2":');
   s = s.replace(/'([^'\\]*(?:\\.[^'\\]*)*)'/g, '"$1"');
   s = s.replace(/,\s*([}\]])/g, "$1");
@@ -419,7 +419,7 @@ function extractLikelyJsonBlock(raw) {
   return trimmed.slice(Math.min(...starts));
 }
 function looksLikeStructuredPayload(raw) {
-  return /"?(view|chartType|type|data|items|rows|products|results)"?\s*:/.test(raw);
+  return /"?(view|chartType|type|data|items|rows|products|results|columns|xAxisKey)"?\s*:/.test(raw);
 }
 function stripMarkdownTables(raw) {
   return raw.replace(
@@ -804,15 +804,16 @@ function MessageBubble({
     let raw = structuredContent.payload ? structuredContent.text : cleanContent || message.content;
     const hasStructuredUiBlock = Boolean(structuredContent.payload) || /```(?:ui|json|chart)\s*[\s\S]*?"(?:view|chartType|type|data|items|rows|products|results)"\s*:/i.test(raw);
     raw = raw.replace(/([^\n])\n\|/g, "$1\n\n|").replace(/(\|[^\n]*\|)\n\n+(?=\|)/g, "$1\n");
-    if (!isStreaming) {
-      raw = raw.replace(/(?:^|\n)\s*\{[\s\S]*\}\s*(?:\n|$)/g, (match) => {
+    if (!isStreaming && !hasStructuredUiBlock) {
+      raw = raw.replace(/(?:^|\n)\s*(\{[\s\S]+?\})(?:\s*\n|$)/g, (match, body) => {
         if (match.includes("```")) return match;
-        if (!looksLikeStructuredPayload(match)) return match;
-        const type = match.includes('"view"') || match.includes('"chartType"') || match.includes('"type": "pie"') || match.includes('"type":"pie"') || match.includes('"type": "bar"') || match.includes('"type":"bar"') || match.includes('"type": "line"') || match.includes('"type":"line"') ? "ui" : "json";
+        const trimmedBody = body.trim();
+        if (!looksLikeStructuredPayload(trimmedBody)) return match;
+        const type = trimmedBody.includes('"view"') || trimmedBody.includes('"chartType"') || trimmedBody.includes('"type"') || trimmedBody.includes('"xAxisKey"') ? "ui" : "json";
         return `
 
 \`\`\`${type}
-${match.trim()}
+${trimmedBody}
 \`\`\`
 
 `;

package/dist/server.js

@@ -3913,17 +3913,18 @@ var Pipeline = class {
   async initialize() {
     var _a, _b;
     if (this.initialised) return;
-    const CHART_MARKER = "<!-- UI_PROTOCOL_V6 -->";
+    const CHART_MARKER = "<!-- UI_PROTOCOL_V7 -->";
     const chartInstruction = `
 
 ${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.
+### UNIVERSAL UI PROTOCOL (MANDATORY)
+CRITICAL: When providing visual data (carousels, charts, tables), you MUST wrap the JSON payload in a \`\`\`ui\`\`\` code block. 
+NEVER output naked JSON. If you provide a visualization, do not also provide a markdown table of the same data unless explicitly asked.
 
 1. VIEW SELECTION
-   - 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.
+   - Use "carousel" for browsing products, items, or catalogs. (e.g., "show me beauty products").
+   - Use "chart" ONLY for numerical aggregations (counts, sums, percentages).
+   - Use "table" for technical specs or row-heavy comparisons.
 
 2. REQUIRED JSON SHAPE
    {
@@ -3931,52 +3932,31 @@ When the user asks for a visual representation, comparison, distribution, breakd
      "title": "Short heading",
      "description": "One sentence describing the view",
      "chartType": "pie" | "bar" | "line", // Required if view is "chart"
-     "xAxisKey": "label",
-     "dataKeys": ["value"],
-     "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
-     "insights": ["Short takeaway 1", "Short takeaway 2"],
-     "data": []
+     "data": [] // Array of objects
    }
 
 3. DATA RULES
-   - 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.
+   - Build the UI payload from retrieved context only.
+   - For CAROUSEL: "data" items MUST have { id, name, brand, price, image, link }.
+   - For CHART: "data" items MUST have { label, value }.
 
 4. FORMAT RULES
-   - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - Put natural language explanation before or after the block, not inside.
+   - Wrap the JSON in \`\`\`ui ... \`\`\` blocks.
+   - Place natural language text OUTSIDE the block.
 
-5. EXAMPLES
-User: "show me beauty products"
-Assistant:
+5. EXAMPLE
+User: "find me beauty products"
+Assistant: "I found several beauty products in our catalog:"
 \`\`\`ui
 {
   "view": "carousel",
   "title": "Beauty Products",
-  "description": "Browse our latest skincare and makeup collection.",
+  "description": "Latest skincare and makeup items.",
   "data": [
-    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
-    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." }
   ]
 }
 \`\`\`
-
-User: "breakdown of products by category"
-Assistant:
-\`\`\`ui
-{
-  "view": "chart",
-  "title": "Category Breakdown",
-  "chartType": "pie",
-  "xAxisKey": "label",
-  "dataKeys": ["value"],
-  "data": [
-    { "label": "Beauty", "value": 15 },
-    { "label": "Fragrances", "value": 8 }
-  ]
-}
 \`\`\``;
     if (!((_a = this.config.llm.systemPrompt) == null ? void 0 : _a.includes(CHART_MARKER))) {
       this.config.llm.systemPrompt = (this.config.llm.systemPrompt || "") + chartInstruction;

package/dist/server.mjs

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@retrivora-ai/rag-engine",
-  "version": "1.6.8",
+  "version": "1.6.9",
   "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

@@ -32,8 +32,8 @@ function sanitizeJson(raw: string): string {
     },
   );
 
-  // 2. Strip JS-style single-line comments
-  s = s.replace(/\/\/[^\n]*/g, '');
+  // 2. Strip JS-style single-line comments, but avoid URL protocols like https://
+  s = s.replace(/(^|[^\:])\/\/[^\n]*/g, '$1');
 
   // 3. Quote bare (unquoted) object keys
   s = s.replace(/([{,]\s*)([A-Za-z_$][A-Za-z0-9_$]*)\s*:/g, '$1"$2":');
@@ -103,7 +103,7 @@ function extractLikelyJsonBlock(raw: string): string {
 }
 
 function looksLikeStructuredPayload(raw: string): boolean {
-  return /"?(view|chartType|type|data|items|rows|products|results)"?\s*:/.test(raw);
+  return /"?(view|chartType|type|data|items|rows|products|results|columns|xAxisKey)"?\s*:/.test(raw);
 }
 
 function stripMarkdownTables(raw: string): string {
@@ -718,17 +718,23 @@ export function MessageBubble({
       .replace(/(\|[^\n]*\|)\n\n+(?=\|)/g, '$1\n'); // Remove blank lines between rows
 
     // 2. HEALING: Detect naked JSON charts/products and wrap them if markers are missing
-    // This handles models (like Llama 3.2) that often omit the ```chart markers.
-    if (!isStreaming) {
+    // This handles models (like Llama 3.2) that often omit the ```ui markers.
+    if (!isStreaming && !hasStructuredUiBlock) {
       // Look for objects that look like chart or product data
-      raw = raw.replace(/(?:^|\n)\s*\{[\s\S]*\}\s*(?:\n|$)/g, (match) => {
+      raw = raw.replace(/(?:^|\n)\s*(\{[\s\S]+?\})(?:\s*\n|$)/g, (match, body) => {
         // Only wrap if not already in a code block
         if (match.includes('```')) return match;
-        if (!looksLikeStructuredPayload(match)) return match;
-        const type = match.includes('"view"') || match.includes('"chartType"') || match.includes('"type": "pie"') || match.includes('"type":"pie"') || match.includes('"type": "bar"') || match.includes('"type":"bar"') || match.includes('"type": "line"') || match.includes('"type":"line"')
+        const trimmedBody = body.trim();
+        if (!looksLikeStructuredPayload(trimmedBody)) return match;
+        
+        const type = trimmedBody.includes('"view"') || 
+                     trimmedBody.includes('"chartType"') || 
+                     trimmedBody.includes('"type"') || 
+                     trimmedBody.includes('"xAxisKey"')
           ? 'ui'
           : 'json';
-        return `\n\n\`\`\`${type}\n${match.trim()}\n\`\`\`\n\n`;
+          
+        return `\n\n\`\`\`${type}\n${trimmedBody}\n\`\`\`\n\n`;
       });
     }
 

package/src/core/Pipeline.ts

@@ -101,15 +101,16 @@ 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_V6 -->';
+    const CHART_MARKER = '<!-- UI_PROTOCOL_V7 -->';
     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.
+### UNIVERSAL UI PROTOCOL (MANDATORY)
+CRITICAL: When providing visual data (carousels, charts, tables), you MUST wrap the JSON payload in a \`\`\`ui\`\`\` code block. 
+NEVER output naked JSON. If you provide a visualization, do not also provide a markdown table of the same data unless explicitly asked.
 
 1. VIEW SELECTION
-   - 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.
+   - Use "carousel" for browsing products, items, or catalogs. (e.g., "show me beauty products").
+   - Use "chart" ONLY for numerical aggregations (counts, sums, percentages).
+   - Use "table" for technical specs or row-heavy comparisons.
 
 2. REQUIRED JSON SHAPE
    {
@@ -117,52 +118,31 @@ When the user asks for a visual representation, comparison, distribution, breakd
      "title": "Short heading",
      "description": "One sentence describing the view",
      "chartType": "pie" | "bar" | "line", // Required if view is "chart"
-     "xAxisKey": "label",
-     "dataKeys": ["value"],
-     "columns": ["dynamicFieldKey1", "dynamicFieldKey2"],
-     "insights": ["Short takeaway 1", "Short takeaway 2"],
-     "data": []
+     "data": [] // Array of objects
    }
 
 3. DATA RULES
-   - 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.
+   - Build the UI payload from retrieved context only.
+   - For CAROUSEL: "data" items MUST have { id, name, brand, price, image, link }.
+   - For CHART: "data" items MUST have { label, value }.
 
 4. FORMAT RULES
-   - Return valid JSON inside the \`\`\`ui\`\`\` block.
-   - Put natural language explanation before or after the block, not inside.
+   - Wrap the JSON in \`\`\`ui ... \`\`\` blocks.
+   - Place natural language text OUTSIDE the block.
 
-5. EXAMPLES
-User: "show me beauty products"
-Assistant:
+5. EXAMPLE
+User: "find me beauty products"
+Assistant: "I found several beauty products in our catalog:"
 \`\`\`ui
 {
   "view": "carousel",
   "title": "Beauty Products",
-  "description": "Browse our latest skincare and makeup collection.",
+  "description": "Latest skincare and makeup items.",
   "data": [
-    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." },
-    { "id": "2", "name": "Lipstick", "brand": "Chic", "price": "$12.99", "image": "...", "link": "..." }
+    { "id": "1", "name": "Mascara", "brand": "Essence", "price": "$9.99", "image": "...", "link": "..." }
   ]
 }
 \`\`\`
-
-User: "breakdown of products by category"
-Assistant:
-\`\`\`ui
-{
-  "view": "chart",
-  "title": "Category Breakdown",
-  "chartType": "pie",
-  "xAxisKey": "label",
-  "dataKeys": ["value"],
-  "data": [
-    { "label": "Beauty", "value": 15 },
-    { "label": "Fragrances", "value": 8 }
-  ]
-}
 \`\`\``;
 
     if (!this.config.llm.systemPrompt?.includes(CHART_MARKER)) {