@eigenpal/cli 0.4.9 → 0.4.11

package/CHANGELOG.md

@@ -34,6 +34,7 @@
 
 ### Minor Changes
 
+- c15ce88: Add the `eigenpal agent` command tree for managing agents, triggers, datasets, executions, experiments, and sessions from the terminal.
 - c82a215: `eigenpal auth login` now shows an interactive server picker when no `--base-url` flag or `EIGENPAL_BASE_URL` env is set:
   - **Cloud** (`https://studio.eigenpal.com`) is the default highlighted option.
   - Any on-prem URLs already in your credentials file are surfaced as separate options labelled with the profile names that use them — re-login against an existing on-prem deployment without retyping the URL.
@@ -211,6 +212,25 @@
 
   `@` path syntax (`--code @file.js`, `--inputs items=@arr.json`) matches `curl -d @file` / `gh --body-file -`. Bare paths and `-` (stdin) work too.
 
+- 4137eb8: custom-script evaluator: the YAML now carries the entire
+  `function scoreScript(expected, actual) { ... }` declaration in a single
+  `function` field. Previous formats (`code`, then `body`) wrapped the
+  text implicitly; the new shape stores the function declaration verbatim
+  so the YAML matches the dashboard editor 1-for-1.
+
+  `workflow validate` and `workflow evaluators validate` flag YAML where
+  the function fails to parse, the signature does not match
+  `function scoreScript(expected, actual)` exactly, or the body contains
+  neither `return` nor `throw` — same checks the dashboard runs at form
+  save. The function must return a number in [0, 1]; throws are caught
+  and scored as 0.
+
+  Existing evaluator YAML must be ported by hand: rename `body` (or
+  `code`) to `function`, and add the `function scoreScript(expected,
+actual) { ... }` declaration around your statements. Parameter order is
+  load-bearing — swapping `expected` and `actual` would silently invert
+  every score.
+
 - 3da0612: All list commands now support `--limit` / `--offset` pagination consistently.
   - CLI: `workflow execution list`, `workflow version list`, and `workflow step-type list` previously had no `--offset` (or no pagination at all). All six list commands now accept `--limit`/`--offset` with defaults of 50/0.
   - Server: `GET /api/workflows/:id/versions` now reads `?limit=` and `?offset=` query params (defaults 50/0; max limit 100). The `listVersions` repo method gained an optional `{ limit, offset }` argument.
@@ -233,6 +253,36 @@
   Document the CLI exit-code contract (0 = success, 1 = runtime error,
   2 = misuse / recoverable failure) in `packages/cli/CLAUDE.md`.
 
+- 4b1f81c: `transform.script` now accepts a full function declaration via
+  `with.function:`, mirroring the custom-script evaluator. Parameter
+  names and order must equal `Object.keys(inputs)`:
+
+  ```yaml
+  - type: transform.script
+    with:
+      inputs:
+        items: '{{ steps.x.output }}'
+        taxRate: '{{ input.rate }}'
+      function: |
+        function script(items, taxRate) {
+          return items.length * taxRate;
+        }
+  ```
+
+  Authoring is now Monaco-backed in the dashboard, with input keys
+  surfaced as typed declarations so `items.` autocompletes against the
+  upstream step's output schema.
+
+  The legacy `with.code:` shape (a bare statement body, with input keys
+  leaking in as globals) still loads — the worker auto-wraps it via
+  `wrapBodyAsScriptFunction` at handler entry, and the dashboard
+  migrates `code:` to `function:` on the next save. New workflows
+  should use `function:`. The schema rejects:
+  - function names other than `script`
+  - parameter lists that don't match `Object.keys(inputs)` in order
+  - `async` / `import()` / `require()` (sandbox-incompatible)
+  - bodies with no `return` or `throw`
+
 - 3da0612: CLI: cleaner workflow command tree + matching `--json` shape.
 
   **Tree restructure** — the `workflow definition` namespace is gone. Its three verbs are core operations on the workflow itself, so they move up one level:
@@ -256,6 +306,7 @@
 
 ### Patch Changes
 
+- c15ce88: Rename agent API calls to `/v1/agents` and scope execution helpers under their owning workflow or agent.
 - 71361fd: `auth login`: simplified flow. Removed the dead localhost-callback server (the
   dashboard never POSTed to it — every login fell through to copy-paste anyway).
   The browser now opens to `/developers/api-keys?from=cli` with a clearer prompt
@@ -283,6 +334,11 @@
 
   Interactive profiles are unchanged: when you log in via `eigenpal auth login`, the profile stores both apiKey and baseUrl, and every subsequent command derives baseUrl from that profile. Set `EIGENPAL_PROFILE=<name>` to switch profiles per-shell without modifying state.
 
+- 542fe0e: CLI: surface evaluator entry-level fields (`name`, `description`, `weight`) so agents and humans can discover the optional `description` field on every evaluator.
+  - `workflow evaluator-type get <type>` now emits `entrySchema` alongside `configSchema`. Inspect with `eigenpal workflow evaluator-type get llm-judge | jq '.entrySchema'`.
+  - The skill reference now renders a "Common entry fields" table per type and a "Writing descriptions for stakeholders" section explaining the convention: each evaluator's `description` should be a one-sentence, plain-language summary aimed at non-technical reviewers in the dashboard.
+  - `init` templates `pdf-extraction` and `text-classification` now ship a `description:` line on their evaluator entries.
+
 - d41ee8b: CLI: fix `eigenpal status` error UX + harden `formatCliError` for real-world connection failures.
   - `eigenpal status` against an unreachable base URL no longer mis-diagnoses the failure as an auth problem. Previously, `EIGENPAL_BASE_URL=http://localhost:9999 eigenpal status` printed "Authentication check failed; try `eigenpal auth login`" — the wrong rabbit hole. The status command now rethrows non-auth errors (connection refused, DNS NXDOMAIN, timeout, HTML responses, 5xx) so `formatCliError` upstream can surface the right hint: `Could not connect to the server at <url> ... Set EIGENPAL_BASE_URL or pass --base-url <url>.` Only real 401/403 responses are treated as auth failures.
   - `formatCliError` now detects connection failures wrapped in any Error shape — bare `Error('ENOTFOUND ...')`, `Error` with `code: 'ECONNREFUSED'`, and `TypeError('fetch failed')` whose `.cause` carries the underlying error. Previously only `TypeError` whose message contained `fetch`/`URL` was recognized, so `getaddrinfo`-style errors fell through to the generic raw-message branch and lost the URL context.