@mastra/mcp-docs-server 1.3.7-alpha.1 → 1.3.7-alpha.5

package/.docs/reference/vectors/turbopuffer.md

@@ -28,11 +28,13 @@ The TurbopufferVector class provides vector search using [Turbopuffer](https://t
 
 ### `createIndex()`
 
+Turbopuffer has no explicit create-index operation. `createIndex()` validates the arguments and records the dimension and metric locally; the namespace is created in Turbopuffer on the first `upsert()`.
+
 **indexName** (`string`): Name of the index to create
 
 **dimension** (`number`): Vector dimension (must match your embedding model)
 
-**metric** (`'cosine' | 'euclidean' | 'dotproduct'`): Distance metric for similarity search (Default: `cosine`)
+**metric** (`'cosine' | 'euclidean'`): Distance metric for similarity search. 'dotproduct' isn't supported and throws an error. (Default: `cosine`)
 
 ### `upsert()`
 
@@ -80,7 +82,7 @@ interface IndexStats {
 
 ### `updateVector()`
 
-Update a single vector by ID or by metadata filter. Either `id` or `filter` must be provided, but not both.
+Update a single vector by ID, or every vector that matches a metadata filter. Either `id` or `filter` must be provided, but not both.
 
 **indexName** (`string`): Name of the index containing the vector
 
@@ -114,7 +116,7 @@ Query results are returned in this format:
 interface QueryResult {
   id: string
   score: number
-  metadata: Record<string, any>
+  metadata?: Record<string, any>
   vector?: number[] // Only included if includeVector is true
 }
 ```
@@ -144,17 +146,21 @@ schemaConfigForIndex: (indexName: string) => {
 
 ## Error handling
 
-The store throws typed errors that can be caught:
+The store throws `MastraError` instances from `@mastra/core/error`:
 
 ```typescript
+import { MastraError } from '@mastra/core/error'
+
 try {
   await store.query({
     indexName: 'index_name',
     queryVector: queryVector,
   })
 } catch (error) {
-  if (error instanceof VectorStoreError) {
-    console.log(error.code) // 'connection_failed' | 'invalid_dimension' | etc
+  if (error instanceof MastraError) {
+    console.log(error.id) // 'MASTRA_VECTOR_TURBOPUFFER_QUERY_FAILED'
+    console.log(error.domain) // 'STORAGE'
+    console.log(error.category) // 'USER' | 'THIRD_PARTY'
     console.log(error.details) // Additional error context
   }
 }

package/.docs/reference/vectors/upstash.md

@@ -8,6 +8,8 @@ The UpstashVector class provides vector search using [Upstash Vector](https://up
 
 ## Constructor options
 
+**id** (`string`): Unique identifier for this vector store instance
+
 **url** (`string`): Upstash Vector database URL
 
 **token** (`string`): Upstash Vector API token
@@ -194,24 +196,28 @@ Query results are returned in this format:
 interface QueryResult {
   id: string
   score: number
-  metadata: Record<string, any>
+  metadata?: Record<string, any>
   vector?: number[] // Only included if includeVector is true
 }
 ```
 
 ## Error handling
 
-The store throws typed errors that can be caught:
+The store throws `MastraError` instances from `@mastra/core/error`:
 
 ```typescript
+import { MastraError } from '@mastra/core/error'
+
 try {
   await store.query({
     indexName: 'index_name',
     queryVector: queryVector,
   })
 } catch (error) {
-  if (error instanceof VectorStoreError) {
-    console.log(error.code) // 'connection_failed' | 'invalid_dimension' | etc
+  if (error instanceof MastraError) {
+    console.log(error.id) // 'MASTRA_VECTOR_UPSTASH_QUERY_FAILED'
+    console.log(error.domain) // 'STORAGE'
+    console.log(error.category) // 'USER' | 'THIRD_PARTY'
     console.log(error.details) // Additional error context
   }
 }

package/.docs/reference/vectors/vectorize.md

@@ -133,17 +133,21 @@ interface QueryResult {
 
 ## Error handling
 
-The store throws typed errors that can be caught:
+The store throws `MastraError` instances from `@mastra/core/error`:
 
 ```typescript
+import { MastraError } from '@mastra/core/error'
+
 try {
   await store.query({
     indexName: 'index_name',
     queryVector: queryVector,
   })
 } catch (error) {
-  if (error instanceof VectorStoreError) {
-    console.log(error.code) // 'connection_failed' | 'invalid_dimension' | etc
+  if (error instanceof MastraError) {
+    console.log(error.id) // 'MASTRA_VECTOR_VECTORIZE_QUERY_FAILED'
+    console.log(error.domain) // 'STORAGE'
+    console.log(error.category) // 'USER' | 'THIRD_PARTY'
     console.log(error.details) // Additional error context
   }
 }

package/.docs/reference/vectors/weaviate.md

@@ -50,7 +50,7 @@ The `WeaviateVector` class provides vector search using [Weaviate](https://weavi
 
 **indexName** (`string`): Name of the index to query.
 
-**queryVector** (`number[]`): Query vector to find similar vectors for.
+**queryVector** (`number[]`): Query vector to find similar vectors for. At least one of queryVector or filter must be provided.
 
 **topK** (`number`): Number of results to return. (Default: `10`)
 

package/.docs/reference/voice/composite-voice.md

@@ -10,13 +10,11 @@ CompositeVoice supports both Mastra voice providers and AI SDK model providers
 
 ## Constructor parameters
 
-**config** (`object`): Configuration object for the composite voice service
+**input** (`MastraVoice | TranscriptionModel`): Voice provider or AI SDK transcription model to use for speech-to-text operations. AI SDK models are automatically wrapped.
 
-**config.input** (`MastraVoice | TranscriptionModel`): Voice provider or AI SDK transcription model to use for speech-to-text operations. AI SDK models are automatically wrapped.
+**output** (`MastraVoice | SpeechModel`): Voice provider or AI SDK speech model to use for text-to-speech operations. AI SDK models are automatically wrapped.
 
-**config.output** (`MastraVoice | SpeechModel`): Voice provider or AI SDK speech model to use for text-to-speech operations. AI SDK models are automatically wrapped.
-
-**config.realtime** (`MastraVoice`): Voice provider to use for real-time speech-to-speech operations
+**realtime** (`MastraVoice`): Voice provider to use for real-time speech-to-speech operations
 
 ## Methods
 
@@ -30,9 +28,10 @@ Converts text to speech using the configured speaking provider.
 
 Notes:
 
-- If no speaking provider is configured, this method will throw an error
-- Options are passed through to the configured speaking provider
-- Returns a stream of audio data
+- If a realtime provider is configured, it handles the call; otherwise the speaking provider is used
+- Throws a `MastraError` only when neither a realtime nor a speaking provider is configured
+- Options are passed through to the provider that handles the call
+- Returns a stream of audio data, or `void` when a realtime provider handles the call
 
 ### `listen()`
 
@@ -44,13 +43,14 @@ Converts speech to text using the configured listening provider.
 
 Notes:
 
-- If no listening provider is configured, this method will throw an error
-- Options are passed through to the configured listening provider
-- Returns either a string or a stream of transcribed text, depending on the provider
+- If a realtime provider is configured, it handles the call; otherwise the listening provider is used
+- Throws a `MastraError` only when neither a realtime nor a listening provider is configured
+- Options are passed through to the provider that handles the call
+- Returns a string or a stream of transcribed text, depending on the provider, or `void` when a realtime provider emits results through events
 
 ### `getSpeakers()`
 
-Returns a list of available voices from the speaking provider, where each node contains:
+Returns a list of available voices from the realtime provider, or from the speaking provider when no realtime provider is configured, where each node contains:
 
 **voiceId** (`string`): Unique identifier for the voice
 
@@ -58,10 +58,10 @@ Returns a list of available voices from the speaking provider, where each node c
 
 Notes:
 
-- Returns voices from the speaking provider only
-- If no speaking provider is configured, returns an empty array
+- Returns voices from the realtime provider when one is configured, otherwise from the speaking provider
+- Throws a `MastraError` when neither a realtime nor a speaking provider is configured
 - Each voice object will have at least a voiceId property
-- Additional voice properties depend on the speaking provider
+- Additional voice properties depend on the provider
 
 ## Usage examples
 

package/.docs/reference/voice/mastra-voice.md

@@ -141,7 +141,7 @@ Converts speech to text using the configured listening model.
 
 ```typescript
 abstract listen(
-  audioStream: NodeJS.ReadableStream,
+  audioStream: NodeJS.ReadableStream | unknown,
   options?: {
     [key: string]: unknown;
   }
@@ -150,31 +150,32 @@ abstract listen(
 
 Purpose:
 
-- Takes an audio stream and converts it to text using the provider's speech-to-text service
+- Takes an audio stream (or another provider-specific audio input) and converts it to text using the provider's speech-to-text service
 - Supports provider-specific options for transcription configuration
 - Can return either a complete text transcription or a stream of transcribed text
 - Not all providers support this functionality (e.g., PlayAI, Speechify)
 - May return void if the transcription is handled by emitting 'writing' event
 
+## Optional methods
+
+These methods have default implementations but can be overridden by voice providers that support speech-to-speech capabilities.
+
 ### `getSpeakers()`
 
 Returns a list of available voices supported by the provider.
 
 ```typescript
-abstract getSpeakers(): Promise<Array<{ voiceId: string; [key: string]: unknown }>>
+getSpeakers(): Promise<Array<{ voiceId: string; [key: string]: unknown }>>
 ```
 
 Purpose:
 
 - Retrieves the list of available voices/speakers from the provider
+- The default implementation returns an empty array; providers override it to list their voices
 - Each voice must have at least a voiceId property
 - Providers can include additional metadata about each voice
 - Used to discover available voices for text-to-speech conversion
 
-## Optional methods
-
-These methods have default implementations but can be overridden by voice providers that support speech-to-speech capabilities.
-
 ### `connect()`
 
 Establishes a WebSocket or WebRTC connection for communication.
@@ -210,12 +211,13 @@ Purpose:
 Triggers the voice provider to generate a response.
 
 ```typescript
-answer(): Promise<void>
+answer(options?: Record<string, unknown>): Promise<void>
 ```
 
 Purpose:
 
 - Sends a signal to the voice provider to generate a response
+- Accepts optional provider-specific options
 - Used in real-time conversations to prompt the AI to respond
 - Response will be emitted through the event system (e.g., 'speaking' event)
 
@@ -285,9 +287,11 @@ Purpose:
 
 The MastraVoice class includes an event system for real-time communication. Standard event types include:
 
-**speaking** (`{ text: string; audioStream?: NodeJS.ReadableStream; audio?: Int16Array }`): Emitted when the voice provider is speaking, contains audio data
+**speaker** (`NodeJS.ReadableStream`): Emitted with an audio stream for each new response the voice provider speaks
+
+**speaking** (`{ audio?: string }`): Emitted when the voice provider is speaking, contains audio data
 
-**writing** (`{ text: string, role: string }`): Emitted when text is transcribed from speech
+**writing** (`{ text: string; role: 'assistant' | 'user' }`): Emitted when text is transcribed from speech
 
 **error** (`{ message: string; code?: string; details?: unknown }`): Emitted when an error occurs
 
@@ -308,7 +312,7 @@ MastraVoice includes built-in telemetry support through the `traced` method, whi
 ## Notes
 
 - MastraVoice is an abstract class and can't be instantiated directly
-- Implementations must provide concrete implementations for all abstract methods
+- Implementations must provide concrete implementations of the abstract `speak()` and `listen()` methods
 - The class provides a consistent interface across different voice service providers
 - Speech-to-speech capabilities are optional and provider-specific
 - The event system enables asynchronous communication for real-time interactions

package/.docs/reference/voice/voice.addInstructions.md

@@ -54,7 +54,7 @@ This method doesn't return a value.
 
 - Instructions are most effective when they're clear, specific, and relevant to the voice interaction
 - This method is primarily used with real-time voice providers that maintain conversation context
-- If called on a voice provider that doesn't support instructions, it will log a warning and do nothing
+- If called on a voice provider that doesn't support instructions, it will do nothing
 - Instructions added with this method are typically combined with any instructions provided by an associated Agent
 - For best results, add instructions before starting a conversation (before calling `connect()`)
 - Multiple calls to `addInstructions()` may either replace or append to existing instructions, depending on the provider implementation

package/.docs/reference/voice/voice.addTools.md

@@ -64,7 +64,7 @@ This method doesn't return a value.
 
 - Tools must follow the Mastra tool format with name, description, input schema, and execute function
 - This method is primarily used with real-time voice providers that support function calling
-- If called on a voice provider that doesn't support tools, it will log a warning and do nothing
+- If called on a voice provider that doesn't support tools, it will do nothing
 - Tools added with this method are typically combined with any tools provided by an associated Agent
 - For best results, add tools before starting a conversation (before calling `connect()`)
 - The voice provider will automatically handle the invocation of tool handlers when the model decides to use them

package/.docs/reference/voice/voice.answer.md

@@ -52,7 +52,7 @@ Returns a `Promise<void>` that resolves when the response has been triggered.
 ## Notes
 
 - This method is only implemented by real-time voice providers that support speech-to-speech capabilities
-- If called on a voice provider that doesn't support this functionality, it will log a warning and resolve immediately
+- If called on a voice provider that doesn't support this functionality, it will log a debug message and resolve immediately
 - The response audio will typically be emitted through the 'speaking' event rather than returned directly
 - For providers that support it, you can use this method to send a specific response instead of having the AI generate one
 - This method is commonly used in conjunction with `send()` to create a conversational flow

package/.docs/reference/voice/voice.close.md

@@ -51,5 +51,5 @@ This method doesn't return a value.
 - Always call `close()` when you're done with a real-time voice session to free up resources
 - After calling `close()`, you'll need to call `connect()` again if you want to start a new session
 - This method is primarily used with real-time voice providers that maintain persistent connections
-- If called on a voice provider that doesn't support real-time connections, it will log a warning and do nothing
+- If called on a voice provider that doesn't support real-time connections, it will log a debug message and do nothing
 - Failing to close connections can lead to resource leaks and potential billing issues with voice service providers

package/.docs/reference/voice/voice.events.md

@@ -10,7 +10,7 @@ Voice providers emit events during real-time voice interactions. These events ca
 
 These events are commonly implemented across real-time voice providers:
 
-**error** (`Error`): Emitted when an error occurs during voice processing or when audio data format is unsupported
+**error** (`{ message: string; code?: string; details?: unknown }`): Emitted when an error occurs during voice processing or when audio data format is unsupported
 
 **session.created** (`object`): Emitted when a new session is created with the OpenAI service
 
@@ -20,7 +20,7 @@ These events are commonly implemented across real-time voice providers:
 
 **response.done** (`object`): Emitted when the AI assistant has completed its response
 
-**speaker** (`StreamWithId`): Emitted with a new audio stream that can be piped to an audio output
+**speaker** (`NodeJS.ReadableStream`): Emitted with a new audio stream that can be piped to an audio output. Some realtime providers attach an id property to the stream
 
 **writing** (`object`): Emitted when text is being transcribed (user) or generated (assistant)
 

package/.docs/reference/voice/voice.listen.md

@@ -8,7 +8,7 @@ The `listen()` method is a core function available in all Mastra voice providers
 
 ## Parameters
 
-**audioStream** (`NodeJS.ReadableStream`): Audio stream to transcribe. This can be a file stream or a microphone stream.
+**audioStream** (`NodeJS.ReadableStream | unknown`): Audio to transcribe. This is usually a file stream or a microphone stream; some realtime providers accept other audio input types.
 
 **options** (`object`): Provider-specific options for speech recognition
 

package/.docs/reference/voice/voice.off.md

@@ -54,5 +54,5 @@ This method doesn't return a value.
 - The callback passed to `off()` must be the same function reference that was passed to `on()`
 - If the callback isn't found, the method will have no effect
 - This method is primarily used with real-time voice providers that support event-based communication
-- If called on a voice provider that doesn't support events, it will log a warning and do nothing
+- If called on a voice provider that doesn't support events, it will log a debug message and do nothing
 - Removing event listeners is important for preventing memory leaks in long-running applications

package/.docs/reference/voice/voice.on.md

@@ -107,7 +107,7 @@ voice.on('speaker', stream => {
 ## Notes
 
 - This method is primarily used with real-time voice providers that support event-based communication
-- If called on a voice provider that doesn't support events, it will log a warning and do nothing
+- If called on a voice provider that doesn't support events, it will log a debug message and do nothing
 - Event listeners should be registered before calling methods that might emit events
 - To remove an event listener, use the [voice.off()](https://mastra.ai/reference/voice/voice.off) method with the same event name and callback function
 - Multiple listeners can be registered for the same event

package/.docs/reference/voice/voice.send.md

@@ -56,12 +56,12 @@ await voice.send(audioBuffer)
 
 ## Return value
 
-Returns a `Promise<void>` that resolves when the audio data has been accepted by the voice provider.
+Returns a `Promise<void>`. For providers that support real-time audio, it resolves when the provider has accepted the audio data. The default implementation sends nothing and resolves immediately.
 
 ## Notes
 
 - This method is only implemented by real-time voice providers that support speech-to-speech capabilities
-- If called on a voice provider that doesn't support this functionality, it will log a warning and resolve immediately
+- If called on a voice provider that doesn't support this functionality, it will log a debug message and resolve immediately
 - You must call `connect()` before using `send()` to establish the WebSocket connection
 - The audio format requirements depend on the specific voice provider
 - For continuous conversation, you typically call `send()` to transmit user audio, then `answer()` to trigger the AI response

package/.docs/reference/voice/voice.updateConfig.md

@@ -57,7 +57,7 @@ Different voice providers support different configuration options:
 
 ## Notes
 
-- The default implementation logs a warning if the provider doesn't support this method
+- The default implementation logs a debug message if the provider doesn't support this method
 - Configuration updates are typically applied to subsequent operations, not ongoing ones
 - Not all properties that can be set in the constructor can be updated at runtime
 - The specific behavior depends on the voice provider implementation

package/.docs/reference/workflows/dynamic-workflow-definition.md

@@ -128,18 +128,19 @@ Add an `outputSchema` to request structured output from the agent:
 
 Use a `mapping` entry before an agent to build its `{ prompt }` input from workflow data.
 
-Agent entries accept an optional `description` and an `options` object:
+Agent entries accept an `options` object:
 
 ```json
 {
   "type": "agent",
   "id": "summarize",
   "agentId": "support-agent",
-  "description": "Summarize the incoming request",
   "options": { "retries": 2, "metadata": { "team": "support" } }
 }
 ```
 
+The step description comes from the registered agent. A `description` set on the agent entry is ignored when the workflow is rehydrated.
+
 Only `retries` and `metadata` persist. Function-valued options such as `onFinish` and function-valued `toolChoice` are rejected when a code-defined workflow is stored. Other agent call options don't persist.
 
 ### Classifier steps

package/.docs/reference/workflows/run-methods/cancel.md

@@ -14,7 +14,6 @@ This method aborts any running steps and updates the workflow status to 'cancele
 const run = await workflow.createRun()
 
 await run.cancel()
-// Returns: { message: 'Workflow run canceled' }
 ```
 
 ## Parameters
@@ -23,7 +22,7 @@ await run.cancel()
 
 ## Returns
 
-**result** (`Promise<{ message: string }>`): A promise that resolves with { message: 'Workflow run canceled' } when cancellation succeeds
+**result** (`Promise<void>`): A promise that resolves once cancellation is requested and, if storage is configured, the status update to canceled has been attempted. It does not wait for running steps to stop. Calling cancel() on a run that already finished leaves its status unchanged, except with the Inngest engine.
 
 ## How cancellation works
 

package/.docs/reference/workflows/run-methods/resume.md

@@ -118,6 +118,8 @@ try {
 
 Over HTTP, a losing resume returns `409 Conflict`.
 
+This claim only applies to `resume()`. [`timeTravel()`](https://mastra.ai/reference/workflows/run-methods/timeTravel) doesn't claim the run, so concurrent time travel calls aren't rejected.
+
 > **Note:** The claim is enforced atomically by storage adapters that report `supportsConcurrentUpdates()`. Adapters without atomic read-modify-write support (such as ClickHouse, Cloudflare D1, Cloudflare KV, Cloudflare Durable Objects, LanceDB, and Redis) can't enforce it, and the claim is also skipped when `shouldPersistSnapshot` excludes the `running` status.
 
 ## Related

package/.docs/reference/workflows/run-methods/timeTravel.md

@@ -150,6 +150,33 @@ const result = await run.timeTravel({
 })
 ```
 
+## Concurrent time travel calls
+
+`timeTravel()` doesn't claim the run before it executes. It only rejects runs whose stored status is `running`. If two `timeTravel()` calls target the same run at the same time, both can proceed, and the target step and every step after it run once per call.
+
+This matters whenever time travel can be triggered more than once for the same run, such as a "retry from step" button pressed twice or a retried API request. Make sure only one call proceeds per run in your application, for example with a per-run lock or an idempotency key:
+
+```typescript
+const inFlight = new Set<string>()
+
+async function retryFromStep(runId: string, step: string) {
+  if (inFlight.has(runId)) {
+    throw new Error(`Time travel already in progress for run ${runId}`)
+  }
+  inFlight.add(runId)
+  try {
+    const run = await workflow.createRun({ runId })
+    return await run.timeTravel({ step })
+  } finally {
+    inFlight.delete(runId)
+  }
+}
+```
+
+The in-memory set above only protects a single process. If several server instances can handle the same run, use a shared lock instead, such as a database row lock.
+
+Unlike [`resume()`](https://mastra.ai/reference/workflows/run-methods/resume), `timeTravel()` has no `WORKFLOW_RESUME_ALREADY_CLAIMED` equivalent, and the HTTP endpoint doesn't return `409 Conflict` for concurrent calls.
+
 ## Notes
 
 - Time travel requires storage to be configured since it relies on persisted workflow snapshots

package/.docs/reference/workflows/run.md

@@ -44,14 +44,28 @@ if (result.status === 'suspended') {
 
 A workflow run's `status` indicates its current execution state. The possible values are:
 
+**pending** (`string`): The run was created but hasn't started executing yet
+
+**running** (`string`): Workflow execution is in progress
+
+**waiting** (`string`): Workflow execution was interrupted before finishing, for example when the executor was aborted
+
 **success** (`string`): All steps finished executing successfully, with a valid result output
 
 **failed** (`string`): Workflow execution encountered an error during execution, with error details available
 
+**tripwire** (`string`): A processor tripwire stopped workflow execution, with tripwire details available
+
 **suspended** (`string`): Workflow execution is paused waiting for resume, with suspended step information
 
+**paused** (`string`): Workflow execution stopped after a single step because the run uses per-step execution
+
 **canceled** (`string`): Workflow execution was canceled via the cancel() method, stopping any running steps and preventing subsequent steps from executing
 
+**bailed** (`string`): A step called bail() to end the workflow early. The run itself completes with a success status and the bail payload as its result
+
+**skipped** (`string`): Execution was skipped, for example a branch whose condition didn't match. Mainly reported for individual steps
+
 ## Related
 
 - [Run.start()](https://mastra.ai/reference/workflows/run-methods/start)

package/.docs/reference/workflows/workflow-methods/agent.md

@@ -55,7 +55,7 @@ workflow.agent('test-agent', { maxSteps: 3 }).commit()
 
 ## Persisting agent steps
 
-Workflows built with `.agent()` serialize to the same declarative entries that [dynamic workflows](https://mastra.ai/docs/workflows/dynamic-workflows) use. Only `retries` and `metadata` round-trip through storage. Options that hold functions, such as `onFinish` or a function-valued `toolChoice`, throw an error when the workflow is stored.
+Workflows built with `.agent()` serialize to the same declarative entries that [dynamic workflows](https://mastra.ai/docs/workflows/dynamic-workflows) use. Only `structuredOutput.schema` (stored as JSON Schema), `retries`, and `metadata` round-trip through storage. Options that hold functions, such as `onFinish` or a function-valued `toolChoice`, throw an error when the workflow is stored.
 
 ## Related
 

package/.docs/reference/workflows/workflow-methods/branch.md

@@ -10,20 +10,20 @@ The `.branch()` method creates conditional branches between workflow steps, allo
 
 ```typescript
 workflow.branch([
-  [async ({ context }) => true, step1],
-  [async ({ context }) => false, step2],
+  [async () => true, step1],
+  [async () => false, step2],
 ])
 ```
 
 ## Parameters
 
-**steps** (`[() => boolean, Step]`): An array of tuples, each containing a condition function and a step to execute if the condition is true
+**steps** (`[ConditionFunction | { predicate: Predicate }, Step][]`): An array of tuples, each containing a condition (a function returning a boolean, or a declarative { predicate } object) and a step to execute if the condition is true
 
 **options** (`StepFlowEntryOptions`): Optional identity and display metadata for this graph entry. Preserved through serialization and storage; has no effect on execution.
 
 ## Returns
 
-**workflow** (`NewWorkflow`): The workflow instance for method chaining
+**workflow** (`Workflow`): The workflow instance for method chaining
 
 ## Related
 

package/.docs/reference/workflows/workflow-methods/classifier.md

@@ -4,7 +4,7 @@
 
 # Workflow\.classifier()
 
-The `.classifier()` method adds a configured [`Classifier`](https://mastra.ai/reference/classifier/classifier) as a declarative workflow step. It returns a JSON-safe `{ answers, usage }` object that can be consumed by later steps and existing control-flow methods such as [`.branch()`](https://mastra.ai/reference/workflows/workflow-methods/branch).
+The `.classifier()` method adds a configured [`Classifier`](https://mastra.ai/reference/classifier/classifier) as a declarative workflow step and returns the workflow for chaining. The step outputs a JSON-safe `{ answers, usage }` object that can be consumed by later steps and existing control-flow methods such as [`.branch()`](https://mastra.ai/reference/workflows/workflow-methods/branch).
 
 ## Usage example
 

package/.docs/reference/workflows/workflow-methods/create-run.md

@@ -4,7 +4,7 @@
 
 # Workflow\.createRun()
 
-The `.createRun()` method creates a new workflow run instance, allowing you to execute the workflow with specific input data. This is the current API that returns a `Run` instance.
+The `.createRun()` method creates a new workflow run instance, allowing you to execute the workflow with specific input data. It returns a promise that resolves to a `Run` instance.
 
 ## Usage example
 
@@ -22,7 +22,7 @@ await workflow.createRun()
 
 ## Returns
 
-**run** (`Run`): A new workflow run instance that can be used to execute the workflow
+**run** (`Promise<Run>`): A promise that resolves to a new workflow run instance that can be used to execute the workflow
 
 ## Extended usage example
 

package/.docs/reference/workflows/workflow-methods/dountil.md

@@ -16,7 +16,7 @@ workflow.dountil(step1, async ({ inputData }) => true)
 
 **step** (`Step`): The step instance to execute in the loop
 
-**condition** (`(params : ExecuteParams & { iterationCount: number }) => Promise<boolean>`): A function that returns a boolean indicating whether to continue the loop. The function receives the execution parameters and the iteration count.
+**condition** (`((params: ConditionFunctionParams & { iterationCount: number }) => Promise<boolean>) | { predicate: Predicate }`): A function that returns a boolean indicating whether to continue the loop. The function receives the execution parameters (excluding setState and suspend) and the iteration count. A declarative { predicate } object is also accepted.
 
 **options** (`StepFlowEntryOptions`): Optional identity and display metadata for this graph entry. Preserved through serialization and storage; has no effect on execution.
 

package/.docs/reference/workflows/workflow-methods/dowhile.md

@@ -16,7 +16,7 @@ workflow.dowhile(step1, async ({ inputData }) => true)
 
 **step** (`Step`): The step instance to execute in the loop
 
-**condition** (`(params : ExecuteParams & { iterationCount: number }) => Promise<boolean>`): A function that returns a boolean indicating whether to continue the loop. The function receives the execution parameters and the iteration count.
+**condition** (`((params: ConditionFunctionParams & { iterationCount: number }) => Promise<boolean>) | { predicate: Predicate }`): A function that returns a boolean indicating whether to continue the loop. The function receives the execution parameters (excluding setState and suspend) and the iteration count. A declarative { predicate } object is also accepted.
 
 **options** (`StepFlowEntryOptions`): Optional identity and display metadata for this graph entry. Preserved through serialization and storage; has no effect on execution.
 

package/.docs/reference/workflows/workflow-methods/sleepUntil.md

@@ -14,7 +14,7 @@ workflow.sleepUntil(new Date(Date.now() + 5000))
 
 ## Parameters
 
-**dateOrCallback** (`Date | ((params: ExecuteFunctionParams) => Promise<Date>)`): Either a Date object or a callback function that returns a Date. The callback receives execution context and can compute the target time dynamically based on input data.
+**dateOrCallback** (`Date | ExecuteFunction<TState, TPrevSchema, Date, any, any, TEngineType>`): Either a Date object or a step-style execute function that returns a Date. The callback receives the execution context typed to the workflow state and the previous step output, and can compute the target time dynamically based on input data.
 
 **options** (`StepFlowEntryOptions`): Optional identity and display metadata for this graph entry. Preserved through serialization and storage; has no effect on execution.