@synergenius/flow-weaver 0.21.7 → 0.21.11

package/docs/reference/marketplace.md

@@ -15,7 +15,7 @@ The Flow Weaver marketplace is an npm-based ecosystem for sharing reusable node
 | **Node types** | Reusable `@flowWeaver nodeType` functions |
 | **Workflows** | Complete `@flowWeaver workflow` exports |
 | **Patterns** | Reusable `@flowWeaver pattern` fragments |
-| **Export targets** | Deployment targets for `flow-weaver export` |
+| **Export targets** | Deployment targets for `fw export` |
 
 A single package can contain any combination of these.
 
@@ -49,15 +49,15 @@ See [Deployment](deployment) for target-specific usage details.
 Find packages on npm:
 
 ```bash
-flow-weaver market search openai
-flow-weaver market search            # Browse all packages
-flow-weaver market search llm --limit 5
+fw market search openai
+fw market search            # Browse all packages
+fw market search llm --limit 5
 ```
 
 For private registries:
 
 ```bash
-flow-weaver market search openai --registry https://npm.internal.com
+fw market search openai --registry https://npm.internal.com
 ```
 
 ### Install
@@ -65,8 +65,8 @@ flow-weaver market search openai --registry https://npm.internal.com
 Install a package:
 
 ```bash
-flow-weaver market install flow-weaver-pack-openai
-flow-weaver market install flow-weaver-pack-openai@1.0.0
+fw market install flow-weaver-pack-openai
+fw market install flow-weaver-pack-openai@1.0.0
 ```
 
 After installation, the package's node types, workflows, and patterns are available for use in your workflows via `@fwImport`.
@@ -74,7 +74,7 @@ After installation, the package's node types, workflows, and patterns are availa
 ### List Installed
 
 ```bash
-flow-weaver market list
+fw market list
 ```
 
 Shows all installed `flow-weaver-pack-*` packages with their available node types, workflows, and patterns.
@@ -88,19 +88,19 @@ Shows all installed `flow-weaver-pack-*` packages with their available node type
 Create a new marketplace package:
 
 ```bash
-flow-weaver market init openai
+fw market init openai
 ```
 
 This creates a `flow-weaver-pack-openai/` directory with:
-- `package.json` — Configured with `flowweaver-marketplace-pack` keyword
+- `package.json` — Configured with `flow-weaver-marketplace-pack` keyword
 - `src/` — Source directory for node types, workflows, and patterns
 - `tsconfig.json` — TypeScript configuration
 
 Options:
 
 ```bash
-flow-weaver market init openai --description "OpenAI nodes for Flow Weaver" --author "Your Name"
-flow-weaver market init openai -y  # Skip prompts
+fw market init openai --description "OpenAI nodes for Flow Weaver" --author "Your Name"
+fw market init openai -y  # Skip prompts
 ```
 
 ### Package Structure
@@ -124,8 +124,8 @@ flow-weaver-pack-openai/
 Validate your package and generate the manifest:
 
 ```bash
-flow-weaver market pack
-flow-weaver market pack --verbose  # Show parse warnings
+fw market pack
+fw market pack --verbose  # Show parse warnings
 ```
 
 This:
@@ -138,9 +138,9 @@ This:
 Publish to npm:
 
 ```bash
-flow-weaver market publish
-flow-weaver market publish --dry-run  # Preview without publishing
-flow-weaver market publish --tag beta # Publish with dist-tag
+fw market publish
+fw market publish --dry-run  # Preview without publishing
+fw market publish --tag beta # Publish with dist-tag
 ```
 
 ---
@@ -150,7 +150,7 @@ flow-weaver market publish --tag beta # Publish with dist-tag
 The `market pack` command validates packages against additional rules beyond standard workflow validation:
 
 - Package name must start with `flow-weaver-pack-`
-- Must include `flowweaver-marketplace-pack` keyword in `package.json`
+- Must include `flow-weaver-marketplace-pack` keyword in `package.json`
 - All exported node types must have proper annotations
 - All exported workflows must validate successfully
 - No conflicting node type names
@@ -240,7 +240,7 @@ Plugins extend the Flow Weaver Studio IDE with custom UI components, system logi
 ### Scaffold a Plugin
 
 ```bash
-flow-weaver plugin init my-plugin
+fw plugin init my-plugin
 ```
 
 Options:
@@ -267,7 +267,7 @@ Plugins register React components in specific areas of the Studio IDE:
 ### Plugin Structure
 
 ```bash
-flow-weaver plugin init my-plugin --area sidebar
+fw plugin init my-plugin --area sidebar
 ```
 
 Generates:

package/docs/reference/node-conversion.md

@@ -302,4 +302,4 @@ The compiler fully supports async expression nodes -- `await`, async detection,
 
 # Post-Conversion Validation
 
-After conversion, run `flow-weaver validate <file>` to verify the converted node types are correctly parsed.
+After conversion, run `fw validate <file>` to verify the converted node types are correctly parsed.

package/docs/reference/patterns.md

@@ -16,13 +16,13 @@ Patterns are reusable workflow fragments with boundary ports (`IN.`/`OUT.`) inst
 
 ```bash
 # List patterns in file or directory
-flow-weaver pattern list <path> [--json]
+fw pattern list <path> [--json]
 
 # Apply pattern to workflow
-flow-weaver pattern apply <pattern-file> <target-file> [--prefix p] [--name n] [--preview]
+fw pattern apply <pattern-file> <target-file> [--prefix p] [--name n] [--preview]
 
 # Extract pattern from workflow nodes
-flow-weaver pattern extract <source-file> --nodes a,b,c -o <output-file> [--name n] [--preview]
+fw pattern extract <source-file> --nodes a,b,c -o <output-file> [--name n] [--preview]
 ```
 
 ## Pattern Annotation
@@ -68,10 +68,10 @@ When applying a pattern:
 
 ```bash
 # Basic apply
-flow-weaver pattern apply pattern.ts workflow.ts
+fw pattern apply pattern.ts workflow.ts
 
 # With prefix to avoid conflicts
-flow-weaver pattern apply pattern.ts workflow.ts --prefix vt
+fw pattern apply pattern.ts workflow.ts --prefix vt
 
 # Output shows wiring instructions:
 # Applied pattern "validateTransform"
@@ -88,10 +88,10 @@ Extract nodes from an existing workflow to create a reusable pattern:
 
 ```bash
 # Extract specific nodes
-flow-weaver pattern extract my-workflow.ts --nodes validator,transformer -o my-pattern.ts
+fw pattern extract my-workflow.ts --nodes validator,transformer -o my-pattern.ts
 
 # Preview without writing
-flow-weaver pattern extract my-workflow.ts --nodes a,b -o output.ts --preview
+fw pattern extract my-workflow.ts --nodes a,b -o output.ts --preview
 ```
 
 The extractor:

package/docs/reference/scaffold.md

@@ -6,15 +6,15 @@ keywords: [scaffold, templates, create, generate, workflow, node, sequential, fo
 
 # Quick Start
 
-Use the `flow-weaver create` command to scaffold workflows and nodes from templates, or `flow-weaver init` to create a new project.
+Use the `fw create` command to scaffold workflows and nodes from templates, or `fw init` to create a new project.
 
 ## Create a Project
 
 ```bash
-flow-weaver init [directory] [options]
+fw init [directory] [options]
 ```
 
-Creates a new flow-weaver project with recommended structure, dependencies, and a starter workflow.
+Creates a new Flow Weaver project with recommended structure, dependencies, and a starter workflow.
 
 Options:
 - `--name <name>` / `-n` - Project name (defaults to directory name)
@@ -26,15 +26,15 @@ Options:
 - `--force` - Overwrite existing files
 
 ```bash
-flow-weaver init my-project
-flow-weaver init --template ai-agent -y
-flow-weaver init my-project --format cjs --no-git
+fw init my-project
+fw init --template ai-agent -y
+fw init my-project --format cjs --no-git
 ```
 
 ## Create Workflow
 
 ```bash
-flow-weaver create workflow <template> <file> [options]
+fw create workflow <template> <file> [options]
 ```
 
 Options:
@@ -50,14 +50,14 @@ Options:
 - `--config <json>` - Additional configuration as JSON
 
 ```bash
-flow-weaver create workflow ai-agent agent.ts --provider openai --model gpt-4o
-flow-weaver create workflow sequential pipeline.ts --nodes "fetch,parse,store" --async
+fw create workflow ai-agent agent.ts --provider openai --model gpt-4o
+fw create workflow sequential pipeline.ts --nodes "fetch,parse,store" --async
 ```
 
 ## Create Node
 
 ```bash
-flow-weaver create node <name> <file> [--template T] [--line N] [--preview]
+fw create node <name> <file> [--template T] [--line N] [--preview]
 ```
 
 Options:
@@ -72,7 +72,7 @@ Options:
 ## List Templates
 
 ```bash
-flow-weaver templates [--json]
+fw templates [--json]
 ```
 
 # Available Templates
@@ -117,39 +117,39 @@ flow-weaver templates [--json]
 
 ## Scaffold a workflow
 ```bash
-flow-weaver create workflow sequential my-workflow.ts
-flow-weaver validate my-workflow.ts
+fw create workflow sequential my-workflow.ts
+fw validate my-workflow.ts
 ```
 
 ## Scaffold an AI agent
 ```bash
-flow-weaver create workflow ai-agent agent.ts
+fw create workflow ai-agent agent.ts
 ```
 
 ## Add a node to existing file
 ```bash
-flow-weaver create node validateInput my-workflow.ts -t validator
-flow-weaver create node callLLM my-workflow.ts -t llm-call
+fw create node validateInput my-workflow.ts -t validator
+fw create node callLLM my-workflow.ts -t llm-call
 ```
 
 ## Insert at specific line
 ```bash
-flow-weaver create workflow sequential my-file.ts --line 10
+fw create workflow sequential my-file.ts --line 10
 ```
 
 ## Preview before writing
 ```bash
-flow-weaver create workflow foreach my-workflow.ts --preview
-flow-weaver create node myValidator file.ts -t validator --preview
+fw create workflow foreach my-workflow.ts --preview
+fw create node myValidator file.ts -t validator --preview
 ```
 
 # After Scaffolding
 
 1. **Customize** - Replace TODO comments with your logic
-2. **Validate** - Run `flow-weaver validate <file>`
-3. **Compile** - Run `flow-weaver compile <file>`
+2. **Validate** - Run `fw validate <file>`
+3. **Compile** - Run `fw compile <file>`
 
-See `flow-weaver docs iterative-development` for step-by-step workflow building.
+See `fw docs iterative-development` for step-by-step workflow building.
 
 ## Related Topics
 

package/docs/reference/tutorial.md

@@ -25,13 +25,13 @@ Start -> validator -> enricher -> scorer -> Exit
 Use the CLI to generate a starting point:
 
 ```bash
-flow-weaver create workflow sequential my-workflow.ts
+fw create workflow sequential my-workflow.ts
 ```
 
 This creates `my-workflow.ts` with a linear pipeline skeleton. Preview before writing:
 
 ```bash
-flow-weaver create workflow sequential my-workflow.ts --preview
+fw create workflow sequential my-workflow.ts --preview
 ```
 
 Open the generated file. It contains a placeholder workflow function with a single node. You will replace and expand it in the following steps.
@@ -165,12 +165,12 @@ This is useful when:
 - You want to use popular libraries (lodash, date-fns, etc.) directly
 - You don't want to write wrapper boilerplate
 
-Port types are inferred from TypeScript definitions. See `flow-weaver docs jsdoc-grammar` for full syntax.
+Port types are inferred from TypeScript definitions. See `fw docs jsdoc-grammar` for full syntax.
 
 After adding each function, validate to catch errors early:
 
 ```bash
-flow-weaver validate my-workflow.ts
+fw validate my-workflow.ts
 ```
 
 # Step 3: Wire the Workflow
@@ -217,7 +217,7 @@ Key points:
 Run the validator to check for annotation errors, missing connections, and type mismatches:
 
 ```bash
-flow-weaver validate my-workflow.ts
+fw validate my-workflow.ts
 ```
 
 If everything is correct you will see a success message. If there are issues, the output describes each problem. Common things to check:
@@ -230,7 +230,7 @@ If everything is correct you will see a success message. If there are issues, th
 For machine-readable output (useful in CI):
 
 ```bash
-flow-weaver validate my-workflow.ts --json
+fw validate my-workflow.ts --json
 ```
 
 # Step 5: Compile
@@ -238,7 +238,7 @@ flow-weaver validate my-workflow.ts --json
 Generate the executable code:
 
 ```bash
-flow-weaver compile my-workflow.ts
+fw compile my-workflow.ts
 ```
 
 This compiles the workflow in-place, modifying the source file directly. The compiled file contains:
@@ -252,7 +252,7 @@ The generated function has the same signature as your placeholder, so existing i
 For production builds (no debug events):
 
 ```bash
-flow-weaver compile my-workflow.ts --production
+fw compile my-workflow.ts --production
 ```
 
 # Step 6: Run
@@ -294,7 +294,7 @@ When the workflow does not behave as expected, use these techniques:
 ## Verbose validation
 
 ```bash
-flow-weaver validate my-workflow.ts --verbose
+fw validate my-workflow.ts --verbose
 ```
 
 Shows detailed information about parsed annotations, port types, and connection resolution.
@@ -306,8 +306,8 @@ Open the compiled source file and read the execution logic. Each node call is vi
 ## Describe the workflow structure
 
 ```bash
-flow-weaver describe my-workflow.ts
-flow-weaver describe my-workflow.ts --format mermaid
+fw describe my-workflow.ts
+fw describe my-workflow.ts --format mermaid
 ```
 
 Outputs the workflow graph as JSON or as a Mermaid diagram for visual inspection.
@@ -461,10 +461,10 @@ export function processRecord(
 
 ```bash
 # Validate
-flow-weaver validate my-workflow.ts
+fw validate my-workflow.ts
 
 # Compile
-flow-weaver compile my-workflow.ts
+fw compile my-workflow.ts
 
 # Run (from another file or a script)
 npx ts-node -e "
@@ -478,10 +478,10 @@ npx ts-node -e "
 
 # Alternative: Dev Mode
 
-Instead of running validate, compile, and run separately, use `flow-weaver dev` to do all three in a single watch loop:
+Instead of running validate, compile, and run separately, use `fw dev` to do all three in a single watch loop:
 
 ```bash
-flow-weaver dev my-workflow.ts --params '{"record": {"name": "Alice", "age": 30, "email": "alice@edu.com"}}'
+fw dev my-workflow.ts --params '{"record": {"name": "Alice", "age": 30, "email": "alice@edu.com"}}'
 ```
 
 This watches for file changes, recompiles, and re-runs automatically.
@@ -491,23 +491,23 @@ This watches for file changes, recompiles, and re-runs automatically.
 Visualize your workflow as an SVG diagram:
 
 ```bash
-flow-weaver diagram my-workflow.ts -o my-workflow.svg
-flow-weaver diagram my-workflow.ts --theme light -o my-workflow.svg
+fw diagram my-workflow.ts -o my-workflow.svg
+fw diagram my-workflow.ts --theme light -o my-workflow.svg
 ```
 
 # Next Steps
 
 Now that you have a working workflow, explore these topics to go further:
 
-- **CLI Reference** (`flow-weaver docs cli-reference`) -- Complete reference for all CLI commands and flags
-- **Advanced Annotations** (`flow-weaver docs advanced-annotations`) -- Pull execution, merge strategies, auto-connect, path/map sugar
-- **Compilation** (`flow-weaver docs compilation`) -- TypeScript and Inngest compilation targets, production mode, serve handlers
-- **Deployment** (`flow-weaver docs deployment`) -- Export to Lambda, Vercel, Cloudflare, Inngest; HTTP serve mode
-- **Built-in Nodes** (`flow-weaver docs built-in-nodes`) -- delay, waitForEvent, invokeWorkflow nodes and the mock system for testing
-- **Marketplace** (`flow-weaver docs marketplace`) -- Install and publish reusable node type packages
-- **Patterns** (`flow-weaver docs patterns`) -- Extract reusable workflow fragments and apply them across projects
-- **Scoped ports and forEach** (`flow-weaver docs export-interface`) -- Iterate over arrays using scoped ports and callback parameters
-- **Expression nodes** (`flow-weaver docs node-conversion`) -- Write pure functions without `execute`/`onSuccess`/`onFailure` boilerplate
-- **Scaffolding templates** (`flow-weaver docs scaffold`) -- Generate workflows from templates like `sequential`, `foreach`, `conditional`, and more
-- **Debugging** (`flow-weaver docs debugging`) -- WebSocket debugger, validation diagnostics, and error resolution
-- **JSDoc grammar** (`flow-weaver docs jsdoc-grammar`) -- Full annotation syntax reference including metadata brackets, scope clauses, and positioning
+- **CLI Reference** (`fw docs cli-reference`) -- Complete reference for all CLI commands and flags
+- **Advanced Annotations** (`fw docs advanced-annotations`) -- Pull execution, merge strategies, auto-connect, path/map sugar
+- **Compilation** (`fw docs compilation`) -- TypeScript and Inngest compilation targets, production mode, serve handlers
+- **Deployment** (`fw docs deployment`) -- Export to Lambda, Vercel, Cloudflare, Inngest; HTTP serve mode
+- **Built-in Nodes** (`fw docs built-in-nodes`) -- delay, waitForEvent, invokeWorkflow nodes and the mock system for testing
+- **Marketplace** (`fw docs marketplace`) -- Install and publish reusable node type packages
+- **Patterns** (`fw docs patterns`) -- Extract reusable workflow fragments and apply them across projects
+- **Scoped ports and forEach** (`fw docs export-interface`) -- Iterate over arrays using scoped ports and callback parameters
+- **Expression nodes** (`fw docs node-conversion`) -- Write pure functions without `execute`/`onSuccess`/`onFailure` boilerplate
+- **Scaffolding templates** (`fw docs scaffold`) -- Generate workflows from templates like `sequential`, `foreach`, `conditional`, and more
+- **Debugging** (`fw docs debugging`) -- WebSocket debugger, validation diagnostics, and error resolution
+- **JSDoc grammar** (`fw docs jsdoc-grammar`) -- Full annotation syntax reference including metadata brackets, scope clauses, and positioning

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synergenius/flow-weaver",
-  "version": "0.21.7",
+  "version": "0.21.11",
   "description": "Deterministic workflow compiler for AI agents. Compiles to standalone TypeScript, no runtime dependencies.",
   "private": false,
   "type": "module",
@@ -93,7 +93,8 @@
     }
   },
   "bin": {
-    "flow-weaver": "./dist/cli/flow-weaver.mjs"
+    "flow-weaver": "./dist/cli/flow-weaver.mjs",
+    "fw": "./dist/cli/flow-weaver.mjs"
   },
   "files": [
     "dist",