@duvoai/cli 1.52.0 → 1.54.0

package/dist/bin/duvo.js

@@ -3070,6 +3070,23 @@ var CASE_OUTCOME_SEVERITY = {
   MEDIUM: "medium",
   LOW: "low"
 };
+var CASE_MANUAL_STATUS_TARGETS_BY_STATE = {
+  pending: ["completed", "failed", "canceled"],
+  postponed: ["pending", "completed", "failed", "canceled"],
+  in_progress: ["pending", "completed", "failed", "canceled"],
+  needs_input: ["pending", "completed", "failed", "canceled"],
+  evaluating: ["pending", "completed", "failed", "canceled"],
+  success: ["pending", "completed", "failed", "canceled"],
+  issues: ["pending", "completed", "failed", "canceled"],
+  completed: ["pending", "failed", "canceled"],
+  failed: ["pending", "completed", "canceled"],
+  canceled: ["pending", "completed", "failed"]
+};
+function caseManualStatusTargetsFor(status) {
+  return CASE_MANUAL_STATUS_TARGETS_BY_STATE[status];
+}
+__name(caseManualStatusTargetsFor, "caseManualStatusTargetsFor");
+__name2(caseManualStatusTargetsFor, "caseManualStatusTargetsFor");
 var CASE_PRIORITY = {
   NONE: "none",
   MEDIUM: "medium",
@@ -4182,6 +4199,17 @@ var clarityProcessLandscapeFullNodeSchema = z19.object({
   id: z19.guid(),
   parentId: z19.guid().nullable(),
   processId: z19.guid().nullable(),
+  /**
+   * Whether this node is a container or work. Load-bearing for callers that
+   * create nodes: a new node's parent must be an `area`, and `processId` does
+   * NOT discriminate — it is null for areas and for proposed processes alike,
+   * so without this an agent can only guess from the name (DUVO-9512).
+   *
+   * Optional for the same reason as the priority fields below — a client keeps
+   * parsing responses from a server that predates it; the backend always
+   * emits it.
+   */
+  nodeKind: z19.enum(["area", "process"]).optional(),
   name: z19.string(),
   ownerLabel: z19.string().nullable(),
   sortOrder: z19.number(),
@@ -12469,8 +12497,8 @@ var automationDetailResponseApiSchema = z66.object({
 });
 var createAutomationResponseApiSchema = z66.object({
   automation: automationSummaryApiSchema,
-  draft_revision_id: z66.guid().describe(
-    "The draft revision the new automation was created with. A manually created automation has no live revision until it is first activated, so this is where its first agent build belongs."
+  draft_revision_id: z66.guid().nullable().describe(
+    "The draft revision the new automation was created with, or null when the team isn't on revision semantics and the automation is a bare container. A manually created automation has no live revision until it is first activated, so this is where its first agent build belongs."
   ),
   first_agent_id: z66.guid().describe(
     "The automation's first agent, created alongside it with a default build bound into the draft revision, so the caller can open it directly."
@@ -13450,15 +13478,26 @@ var casesStatsSchema = z76.object({
   total: z76.number(),
   /** `pending` — unowned, idle, not postponed; claimable now. */
   pending: z76.number(),
-  /** `in_progress` — owned by a run with no open HITL token. */
+  /**
+   * `in_progress` — work still moving. Owned by a run with no open HITL token,
+   * plus the `evaluating` window: a case that settled OK and is waiting on its
+   * whole-case evaluation has no verdict yet, so it reads as still in progress
+   * rather than as its own bucket.
+   */
   processing: z76.number(),
   /** `needs_input` — owned by a run holding an open HITL token. */
   needs_input: z76.number(),
   /** `postponed` — unowned, scheduled for later. */
   postponed: z76.number(),
   /**
-   * `evaluating` — settled OK with its whole-case evaluation still resolving
-   * (no stored outcome yet). Transient, and bounded by the recovery sweep.
+   * `evaluating` — settled OK with its whole-case evaluation still resolving (no
+   * stored outcome yet). Transient, and bounded by the recovery sweep.
+   *
+   * NOT a bucket, and deliberately excluded from the partition sum above: these
+   * cases are counted inside `processing`, because a case with no verdict yet has
+   * not reached an outcome. Kept as a response field because it shipped as one —
+   * dropping it is a breaking change needing its own deprecation window — and it
+   * is still useful on its own as "how many are waiting on a verdict".
    */
   evaluating: z76.number(),
   /** `success` + `completed` — finished cleanly. */
@@ -13494,13 +13533,13 @@ var casesStatsSchema = z76.object({
     description: "Deprecated alias of needs_input. Read needs_input instead."
   }),
   /**
-   * @deprecated Every settled-OK case (`status = completed`) — i.e.
-   * `resolved + evaluating +` the `issues` share of `needs_review`. Not a
-   * synonym for `resolved`, which excludes the other two.
+   * @deprecated Every settled-OK case (`status = completed`) — i.e. `resolved +`
+   * the evaluating share of `processing` + the `issues` share of `needs_review`.
+   * Not a synonym for `resolved`, which excludes the other two.
    */
   completed: z76.number().meta({
     deprecated: true,
-    description: "Deprecated count of all settled-OK cases. Read resolved (finished cleanly), evaluating, and needs_review instead."
+    description: "Deprecated count of all settled-OK cases. Read resolved (finished cleanly), processing, and needs_review instead."
   }),
   /**
    * @deprecated Every errored-or-stopped case (`status = failed`) — i.e. the
@@ -13897,7 +13936,12 @@ var FEATURE_FLAG_CATALOGUE = {
   AUTOMATIONS: {
     key: "automations",
     defaultValue: false,
-    description: "Exposes the versioned Automations migration entry point. When on, Managers see a 'Migrate to automations' action on the Agents page that sorts the team's standalone agents and queues into Automations (one per connected closure, via the same closure logic as the cross-team move) and stamps team.automations_migrated_at. The stamped timestamp \u2014 not this flag \u2014 drives the Automations sidebar entry. Resolved by team/org (user-level overrides are ignored by the migration gate). Off-by-default for staged, per-team rollout."
+    description: "Exposes the Automations workspace migration entry point. When on, Managers see a 'Migrate to automations' action on the Agents page that sorts the team's standalone agents and queues into Automations (one per connected closure, via the same closure logic as the cross-team move) and stamps team.automations_migrated_at. Which conversion runs is decided by AUTOMATION_VERSIONING, not by this flag: off (the default) writes automation containers and identity FKs only, so builds, triggers and schedules keep their existing lifecycle and a global admin can reverse the move from the team's admin panel; on, the same entry point converts straight to revision semantics and additionally stamps team.automation_revisions_migrated_at, which is not reversible. Revision semantics are also reachable for an already-converted team through the separate phase-2 cutover. The workspace stamp \u2014 not this flag \u2014 drives the Automations sidebar entry. Resolved by team/org (user-level overrides are ignored by the migration gate). Off-by-default for staged, per-team rollout."
+  },
+  AUTOMATION_VERSIONING: {
+    key: "automation_versioning",
+    defaultValue: false,
+    description: "Makes the Automations migration convert straight to revision semantics instead of the lite workspace. When off (the default), POST /automations/migrate writes automation containers only and stamps team.automations_migrated_at; when on, it also snapshots each automation's current live builds, queue routing, trigger configs and recurring schedules as revision 1 and stamps team.automation_revisions_migrated_at. Only applies to a team that is still standalone \u2014 it is not the lite-to-versioned cutover, which resolves its groups from existing automation membership rather than by closure discovery. Resolved by team/org (user-level overrides are ignored by the migration gate), and only consulted for a team that also has AUTOMATIONS on."
   },
   AGENT_SELF_SCHEDULING: {
     key: "agent_self_scheduling",
@@ -22383,10 +22427,14 @@ function parsePriority(raw) {
 __name(parsePriority, "parsePriority");
 
 // src/commands/cases/bulk-update-status.ts
-var CASE_TERMINAL_STATUSES = ["completed", "failed"];
+var CASE_TERMINAL_STATUSES = [
+  "completed",
+  "failed",
+  "canceled"
+];
 function registerCasesBulkUpdateStatus(cases) {
   cases.command("bulk-update-status").description(
-    "Update the status of multiple cases to completed or failed (1-100). Interrupts any active runs."
+    "Update the status of multiple cases to completed, failed, or canceled (1-100). Interrupts any active runs. Use canceled for a deliberate human stop, as distinct from a system failure."
   ).requiredOption("--queue <id>", "ID of the queue the cases belong to").requiredOption("--ids <list>", "comma-separated case IDs (1-100)").requiredOption(
     "--status <status>",
     `terminal status (${CASE_TERMINAL_STATUSES.join(", ")})`
@@ -43102,7 +43150,7 @@ __name(isStandaloneBinary, "isStandaloneBinary");
 import { createRequire } from "node:module";
 function getPackageMeta() {
   if (true) {
-    return { name: "@duvoai/cli", version: "1.52.0" };
+    return { name: "@duvoai/cli", version: "1.54.0" };
   }
   const require2 = createRequire(import.meta.url);
   const raw = require2("../../package.json");