@erdoai/cli 0.101.0 → 0.101.1

package/dist/index.js

@@ -1087,10 +1087,12 @@ var ErdoClient = class {
     return this.request("POST", "/v1/datasets-ensure", input);
   }
   // Correct which dataset carries a purpose. Pass `purpose` to set one,
-  // `clear_purpose` to remove it; moving a purpose is clearing it from the old
-  // dataset and setting it on the right one. Setting a purpose the org already
-  // uses elsewhere succeeds and answers with a warning naming what it shadows,
-  // since one purpose is meant to map to one dataset.
+  // `clear_purpose` to remove it. Setting a purpose another dataset carries is
+  // an atomic MOVE — the old carrier is cleared in the same transaction — and
+  // the response warns naming the dataset it moved from. Pass
+  // `purpose_sibling: true` only to declare a deliberate parallel carrier (a
+  // separate program a human chose to run), which leaves the other carriers
+  // alone.
   setDatasetPurpose(slug, input) {
     return this.request("POST", `/v1/datasets/${encodeURIComponent(slug)}/schema`, input);
   }
@@ -6152,8 +6154,11 @@ datasetsCmd.command("ensure <purpose>").description(
   }
 });
 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. Moving a purpose is two calls \u2014 clear it from the old dataset, set it on the right one. Setting a purpose the org already uses elsewhere succeeds and prints a warning naming what it now shadows."
+  "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(
+  "--sibling",
+  "declare this dataset a deliberate parallel carrier of the purpose (a separate program a human chose to run) instead of moving the purpose off other datasets"
+).option(
   "--description <text>",
   "description for a purpose new to this org; ignored when the org already has an entry for it"
 ).action(async (slug, purpose, opts) => {
@@ -6169,6 +6174,7 @@ datasetsCmd.command("set-purpose <slug> [purpose]").description(
     const res = await new ErdoClient().setDatasetPurpose(slug, {
       ...purpose ? { purpose } : {},
       ...opts.clear ? { clear_purpose: true } : {},
+      ...opts.sibling ? { purpose_sibling: true } : {},
       ...opts.description ? { purpose_description: opts.description } : {}
     });
     for (const w of res.warnings ?? []) console.error(`warning: ${w}`);

package/package.json

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