@eigenpal/cli 0.7.2 → 0.9.0

package/dist/skill/reference/debugging.md

@@ -54,7 +54,7 @@ The grouped run payload includes:
     substitution. Lets you see what the LLM actually got, what URL
     HTTP actually hit, what items the script actually saw. Populated
     for `ai.*` / `transform.*` / `action.*`. Null for `control.*`
-    (orchestration steps don't have a meaningful resolved config).
+    (orchestration steps do not have a meaningful resolved config).
   - `output` — what the step returned
   - `error` — error message + code when `status: 'failed'`
   - `durationMs`
@@ -108,7 +108,7 @@ no network or filesystem, so most timeouts are infinite-loop bugs.
 
 ### `step_type_unknown`
 
-`workflow.yaml` references a `type:` that the deployment doesn't know
+`workflow.yaml` references a `type:` that the deployment does not know
 about. Common after a typo or a step type that was renamed.
 
 ```bash
@@ -219,7 +219,7 @@ broken. If you see:
   Set EIGENPAL_BASE_URL or pass --base-url <url>.
 ```
 
-That's a **connection** error — the URL is wrong, the server is down,
+That is a **connection** error — the URL is wrong, the server is down,
 or your network is blocked. The URL the CLI tried is echoed back so a
 stale `EIGENPAL_BASE_URL` is immediately obvious.
 
@@ -230,13 +230,13 @@ If instead you see:
   Run `eigenpal auth login`, or set EIGENPAL_API_KEY in your env.
 ```
 
-That's an **auth** error — the URL works but your key is missing /
+That is an **auth** error — the URL works but your key is missing /
 expired / scoped to the wrong tenant. Run `auth list` to see configured
 profiles, or `auth use <name>` to switch.
 
 ## 8. Override a flaky step in eval mode
 
-If a step calls an external system that's unreliable (an external API, a
+If a step calls an external system that is unreliable (an external API, a
 private API, a rate-limited connector), short-circuit it for evals via
 the example's `meta.json`:
 

package/dist/skill/reference/evaluators.md

@@ -54,7 +54,7 @@ finance) who never see the YAML or the judge prompt. Write it for them:
 
 ## Evaluator types
 
-### `exact-diff` — JSON deep-diff against `expected/output.json` or `expected/error.json`
+### `exact-diff` — JSON deep-diff against `expected.json`
 
 ```yaml
 - name: invoice-fields
@@ -71,8 +71,8 @@ finance) who never see the YAML or the judge prompt. Write it for them:
   is compared.
 
 `exact-diff` branches on the example's expected shape: success-expected
-examples (`expected/output.json`) are diffed against the workflow's actual
-output, and failure-expected examples (`expected/error.json`, see
+examples (`expected.json`) are diffed against the workflow's actual output, and
+failure-expected examples (`expected.json` with `$error`, see
 `reference/dataset-format.md`) are matched against the `control.fail`
 envelope persisted to `executions.error`. The same evaluator handles both
 paths; you do not need a separate evaluator for failure cases.
@@ -106,7 +106,7 @@ paths; you do not need a separate evaluator for failure cases.
       Pick the label that best matches the tone of the response.
 ```
 
-`promptExtension` is the only required field — it's appended to the harness
+`promptExtension` is the only required field — it is appended to the harness
 prompt and tells the judge what "good" looks like for this workflow. The
 harness handles JSON parsing, retries, and feeds the judge `actual`,
 `expected`, and example metadata. In `discrete` mode the judge MUST return
@@ -140,7 +140,7 @@ verbatim, same text the dashboard editor shows. The `: number` return-type annot
 enforced at parse time. The dashboard seeds new evaluators with a
 `WorkflowOutput` type alias derived from the workflow's `output:`
 declaration, plus `Expected` / `Actual` aliases for compatibility. Plain
-`unknown` works too if you don't want a typed signature.
+`unknown` works too if you do not want a typed signature.
 
 The signature shape is **locked**:
 
@@ -151,7 +151,7 @@ The signature shape is **locked**:
   and scored as 0).
 
 `workflow validate` and `workflow evaluators validate` flag YAML where
-the function fails to parse, the signature doesn't match, or the body
+the function fails to parse, the signature does not match, or the body
 contains neither `return` nor `throw` — so a hand-edited config errors
 before it reaches the worker.
 
@@ -224,7 +224,7 @@ eigenpal workflow experiment results <workflow-id> <batch-id> \
   --format csv --out results.csv
 ```
 
-The signed-URL pattern means large result sets don't go through the CLI
+The signed-URL pattern means large result sets do not go through the CLI
 process — `--out` writes the file directly from the server's storage.
 
 ## Stabilizing flaky judges
@@ -264,9 +264,9 @@ _Generated from `EvalConfigYamlSchema` in `@eigenpal/types/src/eval/evaluator-co
 | Field | Type | Required | Default | Description |
 | --- | --- | --- | --- | --- |
 | `numericTolerance` | number | no | `0.000001` | Maximum absolute difference between numeric values that still counts as equal. Use 1e-6 for floats, 0 for exact integer match. |
-| `allowExtraFields` | boolean | no | `true` | When on, extra fields in the actual output don't fail the diff. Off = actual must match expected exactly. |
+| `allowExtraFields` | boolean | no | `true` | When on, extra fields in the actual output do not fail the diff. Off = actual must match expected exactly. |
 | `passThreshold` | number | no | `1` | Minimum diff score this evaluator must reach for a run to pass. 1.0 = perfect match required. |
-| `paths` | array<string> | no |  | Dot-paths to scope the diff to a subset of the expected tree. Empty = diff entire expected. Syntax: `header.id`, `lineItems[].total`, `lineItems[0].sku`. Use this when expected has noisy sections you don't want to score. |
+| `paths` | array<string> | no |  | Dot-paths to scope the diff to a subset of the expected tree. Empty = diff entire expected. Syntax: `header.id`, `lineItems[].total`, `lineItems[0].sku`. Use this when expected has noisy sections you do not want to score. |
 
 
 ### `llm-judge` — LLM-as-judge scoring
@@ -286,7 +286,7 @@ _Generated from `EvalConfigYamlSchema` in `@eigenpal/types/src/eval/evaluator-co
 | Field | Type | Required | Default | Description |
 | --- | --- | --- | --- | --- |
 | `function` | string | yes |  | Full TypeScript source for optional `type` aliases plus `function scoreScript(expected, actual): number { ... }`. Receives `expected` (the example's expected output) and `actual` (the workflow's actual output), returns a number in [0, 1] (the `: number` annotation is required). The `: number` return-type annotation is required and enforced at parse time. Throws are caught and scored as 0. |
-| `timeoutMs` | integer | no | `5000` | Maximum wall-clock time the script can run before it's killed and the run is marked failed. |
+| `timeoutMs` | integer | no | `5000` | Maximum wall-clock time the script can run before it is killed and the run is marked failed. |
 | `memoryLimitMb` | integer | no | `10` | Maximum memory the sandbox may allocate. Increase if the script processes large arrays or strings. |
 | `passThreshold` | number | no | `1` | Minimum script score this evaluator must reach for a run to pass. |
 <!-- GENERATED:EVALUATOR_CATALOG END -->

package/dist/skill/reference/step-exec.md

@@ -7,7 +7,7 @@
 > retries, no tracing, no credit metering, no tenant-default LLM, no
 > strict-mode response_format) and assumed shell env state
 > (`WORKER_LLM_*`) that real CLI users — who authenticate via
-> `EIGENPAL_API_KEY` — don't have.
+> `EIGENPAL_API_KEY` — do not have.
 >
 > Calling `eigenpal workflow step exec <type>` today exits 2 with a
 > redirect message. The server-side replacement is tracked in EIG-104:
@@ -30,7 +30,7 @@ eigenpal workflow experiment status <workflow-id> <batchId> --watch
 ```
 
 For `--example-id`, the human slug works too (`ex-01-koifer-97zf`),
-not just the `evx_…` id — added as part of the same iteration.
+not the `evx_…` id — added as part of the same iteration.
 
 To inspect what a step actually produced (input / output / resolved
 config), use:

package/dist/skill/reference/step-types.md

@@ -1,7 +1,7 @@
 # Step types
 
 The catalog is generated from `STEP_SCHEMAS` in
-`@eigenpal/types/src/workflow/step-configs.ts`. **Don't memorize fields
+`@eigenpal/types/src/workflow/step-configs.ts`. **Do not memorize fields
 — introspect.** The CLI reads the live schema:
 
 ```bash
@@ -106,7 +106,7 @@ Reference user-supplied schema fields the same way:
 
 `control.parallel`, `control.parallel_map`, `control.foreach`, `control.if`,
 and `control.block` contain nested steps. The auto-generated catalog below
-can't render that shape, so the YAML form lives here. Same for the scoping
+cannot render that shape, so the YAML form lives here. Same for the scoping
 rules — important because the runtime treats nested steps differently from
 top-level ones, and getting the access path wrong silently returns
 `undefined` (no error).
@@ -114,7 +114,7 @@ top-level ones, and getting the access path wrong silently returns
 ### `control.parallel` — independent branches
 
 Runs each branch concurrently. Use when several pieces of work share input
-but don't depend on each other.
+but do not depend on each other.
 
 ```yaml
 - name: enrich
@@ -242,7 +242,7 @@ to preserve intermediate outputs).
 
 > ⚠️ Foreach does NOT isolate scopes — the last iteration's inner step
 > outputs technically persist on the top-level `steps` map and `steps.<inner>.output.x`
-> resolves at runtime. That's an only-the-last-row footgun; the autocomplete
+> resolves at runtime. That is an only-the-last-row hazard; the autocomplete
 > hides these names and you should treat `steps.<foreach>.output.items[]`
 > as the only correct access.
 
@@ -304,7 +304,7 @@ not visible — the block runs in an isolated scope.
 `ai.classify` + `control.fail` together let a workflow reject bad inputs
 fast with a typed HTTP-style status code that callers (and evals) can
 match against. The classifier picks one label from a closed set; the
-fail step terminates the run when the label is one you don't want to
+fail step terminates the run when the label is one you do not want to
 process.
 
 ```yaml
@@ -339,7 +339,7 @@ process.
 The synchronous run endpoint surfaces the `statusCode` as the HTTP
 response status; async runs persist `{ code, message, step }` to
 `executions.error` so the eval scorer can match against
-`expected/error.json` (see `reference/dataset-format.md`). When
+`expected.json` with `$error` (see `reference/dataset-format.md`). When
 `condition` is omitted, `control.fail` always fails when reached, so
 compose with `control.if` for legacy gating.
 
@@ -526,7 +526,7 @@ Merge multiple named inputs into a single output
 
 #### `transform.template` — Fill Template
 
-Fill a DOCX template with data. Use list_templates tool to get template IDs and their placeholder schemas.
+Fill a DOCX template with data from previous steps. Select a template in the workflow builder or provide a template ID from your workspace.
 
 **Config** (in `step.with`):
 

package/dist/skill/reference/workflow-yaml.md

@@ -326,7 +326,7 @@ same per-page representation.
 Description-writing tips (mirrors Reducto's guidance):
 
 - Use the document's own terminology — a Slovak contract calls it `Príloha`,
-  not "annex". List the multilingual variants you've seen.
+  not "annex". List the multilingual variants you have seen.
 - Mention stable visual cues if any — a centered title-page header, a
   signature line, the start of a specific table.
 - Be specific. "The collateral schedule table at the start of Príloha 2"
@@ -442,11 +442,11 @@ eigenpal workflow push --file workflow.yaml --workflow-id wf_… --bump patch
 `--bump` requires `--workflow-id` (it bumps from the current server
 version). `--set-version` works with or without `--workflow-id`. The
 YAML's top-level `version:` field is the fallback when neither flag is
-passed — server rejects pushes whose version doesn't strictly increase.
+passed — server rejects pushes whose version does not strictly increase.
 
 ## Discover step + evaluator types
 
-Don't memorize fields — introspect:
+Do not memorize fields — introspect:
 
 ```bash
 eigenpal workflow step-type      list                 # full step catalog
@@ -456,7 +456,7 @@ eigenpal workflow evaluator-type get <type>           # config schema for one ev
 ```
 
 Both catalogs are generated from the canonical Zod schemas in
-`@eigenpal/types`, so they're always in sync with what the deployment
+`@eigenpal/types`, so they are always in sync with what the deployment
 supports.
 
 <!-- GENERATED:WORKFLOW_REFERENCE START -->

package/dist/templates/blank/README.md

@@ -12,10 +12,11 @@ eigenpal run workflows.__NAME__ --example sample
 ```
 
 Add more examples under `dataset/examples/<name>/`. Each example needs an
-`input/arguments.json`; `expected/output.json` and `meta.json` are optional.
-File arguments live in `input/<arg-name>/<filename>`.
+`input.json`; `expected.json` and `meta.json` are optional. File arguments live
+under `input/` and are referenced from `input.json` with
+`{ "$file": "input/<filename>" }`.
 
-When you're ready to push this workflow to the server:
+When you are ready to push this workflow to the server:
 
 ```bash
 eigenpal workflow push --file workflow.yaml

package/dist/templates/blank/evaluators.yaml

@@ -1,5 +1,5 @@
 # Evaluators run after every workflow execution that's part of an eval batch.
-# Comment them in once you have an `expected/output.json` to compare against.
+# Comment them in once you have an `expected.json` output object to compare against.
 #
 # evaluators:
 #   - name: exact-match

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eigenpal/cli",
-  "version": "0.7.2",
+  "version": "0.9.0",
   "description": "Eigenpal CLI — author and run document workflows from your terminal. Agent-ready.",
   "keywords": [
     "eigenpal",

package/dist/skill/reference/cli/completion.md

@@ -1,9 +0,0 @@
-# eigenpal completion
-
-Print a shell completion script to stdout (supported shells: bash, zsh, fish). Pipe into the appropriate completion file for your shell — see the script header for install instructions.
-
-### Arguments
-
-| Name    | Required | Variadic | Description |
-| ------- | -------- | -------- | ----------- |
-| `shell` | yes      | no       |             |

package/dist/skill/reference/cli/git.md

@@ -1,9 +0,0 @@
-# eigenpal git
-
-Passthrough to git with organization remote auth and committer identity.
-
-### Arguments
-
-| Name      | Required | Variadic | Description            |
-| --------- | -------- | -------- | ---------------------- |
-| `gitArgs` | no       | yes      | Git arguments after -- |