workflow 4.2.0-beta.72 → 4.2.0-beta.74

package/docs/getting-started/astro.mdx

@@ -2,7 +2,7 @@
 title: Astro
 description: Set up your first durable workflow in an Astro application.
 type: guide
-summary: Set up Workflow DevKit in an Astro app.
+summary: Set up Workflow SDK in an Astro app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -105,7 +105,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 * We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-* The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+* The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -210,20 +210,20 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:4321/api/si
 
 Check the Astro development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 npx workflow inspect runs
 # or add '--web' for an interactive Web based UI
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 ---
 
 ## Deploying to Production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/express.mdx

@@ -2,7 +2,7 @@
 title: Express
 description: Set up your first durable workflow in an Express application.
 type: guide
-summary: Set up Workflow DevKit in an Express app.
+summary: Set up Workflow SDK in an Express app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -136,7 +136,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 - We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-- The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+- The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -237,7 +237,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Express development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -246,7 +246,7 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 </Step>
 
@@ -256,7 +256,7 @@ npx workflow inspect runs
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/fastify.mdx

@@ -2,7 +2,7 @@
 title: Fastify
 description: Set up your first durable workflow in a Fastify application.
 type: guide
-summary: Set up Workflow DevKit in a Fastify app.
+summary: Set up Workflow SDK in a Fastify app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -135,7 +135,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 - We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-- The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+- The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 ## Create Your Workflow Steps
 
 Let's now define those missing functions:
@@ -227,13 +227,13 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Fastify development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 npx workflow inspect runs # add '--web' for an interactive Web based UI
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 </Step>
 
@@ -243,7 +243,7 @@ npx workflow inspect runs # add '--web' for an interactive Web based UI
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/hono.mdx

@@ -2,7 +2,7 @@
 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.
+summary: Set up Workflow SDK in a Hono app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -121,7 +121,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 - We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-- The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+- The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -221,7 +221,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Hono development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -230,7 +230,7 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 </Step>
 
@@ -238,7 +238,7 @@ npx workflow inspect runs
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/nestjs.mdx

@@ -2,7 +2,7 @@
 title: NestJS
 description: Set up your first durable workflow in a NestJS application.
 type: guide
-summary: Set up Workflow DevKit in a NestJS app.
+summary: Set up Workflow SDK in a NestJS app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -59,7 +59,7 @@ When using ESM with NestJS, local imports must include the `.js` extension (e.g.
 
 ### Configure NestJS to use SWC
 
-NestJS supports SWC as an alternative compiler for faster builds. The Workflow DevKit uses an SWC plugin to transform workflow files.
+NestJS supports SWC as an alternative compiler for faster builds. The Workflow SDK uses an SWC plugin to transform workflow files.
 
 Install the required SWC packages:
 
@@ -190,7 +190,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 - We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-- The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+- The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -291,7 +291,7 @@ curl -X POST -H "Content-Type: application/json" -d '{"email":"hello@example.com
 
 Check the NestJS development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -300,7 +300,7 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 </Step>
 

package/docs/getting-started/next.mdx

@@ -2,7 +2,7 @@
 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.
+summary: Set up Workflow SDK in a Next.js app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -141,7 +141,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 * We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-* The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+* The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -245,7 +245,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Next.js development server logs to see your workflow execute, as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -254,11 +254,11 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and need no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and need no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/nitro.mdx

@@ -2,7 +2,7 @@
 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.
+summary: Set up Workflow SDK in a Nitro app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -101,7 +101,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 - We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-- The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+- The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -205,7 +205,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Nitro development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -214,7 +214,7 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 </Step>
 
@@ -222,7 +222,7 @@ npx workflow inspect runs
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/nuxt.mdx

@@ -2,7 +2,7 @@
 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.
+summary: Set up Workflow SDK in a Nuxt app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -100,7 +100,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 - We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-- The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+- The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -206,7 +206,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Nuxt development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -215,7 +215,7 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 </Step>
 
@@ -223,7 +223,7 @@ npx workflow inspect runs
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/sveltekit.mdx

@@ -2,7 +2,7 @@
 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.
+summary: Set up Workflow SDK in a SvelteKit app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -102,7 +102,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 * We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-* The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+* The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -209,7 +209,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:5173/api/si
 
 Check the SvelteKit development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -218,11 +218,11 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

package/docs/getting-started/vite.mdx

@@ -2,7 +2,7 @@
 title: Vite
 description: Set up your first durable workflow in a Vite application.
 type: guide
-summary: Set up Workflow DevKit in a Vite app.
+summary: Set up Workflow SDK in a Vite app.
 prerequisites:
   - /docs/getting-started
 related:
@@ -111,7 +111,7 @@ export async function handleUserSignup(email: string) {
 We'll fill in those functions next, but let's take a look at this code:
 
 * We define a **workflow** function with the directive `"use workflow"`. Think of the workflow function as the _orchestrator_ of individual **steps**.
-* The Workflow DevKit's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
+* The Workflow SDK's `sleep` function allows us to suspend execution of the workflow without using up any resources. A sleep can be a few seconds, hours, days, or even months long.
 
 ## Create Your Workflow Steps
 
@@ -213,7 +213,7 @@ curl -X POST --json '{"email":"hello@example.com"}' http://localhost:3000/api/si
 
 Check the Vite development server logs to see your workflow execute as well as the steps that are being processed.
 
-Additionally, you can use the [Workflow DevKit CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
+Additionally, you can use the [Workflow SDK CLI or Web UI](/docs/observability) to inspect your workflow runs and steps in detail.
 
 ```bash
 # Open the observability Web UI
@@ -222,13 +222,13 @@ npx workflow web
 npx workflow inspect runs
 ```
 
-![Workflow DevKit Web UI](/o11y-ui.png)
+![Workflow SDK Web UI](/o11y-ui.png)
 
 ---
 
 ## Deploying to production
 
-Workflow DevKit apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
+Workflow SDK apps currently work best when deployed to [Vercel](https://vercel.com/home) and needs no special configuration.
 
 <FluidComputeCallout />
 

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

@@ -1,6 +1,6 @@
 ---
 title: How the Directives Work
-description: Deep dive into the internals of how Workflow DevKit directives transform your code.
+description: Deep dive into the internals of how Workflow SDK directives transform your code.
 type: conceptual
 summary: Learn how the compiler transforms directive-annotated code into three execution modes.
 prerequisites:
@@ -10,10 +10,10 @@ related:
 ---
 
 <Callout>
-This is an advanced guide that dives into internals of the Workflow DevKit directive and is not required reading to use workflows. To simply use the Workflow DevKit, check out the [getting started](/docs/getting-started) guides for your framework.
+This is an advanced guide that dives into internals of the Workflow SDK directive and is not required reading to use workflows. To simply use the Workflow SDK, check out the [getting started](/docs/getting-started) guides for your framework.
 </Callout>
 
-Workflows use special directives to mark code for transformation by the Workflow DevKit compiler. This page explains how `"use workflow"` and `"use step"` directives work, what transformations are applied, and why they're necessary for durable execution.
+Workflows use special directives to mark code for transformation by the Workflow SDK compiler. This page explains how `"use workflow"` and `"use step"` directives work, what transformations are applied, and why they're necessary for durable execution.
 
 ## Directives Overview
 
@@ -210,7 +210,7 @@ The IDs are generated exactly like in workflow mode to ensure they can be direct
 
 ## Generated Files
 
-When you build your application, the Workflow DevKit generates three handler files in `.well-known/workflow/v1/`:
+When you build your application, the Workflow SDK generates three handler files in `.well-known/workflow/v1/`:
 
 ### `flow.js`
 
@@ -268,7 +268,7 @@ Contains webhook handling logic for delivering external data to running workflow
 
 ## Why Three Modes?
 
-The multi-mode transformation enables the Workflow DevKit's durable execution model:
+The multi-mode transformation enables the Workflow SDK's durable execution model:
 
 1. **Step Mode** (required) - Bundles executable step functions that can access the full runtime
 2. **Workflow Mode** (required) - Creates orchestration logic that can replay from event logs
@@ -320,7 +320,7 @@ The compiler generates stable IDs for workflows and steps based on file paths an
 - **Portable**: Works across different runtimes and deployments
 
 <Callout type="info">
-  Although IDs can change when files are moved or functions are renamed, Workflow DevKit function assume atomic versioning in the World. This means changing IDs won't break old workflows from running, but will prevent run from being upgraded and will cause your workflow/step names to change in the observability across deployments.
+  Although IDs can change when files are moved or functions are renamed, Workflow SDK function assume atomic versioning in the World. This means changing IDs won't break old workflows from running, but will prevent run from being upgraded and will cause your workflow/step names to change in the observability across deployments.
 </Callout>
 
 ## Framework Integration

package/docs/how-it-works/encryption.mdx

@@ -1,6 +1,6 @@
 ---
 title: Encryption
-description: Learn how Workflow DevKit encrypts user data end-to-end in the event log.
+description: Learn how Workflow SDK encrypts user data end-to-end in the event log.
 type: conceptual
 summary: Understand how workflow and step data is encrypted at rest.
 prerequisites:
@@ -11,10 +11,10 @@ related:
 ---
 
 <Callout>
-This guide explains how Workflow DevKit encrypts user data in the event log. Understanding these details is not required to use workflows — encryption is automatic and requires no code changes. For getting started, see the [getting started](/docs/getting-started) guides for your framework.
+This guide explains how Workflow SDK encrypts user data in the event log. Understanding these details is not required to use workflows — encryption is automatic and requires no code changes. For getting started, see the [getting started](/docs/getting-started) guides for your framework.
 </Callout>
 
-Workflow DevKit supports automatic end-to-end encryption of all user data before it is written to the event log. When a `World` implementation provides encryption support, it is safe to pass sensitive data — such as API keys, tokens, or user credentials — as workflow inputs, step arguments, and return values. The storage backend only ever sees ciphertext.
+Workflow SDK supports automatic end-to-end encryption of all user data before it is written to the event log. When a `World` implementation provides encryption support, it is safe to pass sensitive data — such as API keys, tokens, or user credentials — as workflow inputs, step arguments, and return values. The storage backend only ever sees ciphertext.
 
 Encryption support varies by `World` implementation. See the [Worlds](/worlds) page to check which worlds support this feature. `World` implementations opt into encryption by providing a `getEncryptionKeyForRun()` method — the core runtime will use it automatically when present.
 

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

@@ -1,6 +1,6 @@
 ---
 title: Event Sourcing
-description: Learn how Workflow DevKit uses event sourcing internally for debugging and observability.
+description: Learn how Workflow SDK uses event sourcing internally for debugging and observability.
 type: conceptual
 summary: Understand the event log that powers workflow replay and debugging.
 prerequisites:
@@ -10,10 +10,10 @@ related:
 ---
 
 <Callout>
-This guide explores how the Workflow DevKit uses event sourcing internally. Understanding these concepts is helpful for debugging and building observability tools, but is not required to use workflows. For getting started with workflows, see the [getting started](/docs/getting-started) guides for your framework.
+This guide explores how the Workflow SDK uses event sourcing internally. Understanding these concepts is helpful for debugging and building observability tools, but is not required to use workflows. For getting started with workflows, see the [getting started](/docs/getting-started) guides for your framework.
 </Callout>
 
-The Workflow DevKit uses event sourcing to track all state changes in workflow executions. Every mutation creates an event that is persisted to the event log, and entity state is derived by replaying these events.
+The Workflow SDK uses event sourcing to track all state changes in workflow executions. Every mutation creates an event that is persisted to the event log, and entity state is derived by replaying these events.
 
 This page explains the event sourcing model and entity lifecycles.
 
@@ -28,7 +28,7 @@ Event sourcing is a persistence pattern where state changes are stored as a sequ
 - **Consistency**: Events provide a single source of truth for all entity state
 - **Recoverability**: State can be reconstructed from the event log after failures
 
-In the Workflow DevKit, the following entity types are managed through events:
+In the Workflow SDK, the following entity types are managed through events:
 
 - **Runs**: Workflow execution instances (materialized in storage)
 - **Steps**: Individual atomic operations within a workflow (materialized in storage)
@@ -243,7 +243,7 @@ This correlation enables:
 
 ## Entity IDs
 
-All entities in the Workflow DevKit use a consistent ID format: a 4-character prefix followed by an underscore and a [ULID](https://github.com/ulid/spec) (Universally Unique Lexicographically Sortable Identifier).
+All entities in the Workflow SDK use a consistent ID format: a 4-character prefix followed by an underscore and a [ULID](https://github.com/ulid/spec) (Universally Unique Lexicographically Sortable Identifier).
 
 | Entity | Prefix | Example |
 |--------|--------|---------|

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

@@ -1,8 +1,8 @@
 ---
 title: Framework Integrations
-description: Guide for framework authors to integrate Workflow DevKit with custom frameworks or runtimes.
+description: Guide for framework authors to integrate Workflow SDK with custom frameworks or runtimes.
 type: guide
-summary: Build a custom framework integration using the Workflow DevKit compiler and runtime.
+summary: Build a custom framework integration using the Workflow SDK compiler and runtime.
 prerequisites:
   - /docs/foundations/workflows-and-steps
 related:
@@ -10,13 +10,13 @@ related:
 ---
 
 <Callout>
-  **For users:** If you just want to use Workflow DevKit with an existing framework, check out the [Getting Started](/docs/getting-started) guide instead. This page is for framework authors who want to integrate Workflow DevKit with their framework or runtime.
+  **For users:** If you just want to use Workflow SDK with an existing framework, check out the [Getting Started](/docs/getting-started) guide instead. This page is for framework authors who want to integrate Workflow SDK with their framework or runtime.
 </Callout>
 
-This guide walks you through building a framework integration for Workflow DevKit using Bun as a concrete example. The same principles apply to any JavaScript runtime (Node.js, Deno, Cloudflare Workers, etc.).
+This guide walks you through building a framework integration for Workflow SDK using Bun as a concrete example. The same principles apply to any JavaScript runtime (Node.js, Deno, Cloudflare Workers, etc.).
 
 <Callout type="info">
-  **Prerequisites:** Before building a framework integration, we recommend reading [How the Directives Work](/docs/how-it-works/code-transform) to understand the transformation system that powers Workflow DevKit.
+  **Prerequisites:** Before building a framework integration, we recommend reading [How the Directives Work](/docs/how-it-works/code-transform) to understand the transformation system that powers Workflow SDK.
 </Callout>
 
 ## What You'll Build
@@ -46,7 +46,7 @@ flowchart TD
     style J fill:#a78bfa,stroke:#8b5cf6,color:#000
 ```
 
-The purple boxes are what you implement—everything else is provided by Workflow DevKit.
+The purple boxes are what you implement—everything else is provided by Workflow SDK.
 
 ## Example: Bun Integration
 
@@ -259,7 +259,7 @@ class MyFrameworkBuilder extends BaseBuilder {
 }
 ```
 
-If your framework supports virtual server routes and dev mode watching, make sure to adapt accordingly. Please open a PR to the Workflow DevKit if the base builder class is missing necessary functionality.
+If your framework supports virtual server routes and dev mode watching, make sure to adapt accordingly. Please open a PR to the Workflow SDK if the base builder class is missing necessary functionality.
 
 Hook into your framework's build:
 
@@ -341,8 +341,8 @@ const server = Bun.serve({
 ```
 
 Production framework integrations should handle this routing in the plugin instead of leaving it to the user, and this depends on each framework's unique implementaiton.
-Check the Workflow DevKit source code for examples of production framework implementations.
-In the future, the Workflow DevKit will emit more routes under the `.well-known/workflow` namespace.
+Check the Workflow SDK source code for examples of production framework implementations.
+In the future, the Workflow SDK will emit more routes under the `.well-known/workflow` namespace.
 
 ## Security