workflow 5.0.0-beta.35 → 5.0.0-beta.37

package/docs/migration-guides/migrating-from-inngest.mdx

@@ -1,308 +0,0 @@
----
-title: Migrating from Inngest
-description: Move an Inngest TypeScript SDK v3 or v4 app to the Workflow SDK by replacing createFunction, step.run(), step.sleep(), step.waitForEvent(), and step.invoke() with Workflows, Steps, Hooks, and start()/getRun().
-type: guide
-summary: Translate an Inngest app into the Workflow SDK with side-by-side code examples.
-prerequisites:
-  - /docs/getting-started/next
-  - /docs/foundations/workflows-and-steps
-related:
-  - /docs/foundations/starting-workflows
-  - /docs/foundations/errors-and-retries
-  - /docs/foundations/hooks
-  - /docs/foundations/streaming
-  - /docs/deploying/world/vercel-world
----
-
-<CopyPrompt
-  text="Migrate this Inngest code to Workflow SDK. Run `npm i workflow`. Replace each `inngest.createFunction` handler with an exported async function that contains `&quot;use workflow&quot;`. Replace each `step.run()` callback with a helper function that contains `&quot;use step&quot;`. Replace `step.sleep()` with `sleep()` from `workflow`. Replace event waits with `defineHook()` or `createWebhook()` from `workflow`, and resume them from server routes with `resumeHook()` or webhook requests. Start runs from API routes or server code with `start(workflowFn, args)` from `workflow/api`, and use `getRun(runId)` where callers need status, streams, cancellation, or results. Preserve retries by throwing normal errors for retryable failures and `FatalError` for permanent failures. Add a local test or route call that starts the migrated workflow and verifies the same observable behavior as the Inngest function."
-/>
-
-<Callout type="info">
-Install the Workflow SDK migration skill:
-
-```bash
-npx skills add https://github.com/vercel/workflow --skill migrating-to-workflow-sdk
-```
-</Callout>
-
-## Why migrate to the Workflow SDK
-
-- Streaming is built in. Durable progress writes go to named streams via `getWritable()`. There is no separate realtime publish channel or WebSocket layer to operate.
-- Infrastructure and orchestration live in a single deployment. Workflows run where the app runs. There is no separate Inngest Dev Server or event bus to operate.
-- TypeScript-first DX. Steps are named async functions marked with `"use step"`. No inline closures tied to a framework-specific lifecycle.
-- Agent-first tooling: the `npx workflow` CLI, `@workflow/ai` integration for durable AI agents, and a Claude skill for generating workflows.
-
-Inngest code samples in this guide use the v4 two-argument `createFunction({ id, triggers }, handler)` shape. If the app is still on Inngest v3, treat the three-argument form `createFunction({ id }, { event: '...' }, handler)` as equivalent — the `triggers` option in v4 replaces the second argument in v3.
-
-## What changes when you leave Inngest
-
-Inngest defines functions with `inngest.createFunction()`, registers them through a `serve()` handler, and breaks work into steps with `step.run()`, `step.sleep()`, and `step.waitForEvent()`. The platform routes events, schedules steps, and applies retries.
-
-The Workflow SDK replaces that with `"use workflow"` functions that orchestrate `"use step"` functions in plain TypeScript. There is no function registry, event dispatch layer, or SDK client. Durable replay, automatic retries, and step-level persistence are built into the runtime.
-
-Migration collapses the SDK abstraction into plain async functions. Business logic stays the same.
-
-<Callout type="info">
-Inngest's event-bus model is loosely coupled — publishers don't know consumers. `start()` requires the caller to import the workflow function directly, giving stronger type safety but tighter coupling. For event-bus-like fan-out, wrap `start()` in a shared publisher module.
-</Callout>
-
-## Concept mapping
-
-| Inngest | Workflow SDK | Migration note |
-| --- | --- | --- |
-| `inngest.createFunction()` | `"use workflow"` function started with `start()` | No wrapper needed. |
-| `step.run()` | `"use step"` function | Standalone async function with Node.js access. |
-| `step.sleep()` / `step.sleepUntil()` | `sleep()` | `sleep('5m')` for a duration; `sleep(date)` for sleep-until. |
-| `step.waitForEvent()` | `createHook()` or `createWebhook()` | Hooks for typed signals, webhooks for HTTP. |
-| `step.invoke()` | `start()` plus a `"use step"` wrapper around `getRun()` | Spawn a child run, pass `runId` forward, and collect from a step when needed. |
-| `inngest.send()` / event triggers | `start()` from your app boundary | Start workflows directly. |
-| Retry configuration (`retries`) | `RetryableError`, `FatalError`, `maxRetries` | Retry logic lives at the step level. |
-| `step.sendEvent()` | `start()` from the workflow or app boundary | Fan out explicitly, not through an event bus. |
-| Realtime / `step.realtime.publish()` | `getWritable()` / `getWritable({ namespace })` | Named streams are the canonical way for clients to read workflow status. No database or `getRun()` polling required. |
-
-## Translate your first workflow
-
-Start with the shell of a function. Inngest wraps it in `createFunction`; Workflow SDK marks it with a directive.
-
-{/* @skip-typecheck: Inngest SDK types not available */}
-```typescript title="inngest/functions/order.ts"
-export const processOrder = inngest.createFunction(
-  {
-    id: 'process-order',
-    triggers: { event: 'order/created' },
-  },
-  async ({ event, step }) => {
-    return { orderId: event.data.orderId, status: 'completed' };
-  }
-);
-```
-
-```typescript title="workflow/workflows/order.ts"
-export async function processOrder(orderId: string) {
-  'use workflow'; // [!code highlight]
-  return { orderId, status: 'completed' };
-}
-```
-
-**What changed:** the factory + event binding collapses into a plain exported function with a `"use workflow"` directive.
-
-### Add a step
-
-`step.run()` closures become named `"use step"` functions.
-
-```typescript title="workflow/workflows/order.ts"
-async function loadOrder(orderId: string) {
-  'use step'; // [!code highlight]
-  const res = await fetch(`https://example.com/api/orders/${orderId}`);
-  return res.json() as Promise<{ id: string }>;
-}
-```
-
-Call it from the workflow like any async function: `const order = await loadOrder(orderId)`. Additional side effects (`reserveInventory`, `chargePayment`) follow the same shape.
-
-### Start the run
-
-Inngest dispatches via `inngest.send({ name: 'order/created', data: { orderId } })`. Workflow SDK launches directly:
-
-```typescript title="app/api/orders/route.ts"
-import { start } from 'workflow/api';
-import { processOrder } from '@/workflows/order';
-
-const run = await start(processOrder, [orderId]); // [!code highlight]
-```
-
-No event bus, no registry. `start()` returns a handle immediately.
-
-## Wait for an external signal
-
-`step.waitForEvent()` becomes `createHook()` plus `await`.
-
-```typescript title="workflow/workflows/refund.ts (Inngest)"
-const approval = await step.waitForEvent('wait-for-approval', {
-  event: 'refund/approved',
-  match: 'data.refundId',
-  timeout: '7d',
-});
-```
-
-{/* @skip-typecheck: snippet without imports */}
-```typescript title="workflow/workflows/refund.ts (Workflow SDK)"
-using approval = createHook<{ approved: boolean }>({ // [!code highlight]
-  token: `refund:${refundId}:approval`,
-});
-const payload = await approval;
-```
-
-**What changed:** event name + match expression collapse into a single `token` string. The caller supplies that token directly, with no event schema.
-
-### Resume from an API route
-
-Inngest resumes with `inngest.send({ name: 'refund/approved', data: { refundId, approved } })`. The SDK equivalent is `resumeHook`:
-
-```typescript title="app/api/refunds/[refundId]/approve/route.ts"
-import { resumeHook } from 'workflow/api';
-
-export async function POST(request: Request, { params }: { params: Promise<{ refundId: string }> }) {
-  const { refundId } = await params;
-  const { approved } = (await request.json()) as { approved: boolean };
-  await resumeHook(`refund:${refundId}:approval`, { approved }); // [!code highlight]
-  return Response.json({ ok: true });
-}
-```
-
-### Add a timeout and branch on the payload
-
-Inngest's `timeout: '7d'` option maps to a `Promise.race()` with `sleep()`:
-
-{/* @skip-typecheck: continuation snippet */}
-```typescript title="workflow/workflows/refund.ts"
-const result = await Promise.race([
-  approval.then((p) => ({ type: 'decision' as const, approved: p.approved })),
-  sleep('7d').then(() => ({ type: 'timeout' as const })), // [!code highlight]
-]);
-
-if (result.type === 'timeout') return { refundId, status: 'timed-out' };
-if (!result.approved) return { refundId, status: 'rejected' };
-return { refundId, status: 'approved' };
-```
-
-<Callout type="info">
-Event matching disappears. A hook's token encodes the routing (for example, `refund:${refundId}:approval`), and the caller supplies that token to `resumeHook()`.
-</Callout>
-
-## Spawn a child workflow
-
-`step.invoke()` splits into spawn and collect. In v5, call `start()` directly from the workflow to spawn the child. Wrap `getRun()` and `returnValue` access in a `"use step"` function when you need to collect the result. Returning the `Run` object from `start()` lets observability deep-link into the child run.
-
-You can return either the full `Run` object (enables deep-linking) or just `run.runId` (simpler).
-
-{/* @skip-typecheck: snippet without imports */}
-```typescript title="workflow/workflows/parent.ts"
-async function collectResult(runId: string) {
-  'use step';
-  const run = getRun(runId);
-  return await run.returnValue; // [!code highlight]
-}
-
-export async function parentWorkflow(item: string) {
-  'use workflow';
-  const child = await start(childWorkflow, [item]); // [!code highlight]
-  return await collectResult(child.runId);
-}
-```
-
-## What you stop operating
-
-Dropping the Inngest SDK removes several moving parts:
-
-- **No SDK client or serve handler.** Workflow files carry directive annotations. No registry, no serve endpoint.
-- **No event bus.** `start()` launches workflows directly from API routes, server actions, or other entry points. No event schemas or dispatch layer.
-- **No inline step closures.** Steps are named async functions. They type-check and test like any other TypeScript function.
-- **No separate streaming transport.** `getWritable()` delivers progress to clients without WebSockets or SSE glue.
-- **No idle workers.** Workflows suspended on `sleep()` or a hook consume no compute until resumed.
-
-## Step-by-step first migration
-
-Pick one Inngest function and migrate it end-to-end before touching the rest. The steps below describe the smallest viable path.
-
-### Step 1: Install the Workflow SDK
-
-Install the SDK. Framework integrations (`workflow/next`, `workflow/nitro`, `workflow/nuxt`, etc.) are subpath exports of the same `workflow` package — no additional install needed.
-
-```bash
-pnpm add workflow
-```
-
-### Step 2: Convert `createFunction` to a `"use workflow"` export
-
-Replace the factory call with a plain async export. Move the handler body up. The event-binding argument goes away.
-
-```ts title="workflows/order.ts"
-// Before (Inngest)
-// export const processOrder = inngest.createFunction(
-//   { id: "process-order", triggers: { event: "order/created" } },
-//   async ({ event, step }) => { ... }
-// );
-
-// After (Workflow SDK)
-export async function processOrder(orderId: string) {
-  "use workflow"; // [!code highlight]
-  // ...
-}
-```
-
-### Step 3: Convert `step.run` callbacks into named step functions
-
-Each inline callback becomes a named function with `"use step"` on the first line. The workflow calls them with a plain `await`.
-
-```ts
-async function loadOrder(id: string) {
-  "use step"; // [!code highlight]
-  return fetch(`https://example.com/api/orders/${id}`).then((r) => r.json());
-}
-```
-
-Configure per-step retry counts by assigning `maxRetries` as a function property:
-
-```ts
-async function callApi(endpoint: string) {
-  "use step";
-  const response = await fetch(endpoint);
-  return response.json();
-}
-callApi.maxRetries = 5;
-```
-
-See [Errors and retries](/docs/foundations/errors-and-retries) for full retry docs.
-
-### Step 4: Replace `waitForEvent`, `sleep`, and `invoke`
-
-- `step.waitForEvent(...)` → `createHook({ token })` + `await hook`. Resume it from an API route with `resumeHook(token, payload)`.
-- `step.sleep(...)` → `sleep("5m")` from `workflow`.
-- `step.invoke(child, { data })` → call `start(child, [data])` from the workflow, and optionally read its return value from a step with `getRun(run.runId).returnValue`.
-
-### Step 5: Start runs from the app
-
-Delete the `serve()` handler and event dispatch. Launch runs directly from an API route:
-
-```ts title="app/api/orders/route.ts"
-import { start } from "workflow/api";
-import { processOrder } from "@/workflows/order";
-
-export async function POST(req: Request) {
-  const { orderId } = await req.json();
-  const run = await start(processOrder, [orderId]);
-  return Response.json({ runId: run.runId });
-}
-```
-
-### Step 6: Retire the Inngest infrastructure
-
-Remove the `inngest` client, the `serve()` route, event schemas, and the Inngest Dev Server from the app. Verify the run in `npx workflow web` before shipping.
-
-## Features without a 1:1 equivalent
-
-- **Cron / scheduled functions (`triggers: { cron: '...' }`).** The SDK has no built-in scheduler. Trigger runs from Vercel Cron or a system cron calling `start()` from an API route.
-- **Concurrency, throttling, rate limiting, debounce, singleton, priority, and `batchEvents`.** These function-level settings have no direct analog. Enforce limits inside steps (semaphores, external rate-limiter service) or debounce at the publisher before calling `start()`.
-- **`EventSchemas` / typed events.** The event-bus indirection goes away; publishers import the workflow function directly, giving the same type safety through a different mechanism.
-- **Event-bus fan-out by name match.** `inngest.send()` that triggered multiple functions by event name must be replaced by explicit `start()` calls for each target workflow.
-
-## Quick-start checklist
-
-- Replace `inngest.createFunction()` with a `"use workflow"` function; launch it with `start()`.
-- Convert each `step.run()` callback into a named `"use step"` function.
-- Swap `step.sleep()` / `step.sleepUntil()` for `sleep()` from `workflow`.
-- Swap `step.waitForEvent()` for `createHook()` (internal) or `createWebhook()` (HTTP).
-- Model `waitForEvent` timeouts as `Promise.race()` between the hook and `sleep()`.
-- Replace `step.invoke()` with direct `start()` calls and a `"use step"` wrapper around `getRun()` when collecting results.
-- Replace `step.sendEvent()` fan-out with explicit `start()` calls.
-- Remove the Inngest client, `serve()` handler, and event definitions.
-- Push retry configuration down to step boundaries via `maxRetries`, `RetryableError`, and `FatalError`.
-- Use `getStepMetadata().stepId` as the idempotency key for external side effects.
-- Replace `step.realtime.publish()` with `getWritable()`.
-- Deploy and verify end-to-end with the built-in observability UI.
-
----
-
-*Verified against `workflow@5.0.0-beta.1` and Inngest TypeScript SDK v4 on 2026-04-16.*

package/docs/migration-guides/migrating-from-temporal.mdx

@@ -1,317 +0,0 @@
----
-title: Migrating from Temporal
-description: Move a Temporal TypeScript workflow to the Workflow SDK by replacing Activities, Workers, Signals, and Child Workflows with Workflows, Steps, Hooks, and start()/getRun().
-type: guide
-summary: Translate a Temporal app into the Workflow SDK with side-by-side code examples.
-prerequisites:
-  - /docs/getting-started/next
-  - /docs/foundations/workflows-and-steps
-related:
-  - /docs/foundations/starting-workflows
-  - /docs/foundations/errors-and-retries
-  - /docs/foundations/hooks
-  - /docs/foundations/streaming
-  - /docs/deploying/world/vercel-world
----
-
-<CopyPrompt
-  text="Refactor this Temporal TypeScript code to Workflow SDK. Run `npm i workflow`. Replace Temporal workflow functions with exported async functions containing `&quot;use workflow&quot;`. Replace Activities with helper functions containing `&quot;use step&quot;`. Replace timers with `sleep()` from `workflow`. Replace Signals with `defineHook()` plus `resumeHook()` from `workflow/api`, or `createWebhook()` when an HTTP callback URL is needed. Replace Child Workflows with `start(childWorkflow, args)` and coordinate completion with hooks or `getRun()`. Remove Temporal workers; instead expose API routes or server functions that call `start()` and `getRun()` from `workflow/api`. Preserve idempotency and retries with normal errors, `RetryableError`, and `FatalError`, then add a verification path for each migrated workflow."
-/>
-
-<Callout type="info">
-Install the Workflow SDK migration skill:
-
-```bash
-npx skills add https://github.com/vercel/workflow --skill migrating-to-workflow-sdk
-```
-</Callout>
-
-## Why migrate to the Workflow SDK
-
-- Streaming is built in. Durable progress writes go to named streams via `getWritable({ namespace })`, and clients read them directly. No separate WebSocket, SSE, or progress-polling layer to operate.
-- Infrastructure and orchestration live in a single deployment. There is no separate Worker fleet or Temporal Server to run. The runtime, step logic, and orchestration share the app's observability and log aggregation.
-- TypeScript-first developer experience. Workflows and steps live in the same file with plain `await` control flow, `try/catch`, and `Promise.all`.
-- Agent-first tooling. A first-class CLI (`npx workflow`), [`@workflow/ai` integration for durable AI agents](/docs/ai), and a bundled Claude skill for AI-assisted authoring.
-- Per-step retry controls. `RetryableError`, `FatalError`, and `maxRetries` live at the step boundary instead of an Activity-level retry policy configured elsewhere.
-
-## What changes when you leave Temporal
-
-Temporal requires operating a control plane (Temporal Server or Cloud), a Worker fleet, Activity modules wired through `proxyActivities`, and Task Queues. The workflow code is durable; the surrounding infrastructure is substantial.
-
-The Workflow SDK runs on managed infrastructure. Write `"use workflow"` functions that orchestrate `"use step"` functions in the same file, in plain TypeScript. There are no Workers, Task Queues, or separate Activity modules. Durable replay, automatic retries, and event history are handled by the runtime.
-
-Workflow functions must still be deterministic — no `Date.now()`, `Math.random()`, direct network I/O, or wall-clock branches inside `"use workflow"`. Move any such logic into a step, as you do today with Activities.
-
-Migration removes infrastructure and collapses indirection. Business logic stays as regular async TypeScript.
-
-## Concept mapping
-
-| Temporal | Workflow SDK | Migration note |
-| --- | --- | --- |
-| Workflow Definition / Workflow Execution | `"use workflow"` function / run started with `start()` | Keep orchestration code in the workflow function. |
-| Activity | `"use step"` function | Put side effects and Node.js access in steps. |
-| Worker + Task Queue | Managed execution | No worker fleet or polling loop to operate. |
-| Signal | `createHook()` or `createWebhook()` | Use hooks for typed resume signals; webhooks for HTTP callbacks. |
-| Query | `getWritable({ namespace: 'status' })` stream | Durably stream status updates from the workflow. Clients read from the stream instead of polling a database. |
-| Update | `createHook()` + `resumeHook()` (one-way) | Temporal Updates return a value to the caller; hooks do not. If the Update returns data, either write the result to a named stream via `getWritable()` and have the caller read from it, or keep an HTTP read route that fetches the workflow's current state. |
-| Child Workflow | `start()` plus a `"use step"` wrapper around `getRun()` | Spawn a child run and return the `Run` object so observability can deep-link into child runs. |
-| Activity retry policy | Step retries, `RetryableError`, `FatalError`, `maxRetries` | Retries live at the step boundary. |
-| Event History | Workflow event log / run timeline | Same durable replay; built-in observability UI replaces Temporal Web. Search attributes and visibility APIs have no direct equivalent — filter by run status and timestamps instead. |
-
-## Translate your first workflow
-
-### Minimal translation
-
-Start with the directive change. The Temporal definition proxies activities through a module; the Workflow SDK version puts the directive inline.
-
-{/* @skip-typecheck: Temporal SDK types not available */}
-```typescript title="workflows/order.ts (Temporal)"
-import * as wf from '@temporalio/workflow';
-import type * as activities from './activities';
-
-const { chargePayment } = wf.proxyActivities<typeof activities>({
-  startToCloseTimeout: '5 minutes',
-});
-
-export async function processOrder(orderId: string) {
-  await chargePayment(orderId);
-  return { orderId, status: 'completed' };
-}
-```
-
-```typescript title="workflows/order.ts (Workflow SDK)"
-export async function processOrder(orderId: string) {
-  'use workflow'; // [!code highlight]
-  await chargePayment(orderId);
-  return { orderId, status: 'completed' };
-}
-```
-
-**What changed:** `proxyActivities` and the activity module disappear. The orchestrator is plain async TypeScript marked with `"use workflow"`.
-
-### Adding a step
-
-Side effects move into a colocated `"use step"` function:
-
-```typescript title="workflow/workflows/order.ts"
-async function chargePayment(orderId: string) {
-  'use step'; // [!code highlight]
-  await fetch(`https://example.com/api/orders/${orderId}/charge`, {
-    method: 'POST',
-  });
-}
-```
-
-Additional steps (`loadOrder`, `reserveInventory`) follow the same shape and can be called from the workflow in sequence.
-
-### Starting the run
-
-Replace Worker + Task Queue wiring with a single `start()` call from an API route:
-
-```typescript title="app/api/orders/route.ts"
-import { start } from 'workflow/api';
-import { processOrder } from '@/workflows/order';
-
-export async function POST(request: Request) {
-  const { orderId } = (await request.json()) as { orderId: string };
-  const run = await start(processOrder, [orderId]); // [!code highlight]
-  return Response.json({ runId: run.runId });
-}
-```
-
-## Wait for an external signal
-
-### Minimal translation
-
-Temporal needs a signal definition, a handler, and a `condition()` guard. The Workflow SDK collapses all three into a single `createHook()` + `await`.
-
-{/* @skip-typecheck: Temporal SDK types not available */}
-```typescript title="temporal/workflows/refund.ts"
-export const approveRefund = wf.defineSignal<[boolean]>('approveRefund');
-
-export async function refundWorkflow(refundId: string) {
-  let approved: boolean | undefined;
-  wf.setHandler(approveRefund, (v) => { approved = v; });
-  await wf.condition(() => approved !== undefined);
-  return { refundId, approved };
-}
-```
-
-```typescript title="workflow/workflows/refund.ts"
-import { createHook } from 'workflow';
-
-export async function refundWorkflow(refundId: string) {
-  'use workflow';
-  using approval = createHook<{ approved: boolean }>({
-    token: `refund:${refundId}:approval`, // [!code highlight]
-  });
-  const { approved } = await approval; // [!code highlight]
-  return { refundId, approved };
-}
-```
-
-The workflow suspends durably at `await approval` until resumed. No polling, no handler registration.
-
-Requires TypeScript 5.2+ for the `using` keyword. On older TypeScript, assign the hook to a `const` and call `resumeHook()` from the consuming code path.
-
-### Resuming from an API route
-
-Any HTTP caller can resume by token:
-
-```typescript title="app/api/refunds/[refundId]/approve/route.ts"
-import { resumeHook } from 'workflow/api';
-
-export async function POST(request: Request, { params }: { params: Promise<{ refundId: string }> }) {
-  const { refundId } = await params;
-  const body = (await request.json()) as { approved: boolean };
-  await resumeHook(`refund:${refundId}:approval`, body); // [!code highlight]
-  return Response.json({ ok: true });
-}
-```
-
-<Callout type="info">
-Temporal Queries expose in-memory workflow state on demand. In the Workflow SDK, the equivalent is a durable stream: call `getWritable({ namespace: 'status' })` from inside the workflow to write status updates, and have clients read from the end of that stream to get the current state. Hooks are the write channel for resuming a paused workflow with new data.
-</Callout>
-
-## Spawn a child workflow
-
-### Minimal translation
-
-In v5, call `start()` directly from the workflow to spawn a child run. Wrap `getRun()` and `returnValue` access in a `"use step"` function when you need to await the child result. Return the `Run` object (not a plain `runId` string) so workflow observability can deep-link into child runs.
-
-```typescript title="workflow/workflows/parent.ts"
-import { start } from 'workflow/api';
-
-export async function parentWorkflow(item: string) {
-  'use workflow';
-  const child = await start(childWorkflow, [item]); // [!code highlight]
-  return { childRunId: child.runId };
-}
-```
-
-### Awaiting the child's return value
-
-A second step fetches the run and awaits `returnValue`:
-
-```typescript title="workflow/workflows/parent.ts"
-import { getRun } from 'workflow/api';
-
-async function collectResult(runId: string) {
-  'use step';
-  const run = getRun(runId);
-  return (await run.returnValue) as { item: string; result: string }; // [!code highlight]
-}
-```
-
-Call `start()` and then `collectResult()` from the parent in sequence: `const result = await collectResult(child.runId)`. To fan out, call `start()` inside a loop, then `Promise.all` the `collectResult` calls.
-
-<Callout type="warn">
-Activity retry policy moves to the step boundary. Use `maxRetries`, `RetryableError`, and `FatalError` on each step instead of a single workflow-wide retry block.
-
-Temporal's per-activity timeouts (`startToCloseTimeout`, `scheduleToCloseTimeout`, `heartbeatTimeout`) have no direct Workflow SDK equivalent. Enforce per-step deadlines inside the step using `AbortSignal.timeout(ms)` (e.g. on `fetch`), or wrap the call from the workflow in `Promise.race(step(), sleep('5m'))` to bail out after a bounded duration.
-
-Temporal's retry policy knobs (`initialInterval`, `backoffCoefficient`, `maximumInterval`, `nonRetryableErrorTypes`) don't port 1:1 — only `maxRetries` is configurable at the step boundary. Classify retryability with `RetryableError` (retryable) and `FatalError` (terminal) instead of listing error types, and control the delay between attempts with `new RetryableError(msg, { retryAfter: '5s' })`.
-
-Set `maxRetries` as a property assignment on the step function:
-
-```typescript
-async function chargePayment(orderId: string) {
-  "use step";
-  // ...
-}
-chargePayment.maxRetries = 5;
-```
-
-See [/docs/foundations/errors-and-retries](/docs/foundations/errors-and-retries) for full retry docs.
-</Callout>
-
-## What you stop operating
-
-- **Temporal Server or Cloud.** Durable state lives in the managed event log.
-- **Worker fleet.** The runtime schedules execution; workflows run where the app runs.
-- **Task Queues.** No queue routing to configure or monitor.
-- **Activity modules and `proxyActivities`.** Steps live next to the workflow that calls them.
-- **Custom progress transport.** `getWritable()` streams updates from steps.
-
-Suspended workflows (on `sleep()` or a hook) consume no compute until resumed.
-
-## Step-by-step first migration
-
-Pick one Temporal workflow and migrate it end-to-end before touching the rest. The steps below describe the smallest viable path.
-
-### Step 1: Install the Workflow SDK
-
-Add the runtime. The Next.js integration ships as a subpath (`workflow/next`) of the same package.
-
-```bash
-pnpm add workflow
-```
-
-### Step 2: Collapse Activities into step functions
-
-Delete the `activities/` module and the `proxyActivities` call. Each former Activity becomes a plain async function with `"use step"` on the first line, living next to the orchestrator.
-
-```ts title="workflows/order.ts"
-async function loadOrder(id: string) {
-  "use step"; // [!code highlight]
-  return fetch(`/api/orders/${id}`).then((r) => r.json());
-}
-```
-
-### Step 3: Mark the orchestrator with `"use workflow"`
-
-Keep the existing control flow: `await`, `try/catch`, `Promise.all`. The directive turns the function into a durable replay target.
-
-```ts
-export async function processOrder(orderId: string) {
-  "use workflow"; // [!code highlight]
-  const order = await loadOrder(orderId);
-  // ...
-}
-```
-
-### Step 4: Replace Signals with hooks
-
-Swap `defineSignal` + `setHandler` for `createHook()`. Callers `resumeHook(token, payload)` instead of `handle.signal(signalDef, payload)` on a `WorkflowHandle` obtained from `client.workflow.getHandle(workflowId)`.
-
-### Step 5: Start runs from an API route or server action
-
-Delete the Worker bootstrap. Launch runs from an API route or server action with `start()`:
-
-```ts title="app/api/orders/route.ts"
-import { start } from "workflow/api";
-import { processOrder } from "@/workflows/order";
-
-export async function POST(req: Request) {
-  const { orderId } = await req.json();
-  const run = await start(processOrder, [orderId]);
-  return Response.json({ runId: run.runId });
-}
-```
-
-### Step 6: Retire the Temporal infrastructure
-
-Remove the Worker process, `@temporalio/*` dependencies, and the Temporal Server or Cloud connection. Verify the run in the built-in observability UI (`npx workflow web`) before shipping.
-
-## Features without a 1:1 equivalent
-
-- **Search attributes / visibility queries.** Temporal's search attribute system has no direct analog. Filter runs by status and timestamps via `getRun()` / observability UI.
-- **Event history archival.** Temporal archives histories to S3/GCS for long-term retention. Workflow SDK event logs are durable, but retention depends on the integration you are using. For example, see [Vercel Workflow Storage Retention](https://vercel.com/docs/workflows/pricing#storage-retention) for Vercel.
-- **Per-activity timeouts (`startToCloseTimeout`, `scheduleToCloseTimeout`, `heartbeatTimeout`).** Implement deadlines inside the step with `AbortSignal.timeout(ms)`, or wrap the call in `Promise.race(step(), sleep(...))` from the workflow.
-- **Rich retry policy (`initialInterval`, `backoffCoefficient`, `maximumInterval`, `nonRetryableErrorTypes`).** Only `maxRetries` is configurable. Classify retryability with `RetryableError`/`FatalError`; control delay between attempts via `new RetryableError(msg, { retryAfter: '5s' })`.
-- **Workers + task queues.** Managed deployments replace workers; self-hosted deployments still need a `World` implementation (see [/docs/deploying/building-a-world](/docs/deploying/building-a-world)).
-
-## Quick-start checklist
-
-- Move orchestration into a `"use workflow"` function.
-- Convert each Activity into a `"use step"` function.
-- Remove Worker and Task Queue code. Start workflows from the app with `start()`.
-- Replace Signals with `createHook()` or `createWebhook()` for HTTP callers.
-- Use `start()` directly for child workflows, and wrap `getRun()` in a `"use step"` function when collecting results. Return the `Run` object from `start()` so observability can deep-link into child runs.
-- Set retry policy per step with `maxRetries`, `RetryableError`, and `FatalError`.
-- Use `getStepMetadata().stepId` as the idempotency key for external side effects.
-- Stream status and progress from steps with `getWritable({ namespace: 'status' })`, and have clients read from the stream instead of polling.
-- Deploy the app and verify runs end-to-end in the built-in observability UI.
-
----
-*Verified against `workflow@5.0.0-beta.1` and `@temporalio/workflow@1.16` on 2026-04-16.*