@dbx-tools/shared-mastra 0.3.4 → 0.3.6

package/README.md

@@ -10,7 +10,8 @@ selection fields, and Mastra response schemas used by
 Key features:
 
 - Route constants for the AppKit-Mastra client surface, including history,
-  threads, suggestions, model lists, embeds, and feedback.
+  threads, suggestions, model lists, the per-agent default-model lookup,
+  embeds, and feedback.
 - Header/query/body constants for thread selection and model override requests.
 - Embed-marker parsing for delayed chart and statement-data payloads in
   streaming assistant text.
@@ -28,7 +29,7 @@ const config = wire.MastraClientConfigSchema.parse(await response.json());
 ```
 
 `wire.MastraClientConfigSchema` describes the plugin-published client config:
-mount path, default agent, feedback enablement, and MCP route details. Use it to
+mount path, default agent, the agent roster, and feedback enablement. Use it to
 bootstrap a UI without hard-coding server paths.
 
 ## Use Route Constants
@@ -41,7 +42,8 @@ const threadsUrl = `${basePath}${routes.MASTRA_ROUTES.threads}`;
 ```
 
 `routes.MASTRA_ROUTES` keeps client fetch calls aligned with plugin route names
-for history, threads, models, suggestions, feedback, and embeds.
+for history, threads, models, the default-model lookup, suggestions, feedback,
+and embeds.
 
 ## Select Threads And Models
 

package/package.json

@@ -12,16 +12,16 @@
   },
   "dependencies": {
     "zod": "^4.3.6",
-    "@dbx-tools/shared-core": "0.3.4",
-    "@dbx-tools/shared-genie": "0.3.4",
-    "@dbx-tools/shared-model": "0.3.4"
+    "@dbx-tools/shared-core": "0.3.6",
+    "@dbx-tools/shared-model": "0.3.6",
+    "@dbx-tools/shared-genie": "0.3.6"
   },
   "main": "index.ts",
   "license": "UNLICENSED",
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.3.4",
+  "version": "0.3.6",
   "types": "index.ts",
   "type": "module",
   "exports": {

package/src/routes.ts

@@ -5,9 +5,9 @@
  * `@dbx-tools/appkit-mastra-ui`) so a relayout - or a rename of a
  * sub-path - is a one-line change here and the two can never drift.
  *
- * The agent-scoped segments (`history`, `threads`, `suggestions`) take
- * an optional `/:agentId` suffix; the default agent uses the bare
- * segment. Conversation streaming itself rides the standard Mastra
+ * The agent-scoped segments (`history`, `threads`, `suggestions`,
+ * `defaultModel`) take an optional `/:agentId` suffix; the default agent
+ * uses the bare segment. Conversation streaming itself rides the standard Mastra
  * agent routes (`@mastra/client-js`'s `getAgent(id).stream()`), so
  * there's no chat segment here.
  *
@@ -22,11 +22,13 @@ export const MASTRA_ROUTES = {
   feedback: "/route/feedback",
   suggestions: "/suggestions",
   models: "/models",
-  // The serving-endpoint id an agent falls back to when the client pins no
-  // model. Agent-scoped via an optional `?agentId=`; the default agent is
-  // used when omitted. Returns `{ agentId, model }` where `model` is null
-  // when the agent resolves its model dynamically at call time (nothing
-  // static to advertise). Lets the picker label its "Server default" option.
+  // The static serving-endpoint an agent falls back to when the client pins
+  // no model. Agent-scoped like `history`/`threads`/`suggestions` via an
+  // optional `/:agentId` suffix; the default agent uses the bare segment.
+  // Returns `{ agentId, model, displayName }` where `model` and `displayName`
+  // are null when the agent resolves its model dynamically at call time
+  // (nothing static to advertise). Lets the picker label its default option
+  // with the humanized model name.
   defaultModel: "/default-model",
   embed: "/embed",
 } as const;

package/src/wire.ts

@@ -591,8 +591,9 @@ export type GenieDatasetData = z.infer<typeof GenieDatasetDataSchema>;
  *
  * `option` is intentionally NOT included. The resolved Echarts
  * spec lives off-band in the chart cache: the host UI fetches it
- * by `chartId` via `${MastraClientConfig.embedPathTemplate}`
- * (`/embed/chart/:id`, see {@link Chart}). Embedding the full spec inline would
+ * by `chartId` from the plugin's embed route (derived from
+ * `basePath` + {@link MASTRA_ROUTES}.embed, i.e. `/embed/chart/:id`;
+ * see {@link Chart}). Embedding the full spec inline would
  * inflate every dataset by several KB per chart and round-trip
  * through the LLM context for zero benefit (the model only needs
  * the `chartId` to place a `[chart:<chartId>]` marker in its