@erdoai/cli 0.88.0 → 0.89.0

package/dist/index.js

@@ -1153,6 +1153,23 @@ var ErdoClient = class {
       `/v1/datasets/${encodeURIComponent(slug)}/refresh/run`
     );
   }
+  // --- lead identity ---
+  // Preview or perform a dataset's permanent-lead-identity migration: give every
+  // pipeline writer the producer contract, backfill the IDs, and publish the
+  // identity config in one transaction.
+  //
+  // apply:false mutates nothing and is the way to read readiness — `ready`, the
+  // `blockers` holding it up, and how many rows would be assigned an identity.
+  // apply:true needs an operation_key: replaying the same key settles an apply
+  // whose response was lost, while a different key against a migrated dataset is
+  // refused rather than migrating twice.
+  maintainLeadIdentity(slug, body) {
+    return this.request(
+      "POST",
+      `/v1/datasets/${encodeURIComponent(slug)}/lead-identity/maintain`,
+      body
+    );
+  }
   // --- bounded outreach ---
   putOutreachBatch(batch, body) {
     return this.request(
@@ -5653,6 +5670,49 @@ datasetsCmd.command("set-purpose <slug> [purpose]").description(
     fail(e);
   }
 });
+var leadIdentityCmd = datasetsCmd.command("lead-identity").description(
+  "Permanent lead identity \u2014 one lead is one row, however many ways they got in touch. Migrating a dataset gives every row a canonical_lead_id, points every pipeline writer at it, and makes the resolver the only thing that decides whether a submission is a new lead or an existing one."
+);
+leadIdentityCmd.command("maintain <slug>").description(
+  "Preview or perform the migration for one dataset. Without --apply it mutates nothing and reports readiness: whether the dataset is ready, what blocks it, and how many rows would be assigned an identity. Run the preview first and read the blockers \u2014 apply refuses outright while any consumer is incompatible, unverifiable, queued or running, because the backfill rewrites the file every one of them reads."
+).option(
+  "--apply",
+  "perform the migration rather than preview it; requires --operation-key"
+).option(
+  "--operation-key <key>",
+  "the migration receipt. Replaying the same key settles an apply whose response was lost; a different key against an already-migrated dataset is refused rather than migrating it twice."
+).option("--email-column <column>", "the dataset's email column (detected when omitted)").option("--phone-column <column>", "the dataset's phone column (detected when omitted)").option(
+  "--conversion-id-column <column>",
+  "optional conversion id column; must differ from both contact columns"
+).option(
+  "--default-calling-code <code>",
+  "calling code a phone written in national form belongs to, so one number written two ways is one lead (default 1)"
+).action(
+  async (slug, opts) => {
+    try {
+      if (opts.apply && !opts.operationKey) {
+        fail(
+          new Error(
+            "--apply requires --operation-key so an uncertain retry can settle rather than migrating twice"
+          )
+        );
+        return;
+      }
+      print(
+        await new ErdoClient().maintainLeadIdentity(slug, {
+          apply: Boolean(opts.apply),
+          operation_key: opts.operationKey,
+          email_column: opts.emailColumn,
+          phone_column: opts.phoneColumn,
+          conversion_id_column: opts.conversionIdColumn,
+          default_calling_code: opts.defaultCallingCode
+        })
+      );
+    } catch (e) {
+      fail(e);
+    }
+  }
+);
 datasetsCmd.command("query <slug> <question>").description(
   "Ask a natural-language question of a dataset \u2014 Erdo writes and runs the SQL, and answers with that SQL alongside the values. It runs an agent, so it is slower and two identical questions can produce two different queries: for a deterministic or scripted read, write the SQL yourself with `datasets fetch --sql`."
 ).action(async (slug, question) => {

package/package.json

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