workflow 5.0.0-beta.21 → 5.0.0-beta.23

package/docs/ai/index.mdx

@@ -3,6 +3,7 @@ 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 SDK.
+manualCards: true
 related:
   - /docs/foundations/workflows-and-steps
   - /docs/foundations/streaming

package/docs/changelog/turbo-mode.md

@@ -19,7 +19,7 @@ Turbo mode removes all three costs **for the first delivery of the first invocat
 
 When the handler detects the first delivery of the first invocation, it:
 
-1. **Backgrounds `run_started`.** The event is written without awaiting; the run entity is synthesized locally from the queued run input (status `running`, `startedAt` now) so replay can begin immediately. The `run_started` round-trip overlaps replay instead of blocking it. This reuses the [resilient start](./resilient-start) contract — `run_started` carrying the run input creates the run on the fly (synthetic `run_created`) if it doesn't exist yet.
+1. **Backgrounds `run_started`.** The event is written without awaiting; the run entity is synthesized locally from the queued run input (status `running`, `startedAt` now) so replay can begin immediately. The `run_started` round-trip overlaps replay instead of blocking it. This reuses the [resilient start](./resilient-start) contract — `run_started` carrying the run input creates the run on the fly (synthetic `run_created`) if it doesn't exist yet. Because turbo uses this `run_started` purely as a write barrier and never reads its response, it also asks the World to **skip the `run_started` event-log preload** (the list+resolve the World normally returns so a run can skip its first `events.list`). That preload would be wasted work here — and, since the first `step_started` is chained on the `run_started` barrier, trimming the `run_started` request directly shortens the wait before the first durable `step_started` (and therefore time-to-second-step). A World that ignores the hint stays correct; the runtime simply falls back to `events.list` if it ever needs the log.
 2. **Skips the initial event-log load.** Nothing has been written, so the first replay runs against an empty log. The second loop iteration does a normal incremental load once the first step's events exist.
 3. **Forces optimistic inline start** for that invocation, independent of `WORKFLOW_OPTIMISTIC_INLINE_START`. The step body runs immediately against locally-synthesized state; only the `step_started` network write waits for the backgrounded `run_started`.
 

package/docs/deploying/index.mdx

@@ -4,6 +4,7 @@ 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.
+manualCards: true
 related:
   - /docs/deploying/world/local-world
   - /docs/deploying/world/postgres-world

package/docs/errors/index.mdx

@@ -9,50 +9,7 @@ related:
 
 Fix common mistakes when creating and executing workflows in the **Workflow SDK**.
 
-<Cards>
-    <Card href="/docs/errors/fetch-in-workflow" title="fetch-in-workflow">
-        Learn how to use fetch in workflow functions.
-    </Card>
-    <Card href="/docs/errors/hook-conflict" title="hook-conflict">
-        Learn how to handle hook token conflicts between workflows.
-    </Card>
-    <Card href="/docs/errors/node-js-module-in-workflow" title="node-js-module-in-workflow">
-        Learn how to use Node.js modules in workflows.
-    </Card>
-    <Card href="/docs/errors/serialization-failed" title="serialization-failed">
-        Learn how to handle serialization failures in workflows.
-    </Card>
-    <Card href="/docs/errors/start-invalid-workflow-function" title="start-invalid-workflow-function">
-        Learn how to start an invalid workflow function.
-    </Card>
-    <Card href="/docs/errors/timeout-in-workflow" title="timeout-in-workflow">
-        Learn how to handle timing delays in workflow functions.
-    </Card>
-    <Card href="/docs/errors/webhook-invalid-respond-with-value" title="webhook-invalid-respond-with-value">
-        Learn how to use the correct `respondWith` values for webhooks.
-    </Card>
-    <Card href="/docs/errors/webhook-response-not-sent" title="webhook-response-not-sent">
-        Learn how to send responses when using manual webhook response mode.
-    </Card>
-    <Card href="/docs/errors/corrupted-event-log" title="corrupted-event-log">
-        Learn how to handle corrupted or invalid event logs.
-    </Card>
-    <Card href="/docs/errors/replay-divergence" title="replay-divergence">
-        Learn how workflow replay divergence is recovered automatically.
-    </Card>
-    <Card href="/docs/errors/step-not-registered" title="step-not-registered">
-        Resolve step not registered errors caused by deployment mismatches.
-    </Card>
-    <Card href="/docs/errors/step-executed-multiple-times" title="Step executed multiple times">
-        Diagnose duplicate step_started events from function crashes, timeouts, or OOMs.
-    </Card>
-    <Card href="/docs/errors/workflow-not-registered" title="workflow-not-registered">
-        Resolve workflow not registered errors caused by deployment mismatches.
-    </Card>
-    <Card href="/docs/errors/runtime-decryption-failed" title="runtime-decryption-failed">
-        Resolve runtime decryption failures from the SDK's encryption layer.
-    </Card>
-</Cards>
+<AutoCards />
 
 ## Learn More
 

package/docs/foundations/index.mdx

@@ -10,29 +10,4 @@ related:
 
 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.
 
-<Cards>
-    <Card href="/docs/foundations/workflows-and-steps" title="Workflows and Steps">
-        Learn about the building blocks of durability
-    </Card>
-    <Card href="/docs/foundations/starting-workflows" title="Starting Workflows">
-        Trigger workflows and track their execution using the `start()` function.
-    </Card>
-    <Card href="/docs/foundations/errors-and-retries" title="Errors & Retrying">
-        Types of errors and how retrying work in workflows.
-    </Card>
-    <Card href="/docs/foundations/hooks" title="Webhooks (and hooks)">
-        Respond to external events in your workflow using hooks and webhooks.
-    </Card>
-    <Card href="/docs/foundations/streaming" title="Streaming">
-        Stream data in real-time to clients without waiting for the workflow to complete.
-    </Card>
-    <Card href="/docs/foundations/serialization" title="Serialization">
-        Understand which types can be passed between workflow and step functions.
-    </Card>
-    <Card href="/docs/foundations/idempotency" title="Idempotency">
-        Prevent duplicate side effects when retrying operations.
-    </Card>
-    <Card href="/docs/foundations/versioning" title="Versioning">
-        Understand how runs stay pinned to deployments and when to opt in to newer code.
-    </Card>
-</Cards>
+<AutoCards />

package/docs/meta.json

@@ -1,6 +1,5 @@
 {
   "pages": [
-    "introduction",
     "---",
     "getting-started",
     "foundations",

package/docs/observability/index.mdx

@@ -79,11 +79,4 @@ When deployed to Vercel, workflow data is [encrypted end-to-end](/docs/how-it-wo
 
 ## More Observability Features
 
-<Cards>
-    <Card href="/docs/observability/tracing" title="Tracing">
-        Distributed tracing with OpenTelemetry for workflow runs, steps, and queue deliveries.
-    </Card>
-    <Card href="/docs/observability/attributes" title="Attributes">
-        Attach experimental metadata to workflow runs for observability.
-    </Card>
-</Cards>
+<AutoCards />

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "workflow",
-  "version": "5.0.0-beta.21",
+  "version": "5.0.0-beta.23",
   "description": "Workflow SDK - Build durable, resilient, and observable workflows",
   "main": "dist/typescript-plugin.cjs",
   "type": "module",
@@ -57,18 +57,18 @@
   },
   "dependencies": {
     "ms": "2.1.3",
-    "@workflow/astro": "5.0.0-beta.21",
-    "@workflow/cli": "5.0.0-beta.21",
+    "@workflow/astro": "5.0.0-beta.23",
+    "@workflow/cli": "5.0.0-beta.23",
+    "@workflow/core": "5.0.0-beta.23",
     "@workflow/errors": "5.0.0-beta.8",
     "@workflow/typescript-plugin": "5.0.0-beta.4",
     "@workflow/utils": "5.0.0-beta.4",
-    "@workflow/core": "5.0.0-beta.21",
-    "@workflow/next": "5.0.0-beta.21",
-    "@workflow/nest": "5.0.0-beta.21",
-    "@workflow/nitro": "5.0.0-beta.21",
-    "@workflow/nuxt": "5.0.0-beta.21",
-    "@workflow/sveltekit": "5.0.0-beta.21",
-    "@workflow/rollup": "5.0.0-beta.21"
+    "@workflow/next": "5.0.0-beta.23",
+    "@workflow/nest": "5.0.0-beta.23",
+    "@workflow/nitro": "5.0.0-beta.23",
+    "@workflow/nuxt": "5.0.0-beta.23",
+    "@workflow/sveltekit": "5.0.0-beta.23",
+    "@workflow/rollup": "5.0.0-beta.23"
   },
   "devDependencies": {
     "@types/ms": "2.1.0",