@mastra/client-js 1.42.5-alpha.1 → 1.42.5-alpha.2

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-client-js
 description: Documentation for @mastra/client-js. Use when working with @mastra/client-js APIs, configuration, or implementation.
 metadata:
   package: "@mastra/client-js"
-  version: "1.42.5-alpha.1"
+  version: "1.42.5-alpha.2"
 ---
 
 ## When to use

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.42.5-alpha.1",
+  "version": "1.42.5-alpha.2",
   "package": "@mastra/client-js",
   "exports": {},
   "modules": {}

package/dist/docs/references/docs-harness-schedules.md

@@ -8,7 +8,7 @@
 
 > **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
-A schedule runs an agent on a cron cadence. On each fire, Mastra sends a prompt to the agent, either as a [signal](https://mastra.ai/docs/harness/signals) into a thread or as a threadless [`agent.generate()`](https://mastra.ai/reference/agents/generate) run. Use schedules for recurring agent work such as daily summaries, periodic checks, or scheduled nudges into a conversation.
+A schedule runs an agent on a cron cadence. On each fire, Mastra sends a prompt either as a [signal](https://mastra.ai/docs/harness/signals) into a thread or as a threadless [`agent.generate()`](https://mastra.ai/reference/agents/generate) run. Use schedules for recurring work such as daily summaries and periodic checks, including scheduled nudges into a conversation.
 
 Schedules are persisted, so they survive restarts and redeploys. Manage them at runtime through [`mastra.schedules`](https://mastra.ai/reference/schedules/overview), the canonical create, read, update, and delete (CRUD) surface. The same surface also manages [workflow schedules](https://mastra.ai/docs/workflows/scheduled-workflows) (pass `workflowId` instead of `agentId` to schedule a workflow).
 

package/dist/docs/references/docs-harness-signals.md

@@ -8,7 +8,7 @@
 
 > **Beta:** Breaking changes may occur without a major version bump until the API is stable.
 
-Signals are a way to interact with an agent through a thread. Instead of starting every interaction with `agent.stream()`, subscribe to a thread and send messages or signals. Mastra either wakes the agent when the thread is idle or drops input into the running agent loop, or alternatively queues input for the next turn.
+Signals let you interact with an agent through a thread. Instead of starting every interaction with `agent.stream()`, subscribe to a thread and send messages or signals. Mastra wakes an idle agent or delivers input to its running loop; alternatively, it queues the input for the next turn.
 
 Use message APIs for user-authored input. Use `sendSignal()` for lower-level system context, such as background task notifications, policy reminders, or processor-generated context.
 

package/dist/docs/references/docs-server-mastra-client.md

@@ -305,7 +305,7 @@ export const colorAgent = new Agent({
 
 ## Use MastraClient on the server
 
-You can also use `MastraClient` in server-side environments such as API routes, serverless functions, or actions. The usage remains the same, but you may need to recreate the response for your client:
+Server-side API routes and serverless functions, including actions, can also use `MastraClient`. The usage is unchanged, although you may need to recreate the response for your client:
 
 ```typescript
 export async function action() {

package/dist/docs/references/docs-studio-editor.md

@@ -77,7 +77,7 @@ An instruction block can include values from the current request. For example, `
 
 ### Prompt blocks
 
-A prompt block is a saved piece of instruction text that can be used by more than one agent. Create one under **Prompts**, publish it, then open an agent's **Instructions** section and select **Add block**.
+A prompt block is a saved piece of instruction text that can be used by more than one agent. Create and publish one under **Prompts**. Then open an agent's **Instructions** section and select **Add block**.
 
 For example, agents for support, returns, and order status may all need the same refund policy. Save the policy as a prompt block and add it to each agent. When the policy changes, update and publish the block once instead of editing three agents.
 

package/dist/docs/references/reference-editor-versioning.md

@@ -10,7 +10,7 @@ See [Editor versioning](https://mastra.ai/docs/studio/editor) for release and ex
 
 ## Database lifecycle
 
-The resource record stores an `activeVersionId`. Individual snapshots don't store a lifecycle status.
+The resource record stores an `activeVersionId`, while individual snapshots don't store a lifecycle status.
 
 | Term       | Meaning                                                                                      |
 | ---------- | -------------------------------------------------------------------------------------------- |

package/package.json

@@ -1,14 +1,13 @@
 {
   "name": "@mastra/client-js",
-  "version": "1.42.5-alpha.1",
+  "version": "1.42.5-alpha.2",
   "description": "The official TypeScript library for the Mastra Client API",
   "author": "",
   "type": "module",
   "types": "dist/index.d.ts",
   "main": "dist/index.js",
   "files": [
-    "dist",
-    "CHANGELOG.md"
+    "dist"
   ],
   "exports": {
     ".": {
@@ -39,8 +38,8 @@
     "canonicalize": "^1.0.8",
     "jose": "^6.2.1",
     "json-schema": "^0.4.0",
-    "@mastra/core": "1.63.3-alpha.1",
-    "@mastra/schema-compat": "1.3.7"
+    "@mastra/core": "1.64.0-alpha.2",
+    "@mastra/schema-compat": "1.3.8-alpha.0"
   },
   "peerDependencies": {
     "zod": "^3.25.0 || ^4.0.0"
@@ -58,8 +57,8 @@
     "zod": "^4.4.3",
     "@internal/ai-sdk-v4": "0.0.76",
     "@internal/lint": "0.0.129",
-    "@internal/ai-sdk-v5": "0.0.76",
-    "@internal/types-builder": "0.0.104"
+    "@internal/types-builder": "0.0.104",
+    "@internal/ai-sdk-v5": "0.0.76"
   },
   "engines": {
     "node": ">=22.13.0"