workflow 4.1.0-beta.51 → 4.1.0-beta.53

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

@@ -1,5 +1,6 @@
 ---
 title: Chat Session Modeling
+description: Model chat sessions at different architectural layers to control state ownership and handle interruptions.
 ---
 
 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,5 +1,6 @@
 ---
 title: Patterns for Defining Tools
+description: Common patterns for defining tools in durable AI agents using Workflow DevKit.
 ---
 
 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,5 +1,6 @@
 ---
 title: Human-in-the-Loop
+description: Wait for human input or external events before proceeding in your AI agent workflows.
 ---
 
 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,5 +1,6 @@
 ---
 title: Building Durable AI Agents
+description: Build AI agents that survive crashes, scale across requests, and maintain state with durable LLM tool-call loops.
 ---
 
 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,5 +1,6 @@
 ---
 title: Queueing User Messages
+description: Inject messages during an agent's turn, before tool calls complete or while the model is reasoning.
 ---
 
 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,5 +1,6 @@
 ---
 title: Resumable Streams
+description: Handle network interruptions, page refreshes, and timeouts without losing agent progress.
 ---
 
 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,5 +1,6 @@
 ---
 title: Sleep, Suspense, and Scheduling
+description: Schedule recurring actions, handle rate limiting, and wait for external state in AI agents.
 ---
 
 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,5 +1,6 @@
 ---
 title: Streaming Updates from Tools
+description: Show progress updates and stream step output to users during long-running tool executions.
 ---
 
 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,5 +1,6 @@
 ---
 title: API Reference
+description: Complete reference for all Workflow DevKit functions and primitives by package.
 ---
 
 All the functions and primitives that come with Workflow DevKit by package.

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

@@ -1,5 +1,6 @@
 ---
 title: createHook
+description: Create a low-level hook to resume workflows with arbitrary payloads.
 ---
 
 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,5 +1,6 @@
 ---
 title: createWebhook
+description: Create webhooks to suspend and resume workflows via HTTP requests.
 ---
 
 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,5 +1,6 @@
 ---
 title: defineHook
+description: Create type-safe hooks with consistent payload types and optional validation.
 ---
 
 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,5 +1,6 @@
 ---
 title: FatalError
+description: Throw to mark a step as permanently failed without retrying.
 ---
 
 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,5 +1,6 @@
 ---
 title: fetch
+description: Make HTTP requests from workflows with automatic serialization and retry semantics.
 ---
 
 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,5 +1,6 @@
 ---
 title: getStepMetadata
+description: Access retry attempts and timing information within step functions.
 ---
 
 Returns metadata available in the current step function.

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

@@ -1,5 +1,6 @@
 ---
 title: getWorkflowMetadata
+description: Access run IDs and timing information within workflow functions.
 ---
 
 Returns additional metadata available in the current workflow function.

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

@@ -1,5 +1,6 @@
 ---
 title: "workflow"
+description: Core workflow primitives for steps, streaming, webhooks, and error handling.
 ---
 
 Core workflow primitives including steps, context management, streaming, webhooks, and error handling.

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

@@ -1,5 +1,6 @@
 ---
 title: RetryableError
+description: Throw to retry a step, optionally after a specified duration.
 ---
 
 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,5 +1,6 @@
 ---
 title: sleep
+description: Suspend a workflow for a duration or until a date without consuming resources.
 ---
 
 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,5 +1,6 @@
 ---
 title: DurableAgent
+description: Create AI agents that maintain state, call tools, and handle interruptions gracefully.
 ---
 
 <Callout type="warn">

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

@@ -1,6 +1,7 @@
 ---
 title: "@workflow/ai"
 icon: FlaskConical
+description: Helpers for building AI-powered workflows with the AI SDK.
 ---
 
 <Callout type="warn">

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

@@ -1,5 +1,6 @@
 ---
 title: WorkflowChatTransport
+description: Chat transport with automatic reconnection and recovery from interrupted streams.
 ---
 
 <Callout type="warn">

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

@@ -1,5 +1,6 @@
 ---
 title: getHookByToken
+description: Retrieve hook details and workflow run information by token.
 ---
 
 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,5 +1,6 @@
 ---
 title: getRun
+description: Retrieve workflow run metadata and status without waiting for completion.
 ---
 
 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,5 +1,6 @@
 ---
 title: getWorld
+description: Access the World instance for low-level storage, queuing, and streaming operations.
 ---
 
 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,5 +1,6 @@
 ---
 title: "workflow/api"
+description: Runtime functions to inspect runs, start workflows, and access world data.
 ---
 
 API reference for runtime functions from the `workflow/api` package.

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

@@ -1,5 +1,6 @@
 ---
 title: resumeHook
+description: Resume a paused workflow by sending a payload to a hook token.
 ---
 
 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,5 +1,6 @@
 ---
 title: resumeWebhook
+description: Resume a paused workflow by sending an HTTP request to a webhook token.
 ---
 
 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,5 +1,6 @@
 ---
 title: start
+description: Start and enqueue a new workflow run.
 ---
 
 Start/enqueue a new workflow run.

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

@@ -1,5 +1,6 @@
 ---
 title: "workflow/next"
+description: Next.js integration for automatic bundling and runtime configuration.
 ---
 
 Next.js integration for Workflow DevKit that automatically configures bundling and runtime support.

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

@@ -1,5 +1,6 @@
 ---
 title: withWorkflow
+description: Configure webpack/turbopack to transform workflow directives in Next.js.
 ---
 
 Configures webpack/turbopack loaders to transform workflow code (`"use step"`/`"use workflow"` directives)
@@ -48,42 +49,4 @@ export default async function config(
   }
   return nextConfig;
 }
-```
-
-## Configuration
-
-The second argument to `withWorkflow` accepts the following options:
-
-### `workflows.dirs`
-
-Directories to scan for workflows and steps. If provided, this completely overrides the defaults.
-
-- **Type:** `string[]`
-- **Default:** `['pages', 'app', 'src/pages', 'src/app']`
-
-```typescript title="next.config.ts" lineNumbers
-import { withWorkflow } from "workflow/next";
-import type { NextConfig } from "next";
-
-const nextConfig: NextConfig = {};
-
-export default withWorkflow(nextConfig, {
-  workflows: {
-    dirs: ['workflows', 'src/workflows'], // [!code highlight]
-  },
-});
-```
-
-### `workflows.local.port`
-
-Port for the local workflow server during development.
-
-- **Type:** `number`
-- **Default:** Uses the `PORT` environment variable
-
-### `workflows.local.dataDir`
-
-Directory for storing local workflow data during development.
-
-- **Type:** `string`
-- **Default:** `'.next/workflow-data'`
+``` 

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

@@ -1,5 +1,6 @@
 ---
 title: Building a World
+description: Implement the World interface to run workflows on any custom infrastructure.
 ---
 
 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

@@ -1,6 +1,7 @@
 ---
 title: Deploying
 icon: Rocket
+description: Deploy workflows locally, on Vercel, or anywhere using pluggable World adapters.
 ---
 
 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,5 +1,6 @@
 ---
 title: Local World
+description: Zero-config world bundled with Workflow for local development. No external services required.
 ---
 
 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,5 +1,6 @@
 ---
 title: Postgres World
+description: Production-ready, self-hosted world using PostgreSQL for storage and pg-boss for job processing.
 ---
 
 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,5 +1,6 @@
 ---
 title: Vercel World
+description: Fully-managed world for Vercel deployments with automatic storage, queuing, and authentication.
 ---
 
 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.
@@ -126,3 +127,7 @@ For more details, see the [Vercel Workflow documentation](https://vercel.com/doc
 See the [Vercel Workflow documentation](https://vercel.com/docs/workflow) for current pricing and to learn more.
 
 For self-hosted deployments, use the [Postgres World](/worlds/postgres). For local development, use the [Local World](/worlds/local).
+
+## Limitations
+
+- **Single-region deployment** - The backend infrastructure is currently deployed only in `iad1`. Applications in other regions will route workflow requests to `iad1`, which may result in higher latency. For best performance, deploy your Vercel apps using Workflow to `iad1`. Global deployment is planned to colocate the backend closer to your applications.

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

@@ -1,5 +1,6 @@
 ---
 title: fetch-in-workflow
+description: Use the workflow fetch step function instead of global fetch in workflows.
 ---
 
 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,5 +1,6 @@
 ---
 title: hook-conflict
+description: Hook tokens must be unique across all running workflows in your project.
 ---
 
 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,5 +1,6 @@
 ---
 title: Errors
+description: Fix common mistakes when creating and executing workflows.
 ---
 
 Fix common mistakes when creating and executing workflows in the **Workflow DevKit**.

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

@@ -1,5 +1,6 @@
 ---
 title: node-js-module-in-workflow
+description: Move Node.js core module usage to step functions instead of workflows.
 ---
 
 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,5 +1,6 @@
 ---
 title: serialization-failed
+description: Ensure all data passed between workflow and step functions is serializable.
 ---
 
 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,5 +1,6 @@
 ---
 title: start-invalid-workflow-function
+description: Ensure you pass a valid workflow function to start() with proper configuration.
 ---
 
 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,5 +1,6 @@
 ---
 title: timeout-in-workflow
+description: Use the sleep function instead of setTimeout or setInterval in workflows.
 ---
 
 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,5 +1,6 @@
 ---
 title: webhook-invalid-respond-with-value
+description: The respondWith option must be "manual" or a Response object.
 ---
 
 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,5 +1,6 @@
 ---
 title: webhook-response-not-sent
+description: Manual webhooks must send a response before execution completes.
 ---
 
 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,5 +1,6 @@
 ---
 title: Common Patterns
+description: Implement distributed patterns using familiar async/await syntax with no new APIs to learn.
 ---
 
 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,5 +1,6 @@
 ---
 title: Errors & Retrying
+description: Customize retry behavior with FatalError and RetryableError for robust error handling.
 ---
 
 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,5 +1,6 @@
 ---
 title: Hooks & Webhooks
+description: Pause workflows and resume them later with external data, user interactions, or HTTP requests.
 ---
 
 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,5 +1,6 @@
 ---
 title: Idempotency
+description: Ensure operations can be safely retried without producing duplicate side effects.
 ---
 
 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,5 +1,6 @@
 ---
 title: Foundations
+description: Learn the core concepts of workflow programming to build durable, long-running applications.
 ---
 
 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,5 +1,6 @@
 ---
 title: Serialization
+description: Understand how workflow data is serialized and persisted across suspensions and resumptions.
 ---
 
 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,5 +1,6 @@
 ---
 title: Starting Workflows
+description: Trigger workflow execution with the start() function and track progress with Run objects.
 ---
 
 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,5 +1,6 @@
 ---
 title: Streaming
+description: Stream data in real-time to clients for progress updates and incremental content delivery.
 ---
 
 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,5 +1,6 @@
 ---
 title: Workflows and Steps
+description: Build long-running, stateful application logic that persists progress and resumes after failures.
 ---
 
 import { File, Folder, Files } from "fumadocs-ui/components/files";

package/docs/getting-started/astro.mdx

@@ -1,5 +1,6 @@
 ---
 title: Astro
+description: Set up your first durable workflow in an Astro application.
 ---
 
 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,5 +1,6 @@
 ---
 title: Express
+description: Set up your first durable workflow in an Express application.
 ---
 
 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,5 +1,6 @@
 ---
 title: Fastify
+description: Set up your first durable workflow in a Fastify application.
 ---
 
 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/index.mdx

@@ -62,6 +62,7 @@ import { Next, Nitro, SvelteKit, Nuxt, Hono, Bun, AstroDark, AstroLight, TanStac
       <div className="flex flex-col items-center justify-center gap-2">
         <Nest className="size-16" />
         <span className="font-medium">NestJS</span>
+        <Badge variant="secondary">Experimental</Badge>
       </div>
     </Card>
     <Card className="opacity-50">

package/docs/getting-started/nestjs.mdx

@@ -1,5 +1,6 @@
 ---
 title: NestJS
+description: Set up your first durable workflow in a NestJS application.
 ---
 
 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.
@@ -241,7 +242,8 @@ Taking a look at this code:
 
 To invoke your new workflow, update your controller with a new endpoint:
 
-{/* @skip-typecheck - NestJS decorators require special TypeScript config */}
+{/*@skip-typecheck - NestJS decorators require special TypeScript config*/}
+
 ```typescript title="src/app.controller.ts" lineNumbers
 import { Body, Controller, Post } from '@nestjs/common';
 import { start } from 'workflow/api';
@@ -288,7 +290,7 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-<img src="/o11y-ui.png" alt="Workflow DevKit Web UI" />
+![Workflow DevKit Web UI](/o11y-ui.png)
 
 </Step>
 
@@ -300,7 +302,8 @@ npx workflow inspect runs
 
 The `WorkflowModule.forRoot()` method accepts optional configuration:
 
-{/* @skip-typecheck - Configuration snippet, WorkflowModule not imported */}
+{/*@skip-typecheck - Configuration snippet, WorkflowModule not imported*/}
+
 ```typescript
 WorkflowModule.forRoot({
   // Directory to scan for workflow files (default: ['src'])

package/docs/getting-started/next.mdx

@@ -257,45 +257,6 @@ Check the [Deploying](/docs/deploying) section to learn how your workflows can b
 
 ## Troubleshooting
 
-### Out of Memory (OOM) during build
-
-When using `withWorkflow()` in a large Next.js application, the "Discovering workflow directives" phase may consume excessive memory, causing builds to fail with OOM errors on standard build machines (e.g., 16 GB RAM).
-
-**Solution:** Use the `workflows.dirs` option to limit the directories scanned for workflow directives. By default, `withWorkflow` scans `['pages', 'app', 'src/pages', 'src/app']`, which in large applications can include thousands of files.
-
-If your workflows are located in a specific directory, configure `dirs` to only scan that directory:
-
-```typescript title="next.config.ts" lineNumbers
-import { withWorkflow } from "workflow/next";
-import type { NextConfig } from "next";
-
-const nextConfig: NextConfig = {};
-
-export default withWorkflow(nextConfig, {
-  workflows: {
-    // Only scan the workflows directory instead of the entire app
-    dirs: ['workflows'], // [!code highlight]
-  },
-});
-```
-
-If you need workflows in both app routes and a dedicated directory:
-
-```typescript title="next.config.ts" lineNumbers
-import { withWorkflow } from "workflow/next";
-import type { NextConfig } from "next";
-
-const nextConfig: NextConfig = {};
-
-export default withWorkflow(nextConfig, {
-  workflows: {
-    dirs: ['app/api', 'workflows'], // [!code highlight]
-  },
-});
-```
-
-This significantly reduces memory usage and build times by avoiding scanning unrelated application code.
-
 ### Next.js 16.1+ compatibility
 
 If you see this error when upgrading to Next.js 16.1 or later:

package/docs/getting-started/vite.mdx

@@ -1,5 +1,6 @@
 ---
 title: Vite
+description: Set up your first durable workflow in a Vite application.
 ---
 
 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,5 +1,6 @@
 ---
 title: How the Directives Work
+description: Deep dive into the internals of how Workflow DevKit directives transform your code.
 ---
 
 <Callout>

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

@@ -1,5 +1,6 @@
 ---
 title: Event Sourcing
+description: Learn how Workflow DevKit uses event sourcing internally for debugging and observability.
 ---
 
 <Callout>

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

@@ -1,5 +1,6 @@
 ---
 title: Framework Integrations
+description: Guide for framework authors to integrate Workflow DevKit with custom frameworks or runtimes.
 ---
 
 <Callout>

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

@@ -1,5 +1,6 @@
 ---
 title: Understanding Directives
+description: Explore how JavaScript directives enable the Workflow DevKit's durable execution model.
 ---
 
 import { File, Folder, Files } from "fumadocs-ui/components/files";

package/docs/observability/index.mdx

@@ -1,5 +1,6 @@
 ---
 title: Observability
+description: Inspect, monitor, and debug workflows through the CLI and Web UI with powerful observability tools.
 ---
 
 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.51",
+  "version": "4.1.0-beta.53",
   "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.25",
-    "@workflow/cli": "4.1.0-beta.51",
-    "@workflow/core": "4.1.0-beta.51",
+    "@workflow/astro": "4.0.0-beta.27",
+    "@workflow/cli": "4.1.0-beta.53",
+    "@workflow/core": "4.1.0-beta.53",
     "@workflow/errors": "4.1.0-beta.14",
     "@workflow/typescript-plugin": "4.0.1-beta.4",
-    "@workflow/next": "4.0.1-beta.47",
-    "@workflow/nest": "0.0.0-beta.0",
-    "@workflow/nitro": "4.0.1-beta.46",
-    "@workflow/nuxt": "4.0.1-beta.35",
-    "@workflow/sveltekit": "4.0.0-beta.40",
-    "@workflow/rollup": "4.0.0-beta.9"
+    "@workflow/next": "4.0.1-beta.49",
+    "@workflow/nest": "0.0.0-beta.2",
+    "@workflow/nitro": "4.0.1-beta.48",
+    "@workflow/nuxt": "4.0.1-beta.37",
+    "@workflow/sveltekit": "4.0.0-beta.42",
+    "@workflow/rollup": "4.0.0-beta.10"
   },
   "devDependencies": {
     "@types/ms": "2.1.0",