@meistrari/tela-cli 1.6.0 → 1.8.0

package/dist/docs/workflow-code/cli.md

@@ -1,6 +1,6 @@
 ## CLI
 
-The workflow command group documents implemented `init`, `create`, `compile`, `docs`, `codegen`, `sync`, and `publish` workflows. Current MVP behavior is local-first until you run an explicit remote lifecycle command such as `create`, `sync`, or `publish`.
+The workflow command group documents implemented `init`, `create`, `compile`, `docs`, `codegen`, `sync`, `publish`, and `watch` workflows. Current MVP behavior is local-first until you run an explicit remote lifecycle command such as `create`, `sync`, `publish`, or `watch`.
 
 ### Command surface
 
@@ -13,10 +13,11 @@ The workflow command group documents implemented `init`, `create`, `compile`, `d
 | `create <target> [--project <project-id>] [--config <path>] [--env <path>] [--json]` | Implemented | Yes | Provision a remote workflow, bind it to the active context, scaffold source, and sync when possible. |
 | `sync [target] [--config <path>] [--env <path>] [--yes] [--json]` | Implemented | Yes | Synchronize local compiled workflow(s) with configured Tela prompt(s). |
 | `publish [target] [--environment <name>] [--create-environment-if-missing] [--config <path>] [--env <path>] [--yes] [--json]` | Implemented | Yes | Publish local-matching workflow version(s) to the selected workflow environment. |
+| `watch [target] [--config <path>] [--env <path>] [--json]` | Implemented | Yes | Run an initial compile, codegen, and sync cycle, then serialize debounced source, config, and Tela context changes until stopped. |
 
 ### Target selection
 
-The positional target is the key inside `workflow-code.config.ts` `workflows`. `create` always requires exactly one target. If `compile` sees exactly one configured workflow, the target may be omitted; with multiple workflows it is required. `sync` and `publish` use the same target key and run every configured workflow when it is omitted. For publish, `--environment <name>` selects the workflow publication environment and is independent from the active Tela Local context. `--env <path>` remains scoped to dotenv-backed config/source evaluation and does not select the remote Tela context.
+The positional target is the key inside `workflow-code.config.ts` `workflows`. `create` always requires exactly one target. If `compile` sees exactly one configured workflow, the target may be omitted; with multiple workflows it is required. `sync`, `publish`, and `watch` use the same target key and run every configured workflow when it is omitted. For publish, `--environment <name>` selects the workflow publication environment and is independent from the active Tela Local context. `--env <path>` remains scoped to dotenv-backed config/source evaluation and does not select the remote Tela context.
 
 ```bash
 tela workflow compile
@@ -29,6 +30,8 @@ tela workflow sync
 tela workflow sync invoice-processing --env .env.staging --json
 tela workflow publish
 tela workflow publish invoice-processing --environment staging --json
+tela workflow watch
+tela workflow watch invoice-processing --env .env.staging
 ```
 
 ### init
@@ -224,6 +227,29 @@ tela workflow publish invoice-processing --environment dev --create-environment-
 tela workflow publish --environment production --yes --json
 ```
 
+### watch
+
+**Description.** `tela workflow watch` runs an initial compile, codegen, and sync cycle for the selected workflow(s), then watches local source files, the workflow-code config, and the active Tela Local config file (`~/.tela/config.json` or `$TELA_HOME/config.json`) for changes. Rapid edits debounce into one re-run, and file events that arrive while a cycle is already running coalesce into one serialized follow-up cycle, so codegen and sync do not overlap.
+
+Each cycle reloads config before syncing, so newly added targets, changed entries, and newly imported source files are picked up without restarting watch. Each cycle also refreshes the shared workspace catalog (the same mechanism as `codegen`) and, when the active Tela Local context changes, automatically switches to that context's lockfile before the next sync while reporting the prior and new context in human output. If the active context is unchanged, watch prints no context-change notice.
+
+A compile failure in one workflow blocks only that workflow's sync and does not stop the watch loop. Watch never publishes and ignores project `.tela/` writes, including lockfiles, catalog snapshots, and generated augmentation files, so it cannot trigger itself. Watcher backend errors are reported with diagnostics and close the watcher. Stop watch with Ctrl+C; the routed Tela CLI removes its SIGINT handler after shutdown.
+
+| Prop | Type | Required | Description |
+|---|---|---:|---|
+| `target` | Positional | No | Config `workflows` key to watch. Omit to watch every configured workflow. |
+| `--config <path>` | Flag | No | Load a custom config file instead of `workflow-code.config.ts`. |
+| `--env <path>` | Flag | No | Load a custom dotenv file before evaluating config. |
+| `--json` | Flag | No | Emit one JSON line per watch cycle (codegen and per-target sync results, plus a context-changed flag) instead of formatted terminal output. |
+
+**Examples.**
+
+```bash
+tela workflow watch
+tela workflow watch invoice-processing
+tela workflow watch invoice-processing --env .env.staging
+```
+
 
 
 ### JSON diagnostics

package/dist/docs/workflow-code/manifest.json

@@ -20,7 +20,7 @@
       "slug": "cli",
       "title": "CLI",
       "file": "cli.md",
-      "sha256": "aaa6b661a7adf7bebcb22a0881e604034886515440468fad7e20c7e5ce3a2e6d"
+      "sha256": "e1ad966acd236d4b80ccedc101f808f295b1917b05cf16831131265c22a6e8a2"
     },
     {
       "slug": "config",