@erdoai/cli 0.112.0 → 0.115.0

package/dist/index.js

@@ -32,7 +32,7 @@ function describeRefreshWrites(strategy, mode, key, liveMode) {
 import { readFileSync as readFileSync4 } from "fs";
 import { basename } from "path";
 import { password, select } from "@inquirer/prompts";
-import { Command as Command2 } from "commander";
+import { Command as Command2, Option as Option2 } from "commander";
 
 // src/config.ts
 import { existsSync, mkdirSync, readFileSync, writeFileSync } from "fs";
@@ -1165,6 +1165,9 @@ var ErdoClient = class {
   // separate program a human chose to run), which leaves the other carriers
   // alone.
   setDatasetPurpose(slug, input) {
+    return this.updateDatasetSchema(slug, input);
+  }
+  updateDatasetSchema(slug, input) {
     return this.request("POST", `/v1/datasets/${encodeURIComponent(slug)}/schema`, input);
   }
   // The endpoint's field is `question` (QueryDataNaturalLanguageInput). Sending  // The endpoint's field is `question` (QueryDataNaturalLanguageInput). Sending
@@ -6579,6 +6582,19 @@ datasetsCmd.command("ensure <purpose>").description(
     fail(e);
   }
 });
+datasetsCmd.command("update-schema <slug>").description("Evolve an existing dataset's column contract. For populated lead-identity datasets, use add_column operations only; existing rows and lead ids are preserved.").requiredOption("--input <file>", "JSON request containing operations and optional class/purpose changes").action(async (slug, opts) => {
+  try {
+    const input = JSON.parse(readFileSync4(opts.input, "utf8"));
+    if (!input || typeof input !== "object" || Array.isArray(input)) {
+      throw new Error("--input must contain a JSON object");
+    }
+    const result = await new ErdoClient().updateDatasetSchema(slug, input);
+    console.log(JSON.stringify(result, null, 2));
+    for (const warning of result.warnings ?? []) console.error(`warning: ${warning}`);
+  } catch (e) {
+    fail(e);
+  }
+});
 datasetsCmd.command("set-purpose <slug> [purpose]").description(
   "Set (or with --clear, remove) the dataset's purpose \u2014 the org-vocabulary role `datasets purposes` reports. Use it to CORRECT a purpose that names the wrong dataset: one purpose maps to one dataset per org, so a purpose left on the wrong one points everything that resolves through the vocabulary at the wrong rows. Setting a purpose another dataset carries is an atomic MOVE: the old carrier is cleared in the same transaction, so one call on the right dataset lands it (the response says which dataset it moved from). Use --sibling only when deliberately running a parallel table for the same purpose."
 ).option("--clear", "remove the dataset's purpose instead of setting one").option(
@@ -7413,7 +7429,7 @@ unavailable: ${source} \u2014 ${reason}`);
     fail(e);
   }
 });
-var leadNextActionsCmd = leadsCmd.command("next-actions").description("Read the suggested next action for each lead, hold or close a lead, and dry-run the playbook on one lead");
+var leadNextActionsCmd = leadsCmd.command("next-actions").description("Read the suggested next action for each lead, hold, close or start a lead, and dry-run the playbook on one lead");
 leadNextActionsCmd.command("list").description(
   "List each lead's current suggestion, highest priority first. --status pending_approval lists the cards waiting for a person."
 ).option("--dataset <slug>", "narrow to one lead dataset").option(
@@ -7526,6 +7542,22 @@ leadNextActionsCmd.command("close <dataset> <lead>").description(
     fail(e);
   }
 });
+leadNextActionsCmd.command("start <dataset> <lead>").description(
+  "Have the follow-up engine work this lead now. By itself the engine only reaches leads captured after it was switched on, and never test traffic; this brings one of those in, and Erdo decides for it straight away. With --reset, start the lead over: anything open is withdrawn and Erdo reads the lead afresh from now, as if it had just been captured. Nothing is deleted, and opt-outs still apply. Refused when the engine is switched off, or (without --reset) when it already has the lead."
+).option("--reset", "start the lead over: Erdo reads nothing from before now").option("--note <text>", "why, in the desk's words").option("--json", "print the raw JSON result instead of a summary").action(async (dataset, lead, opts) => {
+  try {
+    const res = await new ErdoClient().recordLeadNextAction(dataset, lead, { kind: "start", reset: opts.reset, note: opts.note });
+    if (opts.json) {
+      print(res);
+      return;
+    }
+    console.log(
+      opts.reset ? `Started lead ${res.lead_reference} over. Erdo is deciding its first step now.` : `Started follow-up on lead ${res.lead_reference}. Erdo is deciding its next step now.`
+    );
+  } catch (e) {
+    fail(e);
+  }
+});
 leadNextActionsCmd.command("resume <dataset> <lead>").description(
   "End the lead's hold or close now, so Erdo works the lead again. Nothing is sent from here: Erdo decides for the lead on its next pass, within about fifteen minutes. Refused when the lead is not held or closed."
 ).option("--json", "print the raw JSON result instead of a summary").action(async (dataset, lead, opts) => {
@@ -8141,7 +8173,7 @@ autoCmd.command("run <id>").description("Trigger an automation now").action(asyn
     fail(e);
   }
 });
-autoCmd.command("update <id>").description("Edit an automation \u2014 rename, reschedule, or replace its script/instructions").option("--name <name>", "New name").option("--description <text>", "New description").option("--instructions <text>", "Replacement instructions (agent automation)").option("--script-js <js>", "Replacement script body (scripted automation)").option(
+autoCmd.command("update <id>").description("Edit an automation \u2014 rename, reschedule, or replace its script/instructions").option("--name <name>", "New name").option("--description <text>", "New description").option("--instructions <text>", "Replacement instructions (agent automation)").addOption(new Option2("--agent-key <key>", "Executor for an agent automation; omit to keep current").choices(["erdo.heartbeat-executor", "erdo.workflow-executor"])).option("--script-js <js>", "Replacement script body (scripted automation)").option(
   "--script-file <path>",
   "Read the replacement script body from a file (scripted automation)"
 ).option("--interval <minutes>", "New interval in minutes (minimum 5)", (v) => parseInt(v, 10)).option("--timezone <tz>", "New scheduling timezone, e.g. America/New_York").action(
@@ -8156,6 +8188,7 @@ autoCmd.command("update <id>").description("Edit an automation \u2014 rename, re
         name: opts.name,
         description: opts.description,
         instructions: opts.instructions,
+        agent_key: opts.agentKey,
         script_js: scriptJs,
         interval_minutes: opts.interval,
         timezone: opts.timezone

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@erdoai/cli",
-  "version": "0.112.0",
+  "version": "0.115.0",
   "description": "Erdo CLI — drive datasets, pages, and evals from the terminal or CI",
   "type": "module",
   "bin": {