@walkeros/cli 2.0.1 → 2.1.1

package/CHANGELOG.md

@@ -1,5 +1,71 @@
 # @walkeros/cli
 
+## 2.1.1
+
+### Patch Changes
+
+- Updated dependencies [fab477d]
+  - @walkeros/core@2.1.1
+  - @walkeros/server-core@2.1.1
+
+## 2.1.0
+
+### Minor Changes
+
+- cb2da05: Add data contracts for centralized event validation and documentation
+- fed78f0: Replace deployment polling with SSE streaming for real-time status
+  updates
+- 3eb6416: Add unified `env.respond` capability. Any step (transformer,
+  destination) can now customize HTTP responses via
+  `env.respond({ body, status?, headers? })`. Sources configure the response
+  handler — Express source uses createRespond for idempotent first-call-wins
+  semantics. CLI serve mode removed (superseded by response-capable flows).
+- 39780b0: Add event usage counters to heartbeat reporting
+- dd53425: Simplify `walkeros run collect` to `walkeros run` — the mode concept
+  has been removed
+- 66aaf2d: Runner-owned health server: The runner now provides /health and
+  /ready endpoints independently of flow sources. Express source's `status`
+  setting and fetch source's `healthPath` setting have been removed — health
+  endpoints are no longer source responsibilities.
+- 97df0b2: Simplify validate command: file-first argument, --type defaults to
+  flow, deep validation merged into flow, entry validation moved to --path
+- 026c412: Unified simulation API: single simulate() function replaces
+  simulateSource/simulateDestination/simulateTransformer/simulateFlow. Built-in
+  call tracking for destinations via wrapEnv. No bundling required for
+  simulation.
+
+### Patch Changes
+
+- fed78f0: Show logo only on bare `walkeros` call, not before every command
+- 7b7e37b: Consolidate flow validation to use core's validateFlowSetup, adding
+  $var/$def reference checking and IntelliSense context extraction
+- 5145662: Use os.tmpdir() as default temp directory to fix permission errors in
+  containers
+- 02a7958: Add WARN log level (ERROR=0, WARN=1, INFO=2, DEBUG=3). Logger
+  instances expose `warn()` method routed to `console.warn` and `json()` method
+  for structured output. Config accepts optional `jsonHandler`. MockLogger
+  includes both as jest mocks. CLI logger unified with core logger via
+  `createCLILogger()` factory.
+- 3bc32de: Surface mapping field in examples_list and ExampleLookupResult
+- 5145662: Add --output URL support, -f shorthand for --flow, and lazy-load
+  esbuild in runtime
+- 7fc4cee: Fix server bundle port forwarding from runtime context to source
+  configs
+- 1876bb9: Remove unused bundle simulation path, CallTracker, and executor files
+  from simulate command. Simulate now only accepts Flow.Setup config JSON files.
+- Updated dependencies [7fc4cee]
+- Updated dependencies [7fc4cee]
+- Updated dependencies [cb2da05]
+- Updated dependencies [2bbe8c8]
+- Updated dependencies [3eb6416]
+- Updated dependencies [02a7958]
+- Updated dependencies [97df0b2]
+- Updated dependencies [97df0b2]
+- Updated dependencies [026c412]
+- Updated dependencies [7d38d9d]
+  - @walkeros/core@2.1.0
+  - @walkeros/server-core@2.1.0
+
 ## 2.0.1
 
 ## 2.0.0

package/README.md

@@ -48,14 +48,11 @@ walkeros bundle flow.json
 # Test with simulated events (no real API calls)
 walkeros simulate flow.json --event '{"name":"product view"}'
 
-# Or test a pre-built bundle directly
-walkeros simulate dist/bundle.mjs --event '{"name":"product view"}'
-
 # Push real events to destinations
 walkeros push flow.json --event '{"name":"product view"}'
 
 # Run a collection server locally
-walkeros run collect dist/bundle.mjs --port 3000
+walkeros run dist/bundle.mjs --port 3000
 ```
 
 ## Commands
@@ -100,25 +97,17 @@ walkeros bundle flow.json --dockerfile Dockerfile.custom
 ```
 
 The output path uses convention-based defaults: `./dist/bundle.mjs` for server,
-`./dist/walker.js` for web. The `--dockerfile` flag generates a Dockerfile with
-the correct `MODE` (collect/serve) based on flow type.
+`./dist/walker.js` for web.
 
 ### simulate
 
-Test event processing with simulated events. Accepts either a config JSON (which
-gets bundled) or a pre-built bundle (executed directly).
+Test event processing with simulated events. The config JSON gets bundled and
+executed with destination mocking.
 
 ```bash
-walkeros simulate <input> --event '{"name":"page view"}' [options]
+walkeros simulate <config> --event '{"name":"page view"}' [options]
 ```
 
-**Input types:**
-
-- **Config JSON** - Bundled and executed with destination mocking
-- **Pre-built bundle** (`.js`/`.mjs`) - Executed directly, no mocking
-
-The CLI auto-detects the input type by attempting to parse as JSON.
-
 **Options:**
 
 - `-e, --event <json>` - Event to simulate (JSON string, file path, or URL)
@@ -138,23 +127,8 @@ walkeros simulate examples/web-serve.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"}'
-
-# Override platform detection
-walkeros simulate dist/bundle.js --platform server --event '{"name":"page view"}'
 ```
 
-**Platform detection:**
-
-When using pre-built bundles, platform is detected from file extension:
-
-- `.mjs` → server (ESM, Node.js)
-- `.js` → web (IIFE, JSDOM)
-
-Use `--platform` to override if extension doesn't match intended runtime.
-
 ### push
 
 Execute your flow with real API calls to configured destinations. Unlike
@@ -221,14 +195,9 @@ real integrations.
 Run flows locally (no Docker daemon required).
 
 ```bash
-walkeros run <mode> <config-file> [options]
+walkeros run <config-file> [options]
 ```
 
-**Modes:**
-
-- `collect` - HTTP event collection server
-- `serve` - Static file server
-
 **Options:**
 
 - `-p, --port <number>` - Server port
@@ -241,13 +210,10 @@ walkeros run <mode> <config-file> [options]
 
 ```bash
 # Run collection server (auto-bundles JSON)
-walkeros run collect examples/server-collect.json --port 3000
+walkeros run examples/server-collect.json --port 3000
 
 # Run with pre-built bundle
-walkeros run collect examples/server-collect.mjs --port 3000
-
-# Serve static files
-walkeros run serve flow.json --port 8080 --static-dir ./dist
+walkeros run examples/server-collect.mjs --port 3000
 ```
 
 **How it works:**
@@ -257,6 +223,51 @@ walkeros run serve flow.json --port 8080 --static-dir ./dist
 3. Runs in current Node.js process
 4. Press Ctrl+C for graceful shutdown
 
+### validate
+
+Validate flow configurations, events, mappings, or contracts.
+
+```bash
+walkeros validate <config-file> [options]
+```
+
+By default, validates a Flow.Setup file — checking schema, references, and
+cross-step example compatibility.
+
+**Options:**
+
+- `--type <type>` - Validation type (default: `flow`). Also accepts: `event`,
+  `mapping`, `contract`
+- `--path <path>` - Validate a specific entry against its package schema (e.g.,
+  `destinations.snowplow`, `sources.browser`)
+- `--flow <name>` - Flow name for multi-flow configs
+- `--strict` - Treat warnings as errors
+- `--json` - Output as JSON
+- `-v, --verbose` - Verbose output
+- `-s, --silent` - Suppress output
+
+**Exit codes:** `0` = valid, `1` = errors, `2` = warnings (with --strict), `3` =
+input error
+
+**Examples:**
+
+```bash
+# Validate flow config (schema + examples)
+walkeros validate flow.json
+
+# Validate specific flow
+walkeros validate flow.json --flow analytics
+
+# Validate a single event
+walkeros validate event.json --type event
+
+# Validate in CI
+walkeros validate flow.json --json --strict || exit 1
+
+# Validate entry against package schema
+walkeros validate flow.json --path destinations.snowplow
+```
+
 ### deploy
 
 Deploy flows to walkerOS cloud.
@@ -508,7 +519,7 @@ const result = await simulate(
 );
 
 // Run
-await runCommand('collect', {
+await runCommand({
   config: './flow.json',
   port: 3000,
   verbose: true,
@@ -536,7 +547,7 @@ walkeros simulate \
   --event '{"name":"product view","data":{"id":"P123"}}'
 
 # Run server
-walkeros run collect examples/server-collect.json --port 3000
+walkeros run examples/server-collect.json --port 3000
 ```
 
 ## Development Workflow
@@ -557,7 +568,7 @@ walkeros simulate \
 walkeros bundle my-flow.json --stats
 
 # 4. Run locally
-walkeros run collect dist/bundle.mjs --port 3000
+walkeros run dist/bundle.mjs --port 3000
 
 # 5. In another terminal, test it
 curl -X POST http://localhost:3000/collect \
@@ -616,7 +627,7 @@ Run the bundle directly with the CLI:
 walkeros bundle flow.json
 
 # Run in production
-walkeros run collect dist/bundle.mjs --port 8080
+walkeros run dist/bundle.mjs --port 8080
 ```
 
 This runs the flow in the current Node.js process, suitable for deployment on