@duvoai/cli 1.77.2 → 1.78.0

package/dist/bin/duvo.js

@@ -34338,9 +34338,6 @@ var adminOrgAddDomainRequestSchema = z71.object({
 var adminOrgAddDomainResponseSchema = z71.object({
   domain: adminOrgDomainSchema
 });
-var adminOrgAssignTeamRequestSchema = z71.object({
-  teamId: z71.guid()
-});
 var adminOrgAddMemberRequestSchema = z71.object({
   userId: z71.guid(),
   role: z71.enum(ORG_ROLES2.ALL)
@@ -38521,6 +38518,7 @@ var FEATURE_FLAG_CATALOGUE = {
   AGENT_BUILDER_ASK_DUVO: {
     key: "agent_builder_ask_duvo",
     defaultValue: false,
+    implies: ["agent_chat"],
     description: "Routes the Agent Builder prompt input through Ask Duvo instead of building the AOP inline: the welcome hero and the config-editor composer hand their prompt to a fresh Ask Duvo chat that continues the conversation, and the builder input hides itself once handed off. When off, both inputs keep generating and editing the AOP in place. Requires AGENT_CHAT \u2014 the handoff needs the chat surface to land in, so with AGENT_CHAT off this flag does nothing. Separate from AGENT_CHAT so the builder handoff can roll out independently of the rest of Ask Duvo. Off by default for staged rollout."
   },
   BROWSING_RECORDING_SCREENSHOTS: {
@@ -38536,11 +38534,13 @@ var FEATURE_FLAG_CATALOGUE = {
   AGENT_CHAT_UI_RESOURCES: {
     key: "agent_chat_ui_resources",
     defaultValue: false,
+    implies: ["agent_chat"],
     description: "Renders interactive UI-resource preview cards (MCP Apps) in the Ask Duvo transcript \u2014 v1: the Pulse dashboard preview on artifact-applied notices, shown in a sandboxed opaque-origin iframe. Frontend render gate only: snapshot capture and persistence (the transport layer) run regardless, so flipping this on needs no backfill. Off-by-default for staged rollout to internal teams first."
   },
   AGENT_CHAT_V2: {
     key: "agent_chat_v2",
     defaultValue: false,
+    implies: ["agent_chat"],
     description: "Ask Duvo v2 runtime: duvo CLI tool surface via a managed cross-team user-scoped API key, replacing the public-API MCP server \u2014 see specs/ask-duvo-cli-tools/PLAN.md"
   },
   CASE_SCHEMA: {
@@ -38571,6 +38571,7 @@ var FEATURE_FLAG_CATALOGUE = {
   AUTOMATION_VERSIONING: {
     key: "automation_versioning",
     defaultValue: false,
+    implies: ["automations"],
     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_QUEUE_DETAIL_REDESIGN: {
@@ -38746,6 +38747,7 @@ var FEATURE_FLAG_CATALOGUE = {
   META_AGENT_ARTIFACTS: {
     key: "meta_agent_artifacts",
     defaultValue: false,
+    implies: ["agent_chat"],
     description: "Enables Ask Duvo Artifacts \u2014 Ask Duvo binds to the artifact on the current page and can create/edit it (Pulse first). When disabled, chat sends carry no structured page context, the duvoChat Pulse tools refuse, and the artifact endpoints return 404. The `meta_agent_artifacts` key is the legacy name kept deliberately: renaming a flag key orphans its per-team overrides."
   },
   MINUTE_SCHEDULING: {
@@ -38796,6 +38798,7 @@ var FEATURE_FLAG_CATALOGUE = {
   PULSE_EDIT_IN_ASK_DUVO: {
     key: "pulse_edit_in_ask_duvo",
     defaultValue: false,
+    implies: ["agent_chat", "meta_agent_artifacts"],
     description: "Routes Pulse through Ask Duvo instead of the native Pulse chat panel. Covers both halves of a dashboard's life. Editing: clicking 'Edit in chat' opens the Ask Duvo rail bound to the dashboard (so the agent can edit it and prior Pulse chat messages surface in-rail); with the flag off the button toggles the native in-page Pulse chat panel as before. Creating: submitting a prompt on the New Pulse page opens an Ask Duvo conversation whose first message is that prompt and whose hidden companion turn makes the agent build the dashboard immediately, so the build narrates in the conversation instead of in silence; with the flag off New Pulse creates the dashboard directly and lands on its canvas. Text-only submissions take the Ask Duvo path \u2014 a submission carrying file attachments always creates directly, since the in-chat create tool cannot carry them. Requires META_AGENT_ARTIFACTS (which registers the in-chat create/edit tools; without it the agent falls back to the public createPulseDashboard tool and produces a dashboard with no binding and no in-chat progress) and AGENT_CHAT (the surface the conversation lands in). Off-by-default for staged rollout."
   },
   PULSE_OPENUI: {
@@ -38811,6 +38814,11 @@ var FEATURE_FLAG_CATALOGUE = {
   FREIGHT_MODULE: {
     key: "freight_module",
     defaultValue: false,
+    // The hard gate on the surface is `team.automations_migrated_at`, and
+    // AUTOMATIONS is the flag that exposes the migration producing that
+    // stamp: a team without it has no workspace for a Module to install
+    // into, so turning this on alone leaves the surface unreachable.
+    implies: ["automations"],
     description: "Per-team opt-in for the Freight Audit Module. Gates the Automation Modules surface: the 'Modules' entry at the top of the Process Automation sidebar section, the /teams/:teamId/modules page (which lists the Freight Audit module), and the module surfaces on the Automation detail page \u2014 an automation whose name matches a catalog module (currently 'Freight Audit') gets a 'Setup' tab with the static module overview, a 'Modules / {name}' breadcrumb, a 'Demo' badge, and a setup CTA in place of the revision switcher. When off, the nav entry is hidden, the page returns 404, and the detail page renders as a plain automation (a ?tab=setup deep link falls back to General). The surface additionally requires the team to be on the Automations workspace (`automations_migrated_at` stamped) \u2014 `lite` or `versioned`, since a Module installs into an automation and the installer writes the owning automation in whichever shape the team's model holds; for a standalone team the nav entry is hidden and the page redirects to Agents even with the flag on. Also gates the Ask Duvo card on Pulse dashboards: the generator may render a `[data-duvo-ask]` card whose submitted question opens Ask Duvo in the side panel on a fresh chat. When OFF, the frame strips any such card out of the dashboard before writing it in and the parent bridge is inert, so a dashboard built with a card renders without one rather than showing a control that does nothing. The card additionally requires AGENT_CHAT, since a question has nowhere to go without Ask Duvo. Also switches the Ask Duvo transcript to its business-clean reading experience: every consecutive tool call in a turn \u2014 including a subagent delegation and the subagent's own calls \u2014 folds into a single collapsed 'Duvo took N steps' row that expands on click into the individual tool cards, in place of the per-tool rows (and the nested delegation card) shown otherwise. Frontend-only and purely presentational: the running tool still surfaces as the activity-line verb, and turning the flag off restores the per-tool transcript with no data change. Off by default for staged rollout."
   },
   AUTOMATIONS_TO_MODULES: {
@@ -38821,6 +38829,7 @@ var FEATURE_FLAG_CATALOGUE = {
   MODULE_SOLUTIONS_GALLERY: {
     key: "module_solutions_gallery",
     defaultValue: false,
+    implies: ["freight_module"],
     description: "Per-team opt-in for the Module Solutions gallery \u2014 the Explore section's 'Module Solutions' entry and the /teams/:teamId/solutions page, which lays the module catalog out as the supply-chain value chain. Exists for demoing our modules vision: the catalog is mostly placeholder modules mapping out the chain rather than wired surfaces, so it is shown to the teams a demo is being given to and nobody else. When off (default), the Explore section is hidden in the sidebar, the entry drops out of the command palette, and the page returns 404; a module's own /teams/:teamId/modules/:slug workspace is unaffected and keeps answering to FREIGHT_MODULE. Requires FREIGHT_MODULE and the team being on the Automations workspace (`automations_migrated_at` stamped) for the same reason the modules surface does \u2014 a Module installs into an automation, so a team with no workspace has nowhere to put one."
   },
   AUTOMATION_RUN_TOASTS: {
@@ -38867,6 +38876,104 @@ var FEATURE_FLAG_DESCRIPTIONS = Object.fromEntries(
     entry.description
   ])
 );
+var FEATURE_FLAG_IMPLICATIONS = (() => {
+  const implications = {};
+  for (const entry of Object.values(FEATURE_FLAG_CATALOGUE)) {
+    implications[entry.key] = "implies" in entry ? [...entry.implies] : [];
+  }
+  return implications;
+})();
+var FEATURE_FLAG_IMPLIED_BY = (() => {
+  const impliedBy = {};
+  for (const flagKey of Object.keys(
+    FEATURE_FLAG_IMPLICATIONS
+  )) {
+    impliedBy[flagKey] = [];
+  }
+  for (const [flagKey, implied] of Object.entries(
+    FEATURE_FLAG_IMPLICATIONS
+  )) {
+    for (const impliedKey of implied) {
+      impliedBy[impliedKey].push(flagKey);
+    }
+  }
+  return impliedBy;
+})();
+function collectFlagClosure(startKey, edges) {
+  const seen = /* @__PURE__ */ new Set([startKey]);
+  const ordered = [];
+  const visit = /* @__PURE__ */ __name3((flagKey) => {
+    for (const next of edges[flagKey] ?? []) {
+      if (seen.has(next)) {
+        continue;
+      }
+      seen.add(next);
+      visit(next);
+      ordered.push(next);
+    }
+  }, "visit");
+  visit(startKey);
+  return ordered;
+}
+__name(collectFlagClosure, "collectFlagClosure");
+__name3(collectFlagClosure, "collectFlagClosure");
+function getImpliedFeatureFlags(flagKey) {
+  return collectFlagClosure(flagKey, FEATURE_FLAG_IMPLICATIONS);
+}
+__name(getImpliedFeatureFlags, "getImpliedFeatureFlags");
+__name3(getImpliedFeatureFlags, "getImpliedFeatureFlags");
+function getImplyingFeatureFlags(flagKey) {
+  return collectFlagClosure(flagKey, FEATURE_FLAG_IMPLIED_BY);
+}
+__name(getImplyingFeatureFlags, "getImplyingFeatureFlags");
+__name3(getImplyingFeatureFlags, "getImplyingFeatureFlags");
+function findFeatureFlagImplicationCycle() {
+  const visiting = /* @__PURE__ */ new Set();
+  const settled = /* @__PURE__ */ new Set();
+  const path = [];
+  const walk = /* @__PURE__ */ __name3((flagKey) => {
+    if (visiting.has(flagKey)) {
+      return [...path.slice(path.indexOf(flagKey)), flagKey];
+    }
+    if (settled.has(flagKey)) {
+      return null;
+    }
+    visiting.add(flagKey);
+    path.push(flagKey);
+    for (const implied of FEATURE_FLAG_IMPLICATIONS[flagKey] ?? []) {
+      const cycle = walk(implied);
+      if (cycle) {
+        return cycle;
+      }
+    }
+    path.pop();
+    visiting.delete(flagKey);
+    settled.add(flagKey);
+    return null;
+  }, "walk");
+  for (const flagKey of Object.keys(
+    FEATURE_FLAG_IMPLICATIONS
+  )) {
+    const cycle = walk(flagKey);
+    if (cycle) {
+      return cycle;
+    }
+  }
+  return null;
+}
+__name(findFeatureFlagImplicationCycle, "findFeatureFlagImplicationCycle");
+__name3(findFeatureFlagImplicationCycle, "findFeatureFlagImplicationCycle");
+function resolveFeatureFlagWithImplications(flagKey, resolveOwnValue) {
+  const impliedBy = getImplyingFeatureFlags(flagKey).filter(
+    (implyingKey) => resolveOwnValue(implyingKey) === true
+  );
+  if (impliedBy.length > 0) {
+    return { value: true, impliedBy };
+  }
+  return { value: resolveOwnValue(flagKey), impliedBy };
+}
+__name(resolveFeatureFlagWithImplications, "resolveFeatureFlagWithImplications");
+__name3(resolveFeatureFlagWithImplications, "resolveFeatureFlagWithImplications");
 function coerceFlagValue(value) {
   if (value === void 0) {
     return void 0;
@@ -63514,10 +63621,10 @@ var TABLE_COLUMNS40 = [
   { header: "STATUS", cell: /* @__PURE__ */ __name((row) => row.status, "cell") },
   { header: "UPDATED", cell: /* @__PURE__ */ __name((row) => row.updated_at, "cell") }
 ];
-var SCOPE_FLAGS = ["--team", "--shared", "--automation"];
+var SCOPE_FLAGS = ["--published", "--shared", "--automation"];
 function resolveScope(options) {
   const selected = [
-    options.team && "--team",
+    options.published && "--published",
     options.shared && "--shared",
     options.automation && "--automation"
   ].filter((flag) => typeof flag === "string");
@@ -63526,7 +63633,7 @@ function resolveScope(options) {
       `${SCOPE_FLAGS.join(", ")} are different scopes \u2014 pass at most one. You passed ${selected.join(" and ")}.`
     );
   }
-  if (options.team) {
+  if (options.published) {
     return "team";
   }
   if (options.shared) {
@@ -63539,9 +63646,11 @@ function resolveScope(options) {
 }
 __name(resolveScope, "resolveScope");
 function registerPulseList(pulse) {
-  pulse.command("list", { isDefault: true }).description("List your Pulse dashboards").option(
-    "--team",
-    "list dashboards a teammate published to your whole team instead of your own"
+  pulse.command("list", { isDefault: true }).description(
+    "List your Pulse dashboards in the selected team (--team <id>, DUVO_TEAM_ID, or the profile default)"
+  ).option(
+    "--published",
+    "list dashboards a teammate published to the whole team instead of your own"
   ).option("--shared", "deprecated: always returns no dashboards").option(
     "--automation",
     "list the dashboards owned by your team's automations, each prefixed with its automation's name"
@@ -63552,7 +63661,11 @@ function registerPulseList(pulse) {
       max: MAX_LIMIT15
     });
     const offset = parseOffset(options.offset);
-    const { apiKey, apiBaseUrl } = await requireAuthenticatedConfig(this);
+    const config = await requireAuthenticatedConfig(this);
+    const { apiKey, apiBaseUrl } = config;
+    const teamId = await resolveRequiredTeamId(config, {
+      override: getTeamFlag(this)
+    });
     const searchParams = new URLSearchParams();
     const scope = resolveScope(options);
     searchParams.append("scope", scope);
@@ -63560,7 +63673,7 @@ function registerPulseList(pulse) {
     searchParams.append("offset", String(offset));
     const raw = await httpRequest({
       method: "GET",
-      path: "/v2/artifacts",
+      path: buildTeamPath(teamId, "/artifacts"),
       apiKey,
       apiBaseUrl,
       searchParams
@@ -70628,7 +70741,7 @@ __name(isStandaloneBinary, "isStandaloneBinary");
 import { createRequire } from "node:module";
 function getPackageMeta() {
   if (true) {
-    return { name: "@duvoai/cli", version: "1.77.2" };
+    return { name: "@duvoai/cli", version: "1.78.0" };
   }
   const require2 = createRequire(import.meta.url);
   const raw = require2("../../package.json");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@duvoai/cli",
-  "version": "1.77.2",
+  "version": "1.78.0",
   "description": "Command-line interface for the Duvo public API",
   "bin": {
     "duvo": "./dist/bin/duvo.js"