@foresthubai/workflow-cli 0.3.0 → 0.4.1

package/NOTICE

@@ -17,7 +17,7 @@ source must be made available to users of that service — it is the
 repository linked above.
 
 It also bundles @foresthubai/workflow-core (Apache-2.0) and the
-third-party libraries ajv, ajv-formats, js-yaml, and jsep, each under
-its own license. See THIRD_PARTY_NOTICES in the repository.
+third-party libraries ajv, ajv-formats, js-yaml, jsep, and zod, each
+under its own license. See THIRD_PARTY_NOTICES in the repository.
 
 For commercial licensing inquiries: root@foresthub.ai

package/README.md

@@ -27,6 +27,7 @@ fh-workflow open [file.json] [--static|--dev]   Open the visual builder; optiona
 fh-workflow check-schema <file.json>            Structural schema check against the contract. Non-zero on mismatch.
 fh-workflow validate <file.json>                Semantic validation (references, wiring, types). Non-zero on errors.
 fh-workflow update <file.json> [out.json]       Migrate a workflow to the current schema version.
+fh-workflow deploy <file.json> [flags]          Generate a self-contained deployment bundle. --help for flags.
 fh-workflow help | -h | --help                  Print usage.
 ```
 
@@ -67,6 +68,21 @@ Suitable for CI / pre-commit.
 Migrates a workflow document up to the current schema version, in place or to a
 second path.
 
+### `deploy <file.json> [flags]`
+
+Generates a self-contained, **standalone** deployment bundle for an edge controller —
+a directory the engine boots from directly, with no backend and no account. It always
+holds `workflow.json`, `docker-compose.yml`, `.env` (operator config, written `0600`),
+and a `README.md` with the build/transfer/run steps. Workflows that declare hardware,
+MQTT, or custom models additionally get `device_manifest.json`, `external_resources.json`
+(`0600`), and `deployment_mapping.json`.
+
+Missing values are filled in **interactively** at a terminal. Without a terminal (a
+Claude Code skill, CI), supply them through `--values <file.json>` — a partial deploy
+config as JSON; any still-missing required value exits non-zero. LLM provider keys can
+also be passed as flags (`--anthropic-key`, …). Run `fh-workflow deploy --help` for the
+full flag list.
+
 ## In-repo development
 
 From `ts/workflow-cli` (resolves the libraries to **source**, so editing core/builder
@@ -94,7 +110,7 @@ FH_BUILDER_MODE=static npm run open -- sample.json
 | Script | Does |
 | --- | --- |
 | `dev` | `vite` — dev server, blank canvas, HMR |
-| `open` / `check-schema` / `validate` / `cli` | the dev CLI via `tsx` (`cli` = no preset subcommand) |
+| `open` / `check-schema` / `validate` / `deploy` / `cli` | the dev CLI via `tsx` (`cli` = no preset subcommand) |
 | `build` | `vite build` — the SPA bundle → `dist/` |
 | `build:cli` | esbuild — the CLI bundle → `dist-cli/cli.js` (+ `workflow.yaml`) |
 | `build:all` | both of the above; the publishable artifacts |