workflow 4.1.0-beta.55 → 4.1.0-beta.57

package/docs/ai/chat-session-modeling.mdx

@@ -1,6 +1,17 @@
 ---
 title: Chat Session Modeling
 description: Model chat sessions at different architectural layers to control state ownership and handle interruptions.
+type: guide
+summary: Choose between single-turn and multi-turn workflow patterns for managing chat session state.
+prerequisites:
+  - /docs/ai
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/ai/message-queueing
+  - /docs/ai/resumable-streams
+  - /docs/foundations/hooks
+  - /docs/api-reference/workflow-ai/durable-agent
+  - /docs/api-reference/workflow/define-hook
 ---
 
 Chat sessions in AI agents can be modeled at different layers of your architecture. The choice affects state ownership and how you handle interruptions and reconnections.

package/docs/ai/defining-tools.mdx

@@ -1,6 +1,15 @@
 ---
 title: Patterns for Defining Tools
 description: Common patterns for defining tools in durable AI agents using Workflow DevKit.
+type: guide
+summary: Define step-level and workflow-level tools for durable AI agents with stream writing and context access.
+prerequisites:
+  - /docs/ai
+related:
+  - /docs/ai/streaming-updates-from-tools
+  - /docs/ai/sleep-and-delays
+  - /docs/foundations/workflows-and-steps
+  - /docs/api-reference/workflow/get-writable
 ---
 
 This page covers the details for some common patterns when defining tools for AI agents using Workflow DevKit.

package/docs/ai/human-in-the-loop.mdx

@@ -1,6 +1,16 @@
 ---
 title: Human-in-the-Loop
 description: Wait for human input or external events before proceeding in your AI agent workflows.
+type: guide
+summary: Pause agent workflows for human approval using hooks and webhooks, then resume on input.
+prerequisites:
+  - /docs/ai
+  - /docs/foundations/hooks
+related:
+  - /docs/ai/chat-session-modeling
+  - /docs/api-reference/workflow/create-webhook
+  - /docs/api-reference/workflow/define-hook
+  - /docs/foundations/workflows-and-steps
 ---
 
 A common pre-requisite for running AI agents in production is the ability to wait for human input or external events before proceeding.

package/docs/ai/index.mdx

@@ -1,6 +1,16 @@
 ---
 title: Building Durable AI Agents
 description: Build AI agents that survive crashes, scale across requests, and maintain state with durable LLM tool-call loops.
+type: overview
+summary: Convert a basic AI chat app into a durable, resumable agent using Workflow DevKit.
+related:
+  - /docs/foundations/workflows-and-steps
+  - /docs/foundations/streaming
+  - /docs/foundations/errors-and-retries
+  - /docs/ai/defining-tools
+  - /docs/ai/resumable-streams
+  - /docs/ai/human-in-the-loop
+  - /docs/getting-started/next
 ---
 
 AI agents are built on the primitive of LLM and tool-call loops, often with additional processes for data fetching, resource provisioning, or reacting to external events.

package/docs/ai/message-queueing.mdx

@@ -1,6 +1,14 @@
 ---
 title: Queueing User Messages
 description: Inject messages during an agent's turn, before tool calls complete or while the model is reasoning.
+type: guide
+summary: Inject user messages mid-turn using the `prepareStep` callback to influence the agent's next step.
+prerequisites:
+  - /docs/ai
+related:
+  - /docs/ai/chat-session-modeling
+  - /docs/api-reference/workflow-ai/durable-agent
+  - /docs/api-reference/workflow/define-hook
 ---
 
 When using [multi-turn workflows](/docs/ai/chat-session-modeling#multi-turn-workflows), messages typically arrive between agent turns. The workflow waits at a hook, receives a message, then starts a new turn. But sometimes you need to inject messages *during* an agent's turn, before tool calls complete or while the model is reasoning.

package/docs/ai/resumable-streams.mdx

@@ -1,6 +1,15 @@
 ---
 title: Resumable Streams
 description: Handle network interruptions, page refreshes, and timeouts without losing agent progress.
+type: guide
+summary: Reconnect to interrupted agent streams using `WorkflowChatTransport` without losing progress.
+prerequisites:
+  - /docs/ai
+  - /docs/foundations/streaming
+related:
+  - /docs/ai/chat-session-modeling
+  - /docs/api-reference/workflow-ai/workflow-chat-transport
+  - /docs/api-reference/workflow-api/get-run
 ---
 
 When building chat interfaces, it's common to run into network interruptions, page refreshes, or serverless function timeouts, which can break the connection to an in-progress agent.

package/docs/ai/sleep-and-delays.mdx

@@ -1,6 +1,15 @@
 ---
 title: Sleep, Suspense, and Scheduling
 description: Schedule recurring actions, handle rate limiting, and wait for external state in AI agents.
+type: guide
+summary: Pause agent execution with `sleep()` for scheduling, rate limiting, and waiting on external state.
+prerequisites:
+  - /docs/ai
+related:
+  - /docs/ai/defining-tools
+  - /docs/ai/streaming-updates-from-tools
+  - /docs/foundations/errors-and-retries
+  - /docs/api-reference/workflow/sleep
 ---
 
 AI agents sometimes need to pause execution in order to schedule recurring or future actions, wait before retrying an operation (e.g. for rate limiting), or wait for external state to be available.

package/docs/ai/streaming-updates-from-tools.mdx

@@ -1,6 +1,15 @@
 ---
 title: Streaming Updates from Tools
 description: Show progress updates and stream step output to users during long-running tool executions.
+type: guide
+summary: Write custom data parts from step functions to show progress updates during long-running tool calls.
+prerequisites:
+  - /docs/ai
+  - /docs/foundations/streaming
+related:
+  - /docs/ai/defining-tools
+  - /docs/ai/resumable-streams
+  - /docs/api-reference/workflow/get-writable
 ---
 
 After [building a durable AI agent](/docs/ai), we already get UI message chunks for displaying tool invocations and return values. However, for long-running steps, we may want to show progress updates, or stream step output to the user while it's being generated.

package/docs/api-reference/index.mdx

@@ -1,6 +1,8 @@
 ---
 title: API Reference
 description: Complete reference for all Workflow DevKit functions and primitives by package.
+type: overview
+summary: Browse all available functions and primitives organized by package.
 ---
 
 All the functions and primitives that come with Workflow DevKit by package.

package/docs/api-reference/workflow/create-hook.mdx

@@ -1,6 +1,13 @@
 ---
 title: createHook
 description: Create a low-level hook to resume workflows with arbitrary payloads.
+type: reference
+summary: Use createHook to pause a workflow and resume it with an arbitrary payload from an external system.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow/define-hook
+  - /docs/api-reference/workflow/create-webhook
 ---
 
 Creates a low-level hook primitive that can be used to resume a workflow run with arbitrary payloads.

package/docs/api-reference/workflow/create-webhook.mdx

@@ -1,6 +1,12 @@
 ---
 title: createWebhook
 description: Create webhooks to suspend and resume workflows via HTTP requests.
+type: reference
+summary: Use createWebhook to suspend a workflow until an HTTP request is received at a generated URL.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow/create-hook
 ---
 
 Creates a webhook that can be used to suspend and resume a workflow run upon receiving an HTTP request.

package/docs/api-reference/workflow/define-hook.mdx

@@ -1,6 +1,12 @@
 ---
 title: defineHook
 description: Create type-safe hooks with consistent payload types and optional validation.
+type: reference
+summary: Use defineHook to create a reusable, type-safe hook definition with optional schema validation.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow/create-hook
 ---
 
 Creates a type-safe hook helper that ensures the payload type is consistent between hook creation and resumption.

package/docs/api-reference/workflow/fatal-error.mdx

@@ -1,6 +1,12 @@
 ---
 title: FatalError
 description: Throw to mark a step as permanently failed without retrying.
+type: reference
+summary: Throw FatalError in a step to mark it as permanently failed and prevent retries.
+prerequisites:
+  - /docs/foundations/errors-and-retries
+related:
+  - /docs/api-reference/workflow/retryable-error
 ---
 
 When a `FatalError` is thrown in a step, it indicates that the workflow should not retry a step, marking it as failure.

package/docs/api-reference/workflow/fetch.mdx

@@ -1,6 +1,12 @@
 ---
 title: fetch
 description: Make HTTP requests from workflows with automatic serialization and retry semantics.
+type: reference
+summary: Use the workflow-aware fetch to make HTTP requests with automatic serialization and retry semantics.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/errors/fetch-in-workflow
 ---
 
 Makes HTTP requests from within a workflow. This is a special step function that wraps the standard `fetch` API, automatically handling serialization and providing retry semantics.

package/docs/api-reference/workflow/get-step-metadata.mdx

@@ -1,6 +1,10 @@
 ---
 title: getStepMetadata
 description: Access retry attempts and timing information within step functions.
+type: reference
+summary: Call getStepMetadata inside a step to access retry counts, timing, and idempotency keys.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
 ---
 
 Returns metadata available in the current step function.

package/docs/api-reference/workflow/get-workflow-metadata.mdx

@@ -1,6 +1,10 @@
 ---
 title: getWorkflowMetadata
 description: Access run IDs and timing information within workflow functions.
+type: reference
+summary: Call getWorkflowMetadata inside a workflow to access the run ID and timing information.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
 ---
 
 Returns additional metadata available in the current workflow function.

package/docs/api-reference/workflow/get-writable.mdx

@@ -1,6 +1,10 @@
 ---
 title: getWritable
 description: Retrieves the current workflow run's default writable stream.
+type: reference
+summary: Use getWritable to access the workflow run's output stream for real-time data streaming.
+prerequisites:
+  - /docs/foundations/streaming
 ---
 
 The writable stream can be obtained in workflow functions and passed to steps, or called directly within step functions to write data that can be read outside the workflow by using the `readable` property of the [`Run` object](/docs/api-reference/workflow-api/get-run).

package/docs/api-reference/workflow/index.mdx

@@ -1,6 +1,13 @@
 ---
 title: "workflow"
 description: Core workflow primitives for steps, streaming, webhooks, and error handling.
+type: overview
+summary: Explore the core workflow package for steps, streaming, hooks, and error handling.
+related:
+  - /docs/foundations/workflows-and-steps
+  - /docs/foundations/hooks
+  - /docs/foundations/streaming
+  - /docs/foundations/errors-and-retries
 ---
 
 Core workflow primitives including steps, context management, streaming, webhooks, and error handling.

package/docs/api-reference/workflow/retryable-error.mdx

@@ -1,6 +1,12 @@
 ---
 title: RetryableError
 description: Throw to retry a step, optionally after a specified duration.
+type: reference
+summary: Throw RetryableError in a step to trigger a retry with an optional delay.
+prerequisites:
+  - /docs/foundations/errors-and-retries
+related:
+  - /docs/api-reference/workflow/fatal-error
 ---
 
 When a `RetryableError` is thrown in a step, it indicates that the workflow should retry a step. Additionally, it contains a parameter `retryAfter` indicating when the step should be retried after.

package/docs/api-reference/workflow/sleep.mdx

@@ -1,6 +1,12 @@
 ---
 title: sleep
 description: Suspend a workflow for a duration or until a date without consuming resources.
+type: reference
+summary: Use sleep to suspend a workflow for a duration or until a specific date without consuming resources.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/ai/sleep-and-delays
 ---
 
 Suspends a workflow for a specified duration or until an end date without consuming any resources. Once the duration or end date passes, the workflow will resume execution.

package/docs/api-reference/workflow-ai/durable-agent.mdx

@@ -1,6 +1,12 @@
 ---
 title: DurableAgent
 description: Create AI agents that maintain state, call tools, and handle interruptions gracefully.
+type: reference
+summary: Use DurableAgent to build AI agents that maintain state across steps and survive interruptions.
+prerequisites:
+  - /docs/ai
+related:
+  - /docs/ai/defining-tools
 ---
 
 <Callout type="warn">

package/docs/api-reference/workflow-ai/index.mdx

@@ -2,6 +2,10 @@
 title: "@workflow/ai"
 icon: FlaskConical
 description: Helpers for building AI-powered workflows with the AI SDK.
+type: overview
+summary: Explore helpers for integrating AI SDK to build durable AI-powered workflows.
+related:
+  - /docs/ai
 ---
 
 <Callout type="warn">

package/docs/api-reference/workflow-ai/workflow-chat-transport.mdx

@@ -1,6 +1,12 @@
 ---
 title: WorkflowChatTransport
 description: Chat transport with automatic reconnection and recovery from interrupted streams.
+type: reference
+summary: Use WorkflowChatTransport as a drop-in AI SDK transport for automatic stream reconnection.
+prerequisites:
+  - /docs/ai
+related:
+  - /docs/ai/resumable-streams
 ---
 
 <Callout type="warn">

package/docs/api-reference/workflow-api/get-hook-by-token.mdx

@@ -1,6 +1,10 @@
 ---
 title: getHookByToken
 description: Retrieve hook details and workflow run information by token.
+type: reference
+summary: Use getHookByToken to look up a hook's metadata and associated workflow run before resuming it.
+prerequisites:
+  - /docs/foundations/hooks
 ---
 
 Retrieves a hook by its unique token, returning the associated workflow run information and any metadata that was set when the hook was created. This function is useful for inspecting hook details before deciding whether to resume a workflow.

package/docs/api-reference/workflow-api/get-run.mdx

@@ -1,6 +1,10 @@
 ---
 title: getRun
 description: Retrieve workflow run metadata and status without waiting for completion.
+type: reference
+summary: Use getRun to check a workflow run's status and metadata without blocking on completion.
+prerequisites:
+  - /docs/foundations/starting-workflows
 ---
 
 Retrieves the workflow run metadata and status information for a given run ID. This function provides immediate access to workflow run details without waiting for completion, making it ideal for status checking and monitoring.

package/docs/api-reference/workflow-api/get-world.mdx

@@ -1,6 +1,10 @@
 ---
 title: getWorld
 description: Access the World instance for low-level storage, queuing, and streaming operations.
+type: reference
+summary: Use getWorld to access low-level workflow storage, queuing, and streaming backends directly.
+prerequisites:
+  - /docs/deploying
 ---
 
 Retrieves the World instance for direct access to workflow storage, queuing, and streaming backends. This function returns a `World` which provides low-level access to manage workflow runs, steps, events, and hooks.

package/docs/api-reference/workflow-api/index.mdx

@@ -1,6 +1,8 @@
 ---
 title: "workflow/api"
 description: Runtime functions to inspect runs, start workflows, and access world data.
+type: overview
+summary: Explore runtime functions for starting workflows, inspecting runs, and managing hooks.
 ---
 
 API reference for runtime functions from the `workflow/api` package.

package/docs/api-reference/workflow-api/resume-hook.mdx

@@ -1,6 +1,12 @@
 ---
 title: resumeHook
 description: Resume a paused workflow by sending a payload to a hook token.
+type: reference
+summary: Use resumeHook to send a payload to a hook token and resume a paused workflow.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow-api/resume-webhook
 ---
 
 Resumes a workflow run by sending a payload to a hook identified by its token.

package/docs/api-reference/workflow-api/resume-webhook.mdx

@@ -1,6 +1,12 @@
 ---
 title: resumeWebhook
 description: Resume a paused workflow by sending an HTTP request to a webhook token.
+type: reference
+summary: Use resumeWebhook to forward an HTTP request to a webhook token and resume a paused workflow.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow-api/resume-hook
 ---
 
 Resumes a workflow run by sending an HTTP `Request` to a webhook identified by its token.

package/docs/api-reference/workflow-api/start.mdx

@@ -1,6 +1,10 @@
 ---
 title: start
 description: Start and enqueue a new workflow run.
+type: reference
+summary: Use start to programmatically enqueue a new workflow run from outside a workflow function.
+prerequisites:
+  - /docs/foundations/starting-workflows
 ---
 
 Start/enqueue a new workflow run.

package/docs/api-reference/workflow-next/index.mdx

@@ -1,6 +1,10 @@
 ---
 title: "workflow/next"
 description: Next.js integration for automatic bundling and runtime configuration.
+type: overview
+summary: Explore the Next.js integration for automatic workflow bundling and runtime support.
+related:
+  - /docs/getting-started/next
 ---
 
 Next.js integration for Workflow DevKit that automatically configures bundling and runtime support.

package/docs/api-reference/workflow-next/with-workflow.mdx

@@ -1,6 +1,10 @@
 ---
 title: withWorkflow
 description: Configure webpack/turbopack to transform workflow directives in Next.js.
+type: reference
+summary: Wrap your Next.js config with withWorkflow to enable workflow directive transformation.
+prerequisites:
+  - /docs/getting-started/next
 ---
 
 Configures webpack/turbopack loaders to transform workflow code (`"use step"`/`"use workflow"` directives)

package/docs/deploying/building-a-world.mdx

@@ -1,6 +1,15 @@
 ---
 title: Building a World
 description: Implement the World interface to run workflows on any custom infrastructure.
+type: guide
+summary: Build a custom World adapter to run workflows on your own infrastructure.
+prerequisites:
+  - /docs/deploying
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/deploying/world/local-world
+  - /docs/deploying/world/postgres-world
+  - /docs/deploying/world/vercel-world
 ---
 
 A **World** is the abstraction that allows workflows to run on any infrastructure. It handles workflow storage, step execution queuing, and data streaming. This guide explains the World interface and how to implement your own.

package/docs/deploying/index.mdx

@@ -2,6 +2,13 @@
 title: Deploying
 icon: Rocket
 description: Deploy workflows locally, on Vercel, or anywhere using pluggable World adapters.
+type: overview
+summary: Learn how to deploy workflows to different environments using World adapters.
+related:
+  - /docs/deploying/world/local-world
+  - /docs/deploying/world/postgres-world
+  - /docs/deploying/world/vercel-world
+  - /docs/deploying/building-a-world
 ---
 
 Workflows are designed to be highly portable. The same workflow code can run locally during development, on Vercel with zero configuration, or on any infrastructure using **Worlds** — pluggable adapters that handle storage, queuing, and communication.

package/docs/deploying/world/local-world.mdx

@@ -1,6 +1,13 @@
 ---
 title: Local World
 description: Zero-config world bundled with Workflow for local development. No external services required.
+type: integration
+summary: Set up the Local World for zero-config workflow development on your machine.
+prerequisites:
+  - /docs/deploying
+related:
+  - /docs/deploying/world/postgres-world
+  - /docs/deploying/world/vercel-world
 ---
 
 The Local World is bundled with `workflow` and used automatically during local development. No installation or configuration required.

package/docs/deploying/world/postgres-world.mdx

@@ -1,6 +1,13 @@
 ---
 title: Postgres World
 description: Production-ready, self-hosted world using PostgreSQL for storage and pg-boss for job processing.
+type: integration
+summary: Deploy workflows to your own infrastructure using PostgreSQL and pg-boss.
+prerequisites:
+  - /docs/deploying
+related:
+  - /docs/deploying/world/local-world
+  - /docs/deploying/world/vercel-world
 ---
 
 The Postgres World is a production-ready backend for self-hosted deployments. It uses PostgreSQL for durable storage and [pg-boss](https://github.com/timgit/pg-boss) for reliable job processing.

package/docs/deploying/world/vercel-world.mdx

@@ -1,6 +1,13 @@
 ---
 title: Vercel World
 description: Fully-managed world for Vercel deployments with automatic storage, queuing, and authentication.
+type: integration
+summary: Deploy workflows to Vercel with fully-managed storage, queuing, and authentication.
+prerequisites:
+  - /docs/deploying
+related:
+  - /docs/deploying/world/local-world
+  - /docs/deploying/world/postgres-world
 ---
 
 The Vercel World is a fully-managed workflow backend for applications deployed on Vercel. It provides scalable storage, distributed queuing, and automatic authentication with zero configuration.

package/docs/errors/fetch-in-workflow.mdx

@@ -1,6 +1,12 @@
 ---
 title: fetch-in-workflow
 description: Use the workflow fetch step function instead of global fetch in workflows.
+type: troubleshooting
+summary: Resolve the fetch-in-workflow error by using the workflow fetch function.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/api-reference/workflow/fetch
 ---
 
 This error occurs when you try to use `fetch()` directly in a workflow function, or when a library (like the AI SDK) tries to call `fetch()` under the hood.

package/docs/errors/hook-conflict.mdx

@@ -1,6 +1,13 @@
 ---
 title: hook-conflict
 description: Hook tokens must be unique across all running workflows in your project.
+type: troubleshooting
+summary: Resolve hook token conflicts by using unique or auto-generated tokens.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow/create-hook
+  - /docs/api-reference/workflow/define-hook
 ---
 
 This error occurs when you try to create a hook with a token that is already in use by another active workflow run. Hook tokens must be unique across all running workflows in your project.

package/docs/errors/index.mdx

@@ -1,6 +1,10 @@
 ---
 title: Errors
 description: Fix common mistakes when creating and executing workflows.
+type: overview
+summary: Browse and resolve common workflow errors.
+related:
+  - /docs/foundations/errors-and-retries
 ---
 
 Fix common mistakes when creating and executing workflows in the **Workflow DevKit**.

package/docs/errors/node-js-module-in-workflow.mdx

@@ -1,6 +1,12 @@
 ---
 title: node-js-module-in-workflow
 description: Move Node.js core module usage to step functions instead of workflows.
+type: troubleshooting
+summary: Resolve the node-js-module-in-workflow error by moving Node.js modules to step functions.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/how-it-works/understanding-directives
 ---
 
 This error occurs when you try to import or use Node.js core modules (like `fs`, `http`, `crypto`, `path`, etc.) directly inside a workflow function.

package/docs/errors/serialization-failed.mdx

@@ -1,6 +1,12 @@
 ---
 title: serialization-failed
 description: Ensure all data passed between workflow and step functions is serializable.
+type: troubleshooting
+summary: Resolve serialization errors by passing only serializable types across execution boundaries.
+prerequisites:
+  - /docs/foundations/serialization
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 This error occurs when you try to pass non-serializable data between execution boundaries in your workflow. All data passed between workflow functions, step functions, and the workflow runtime must be serializable to persist in the event log.

package/docs/errors/start-invalid-workflow-function.mdx

@@ -1,6 +1,12 @@
 ---
 title: start-invalid-workflow-function
 description: Ensure you pass a valid workflow function to start() with proper configuration.
+type: troubleshooting
+summary: Resolve the start-invalid-workflow-function error by passing a properly configured workflow function.
+prerequisites:
+  - /docs/foundations/starting-workflows
+related:
+  - /docs/api-reference/workflow-api/start
 ---
 
 This error occurs when you try to call `start()` with a function that is not a valid workflow function or when the Workflow DevKit is not configured correctly.

package/docs/errors/timeout-in-workflow.mdx

@@ -1,6 +1,12 @@
 ---
 title: timeout-in-workflow
 description: Use the sleep function instead of setTimeout or setInterval in workflows.
+type: troubleshooting
+summary: Resolve the timeout-in-workflow error by replacing setTimeout with the sleep function.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/api-reference/workflow/sleep
 ---
 
 This error occurs when you try to use `setTimeout()`, `setInterval()`, or related timing functions directly inside a workflow function.

package/docs/errors/webhook-invalid-respond-with-value.mdx

@@ -1,6 +1,12 @@
 ---
 title: webhook-invalid-respond-with-value
 description: The respondWith option must be "manual" or a Response object.
+type: troubleshooting
+summary: Resolve the webhook-invalid-respond-with-value error by using a valid respondWith option.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow/create-webhook
 ---
 
 This error occurs when you provide an invalid value for the `respondWith` option when creating a webhook. The `respondWith` option must be either `"manual"` or a `Response` object.

package/docs/errors/webhook-response-not-sent.mdx

@@ -1,6 +1,12 @@
 ---
 title: webhook-response-not-sent
 description: Manual webhooks must send a response before execution completes.
+type: troubleshooting
+summary: Resolve the webhook-response-not-sent error by ensuring all code paths call respondWith.
+prerequisites:
+  - /docs/foundations/hooks
+related:
+  - /docs/api-reference/workflow/create-webhook
 ---
 
 This error occurs when a webhook is configured with `respondWith: "manual"` but the workflow does not send a response using `request.respondWith()` before the webhook execution completes.

package/docs/foundations/common-patterns.mdx

@@ -1,6 +1,13 @@
 ---
 title: Common Patterns
 description: Implement distributed patterns using familiar async/await syntax with no new APIs to learn.
+type: guide
+summary: Apply sequential, parallel, timeout, and composition patterns in workflows.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/foundations/errors-and-retries
+  - /docs/foundations/hooks
 ---
 
 Common distributed patterns are simple to implement in workflows and require learning no new syntax. You can just use familiar async/await patterns.

package/docs/foundations/errors-and-retries.mdx

@@ -1,6 +1,13 @@
 ---
 title: Errors & Retrying
 description: Customize retry behavior with FatalError and RetryableError for robust error handling.
+type: conceptual
+summary: Control how steps handle failures and customize retry behavior.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/api-reference/workflow/fatal-error
+  - /docs/api-reference/workflow/retryable-error
 ---
 
 By default, errors thrown inside steps are retried. Additionally, Workflow DevKit provides two new types of errors you can use to customize retries.

package/docs/foundations/hooks.mdx

@@ -1,6 +1,14 @@
 ---
 title: Hooks & Webhooks
 description: Pause workflows and resume them later with external data, user interactions, or HTTP requests.
+type: conceptual
+summary: Pause workflows and resume them with external data or HTTP requests.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/api-reference/workflow/create-hook
+  - /docs/api-reference/workflow/create-webhook
+  - /docs/ai/human-in-the-loop
 ---
 
 Hooks provide a powerful mechanism for pausing workflow execution and resuming it later with external data. They enable workflows to wait for external events, user interactions (also known as "human in the loop"), or HTTP requests. This guide will teach you the core concepts, starting with the low-level Hook primitive and building up to the higher-level Webhook abstraction.

package/docs/foundations/idempotency.mdx

@@ -1,6 +1,12 @@
 ---
 title: Idempotency
 description: Ensure operations can be safely retried without producing duplicate side effects.
+type: conceptual
+summary: Prevent duplicate side effects when retrying operations in steps.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/foundations/errors-and-retries
 ---
 
 Idempotency is a property of an operation that ensures it can be safely retried without producing duplicate side effects.

package/docs/foundations/index.mdx

@@ -1,6 +1,11 @@
 ---
 title: Foundations
 description: Learn the core concepts of workflow programming to build durable, long-running applications.
+type: overview
+summary: Explore the core concepts you need to use workflows effectively.
+related:
+  - /docs/foundations/workflows-and-steps
+  - /docs/getting-started
 ---
 
 Workflow programming can be a slight shift from how you traditionally write real-world applications. Learning the foundations now will go a long way toward helping you use workflows effectively.

package/docs/foundations/serialization.mdx

@@ -1,6 +1,12 @@
 ---
 title: Serialization
 description: Understand how workflow data is serialized and persisted across suspensions and resumptions.
+type: conceptual
+summary: Learn which types can be passed between workflow and step functions.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/errors/serialization-failed
 ---
 
 All function arguments and return values passed between workflow and step functions must be serializable. Workflow DevKit uses a custom serialization system built on top of [devalue](https://github.com/sveltejs/devalue). This system supports standard JSON types, as well as a few additional popular Web API types.

package/docs/foundations/starting-workflows.mdx

@@ -1,6 +1,12 @@
 ---
 title: Starting Workflows
 description: Trigger workflow execution with the start() function and track progress with Run objects.
+type: guide
+summary: Trigger workflows and track their execution using the start() function.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/api-reference/workflow-api/start
 ---
 
 Once you've defined your workflow functions, you need to trigger them to begin execution. This is done using the `start()` function from `workflow/api`, which enqueues a new workflow run and returns a `Run` object that you can use to track its progress.

package/docs/foundations/streaming.mdx

@@ -1,6 +1,13 @@
 ---
 title: Streaming
 description: Stream data in real-time to clients for progress updates and incremental content delivery.
+type: conceptual
+summary: Stream real-time data to clients without waiting for workflow completion.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/api-reference/workflow/get-writable
+  - /docs/ai/resumable-streams
 ---
 
 Workflows can stream data in real-time to clients without waiting for the entire workflow to complete. This enables progress updates, AI-generated content, log messages, and other incremental data to be delivered as workflows execute.

package/docs/foundations/workflows-and-steps.mdx

@@ -1,6 +1,13 @@
 ---
 title: Workflows and Steps
 description: Build long-running, stateful application logic that persists progress and resumes after failures.
+type: conceptual
+summary: Understand the two function types that make up a workflow.
+prerequisites:
+  - /docs/foundations
+related:
+  - /docs/how-it-works/understanding-directives
+  - /docs/foundations/serialization
 ---
 
 import { File, Folder, Files } from "fumadocs-ui/components/files";

package/docs/getting-started/astro.mdx

@@ -1,6 +1,12 @@
 ---
 title: Astro
 description: Set up your first durable workflow in an Astro application.
+type: guide
+summary: Set up Workflow DevKit in an Astro app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 This guide will walk through setting up your first workflow in an Astro app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.

package/docs/getting-started/express.mdx

@@ -1,6 +1,12 @@
 ---
 title: Express
 description: Set up your first durable workflow in an Express application.
+type: guide
+summary: Set up Workflow DevKit in an Express app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 This guide will walk through setting up your first workflow in a Express app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.

package/docs/getting-started/fastify.mdx

@@ -1,6 +1,12 @@
 ---
 title: Fastify
 description: Set up your first durable workflow in a Fastify application.
+type: guide
+summary: Set up Workflow DevKit in a Fastify app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 This guide will walk through setting up your first workflow in a Fastify app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.

package/docs/getting-started/hono.mdx

@@ -1,6 +1,12 @@
 ---
 title: Hono
 description: This guide will walk through setting up your first workflow in a Hono app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+type: guide
+summary: Set up Workflow DevKit in a Hono app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 <Steps>

package/docs/getting-started/index.mdx

@@ -1,6 +1,11 @@
 ---
 title: Getting Started
 description: Start by choosing your framework. Each guide will walk you through the steps to install the dependencies and start running your first workflow.
+type: overview
+summary: Choose a framework and start building your first workflow.
+related:
+  - /docs/foundations
+  - /docs/foundations/workflows-and-steps
 ---
 
 import { Next, Nitro, SvelteKit, Nuxt, Hono, Bun, AstroDark, AstroLight, TanStack, Vite, Express, Nest, Fastify } from "@/app/[lang]/(home)/components/frameworks";

package/docs/getting-started/nestjs.mdx

@@ -1,6 +1,12 @@
 ---
 title: NestJS
 description: Set up your first durable workflow in a NestJS application.
+type: guide
+summary: Set up Workflow DevKit in a NestJS app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 This guide will walk through setting up your first workflow in a NestJS app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.

package/docs/getting-started/next.mdx

@@ -1,6 +1,13 @@
 ---
 title: Next.js
 description: This guide will walk through setting up your first workflow in a Next.js app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+type: guide
+summary: Set up Workflow DevKit in a Next.js app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/api-reference/workflow-next
+  - /docs/deploying/world/vercel-world
 ---
 
 <Steps>

package/docs/getting-started/nitro.mdx

@@ -1,6 +1,12 @@
 ---
 title: Nitro
 description: This guide will walk through setting up your first workflow in a Nitro v3 project. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+type: guide
+summary: Set up Workflow DevKit in a Nitro app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 <Steps>

package/docs/getting-started/nuxt.mdx

@@ -1,6 +1,12 @@
 ---
 title: Nuxt
 description: This guide will walk through setting up your first workflow in a Nuxt app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+type: guide
+summary: Set up Workflow DevKit in a Nuxt app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 <Steps>

package/docs/getting-started/sveltekit.mdx

@@ -1,6 +1,12 @@
 ---
 title: SvelteKit
 description: This guide will walk through setting up your first workflow in a SvelteKit app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.
+type: guide
+summary: Set up Workflow DevKit in a SvelteKit app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 <Steps>

package/docs/getting-started/vite.mdx

@@ -1,6 +1,12 @@
 ---
 title: Vite
 description: Set up your first durable workflow in a Vite application.
+type: guide
+summary: Set up Workflow DevKit in a Vite app.
+prerequisites:
+  - /docs/getting-started
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 This guide will walk through setting up your first workflow in a Vite app. Along the way, you'll learn more about the concepts that are fundamental to using the development kit in your own projects.

package/docs/how-it-works/code-transform.mdx

@@ -1,6 +1,12 @@
 ---
 title: How the Directives Work
 description: Deep dive into the internals of how Workflow DevKit directives transform your code.
+type: conceptual
+summary: Learn how the compiler transforms directive-annotated code into three execution modes.
+prerequisites:
+  - /docs/how-it-works/understanding-directives
+related:
+  - /docs/foundations/workflows-and-steps
 ---
 
 <Callout>

package/docs/how-it-works/event-sourcing.mdx

@@ -1,6 +1,12 @@
 ---
 title: Event Sourcing
 description: Learn how Workflow DevKit uses event sourcing internally for debugging and observability.
+type: conceptual
+summary: Understand the event log that powers workflow replay and debugging.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/observability
 ---
 
 <Callout>

package/docs/how-it-works/framework-integrations.mdx

@@ -1,6 +1,12 @@
 ---
 title: Framework Integrations
 description: Guide for framework authors to integrate Workflow DevKit with custom frameworks or runtimes.
+type: guide
+summary: Build a custom framework integration using the Workflow DevKit compiler and runtime.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/deploying/building-a-world
 ---
 
 <Callout>

package/docs/how-it-works/understanding-directives.mdx

@@ -1,6 +1,12 @@
 ---
 title: Understanding Directives
 description: Explore how JavaScript directives enable the Workflow DevKit's durable execution model.
+type: conceptual
+summary: Explore the design decisions behind "use workflow" and "use step" directives.
+prerequisites:
+  - /docs/foundations/workflows-and-steps
+related:
+  - /docs/how-it-works/code-transform
 ---
 
 import { File, Folder, Files } from "fumadocs-ui/components/files";

package/docs/observability/index.mdx

@@ -1,6 +1,12 @@
 ---
 title: Observability
 description: Inspect, monitor, and debug workflows through the CLI and Web UI with powerful observability tools.
+type: guide
+summary: Inspect and debug workflow runs using the CLI and Web UI.
+prerequisites:
+  - /docs/foundations
+related:
+  - /docs/how-it-works/event-sourcing
 ---
 
 Workflow DevKit provides powerful tools to inspect, monitor, and debug your workflows through the CLI and Web UI. These tools allow you to inspect workflow runs, steps, webhooks, [events](/docs/how-it-works/event-sourcing), and stream output.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workflow",
-  "version": "4.1.0-beta.55",
+  "version": "4.1.0-beta.57",
   "description": "Workflow DevKit - Build durable, resilient, and observable workflows",
   "main": "dist/typescript-plugin.cjs",
   "type": "module",
@@ -53,17 +53,17 @@
   },
   "dependencies": {
     "ms": "2.1.3",
-    "@workflow/astro": "4.0.0-beta.29",
-    "@workflow/cli": "4.1.0-beta.55",
-    "@workflow/core": "4.1.0-beta.55",
+    "@workflow/astro": "4.0.0-beta.31",
+    "@workflow/cli": "4.1.0-beta.57",
+    "@workflow/core": "4.1.0-beta.57",
     "@workflow/errors": "4.1.0-beta.15",
     "@workflow/typescript-plugin": "4.0.1-beta.4",
-    "@workflow/next": "4.0.1-beta.51",
-    "@workflow/nest": "0.0.0-beta.4",
-    "@workflow/nitro": "4.0.1-beta.50",
-    "@workflow/nuxt": "4.0.1-beta.39",
-    "@workflow/sveltekit": "4.0.0-beta.44",
-    "@workflow/rollup": "4.0.0-beta.12"
+    "@workflow/next": "4.0.1-beta.53",
+    "@workflow/nest": "0.0.0-beta.6",
+    "@workflow/nitro": "4.0.1-beta.52",
+    "@workflow/nuxt": "4.0.1-beta.41",
+    "@workflow/sveltekit": "4.0.0-beta.46",
+    "@workflow/rollup": "4.0.0-beta.14"
   },
   "devDependencies": {
     "@types/ms": "2.1.0",

package/dist/internal/observability.d.ts

@@ -1,6 +0,0 @@
-/**
- * These are shared observability utilities that are used by the CLI and Web UIs.
- * They might later be moved to be part of the core API.
- */
-export * from '@workflow/core/observability';
-//# sourceMappingURL=observability.d.ts.map

package/dist/internal/observability.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"observability.d.ts","sourceRoot":"","sources":["../../src/internal/observability.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,cAAc,8BAA8B,CAAC"}

package/dist/internal/observability.js

@@ -1,6 +0,0 @@
-/**
- * These are shared observability utilities that are used by the CLI and Web UIs.
- * They might later be moved to be part of the core API.
- */
-export * from '@workflow/core/observability';
-//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoib2JzZXJ2YWJpbGl0eS5qcyIsInNvdXJjZVJvb3QiOiIiLCJzb3VyY2VzIjpbIi4uLy4uL3NyYy9pbnRlcm5hbC9vYnNlcnZhYmlsaXR5LnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOzs7R0FHRztBQUVILGNBQWMsOEJBQThCLENBQUMifQ==