@synergenius/flow-weaver 0.21.10 → 0.21.11

package/docs/reference/compilation.md

@@ -53,7 +53,7 @@ The default `typescript` target generates code that runs directly in Node.js or
 ### Example
 
 ```bash
-flow-weaver compile workflow.ts
+fw compile workflow.ts
 ```
 
 Generates code like:
@@ -79,7 +79,7 @@ export function myWorkflow(params: { data: string }) {
 The `inngest` target generates **durable functions** using [Inngest](https://www.inngest.com/). Each workflow node becomes a `step.run()` call, providing automatic retries, event-driven triggers, and crash recovery.
 
 ```bash
-flow-weaver compile workflow.ts --target inngest
+fw compile workflow.ts --target inngest
 ```
 
 ### Per-Node Durability
@@ -237,7 +237,7 @@ export async function expenseWorkflow(
 Strips all debug instrumentation from generated code. No `STATUS_CHANGED`, `VARIABLE_SET`, or `LOG_ERROR` events are emitted. Use this for deployed workflows.
 
 ```bash
-flow-weaver compile workflow.ts --production
+fw compile workflow.ts --production
 ```
 
 ### Source Maps (`--source-map`)
@@ -245,7 +245,7 @@ flow-weaver compile workflow.ts --production
 Generate source maps alongside compiled output:
 
 ```bash
-flow-weaver compile workflow.ts --source-map
+fw compile workflow.ts --source-map
 ```
 
 ### Module Format (`--format`)
@@ -259,7 +259,7 @@ Control the output module format:
 | `cjs` | CommonJS (`require`/`module.exports`) |
 
 ```bash
-flow-weaver compile workflow.ts --format cjs
+fw compile workflow.ts --format cjs
 ```
 
 ### Strict Mode (`--strict`)
@@ -267,7 +267,7 @@ flow-weaver compile workflow.ts --format cjs
 Promote type coercion warnings to errors:
 
 ```bash
-flow-weaver compile workflow.ts --strict
+fw compile workflow.ts --strict
 ```
 
 Equivalent to adding `@strictTypes` to the workflow annotation.
@@ -277,7 +277,7 @@ Equivalent to adding `@strictTypes` to the workflow annotation.
 Force inline runtime code even when `@synergenius/flow-weaver` is installed as a dependency. Normally the compiler generates an import; this flag embeds the runtime directly.
 
 ```bash
-flow-weaver compile workflow.ts --inline-runtime
+fw compile workflow.ts --inline-runtime
 ```
 
 ### Clean Output (`--clean`)
@@ -285,7 +285,7 @@ flow-weaver compile workflow.ts --inline-runtime
 Omit redundant `@param`/`@returns` annotations from the compiled output. Produces cleaner generated code.
 
 ```bash
-flow-weaver compile workflow.ts --clean
+fw compile workflow.ts --clean
 ```
 
 ### Dry Run (`--dry-run`)
@@ -293,7 +293,7 @@ flow-weaver compile workflow.ts --clean
 Preview compilation output without writing any files:
 
 ```bash
-flow-weaver compile workflow.ts --dry-run
+fw compile workflow.ts --dry-run
 ```
 
 ---
@@ -303,7 +303,7 @@ flow-weaver compile workflow.ts --dry-run
 Generate a complete HTTP handler for receiving Inngest events:
 
 ```bash
-flow-weaver compile workflow.ts --target inngest --serve --framework next
+fw compile workflow.ts --target inngest --serve --framework next
 ```
 
 ### Supported Frameworks
@@ -321,7 +321,7 @@ flow-weaver compile workflow.ts --target inngest --serve --framework next
 Generate Zod schemas for event validation from `@param` annotations:
 
 ```bash
-flow-weaver compile workflow.ts --target inngest --typed-events
+fw compile workflow.ts --target inngest --typed-events
 ```
 
 ---
@@ -337,7 +337,7 @@ Several Inngest annotations can be overridden from the CLI without modifying the
 | `--timeout <duration>` | `@timeout` |
 
 ```bash
-flow-weaver compile workflow.ts --target inngest --retries 5 --timeout "1h"
+fw compile workflow.ts --target inngest --retries 5 --timeout "1h"
 ```
 
 ---

package/docs/reference/concepts.md

@@ -82,7 +82,7 @@ That is it. Two expression-mode functions, one workflow annotation, zero boilerp
 | Use delay/waitForEvent/mocks     | `built-in-nodes`             | debugging           |
 | Publish marketplace packages     | `marketplace`                | —                   |
 
-Use `flow-weaver docs <topic>` to read any topic.
+Use `fw docs <topic>` to read any topic.
 
 ## File Format
 
@@ -91,18 +91,18 @@ Workflows are TypeScript files with JSDoc annotations. Any `.ts`, `.tsx`, `.js`,
 ## CLI Commands
 
 ```bash
-flow-weaver validate <file>   # Check for errors (--json for machine parsing)
-flow-weaver compile <file>    # Generate executable code
-flow-weaver run <file>        # Execute a workflow directly. No compile step needed for testing.
-flow-weaver describe <file>   # Get workflow structure as JSON
-flow-weaver watch <file>      # Watch mode
-flow-weaver dev <file>        # Watch + compile + run in one command
-flow-weaver serve [dir]       # HTTP server exposing workflows as endpoints
-flow-weaver diagram <file>    # Generate SVG diagram
-flow-weaver export <file>     # Export as serverless function or CI/CD pipeline
-flow-weaver docs              # Browse documentation
-flow-weaver docs <topic>      # Read a specific topic
-flow-weaver docs search <q>   # Search across all docs
+fw validate <file>   # Check for errors (--json for machine parsing)
+fw compile <file>    # Generate executable code
+fw run <file>        # Execute a workflow directly. No compile step needed for testing.
+fw describe <file>   # Get workflow structure as JSON
+fw watch <file>      # Watch mode
+fw dev <file>        # Watch + compile + run in one command
+fw serve [dir]       # HTTP server exposing workflows as endpoints
+fw diagram <file>    # Generate SVG diagram
+fw export <file>     # Export as serverless function or CI/CD pipeline
+fw docs              # Browse documentation
+fw docs <topic>      # Read a specific topic
+fw docs search <q>   # Search across all docs
 ```
 
 Options: `-w/--workflow-name`, `--json`, `--format text|mermaid`. See `cli-reference` for all commands and flags.
@@ -350,7 +350,7 @@ Key points:
  */
 ```
 
-See `flow-weaver docs export-interface` for full scope documentation.
+See `fw docs export-interface` for full scope documentation.
 
 ## Node Positioning
 
@@ -372,48 +372,48 @@ Spacing: 180px horizontal (standard), 150px vertical for branches
 ### Recipe 1: Build a Workflow from Scratch
 
 ```
-1. flow-weaver create workflow sequential my-workflow.ts --preview   # preview the template
+1. fw create workflow sequential my-workflow.ts --preview   # preview the template
 2. Write the file with node types + workflow annotations
-3. flow-weaver validate my-workflow.ts                               # check for errors
+3. fw validate my-workflow.ts                               # check for errors
 4. Fix any errors, re-validate
-5. flow-weaver compile my-workflow.ts                                # generate executable code
-6. flow-weaver describe my-workflow.ts --format text                 # verify structure
+5. fw compile my-workflow.ts                                # generate executable code
+6. fw describe my-workflow.ts --format text                 # verify structure
 ```
 
 ### Recipe 2: Add a Node to Existing Workflow
 
 ```
-1. flow-weaver describe my-workflow.ts --format text   # understand current structure
+1. fw describe my-workflow.ts --format text   # understand current structure
 2. Edit the file: add @flowWeaver nodeType function + @node + @connect annotations
-3. flow-weaver validate my-workflow.ts                 # verify
+3. fw validate my-workflow.ts                 # verify
 ```
 
 ### Recipe 3: Debug a Broken Workflow
 
 ```
-1. flow-weaver validate my-workflow.ts                              # get all errors
-2. flow-weaver describe my-workflow.ts --format text                # get full picture
-3. Fix errors based on error codes (see: flow-weaver docs error-codes)
+1. fw validate my-workflow.ts                              # get all errors
+2. fw describe my-workflow.ts --format text                # get full picture
+3. Fix errors based on error codes (see: fw docs error-codes)
 ```
 
 ### Recipe 4: Add Iteration (ForEach)
 
 ```
-1. Read: flow-weaver docs export-interface              # scoped port syntax
+1. Read: fw docs export-interface              # scoped port syntax
 2. Edit file: add forEach node type with scope ports
 3. Edit file: add child node with parent scope reference
 4. Edit file: wire scoped connections (:scopeName suffix)
-5. flow-weaver validate my-workflow.ts                  # verify scope wiring
+5. fw validate my-workflow.ts                  # verify scope wiring
 ```
 
 ## Workflow Development Process
 
 1. **Create file** - Write TypeScript file with types and node functions
 2. **Add annotations** - `@flowWeaver nodeType` and `@flowWeaver workflow`
-3. **Validate** - `flow-weaver validate <file>`
-4. **Test** - Start with `flow-weaver run <file>` for quick testing. Compile only for production deployment.
-5. **Compile** - `flow-weaver compile <file>`
-6. **Inspect** - `flow-weaver describe <file>` for structure
+3. **Validate** - `fw validate <file>`
+4. **Test** - Start with `fw run <file>` for quick testing. Compile only for production deployment.
+5. **Compile** - `fw compile <file>`
+6. **Inspect** - `fw describe <file>` for structure
 
 ## Additional Annotations
 

package/docs/reference/debugging.md

@@ -6,7 +6,7 @@ keywords: [debug, troubleshooting, errors, WebSocket, diagnostics, runtime, vali
 
 # Flow Weaver Debugging Guide
 
-For error code lookup, use `flow-weaver docs error-codes`.
+For error code lookup, use `fw docs error-codes`.
 
 ---
 
@@ -14,11 +14,11 @@ For error code lookup, use `flow-weaver docs error-codes`.
 
 | Error                   | Fix                                                             |
 | ----------------------- | --------------------------------------------------------------- |
-| UNKNOWN_NODE_TYPE       | Check spelling, run `flow-weaver describe <file>`               |
+| UNKNOWN_NODE_TYPE       | Check spelling, run `fw describe <file>`               |
 | MISSING_REQUIRED_INPUT  | Add `@connect` or make port optional with `@input [name]`       |
 | STEP_PORT_TYPE_MISMATCH | STEP ports (execute/onSuccess/onFailure) only connect to STEP   |
 | CYCLE_DETECTED          | Use scoped forEach instead of graph loops                       |
-| UNKNOWN_SOURCE_PORT     | Check port name spelling, run `flow-weaver describe <file>`     |
+| UNKNOWN_SOURCE_PORT     | Check port name spelling, run `fw describe <file>`     |
 
 ---
 
@@ -30,13 +30,13 @@ Flow Weaver can emit real-time execution events over WebSocket for runtime debug
 
 ```bash
 # Compile the workflow (debug mode is the default)
-flow-weaver compile my-workflow.ts
+fw compile my-workflow.ts
 
 # Run with WebSocket debug target
 FLOW_WEAVER_DEBUG=ws://localhost:9000 node my-workflow.generated.js
 ```
 
-Production builds (`flow-weaver compile --production`) strip all debug event code.
+Production builds (`fw compile --production`) strip all debug event code.
 
 ### Event Types
 
@@ -63,7 +63,7 @@ START: What is the problem?
 |
 +-- "Compilation fails" (parse or validation errors)
 |   |
-|   +-- Run: flow-weaver validate <file> --verbose
+|   +-- Run: fw validate <file> --verbose
 |   |
 |   +-- Are there PARSE errors?
 |   |   |
@@ -75,7 +75,7 @@ START: What is the problem?
 |   |   |
 |   |   +-- NO --> Are there VALIDATION errors?
 |   |       |
-|   |       +-- YES --> Look up the error code: flow-weaver docs error-codes
+|   |       +-- YES --> Look up the error code: fw docs error-codes
 |   |       |           Common quick fixes:
 |   |       |           - UNKNOWN_*: Check spelling, use validator suggestions
 |   |       |           - MISSING_REQUIRED_INPUT: Add connection or default
@@ -148,35 +148,35 @@ START: What is the problem?
 
 ## CLI Debugging Commands
 
-### flow-weaver validate -- Validate a Workflow
+### fw validate -- Validate a Workflow
 
 The first command to use when something seems wrong. Returns all errors and warnings with codes, messages, and hints.
 
 ```bash
-flow-weaver validate src/workflows/my-workflow.ts
-flow-weaver validate src/workflows/my-workflow.ts --json    # machine-readable
-flow-weaver validate src/workflows/my-workflow.ts --verbose  # detailed diagnostics
+fw validate src/workflows/my-workflow.ts
+fw validate src/workflows/my-workflow.ts --json    # machine-readable
+fw validate src/workflows/my-workflow.ts --verbose  # detailed diagnostics
 ```
 
-### flow-weaver describe -- Understand Workflow Structure
+### fw describe -- Understand Workflow Structure
 
 Provides a full description of the workflow: nodes, connections, ports, types, and execution graph.
 
 ```bash
-flow-weaver describe src/workflows/my-workflow.ts                      # JSON
-flow-weaver describe src/workflows/my-workflow.ts --format text        # human-readable
-flow-weaver describe src/workflows/my-workflow.ts --format mermaid     # diagram
-flow-weaver describe src/workflows/my-workflow.ts --node fetcher1      # focus on a node
+fw describe src/workflows/my-workflow.ts                      # JSON
+fw describe src/workflows/my-workflow.ts --format text        # human-readable
+fw describe src/workflows/my-workflow.ts --format mermaid     # diagram
+fw describe src/workflows/my-workflow.ts --node fetcher1      # focus on a node
 ```
 
-### flow-weaver run --stream vs --trace
+### fw run --stream vs --trace
 
 Both flags give you execution trace data, but in different ways:
 
 **`--stream`** writes events to stderr in real-time as nodes execute. Each STATUS_CHANGED event prints the node ID, new status, and duration. Use this for live debugging during development — you can watch the workflow progress node by node.
 
 ```bash
-flow-weaver run workflow.ts --stream
+fw run workflow.ts --stream
 # Output (to stderr):
 #   [STATUS_CHANGED] fetcher: → RUNNING
 #   [STATUS_CHANGED] fetcher: → SUCCEEDED (142ms)
@@ -188,10 +188,10 @@ flow-weaver run workflow.ts --stream
 **`--trace`** collects all ExecutionTraceEvent objects during execution and includes them in the output after completion. Use this for post-mortem analysis or programmatic consumption (e.g., in CI or with `--json`).
 
 ```bash
-flow-weaver run workflow.ts --trace
+fw run workflow.ts --trace
 # Shows: "12 events captured" + first 5 events as summary
 
-flow-weaver run workflow.ts --trace --json | jq '.traceCount'
+fw run workflow.ts --trace --json | jq '.traceCount'
 # Outputs: 12
 ```
 
@@ -204,10 +204,10 @@ flow-weaver run workflow.ts --trace --json | jq '.traceCount'
 
 ### Diagnostic Strategy
 
-1. **flow-weaver validate** -- Get all errors and warnings. Fix errors first.
-2. **flow-weaver describe --format text** -- Full readable summary.
-3. **flow-weaver describe --node <id>** -- Trace data flow for a specific node.
-4. **flow-weaver describe --format mermaid** -- Visual graph for inspection.
+1. **fw validate** -- Get all errors and warnings. Fix errors first.
+2. **fw describe --format text** -- Full readable summary.
+3. **fw describe --node <id>** -- Trace data flow for a specific node.
+4. **fw describe --format mermaid** -- Visual graph for inspection.
 
 ---
 
@@ -253,8 +253,8 @@ Scoped ports use direction inversion: scoped OUTPUTS = data parent sends to chil
 When testing workflows that use `delay`, `waitForEvent`, `invokeWorkflow`, or `waitForAgent`, use mocks to avoid real side effects:
 
 ```bash
-flow-weaver run workflow.ts --mocks '{"fast": true, "events": {"app/approved": {"status": "ok"}}}'
-flow-weaver run workflow.ts --mocks-file mocks.json
+fw run workflow.ts --mocks '{"fast": true, "events": {"app/approved": {"status": "ok"}}}'
+fw run workflow.ts --mocks-file mocks.json
 ```
 
 Mock config structure:
@@ -276,7 +276,7 @@ The debug system intercepts execution at two points per node: before it runs (wh
 ### CLI Debug Mode
 
 ```bash
-flow-weaver run workflow.ts --debug --params '{"x": 5}'
+fw run workflow.ts --debug --params '{"x": 5}'
 ```
 
 This starts an interactive debug REPL. The workflow pauses before the first node and waits for your command:
@@ -320,7 +320,7 @@ Debug REPL commands:
 You can set breakpoints at startup with `--breakpoint`:
 
 ```bash
-flow-weaver run workflow.ts --debug --breakpoint processData --breakpoint formatOutput
+fw run workflow.ts --debug --breakpoint processData --breakpoint formatOutput
 ```
 
 ### MCP Debug Tools
@@ -366,7 +366,7 @@ Checkpointing writes workflow state to disk after each node completes. If the pr
 ### Enabling Checkpoints
 
 ```bash
-flow-weaver run workflow.ts --checkpoint --params '{"data": "large-dataset"}'
+fw run workflow.ts --checkpoint --params '{"data": "large-dataset"}'
 ```
 
 This creates a `.fw-checkpoints/` directory next to the workflow file containing one JSON file per run. The file is automatically deleted after successful completion, so you'll only see them after a crash.
@@ -375,13 +375,13 @@ This creates a `.fw-checkpoints/` directory next to the workflow file containing
 
 ```bash
 # Auto-detect the most recent checkpoint
-flow-weaver run workflow.ts --resume
+fw run workflow.ts --resume
 
 # Specify a checkpoint file
-flow-weaver run workflow.ts --resume .fw-checkpoints/myWorkflow-run-123.json
+fw run workflow.ts --resume .fw-checkpoints/myWorkflow-run-123.json
 
 # Resume in debug mode (step through from the resume point)
-flow-weaver run workflow.ts --resume --debug
+fw run workflow.ts --resume --debug
 ```
 
 Via MCP: `fw_resume_from_checkpoint(filePath: "workflow.ts")`.
@@ -416,10 +416,10 @@ Checkpoints live in `.fw-checkpoints/` next to the workflow file. Add this to `.
 
 ## Dev Mode
 
-Use `flow-weaver dev` to watch, compile, and run in a single command:
+Use `fw dev` to watch, compile, and run in a single command:
 
 ```bash
-flow-weaver dev workflow.ts --params '{"data": "test"}'
+fw dev workflow.ts --params '{"data": "test"}'
 ```
 
 This recompiles and re-runs automatically on every file save.

package/docs/reference/deployment.md

@@ -33,13 +33,13 @@ The `export` command automatically discovers installed packs — no configuratio
 The `export` command generates platform-specific handler code, configuration files, and deploy instructions.
 
 ```bash
-flow-weaver export <input> --target <target> --output <dir>
+fw export <input> --target <target> --output <dir>
 ```
 
 ### AWS Lambda
 
 ```bash
-flow-weaver export workflow.ts --target lambda --output dist/
+fw export workflow.ts --target lambda --output dist/
 ```
 
 Generates:
@@ -50,7 +50,7 @@ Generates:
 ### Vercel
 
 ```bash
-flow-weaver export workflow.ts --target vercel --output api/
+fw export workflow.ts --target vercel --output api/
 ```
 
 Generates:
@@ -60,7 +60,7 @@ Generates:
 ### Cloudflare Workers
 
 ```bash
-flow-weaver export workflow.ts --target cloudflare --output worker/
+fw export workflow.ts --target cloudflare --output worker/
 ```
 
 Generates:
@@ -70,7 +70,7 @@ Generates:
 ### Inngest
 
 ```bash
-flow-weaver export workflow.ts --target inngest --output dist/
+fw export workflow.ts --target inngest --output dist/
 ```
 
 Generates:
@@ -80,13 +80,13 @@ Generates:
 Add `--durable-steps` for per-node `step.run()` durability:
 
 ```bash
-flow-weaver export workflow.ts --target inngest --output dist/ --durable-steps
+fw export workflow.ts --target inngest --output dist/ --durable-steps
 ```
 
 ### GitHub Actions
 
 ```bash
-flow-weaver export workflow.ts --target github-actions --output .github/workflows/
+fw export workflow.ts --target github-actions --output .github/workflows/
 ```
 
 Generates:
@@ -96,7 +96,7 @@ Generates:
 ### GitLab CI
 
 ```bash
-flow-weaver export workflow.ts --target gitlab-ci --output .
+fw export workflow.ts --target gitlab-ci --output .
 ```
 
 Generates:
@@ -115,10 +115,10 @@ Secrets are wired as pseudo-node connections: `@connect secret:TOKEN -> node.por
 
 ```bash
 # GitHub Actions
-flow-weaver export pipeline.ts --target github-actions --output .github/workflows/
+fw export pipeline.ts --target github-actions --output .github/workflows/
 
 # GitLab CI
-flow-weaver export pipeline.ts --target gitlab-ci --output .
+fw export pipeline.ts --target gitlab-ci --output .
 ```
 
 See the [CI/CD Pipelines](cicd) topic for the complete annotation reference, validation rules, and full examples.
@@ -130,7 +130,7 @@ See the [CI/CD Pipelines](cicd) topic for the complete annotation reference, val
 Export all workflows in a file as a **unified service** with routing, function registry, and optional API documentation:
 
 ```bash
-flow-weaver export workflows.ts --target lambda --output dist/ --multi
+fw export workflows.ts --target lambda --output dist/ --multi
 ```
 
 ### Features
@@ -140,7 +140,7 @@ flow-weaver export workflows.ts --target lambda --output dist/ --multi
 - **API docs** — Add `--docs` to include Swagger UI at `/docs` and OpenAPI spec at `/openapi.json`
 
 ```bash
-flow-weaver export workflows.ts --target vercel --output api/ --multi --docs
+fw export workflows.ts --target vercel --output api/ --multi --docs
 ```
 
 ### Selecting Workflows
@@ -148,17 +148,17 @@ flow-weaver export workflows.ts --target vercel --output api/ --multi --docs
 Export a subset of workflows from a multi-workflow file:
 
 ```bash
-flow-weaver export workflows.ts --target lambda --output dist/ --multi --workflows validatePipeline,enrichPipeline
+fw export workflows.ts --target lambda --output dist/ --multi --workflows validatePipeline,enrichPipeline
 ```
 
 ---
 
 ## HTTP Serve Mode
 
-Run workflows as HTTP endpoints locally or in production with `flow-weaver serve`:
+Run workflows as HTTP endpoints locally or in production with `fw serve`:
 
 ```bash
-flow-weaver serve [directory] [options]
+fw serve [directory] [options]
 ```
 
 ### Features
@@ -175,17 +175,17 @@ flow-weaver serve [directory] [options]
 
 Development server with hot reload:
 ```bash
-flow-weaver serve ./workflows
+fw serve ./workflows
 ```
 
 Production server:
 ```bash
-flow-weaver serve ./workflows --production --precompile --no-watch --port 8080
+fw serve ./workflows --production --precompile --no-watch --port 8080
 ```
 
 With Swagger UI:
 ```bash
-flow-weaver serve ./workflows --swagger
+fw serve ./workflows --swagger
 # Open http://localhost:3000/docs for API documentation
 ```
 
@@ -206,7 +206,7 @@ Content-Type: application/json
 Generate an OpenAPI specification from all workflows in a directory:
 
 ```bash
-flow-weaver openapi <directory> [options]
+fw openapi <directory> [options]
 ```
 
 The specification is derived from workflow `@param` and `@returns` annotations.
@@ -215,13 +215,13 @@ The specification is derived from workflow `@param` and `@returns` annotations.
 
 ```bash
 # JSON output (default)
-flow-weaver openapi ./workflows --output api-spec.json
+fw openapi ./workflows --output api-spec.json
 
 # YAML output
-flow-weaver openapi ./workflows --format yaml --output api-spec.yaml
+fw openapi ./workflows --format yaml --output api-spec.yaml
 
 # With server URL
-flow-weaver openapi ./workflows --server https://api.example.com --title "My API" --version "2.0.0"
+fw openapi ./workflows --server https://api.example.com --title "My API" --version "2.0.0"
 ```
 
 ### Generated Spec
@@ -236,10 +236,10 @@ Each workflow becomes an endpoint with:
 
 ## Dev Mode with Inngest
 
-For Inngest development, `flow-weaver dev` starts a local dev server with the Inngest Dev Server:
+For Inngest development, `fw dev` starts a local dev server with the Inngest Dev Server:
 
 ```bash
-flow-weaver dev workflow.ts --target inngest --port 8080 --framework express
+fw dev workflow.ts --target inngest --port 8080 --framework express
 ```
 
 This:
@@ -251,10 +251,10 @@ This:
 
 ## Deployment Checklist
 
-1. **Validate** — Run `flow-weaver validate workflow.ts --strict` before deploying
+1. **Validate** — Run `fw validate workflow.ts --strict` before deploying
 2. **Production compile** — Use `--production` to strip debug instrumentation
-3. **Test locally** — Use `flow-weaver serve` or `flow-weaver run` with mocks
-4. **Export** — Generate platform-specific code with `flow-weaver export`
+3. **Test locally** — Use `fw serve` or `fw run` with mocks
+4. **Export** — Generate platform-specific code with `fw export`
 5. **Deploy** — Follow platform-specific instructions in the generated output
 
 ---

package/docs/reference/export-interface.md

@@ -225,5 +225,5 @@ Avoid: `process`, `module`, `require`, `exports`, `console`, `global`
 Always validate after changes:
 
 ```bash
-flow-weaver validate <file>
+fw validate <file>
 ```

package/docs/reference/iterative-development.md

@@ -50,7 +50,7 @@ export function myWorkflow(
 Test:
 
 ```bash
-flow-weaver validate <file>
+fw validate <file>
 ```
 
 ### Phase 3: Create the Nodes
@@ -122,7 +122,7 @@ Add node instances with `@node` and connections with `@connect`:
 Test after each change:
 
 ```bash
-flow-weaver validate <file>
+fw validate <file>
 ```
 
 ### Phase 4: Finalizing
@@ -137,9 +137,9 @@ After everything is connected:
 Final validation:
 
 ```bash
-flow-weaver validate <file>
-flow-weaver compile <file>
-flow-weaver describe <file>  # Get workflow structure as JSON
+fw validate <file>
+fw compile <file>
+fw describe <file>  # Get workflow structure as JSON
 ```
 
 ## Common Mistakes
@@ -168,7 +168,7 @@ If the workflow should return values, connect them: `@connect lastNode.result ->
 
 ### 5. Not Validating After Each Change
 
-Always run `flow-weaver validate` after adding nodes/connections. Don't batch 10 changes then validate -- validate incrementally.
+Always run `fw validate` after adding nodes/connections. Don't batch 10 changes then validate -- validate incrementally.
 
 ### 6. Using Normal Mode When Expression Mode Works