@snf/qa-bot-core 0.2.11-debug.2 → 0.2.11-debug.3

package/dist/types/components/SessionMessageTracker.d.ts

@@ -6,13 +6,12 @@
  * which messages belong to which conversation. Also, RCB's history storage
  * is opaque and unreliable for session restore.
  *
- * Solution: This component listens for every message injection and stores
- * the full message content in our own localStorage. The history dropdown
+ * Solution: This component watches the messages array via useMessages hook
+ * and stores new messages in our own localStorage. The history dropdown
  * restores sessions directly from our storage, not RCB's.
  *
- * Note: react-chatbotify wraps all messages (including plain strings) in JSX
- * before firing events. We use extractTextFromJsx() to recover the text content
- * from bot messages so they appear in restored sessions.
+ * Note: react-chatbotify wraps all messages (including plain strings) in JSX.
+ * We use extractTextFromJsx() to recover the text content from bot messages.
  *
  * Deduplication is handled by session-utils (checks message ID).
  *

package/dist/types/utils/logger.d.ts

@@ -7,7 +7,7 @@
  * Usage for consumers:
  *   localStorage.setItem('QA_BOT_DEBUG', 'true');  // Enable debug logs + version
  */
-export declare const LIB_VERSION = "0.2.11-debug.2";
+export declare const LIB_VERSION = "0.2.11-debug.3";
 export declare const logger: {
     version: () => void;
     session: (action: string, ...args: unknown[]) => void;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@snf/qa-bot-core",
-  "version": "0.2.11-debug.2",
+  "version": "0.2.11-debug.3",
   "description": "A configurable chatbot setup for quick integration of RAG-powered Q&A and rating system",
   "main": "./dist/qa-bot-core.umd.cjs",
   "module": "./dist/qa-bot-core.js",