@eigenpal/cli 0.4.15 → 0.4.17

package/dist/cli.js

@@ -67845,7 +67845,7 @@ var init_evaluator_config = __esm(() => {
     returns: "a number in [0, 1] (the `: number` annotation is required)",
     throws: "caught and scored as 0"
   };
-  CUSTOM_SCRIPT_FUNCTION_DESCRIPTION = `Full TypeScript declaration of \`function scoreScript(expected, actual): number { ... }\`. ` + `Receives \`expected\` (${CUSTOM_SCRIPT_CONTRACT.expected}) ` + `and \`actual\` (${CUSTOM_SCRIPT_CONTRACT.actual}), returns ${CUSTOM_SCRIPT_CONTRACT.returns}. ` + `The \`: number\` return-type annotation is required and enforced at parse time. ` + `Throws are ${CUSTOM_SCRIPT_CONTRACT.throws}.`;
+  CUSTOM_SCRIPT_FUNCTION_DESCRIPTION = `Full TypeScript source for optional \`type\` aliases plus \`function scoreScript(expected, actual): number { ... }\`. ` + `Receives \`expected\` (${CUSTOM_SCRIPT_CONTRACT.expected}) ` + `and \`actual\` (${CUSTOM_SCRIPT_CONTRACT.actual}), returns ${CUSTOM_SCRIPT_CONTRACT.returns}. ` + `The \`: number\` return-type annotation is required and enforced at parse time. ` + `Throws are ${CUSTOM_SCRIPT_CONTRACT.throws}.`;
   CustomScriptConfigSchema = exports_external.object({
     function: exports_external.string().min(1, { message: "required" }).max(CUSTOM_SCRIPT_MAX_BYTES, {
       message: `must be ≤ ${CUSTOM_SCRIPT_MAX_BYTES} bytes`
@@ -67999,14 +67999,18 @@ var init_judge = __esm(() => {
 
 // ../types/src/eval/score-function.ts
 function defaultScoreFunction() {
-  return `/**
+  return `type WorkflowOutput = Record<string, unknown>;
+type Expected = WorkflowOutput;
+type Actual = WorkflowOutput;
+
+/**
  * Score the workflow output against the example's expected output.
  * Return a number in [0, 1]; throws are caught and scored as 0.
  *
  * The \`: number\` return-type annotation is required and enforced at
  * push time. The body is compiled to JS via sucrase before sandbox.
  */
-function scoreScript(expected: Expected, actual: Actual): number {
+function scoreScript(expected: WorkflowOutput, actual: WorkflowOutput): number {
   return JSON.stringify(actual) === JSON.stringify(expected) ? 1 : 0;
 }
 `;
@@ -181225,7 +181229,7 @@ import { fileURLToPath as fileURLToPath6 } from "url";
 // package.json
 var package_default = {
   name: "@eigenpal/cli",
-  version: "0.4.15",
+  version: "0.4.17",
   description: "Eigenpal CLI — author and run document workflows from your terminal. Agent-ready.",
   keywords: [
     "eigenpal",
@@ -186396,7 +186400,8 @@ function registerWorkflowCoreCommands(parent) {
   withBaseUrl(pullCmd).action(action(async (workflow2, opts) => {
     const { client, workflowId } = await buildClientForWorkflow(workflow2, opts);
     const result = await client.get(`/api/v1/workflows/${workflowId}`);
-    await writeOrPrint(opts.out, result?.currentVersion?.yamlContent ?? "");
+    const yaml = result?.currentVersion?.yamlContent ?? "";
+    await writeOrPrint(opts.out, yaml);
   }));
   const pushCmd = parent.command("push").description(descriptionFor("workflow_set_definition")).option("--file <yaml>", "Path to YAML file").option("--workflow-id <id>", "Update existing workflow (default: create new)").option("--bump <level>", "Auto-bump from the server's current version: patch | minor | major. Mutually exclusive with `--version` and with a top-level `version:` in the YAML.").option("--set-version <semver>", "Push at this exact semver (e.g. 1.4.0). Mutually exclusive with `--bump` and with a top-level `version:` in the YAML. (Named `--set-version` to avoid the global `-v, --version` flag.)").addHelpText("after", `
 Examples:
@@ -186494,7 +186499,11 @@ flag would otherwise shadow it. Validation failures come back as
         throw new Error("--bump requires --workflow-id (need a current version to bump from). For a new workflow, use --set-version <X.Y.Z> or omit both.");
       }
       const yamlToSend = opts.setVersion && !extractWorkflowVersion(yamlOnDisk) ? spliceWorkflowVersion2(yamlOnDisk, opts.setVersion) : yamlOnDisk;
-      const result = await client.post("/api/v1/workflows", { yaml: yamlToSend });
+      const createVersion = opts.setVersion ?? extractWorkflowVersion(yamlToSend) ?? undefined;
+      const result = await client.post("/api/v1/workflows", {
+        yaml: yamlToSend,
+        ...createVersion ? { version: createVersion } : {}
+      });
       if (opts.json) {
         printJson2(result);
         return;
@@ -186504,6 +186513,19 @@ flag would otherwise shadow it. Validation failures come back as
       success2(`Created ${ui.bold(id2)} (v${ver})`);
     }
   }));
+  const moveCmd = parent.command("move <workflow-id>").description("Move a workflow to a folder path, creating folders as needed").requiredOption("--folder <path>", "Target folder path (`/` for root)");
+  addJsonFlag(withBaseUrl(moveCmd)).action(action(async (workflow2, opts) => {
+    const { client, workflowId } = await buildClientForWorkflow(workflow2, opts);
+    const result = await client.patch(`/api/v1/workflows/${workflowId}`, {
+      folderPath: opts.folder
+    });
+    if (opts.json) {
+      printJson2(result);
+      return;
+    }
+    const target = opts.folder.trim() === "/" ? "root" : opts.folder;
+    success2(`Moved ${ui.bold(workflowId)} to ${ui.bold(target)}`);
+  }));
 }
 var SEMVER_RE = /^(\d+)\.(\d+)\.(\d+)$/;
 function isBumpLevel(value) {

package/dist/skill/SKILL.md

@@ -110,6 +110,22 @@ The validator emits structured field-path errors with a hint pointing at
 Version bumping rules (`--bump` vs `--set-version` vs YAML `version:`)
 live in [`reference/workflow-yaml.md`](reference/workflow-yaml.md#validate-before-pushing).
 
+### Organize workflows into folders
+
+Folders live on the server, not in `workflow.yaml`. `workflow push` and
+`workflow pull` do not read or write folder placement. Use `workflow move`
+to move workflows between dashboard folders:
+
+```bash
+eigenpal workflow move <workflow-id> --folder billing/invoices
+eigenpal workflow move <workflow-id> --folder /
+```
+
+`--folder /` means root.
+Missing folders in the path are created automatically.
+Default to creating workflows at the top level. Do not move a workflow into
+a folder unless the user specifically asks for that placement.
+
 ### Iterate fast on one step (no server, no DAG)
 
 Tightest possible loop — local sandbox, milliseconds per run. Today
@@ -478,6 +494,7 @@ eigenpal workflow list
 eigenpal workflow push --file workflow.yaml [--workflow-id <workflow-id>]
 eigenpal workflow pull <workflow-id>
 eigenpal workflow validate [path]
+eigenpal workflow move <wf-id> --folder billing/invoices  # use --folder / for root
 
 # Evaluators
 eigenpal workflow evaluators push <workflow-id> --file evaluators.yaml

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

@@ -19,6 +19,7 @@ Manage workflows: push, pull, run, evaluate.
   - [`eigenpal workflow list [options]`](#eigenpal-workflow-list-options)
   - [`eigenpal workflow pull [options] <workflow-id>`](#eigenpal-workflow-pull-options-workflow-id)
   - [`eigenpal workflow push [options]`](#eigenpal-workflow-push-options)
+  - [`eigenpal workflow move [options] <workflow-id>`](#eigenpal-workflow-move-options-workflow-id)
   - [`eigenpal workflow validate [options]`](#eigenpal-workflow-validate-options)
   - [`eigenpal workflow clear-local [options] [examples...]`](#eigenpal-workflow-clear-local-options-examples)
   - [`eigenpal workflow evaluators pull [options] <workflow-id>`](#eigenpal-workflow-evaluators-pull-options-workflow-id)
@@ -60,6 +61,7 @@ workflow
 ├── list
 ├── pull <workflow-id>
 ├── push
+├── move <workflow-id>
 ├── evaluators
 │   ├── pull <workflow-id>
 │   ├── push <workflow-id>
@@ -113,6 +115,7 @@ workflow
 | `eigenpal workflow list [options]`                      | List workflows the caller can read.                                                                                                                                                    |
 | `eigenpal workflow pull [options] <workflow-id>`        | Download the YAML definition of the workflow at its current version.                                                                                                                   |
 | `eigenpal workflow push [options]`                      | Create or update a workflow from a YAML file.                                                                                                                                          |
+| `eigenpal workflow move [options] <workflow-id>`        | Move a workflow to a folder path, creating folders as needed                                                                                                                           |
 | `eigenpal workflow validate [options]`                  | Local-only validation against the templated project layout: ./workflow.yaml + ./evaluators.yaml + ./dataset/. For targeted validation use `evaluators validate` or `dataset validate`. |
 | `eigenpal workflow clear-local [options] [examples...]` | Delete local execution artifacts under ./dataset/examples/. Keeps the latest run per example by default.                                                                               |
 
@@ -235,6 +238,24 @@ Create or update a workflow from a YAML file.
 | `--base-url <url>`       | no       |         | Server base URL                                                                                                                                                                         |
 | `--json`                 | no       |         | Output the raw server response as JSON                                                                                                                                                  |
 
+### `eigenpal workflow move [options] <workflow-id>`
+
+Move a workflow to a folder path, creating folders as needed
+
+### Arguments
+
+| Name          | Required | Variadic | Description |
+| ------------- | -------- | -------- | ----------- |
+| `workflow-id` | yes      | no       |             |
+
+### Options
+
+| Flag               | Required | Default | Description                            |
+| ------------------ | -------- | ------- | -------------------------------------- |
+| `--folder <path>`  | yes      |         | Target folder path (`/` for root)      |
+| `--base-url <url>` | no       |         | Server base URL                        |
+| `--json`           | no       |         | Output the raw server response as JSON |
+
 ### `eigenpal workflow validate [options]`
 
 Local-only validation against the templated project layout: ./workflow.yaml + ./evaluators.yaml + ./dataset/. For targeted validation use `evaluators validate` or `dataset validate`.

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

@@ -11,6 +11,10 @@ on the server, the canonical per-row surface is
 `dataset list` for a table view) — the local folder is a pre-push
 staging area, not a synced mirror.
 
+Dataset folders are unrelated to workflow organization folders. To place
+the workflow itself under dashboard folders, use `workflow move --folder`;
+dataset push/pull never changes folder placement.
+
 ## Required layout
 
 ```

package/dist/skill/reference/debugging.md

@@ -134,6 +134,20 @@ The error envelope tells you exactly where:
 Follow the hint — every field path is dotted into the YAML so you can
 jump straight to the broken line.
 
+### Workflow appears in the wrong folder
+
+Folder placement is controlled by server folder state, not by
+`workflow.yaml`. Move by explicit folder path:
+
+```bash
+eigenpal workflow move <workflow-id> --folder billing/invoices
+eigenpal workflow move <workflow-id> --folder /
+```
+
+`--folder /` moves the workflow back to root. `workflow push` and
+`workflow pull` do not change folder placement. Missing folders in the
+path are created automatically.
+
 ## 4. Compare two executions
 
 ```bash

package/dist/skill/reference/evaluators.md

@@ -6,6 +6,10 @@ attach to a workflow via `workflow evaluators push` and run in batch via
 `EvalConfigYamlSchema` in `@eigenpal/types/src/eval/evaluator-config.ts`;
 this is the agent-facing summary.
 
+Evaluator config does not control dashboard folder placement. Workflow
+organization is managed with `workflow move --folder`;
+`workflow evaluators push` leaves the workflow's folder unchanged.
+
 ## Top-level shape
 
 ```yaml
@@ -109,7 +113,13 @@ one of the keys in `labels`; the harness then looks up the score.
   config:
     passThreshold: 1.0
     function: |
-      function scoreScript(expected: Expected, actual: Actual): number {
+      type WorkflowOutput = {
+        totalAmount: number;
+      };
+      type Expected = WorkflowOutput;
+      type Actual = WorkflowOutput;
+
+      function scoreScript(expected: WorkflowOutput, actual: WorkflowOutput): number {
         const a = actual.totalAmount ?? 0;
         const e = expected.totalAmount ?? 0;
         return Math.abs(a - e) <= 0.01 ? 1 : 0;
@@ -117,12 +127,13 @@ one of the keys in `labels`; the harness then looks up the score.
 ```
 
 Same WASM sandbox as `transform.script` (5s wall clock, 10 MB heap, no
-network). The YAML stores the **whole** `function scoreScript(expected,
-actual): number { ... }` declaration verbatim, same text the dashboard
-editor shows. The `: number` return-type annotation is required and
-enforced at parse time. `Expected` / `Actual` are in-scope type aliases
-in the dashboard editor (both are the workflow's output shape); plain
-`unknown` works too if you don't want them.
+network). The YAML stores the **whole** typed score source (optional
+`type` aliases plus `function scoreScript(expected, actual): number { ... }`)
+verbatim, same text the dashboard editor shows. The `: number` return-type annotation is required and
+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.
 
 The signature shape is **locked**:
 
@@ -267,7 +278,7 @@ _Generated from `EvalConfigYamlSchema` in `@eigenpal/types/src/eval/evaluator-co
 
 | Field | Type | Required | Default | Description |
 | --- | --- | --- | --- | --- |
-| `function` | string | yes |  | Full TypeScript declaration of `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. |
+| `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. |
 | `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. |

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

@@ -26,6 +26,14 @@ output: {...} # object — the workflow's return shape
 version with the same `name` and a different `version` appends to history;
 re-using the same `version` is rejected.
 
+Folder placement is not part of `workflow.yaml`; it lives in the server
+database. Use `workflow move <workflow-id> --folder <path>` to move a
+workflow between dashboard folders. Missing folders in the path are
+created automatically. Use `--folder /` for root. New workflows should stay
+at the top level unless the user specifically asks to place them in a
+folder.
+
+
 ### `triggerMethods`
 
 Required. Each entry adds an invocation surface:

package/package.json

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