Finish renaming "embedded" world to "local" in docs (#269)

Signed-off-by: Nathan Rajlich <n@n8.io>

Author: TooTallNate

CLAUDE.md

@@ -16,7 +16,7 @@ This repository contains the client side SDK code for workflows, along example a
 - **packages/next**: Next.js integration (`@workflow/next`)
 - **packages/cli**: Command-line interface (`@workflow/cli`)
 - **packages/world**: Core interfaces and types for workflow storage backends (`@workflow/world`)
-- **packages/world-embedded**: Filesystem-based workflow backend for local development and testing (`@workflow/world-local`)
+- **packages/world-local**: Filesystem-based workflow backend for local development and testing (`@workflow/world-local`)
 - **packages/world-vercel**: Production workflow backend for Vercel platform deployments (`@workflow/world-vercel`)
 - **packages/swc-plugin-workflow**: SWC compiler plugin for workflow transformations
 - **workbench/example**: Basic workflow examples using the CLI (aka "standalone mode")

docs/content/docs/deploying/index.mdx

@@ -19,7 +19,7 @@ A **World** connects workflows to the infrastructure that powers them. Think of
 
 Worlds are automatically configured depending on the scenario:
 
-- **Local development** - Automatically uses the Embedded World
+- **Local development** - Automatically uses the Local World
 - **Vercel deployments** - Automatically uses the Vercel World
 
 When using other worlds, you can explicitly set configuration through environment variables. Reference the documentation for the appropriate world for configuration details.
@@ -29,7 +29,7 @@ When using other worlds, you can explicitly set configuration through environmen
 Workflow DevKit ships with two world implementations:
 
 <Cards>
-  <Card title="Embedded World" href="/docs/deploying/world/embedded-world">
+  <Card title="Local World" href="/docs/deploying/world/local-world">
     Filesystem-based backend for local development, storing data in `.workflow-data/` directory.
   </Card>
   <Card title="Vercel World" href="/docs/deploying/world/vercel-world">
@@ -75,7 +75,7 @@ Learn more about [Observability](/docs/observability) tools.
 
 ## Learn More
 
-- [Embedded World](/docs/deploying/world/embedded-world) - Local development backend
+- [Local World](/docs/deploying/world/local-world) - Local development backend
 - [Vercel World](/docs/deploying/world/vercel-world) - Production backend for Vercel
 - [World API Reference](/docs/deploying/world) - Building custom worlds
 - [Observability](/docs/observability) - Inspecting workflow data

docs/content/docs/deploying/world/index.mdx

@@ -16,7 +16,7 @@ The workflow `World` is an interface that abstracts how workflows and steps comm
 
 ## Choosing a World implementation
 
-* By default, Workflow uses the [Local world](/docs/deploying/world/embedded-world) for easy local development.
+* By default, Workflow uses the [Local world](/docs/deploying/world/local-world) for easy local development.
 * When deployed on Vercel, Workflow switches to the [Vercel world](/docs/deploying/world/vercel-world).
 
 If you want to use a different World implementation, set the `WORKFLOW_TARGET_WORLD` environment variable to your desired World package's NPM name:
@@ -30,7 +30,7 @@ export MY_WORLD_CONFIG=... # implementation-specific configuration
 
 Workflow DevKit provides two built-in world implementations:
 
-- [Embedded World](/docs/deploying/world/embedded-world) - Filesystem-based for local development
+- [Local World](/docs/deploying/world/local-world) - Filesystem-based for local development
 - [Vercel World](/docs/deploying/world/vercel-world) - Production-ready for Vercel deployments
 
 ## Community Worlds

docs/content/docs/deploying/world/embedded-world.mdx renamed to docs/content/docs/deploying/world/local-world.mdx

@@ -199,3 +199,4 @@ const world = createEmbeddedWorld('./my-data', 3000);
 - [World Interface](/docs/deploying/world) - Understanding the World interface
 - [Vercel World](/docs/deploying/world/vercel-world) - For production deployments
 - [Observability](/docs/observability) - Monitoring and debugging tools
+

docs/content/docs/deploying/world/meta.json

@@ -1,4 +1,4 @@
 {
   "title": "World",
-  "pages": ["world", "embedded-world", "vercel-world", "postgres-world"]
+  "pages": ["world", "local-world", "vercel-world", "postgres-world"]
 }

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

@@ -221,12 +221,12 @@ If workflows don't work after deployment:
 1. Verify `withWorkflow()` is wrapping your Next.js config
 2. Check build logs for errors
 3. Ensure workflow files are in the correct directory
-4. Test locally first with [Embedded World](/docs/deploying/world/embedded-world)
+4. Test locally first with [Local World](/docs/deploying/world/local-world)
 
 ## Learn More
 
 - [World Interface](/docs/deploying/world) - Understanding the World interface
-- [Embedded World](/docs/deploying/world/embedded-world) - For local development
+- [Local World](/docs/deploying/world/local-world) - For local development
 - [Observability](/docs/observability) - Monitoring and debugging tools
 - [Vercel Deployment Documentation](https://vercel.com/docs/deployments/overview)
 - [Workflow Documentation on Vercel](https://vercel.com/docs/workflow)

packages/core/src/runtime.ts

@@ -673,7 +673,7 @@ export const stepEntrypoint =
                   workflowRunId,
                   workflowStartedAt: new Date(+workflowStartedAt),
                   // TODO: there should be a getUrl method on the world interface itself. This
-                  // solution only works for vercel + embedded worlds.
+                  // solution only works for vercel + local worlds.
                   url: process.env.VERCEL_URL
                     ? `https://${process.env.VERCEL_URL}`
                     : `http://localhost:${port ?? 3000}`,