@iblai/mcp 1.12.5 → 1.12.6

package/dist/resources/web-utils.js

@@ -127,7 +127,7 @@ const {
   mode: 'advanced', // or 'default'
   errorHandler: (error) => toast.error(error.message),
   on402Error: () => showSubscriptionModal(),
-  // Expired DM token: mint a fresh one, the rejected message is resent with it.
+  // Expired axd token: mint a fresh one, the rejected message is resent with it.
   on401Error: handle401Error, // from use401TokenRefresh({ tenantKey })
 });
 \`\`\`

package/dist/tools/hook-info.js

@@ -103,7 +103,7 @@ const {
   sendMessageToParentWebsite?: (payload: unknown) => void,
   on402Error?: (message: Error402MessageData) => void,
   onSpendCapError?: (message: SpendCapExceededMessageData) => void,
-  // Mint a fresh DM token after a 401; the rejected message is resent with it.
+  // Mint a fresh axd token after a 401; the rejected message is resent with it.
   on401Error?: (message: Auth401MessageData) => Promise<string | void> | string | void,
 });
 \`\`\`
@@ -151,17 +151,17 @@ const {
 - Offline mode support with local LLM
 - Message queue for pending messages
 - 402 payment required error handling
-- 401 DM token refresh with automatic message resend
+- 401 axd token refresh with automatic message resend
 
-## Recovering from an expired DM token (\`on401Error\`)
+## Recovering from an expired axd token (\`on401Error\`)
 
-A \`{ error, status_code: 401 }\` frame means the DM token sent with the message
+A \`{ error, status_code: 401 }\` frame means the axd token sent with the message
 has expired. The refresh lives entirely in your callback — the hook holds no
 token of its own. It reconnects the socket (the backend closes it after any
 error frame) and resends the rejected message with the token you return.
 
 \`\`\`typescript
-// Ready-made handler: mints app tokens, persists them, returns the new DM token
+// Ready-made handler: mints app tokens, persists them, returns the new axd token
 const { handle401Error } = use401TokenRefresh({ tenantKey });
 // ...
 on401Error: handle401Error,
@@ -173,7 +173,7 @@ abandoned: the 401 falls through to \`errorHandler\` like any other error frame.
 Only ONE retry is attempted per sent message, so a token the backend still
 rejects cannot loop. Later messages carry the \`wsToken\` prop, so update its
 source in the callback too. A shareable-link frame (\`token_type: "link"\`)
-keeps its own token — only the DM token is swapped.
+keeps its own token — only the axd token is swapped.
 
 **File Location**: \`packages/web-utils/src/hooks/chat/use-chat-v2.ts\``,
     use401TokenRefresh: `# use401TokenRefresh Hook
@@ -191,7 +191,7 @@ useAdvancedChat({ ...rest, on401Error: handle401Error });
 
 \`handle401Error()\` POSTs \`platform_key\` to the app-tokens endpoint, writes
 \`axd_token\`/\`dm_token\` and their expiries to storage, and resolves with the new
-DM token — the one the chat socket authenticates with, and what the rejected
+axd token — the one the chat socket authenticates with, and what the rejected
 message is resent with. The write also updates every \`useAxdToken()\` /
 \`useDmToken()\` subscriber.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iblai/mcp",
-  "version": "1.12.5",
+  "version": "1.12.6",
   "description": "MCP server for IBL frontend packages documentation and guidance",
   "type": "module",
   "main": "dist/index.js",