@eigenpal/cli 0.4.2 → 0.4.4

package/dist/skill/reference/dataset-format.md

@@ -5,7 +5,7 @@ itself is the manifest — there is no top-level `manifest.json`. The
 import endpoint **rejects** archives that contain one (legacy format).
 
 This is the format the CLI builds and ships to
-`eigenpal workflow dataset push <wf-id> --file dataset/`. After it lands
+`eigenpal workflow dataset push <workflow-id> --file dataset/`. After it lands
 on the server, the canonical per-row surface is
 `eigenpal workflow dataset example {get,create,update,delete}` (and
 `dataset list` for a table view) — the local folder is a pre-push
@@ -163,10 +163,10 @@ Reports per-example issues:
 
 ```bash
 # Replace = wipes existing examples for the workflow, uploads the folder fresh.
-eigenpal workflow dataset push <wf-id> --file ./dataset --mode replace
+eigenpal workflow dataset push <workflow-id> --file ./dataset --mode replace
 
 # Append = adds to whatever's already on the server.
-eigenpal workflow dataset push <wf-id> --file ./dataset --mode append
+eigenpal workflow dataset push <workflow-id> --file ./dataset --mode append
 ```
 
 The endpoint streams progress as NDJSON. The terminal `done` event
@@ -183,8 +183,8 @@ includes `{ created, expectedSet, … }`:
 To inspect or round-trip what's currently on the server:
 
 ```bash
-eigenpal workflow dataset list <wf-id>
-eigenpal workflow dataset pull <wf-id> --out current.zip
+eigenpal workflow dataset list <workflow-id>
+eigenpal workflow dataset pull <workflow-id> --out current.zip
 # (or omit --out to stream the zip to stdout for piping)
 ```
 
@@ -200,8 +200,8 @@ re-zipping and re-uploading the whole folder.
 ### Inspect one example end-to-end
 
 ```bash
-eigenpal workflow dataset example get <wf-id> <example-id>
-eigenpal workflow dataset example get <wf-id> <example-id> --json | jq '.expectedOutput'
+eigenpal workflow dataset example get <workflow-id> <example-id>
+eigenpal workflow dataset example get <workflow-id> <example-id> --json | jq '.expectedOutput'
 ```
 
 Pretty mode prints labelled `Inputs` / `Expected` / `Metadata` sections;
@@ -216,7 +216,7 @@ eigenpal workflow execution get exec_… --json | jq '.output.data' > /tmp/corre
 
 # 2. Patch the example's expected output in place. PATCH semantics:
 #    every flag you omit is left alone.
-eigenpal workflow dataset example update <wf-id> <example-id> \
+eigenpal workflow dataset example update <workflow-id> <example-id> \
   --expected-file /tmp/correct.json
 ```
 
@@ -226,7 +226,7 @@ empty string to clear an annotation: `--annotation ""`.
 ### Add one new example
 
 ```bash
-eigenpal workflow dataset example create <wf-id> \
+eigenpal workflow dataset example create <workflow-id> \
   --name missing-required-field \
   --input-json '{"language":"en"}' \
   --expected-file /tmp/expected.json \
@@ -243,7 +243,7 @@ scalar args + `expected/output.json`-style outputs.
 ### Delete one bad example
 
 ```bash
-eigenpal workflow dataset example delete <wf-id> <example-id> --yes
+eigenpal workflow dataset example delete <workflow-id> <example-id> --yes
 ```
 
 `--yes` is required for non-TTY shells (CI). Interactive shells may

package/dist/skill/reference/debugging.md

@@ -11,18 +11,21 @@ eigenpal workflow execution compare <a> <b>           # side-by-side diff of two
 ## 1. Reproduce the failure
 
 ```bash
-eigenpal workflow execution run <workflow-name> <example-name>
+eigenpal workflow execution run <workflow-id> <example-name>
 ```
 
-Streams a live step list as the run progresses. Bails to the prompt
-the moment a step transitions to `failed`.
+`<workflow-id>` is either a `wf_…` id or a slug (the YAML's `name:`
+field). The workflow must be pushed (`eigenpal workflow push`) before
+`execution run` works — only saved workflows execute. Streams a live
+step list as the run progresses. Bails to the prompt the moment a step
+transitions to `failed`.
 
 If the workflow is server-stable and the failure is on a real
 historical execution, skip the rerun and pull the recorded execution
 directly:
 
 ```bash
-eigenpal workflow execution list <wf-id> --status failed --limit 5
+eigenpal workflow execution list <workflow-id> --status failed --limit 5
 eigenpal workflow execution get exec_…
 ```
 
@@ -185,7 +188,7 @@ regressions vs improvements; aggregate stats at the bottom.
 
 **No `--workflow-id` needed.** The server resolves the owning workflow
 from each batch id. Both batches must belong to the same workflow within
-your tenant. (Sibling `experiment` subcommands still take `<wf-id>` as
+your tenant. (Sibling `experiment` subcommands still take `<workflow-id>` as
 the first positional — only `compare` is workflow-agnostic.)
 
 ## 7. Connection vs auth errors
@@ -239,14 +242,14 @@ steps were faked. Re-import the dataset (`workflow dataset push
 
 ```bash
 # Kicks off, prints { batchId, executionIds }
-eigenpal workflow experiment run <wf-id>
+eigenpal workflow experiment run <workflow-id>
 
 # --watch polls until every execution is terminal, prints a per-example
 # failure summary, and exits non-zero if any failed/cancelled.
-eigenpal workflow experiment status <wf-id> --batch-id <id> --watch
+eigenpal workflow experiment status <workflow-id> --batch-id <id> --watch
 
 # Without --watch: one-shot snapshot, no polling. Prefer --watch in CI / agents.
-eigenpal workflow experiment status <wf-id> --batch-id <id>
+eigenpal workflow experiment status <workflow-id> --batch-id <id>
 ```
 
 The terminal `--watch` output looks like:

package/dist/skill/reference/evaluators.md

@@ -135,20 +135,20 @@ Reports field-level issues:
 
 ```bash
 # Push the evaluators (overwrites the workflow's existing config).
-eigenpal workflow evaluators push <wf-id> --file evaluators.yaml
+eigenpal workflow evaluators push <workflow-id> --file evaluators.yaml
 
 # Kick off a server-side batch eval over the whole pushed dataset.
 # Returns { batchId, executionIds }.
-eigenpal workflow experiment run <wf-id>
+eigenpal workflow experiment run <workflow-id>
 
 # Or restrict to a single example:
-eigenpal workflow experiment run <wf-id> --example-id evx_…
+eigenpal workflow experiment run <workflow-id> --example-id evx_…
 
 # Watch progress.
-eigenpal workflow experiment status <wf-id> --batch-id <id>
+eigenpal workflow experiment status <workflow-id> --batch-id <id>
 
 # Pull results when done.
-eigenpal workflow experiment results <wf-id> --batch-id <id> \
+eigenpal workflow experiment results <workflow-id> --batch-id <id> \
   --format csv --out results.csv
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eigenpal/cli",
-  "version": "0.4.2",
+  "version": "0.4.4",
   "description": "Eigenpal CLI — author and run document workflows from your terminal. Agent-ready.",
   "keywords": [
     "eigenpal",
@@ -24,7 +24,7 @@
     "url": "git+https://github.com/eigenpal/cli.git"
   },
   "license": "Apache-2.0",
-  "author": "Eigenpal <hello@eigenpal.com> (https://eigenpal.com)",
+  "author": "Jedr Blaszyk <jedr@eigenpal.com> (https://eigenpal.com)",
   "type": "module",
   "main": "./src/index.ts",
   "types": "./src/index.ts",
@@ -49,13 +49,13 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@clack/prompts": "^0.10.1",
+    "@clack/prompts": "^1.3.0",
     "ajv": "^8.17.1",
-    "commander": "^13.1.0",
+    "commander": "^14.0.3",
     "fflate": "0.8.2",
     "openai": "^6.27.0",
     "picocolors": "^1.1.1",
-    "quickjs-emscripten": "^0.31.0",
+    "quickjs-emscripten": "^0.32.0",
     "yaml": "^2.7.0",
     "zod": "^4.0.0"
   },
@@ -63,7 +63,7 @@
     "@eigenpal/types": "workspace:*",
     "@eigenpal/workflow-yaml": "workspace:*",
     "@t3-oss/env-core": "^0.13.11",
-    "typescript": "^5.3.0"
+    "typescript": "^6.0.3"
   },
   "files": [
     "dist",