@walkeros/cli 1.0.0 → 1.0.1-next-1768820936934

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # @walkeros/cli
 
+## 1.0.1-next-1768820936934
+
+### Patch Changes
+
+- eb878df: Improved CLI option consistency and added `--dockerfile` flag
+  improvements
+
+  **Option consistency:**
+  - Added `--flow` option to simulate command for multi-flow configs
+  - Standardized `-v/--verbose` and `-s/--silent` shortcuts across all commands
+  - Removed non-functional `--dry-run` option from all commands
+  - Removed `-f` shortcut from bundle (use `--flow` for consistency)
+  - Unified option description casing (lowercase)
+
+  **Dockerfile improvements:**
+  - Generate correct `MODE=serve` for web flows and `MODE=collect` for server
+    flows
+  - Support copying custom Dockerfiles with `--dockerfile path/to/Dockerfile`
+  - Respects `--flow` parameter for multi-flow configurations
+
 ## 1.0.0
 
 ### Major Changes

package/README.md

@@ -77,22 +77,31 @@ walkeros bundle https://example.com/config.json                  # Remote URL
 
 **Options:**
 
-- `-f, --flow <name>` - Build specific flow (multi-flow configs)
-- `--all` - Build all flows
-- `-s, --stats` - Show bundle statistics
-- `--json` - Output stats as JSON
+- `--flow <name>` - Flow name for multi-flow configs
+- `--all` - Build all flows for multi-flow configs
+- `--stats` - Show bundle statistics
+- `--json` - Output as JSON (implies --stats)
 - `--no-cache` - Disable package caching
+- `--dockerfile [file]` - Generate Dockerfile (or copy custom file) to dist/
 - `-v, --verbose` - Verbose output
+- `-s, --silent` - Suppress output
 
-**Example:**
+**Examples:**
 
 ```bash
 # Bundle with stats
 walkeros bundle examples/server-collect.json --stats
+
+# Bundle with auto-generated Dockerfile
+walkeros bundle flow.json --dockerfile
+
+# Bundle with custom Dockerfile
+walkeros bundle flow.json --dockerfile Dockerfile.custom
 ```
 
 The output path uses convention-based defaults: `./dist/bundle.mjs` for server,
-`./dist/walker.js` for web.
+`./dist/walker.js` for web. The `--dockerfile` flag generates a Dockerfile with
+the correct `MODE` (collect/serve) based on flow type.
 
 ### simulate
 
@@ -112,10 +121,12 @@ The CLI auto-detects the input type by attempting to parse as JSON.
 
 **Options:**
 
-- `-e, --event <json>` - Event JSON string (required)
+- `-e, --event <json>` - Event to simulate (JSON string, file path, or URL)
+- `--flow <name>` - Flow name for multi-flow configs
 - `-p, --platform <platform>` - Platform override (`web` or `server`)
-- `--json` - Output results as JSON
+- `--json` - Output as JSON
 - `-v, --verbose` - Verbose output
+- `-s, --silent` - Suppress output
 
 **Examples:**
 
@@ -125,6 +136,9 @@ walkeros simulate examples/web-serve.json \
   --event '{"name":"page view","data":{"title":"Home"}}' \
   --json
 
+# Simulate specific flow from multi-flow config
+walkeros simulate flow.json --flow server --event '{"name":"test"}'
+
 # Simulate with pre-built bundle
 walkeros simulate dist/bundle.mjs --event '{"name":"page view"}'
 
@@ -219,9 +233,9 @@ walkeros run <mode> <config-file> [options]
 
 - `-p, --port <number>` - Server port
 - `-h, --host <host>` - Server host
-- `--static-dir <dir>` - Static directory (serve mode)
-- `--json` - JSON output
+- `--json` - Output as JSON
 - `-v, --verbose` - Verbose output
+- `-s, --silent` - Suppress output
 
 **Examples:**
 
@@ -537,18 +551,24 @@ Deploy your flows using Docker or Node.js.
 The `walkeros/flow` image runs pre-built bundles in production:
 
 ```bash
-# Build your flow
-walkeros bundle flow.json
+# Build your flow with Dockerfile
+walkeros bundle flow.json --dockerfile
+
+# Deploy (e.g., to Cloud Run)
+gcloud run deploy my-service --source ./dist
+```
 
-# Run with Docker
+Or run locally:
+
+```bash
 docker run -v ./dist:/flow -p 8080:8080 walkeros/flow
 ```
 
-**Custom image:**
+**Custom Dockerfile:**
 
-```dockerfile
-FROM walkeros/flow
-COPY dist/bundle.mjs /app/flow/
+```bash
+# Use a custom Dockerfile with extra packages or configuration
+walkeros bundle flow.json --dockerfile Dockerfile.custom
 ```
 
 **Environment variables:**

package/dist/examples/README.md

@@ -39,6 +39,39 @@ cp examples/web-serve.js ../docker/demos/demo-serve.mjs
 **Important**: Always use `--local` flag when rebuilding examples in the
 devcontainer.
 
+## Comprehensive Example
+
+### flow-complete.json
+
+**Purpose**: Complete reference demonstrating ALL JSON-compatible walkerOS
+features
+
+**Features**: 51 features including variables, definitions, mapping (key, map,
+loop, set), transformers (validator, fingerprint), consent gating, wildcards,
+ingest metadata, and more.
+
+**Architecture**: Two named flows (`web` and `server`) showing full event
+pipeline from browser to server-side forwarding.
+
+**Documentation**: See [flow-complete.md](./flow-complete.md) for the complete
+Feature Inventory and usage examples.
+
+**Try it**:
+
+```bash
+# Web flow (opens browser with demo events)
+walkeros serve examples/flow-complete.json --flow web
+
+# Server flow (HTTP collection endpoint)
+walkeros run examples/flow-complete.json --flow server
+
+# Both (full pipeline)
+# Terminal 1: walkeros run examples/flow-complete.json --flow server
+# Terminal 2: walkeros serve examples/flow-complete.json --flow web
+```
+
+---
+
 ## Web Examples
 
 ### web-serve.json