docs: absorb unique accuracy fixes from PR #1200

Cherry-picked 6 still-needed fixes from #1200 that aren't covered by
this audit PR or #1516:
- Fix npx workflow description (observability)
- Remove fetch from restricted modules list (errors)
- Fix package name @workflow-worlds/postgres → @workflow/world-postgres (deploying)
- Fix stream wording (foundations/starting-workflows)
- Fix import path simple → simple-streaming (foundations/streaming)
- Add close(), getEncryptionKeyForRun(), writeToStreamMulti() to World interface,
  update create() and streamer signatures (deploying/building-a-world)

Author: johnlindquist

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

@@ -34,10 +34,13 @@ A World connects workflows to the infrastructure that powers them. The World int
 ```typescript
 interface World extends Storage, Queue, Streamer {
   start?(): Promise<void>;
+  close?(): Promise<void>;
+  getEncryptionKeyForRun?(run: WorkflowRun): Promise<Uint8Array | undefined>;
+  getEncryptionKeyForRun?(runId: string, context?: Record<string, unknown>): Promise<Uint8Array | undefined>;
 }
 ```
 
-The optional `start()` method initializes any background tasks needed by your World (e.g., queue polling).
+The optional `start()` method initializes background tasks (for example, queue polling). The optional `close()` method releases resources like connection pools and listeners. The optional `getEncryptionKeyForRun()` method returns the AES-256 key used to encrypt data for a run; if it is not implemented, encryption is disabled.
 
 ## The Event Log Model
 
@@ -63,8 +66,8 @@ interface Storage {
   };
 
   events: {
-    // Create a new workflow run (runId must be null - server generates it)
-    create(runId: null, data: RunCreatedEventRequest, params?: CreateEventParams): Promise<EventResult>;
+    // Create a new workflow run (runId may be client-provided or null for server generation)
+    create(runId: string | null, data: RunCreatedEventRequest, params?: CreateEventParams): Promise<EventResult>;
 
     // Create an event for an existing run
     create(runId: string, data: CreateEventRequest, params?: CreateEventParams): Promise<EventResult>;
@@ -88,7 +91,7 @@ interface Storage {
 2. Atomically update the affected entity (run, step, or hook)
 3. Return both the created event and the updated entity
 
-**Run Creation:** For `run_created` events, the `runId` parameter is `null`. Your World generates and returns a new `runId`.
+**Run Creation:** For `run_created` events, the `runId` parameter may be a client-provided string or `null`. When `null`, your World generates and returns a new `runId`.
 
 **Hook Tokens:** Hook tokens must be unique. If a `hook_created` event conflicts with an existing token, return a `hook_conflict` event instead.
 
@@ -165,13 +168,19 @@ The Streamer interface enables real-time data streaming:
 interface Streamer {
   writeToStream(
     name: string,
-    runId: string | Promise<string>,
+    runId: string,
     chunk: string | Uint8Array
   ): Promise<void>;
 
+  writeToStreamMulti?(
+    name: string,
+    runId: string,
+    chunks: (string | Uint8Array)[]
+  ): Promise<void>;
+
   closeStream(
     name: string,
-    runId: string | Promise<string>
+    runId: string
   ): Promise<void>;
 
   readFromStream(
@@ -202,6 +211,7 @@ interface Streamer {
 ```
 
 Streams are identified by a combination of `runId` and `name`. Each workflow run can have multiple named streams.
+`writeToStreamMulti()` is an optional optimization for batching multiple writes.
 
 `getStreamChunks` returns a paginated snapshot of currently available chunks (unlike `readFromStream` which returns a live `ReadableStream` that waits for new chunks). `getStreamInfo` returns the tail index (last chunk index, 0-based, or `-1` when empty) and whether the stream is complete — useful for resolving negative `startIndex` values into absolute positions.
 

docs/content/docs/deploying/index.mdx

@@ -73,7 +73,7 @@ For self-hosting or deploying to other cloud providers, you can use community-ma
 To use a different World implementation, set the `WORKFLOW_TARGET_WORLD` environment variable:
 
 ```bash
-export WORKFLOW_TARGET_WORLD=@workflow-worlds/postgres
+export WORKFLOW_TARGET_WORLD=@workflow/world-postgres
 # Plus any world-specific configuration
 export DATABASE_URL=postgres://...
 ```
@@ -89,7 +89,7 @@ The [Observability tools](/docs/observability) work with any World backend. By d
 npx workflow inspect runs
 
 # Inspect remote workflows
-npx workflow inspect runs --backend @workflow-worlds/postgres
+npx workflow inspect runs --backend @workflow/world-postgres
 ```
 
 Learn more about [Observability](/docs/observability) tools.

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

@@ -69,7 +69,7 @@ async function read(filePath: string) {
 These common Node.js core modules cannot be used in workflow functions:
 
 - File system: `fs`, `path`
-- Network: `http`, `https`, `net`, `dns`, `fetch`
+- Network: `http`, `https`, `net`, `dns`
 - Process: `child_process`, `cluster`
 - Crypto: `crypto` (use Web Crypto API instead)
 - Operating system: `os`

docs/content/docs/foundations/starting-workflows.mdx

@@ -144,7 +144,7 @@ export async function POST(request: Request) {
 }
 ```
 
-Your workflow can write to the stream using [`getWritable()`](/docs/api-reference/workflow/get-writable):
+Your workflow can obtain a writable stream using [`getWritable()`](/docs/api-reference/workflow/get-writable):
 
 ```typescript lineNumbers
 import { getWritable } from "workflow";

docs/content/docs/foundations/streaming.mdx

@@ -44,7 +44,7 @@ Use the `Run` object's `readable` property to consume the stream from your API r
 
 ```typescript title="app/api/stream/route.ts" lineNumbers
 import { start } from "workflow/api";
-import { simpleStreamingWorkflow } from "./workflows/simple";
+import { simpleStreamingWorkflow } from "./workflows/simple-streaming";
 
 export async function POST() {
   const run = await start(simpleStreamingWorkflow);

docs/content/docs/observability/index.mdx

@@ -18,7 +18,7 @@ Workflow DevKit provides powerful tools to inspect, monitor, and debug your work
 npx workflow
 ```
 
-The CLI comes pre-installed with the Workflow DevKit and registers the `workflow` command. If the `workflow` package is not already installed, `npx workflow` will install it globally, or use the local installed version if available.
+The CLI comes pre-installed with the Workflow DevKit and registers the `workflow` command. If the `workflow` package is not already installed, `npx workflow` will download and run the CLI temporarily, or use the local installed version if available.
 
 Get started inspecting your local workflows: