@iblai/mcp 1.12.12 → 1.12.13

package/dist/tools/component-info.js

@@ -1474,7 +1474,7 @@ endpoints (30d default) and \`llm-usage\` (\`today\` default) can never disagree
 **File Location**: \`packages/web-containers/src/components/analytics/analytics-global-filters-context.tsx\``,
     AnalyticsLlmUsageStats: `# AnalyticsLlmUsageStats Component
 
-The Langfuse side of the Cost & LLM tab (the "Usage & latency" sub-tab):
+The Langfuse side of the Cost tab (the "Usage & latency" sub-tab):
 token/call/latency KPIs, spend over time stacked by service, spend by model,
 and latency percentiles (p50/p95) per model. Rendered by
 \`AnalyticsFinancialStats\` — hosts rarely mount it directly.
@@ -1499,7 +1499,7 @@ sub-tab.
 **File Location**: \`packages/web-containers/src/components/analytics/analytics-llm-usage-stats.tsx\``,
     AnalyticsTraces: `# AnalyticsTraces Component
 
-Trace explorer for the Cost & LLM tab: paginated trace list (filter by
+Trace explorer for the Cost tab: paginated trace list (filter by
 service and user, plus session) into one trace into its observations as a waterfall
 with per-span model, tokens and cost. Rendered by \`AnalyticsFinancialStats\`
 as the "Traces" sub-tab.
@@ -1701,7 +1701,7 @@ const { data: status } = useGetMemsearchStatusQuery({ org: tenantKey, userId: us
 - The **Memories by Category** breakdown only renders on the agent scope — it is the one scope with an unpaginated source to aggregate the full filtered set from. See \`useMemory\`.
 - The category filter is likewise agent-scope only: categories belong to a single agent and no other endpoint accepts the param.
 - The content search commits on Enter/blur, not per keystroke.
-- The user filter (\`UserFilterSelect\`, shared with the transcripts filter row and the Cost & LLM **Traces** sub-tab) lists tenant users from \`GET /api/core/platform/users/\` for admins, and from \`GET /api/core/users/accessible/\` with \`required_action=Ibl.Mentor/Memory/list\` for pure watchers (\`isPureWatcher\`), whom the platform endpoint 403s — that call returns only the users whose memories they may list. The accessible endpoint filters per field rather than with one search param, so a typed term containing \`@\` is sent as \`email\` and anything else as \`username\`.
+- The user filter (\`UserFilterSelect\`, shared with the transcripts filter row and the Cost **Traces** sub-tab) lists tenant users from \`GET /api/core/platform/users/\` for admins, and from \`GET /api/core/users/accessible/\` with \`required_action=Ibl.Mentor/Memory/list\` for pure watchers (\`isPureWatcher\`), whom the platform endpoint 403s — that call returns only the users whose memories they may list. The accessible endpoint filters per field rather than with one search param, so a typed term containing \`@\` is sent as \`email\` and anything else as \`username\`.
 - \`UserFilterSelect\` leads the list with a "You" entry that clears the filter back to the caller (and drops the caller from the list below it), which is what an empty value means to the memory endpoints. Surfaces where an empty value means "every user" — transcripts and traces — pass \`showSelfOption={false}\`: the trigger then reads "All users" and the caller stays in the list like anyone else.
 - Users viewing their own memories should pass \`myMemory\`, which bypasses the RBAC scope check server-side.
 

package/package.json

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