@rosthq/cli 0.5.21 → 0.5.23

package/dist/index.js

@@ -42145,7 +42145,7 @@ Decisions should be recorded as human decisions. Handoffs should attach to seats
     order: 45,
     title: "How agents work",
     summary: "How {{brand}} agents operate inside seats, use Charters, report work, and escalate beyond authority.",
-    version: "2026-06-21.3",
+    version: "2026-06-21.4",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing", "operating_rhythm"],
@@ -42239,7 +42239,7 @@ Before an agent goes live, the sandbox dry run rehearses this against fake data
 
 The Agents page shows fleet health first: live state, recent runs, failed runs, open held actions, last activity, cost, and the next operator action. It also shows configuration completeness for each staffed agent seat: Steward chain, lane or runtime substrate, vaulted credentials, granted tools, model config, sandbox dry run, and go-live state, each with a remediation link when incomplete. A seat's Trust Card drills into the same facts: run history, one-run detail, tool-call outcomes, product-visible errors, transcript references, loaded Skill versions, and held confirmations or escalations. Open confirmations stay visible until they are decided or expire, even when they are older than the default activity window. Approving or rejecting a held confirmation from the seat page is scoped to that seat; rejection can include a short reason.
 
-Review the first dry runs, fleet overview, tool-call audit rows, escalations, deliverables, and Signal impact. A seat's completed-work area combines explicit deliverables, work-log evidence, and successful run summaries into one operator-facing trail with safe links labelled as internal, Linear, GitHub, or external. The fleet view at \`/agents\` shows every staffed agent seat at a glance; the agent-native equivalents are \`{{cli}} command agent.list_fleet --json '{}'\` / \`rost_list_agent_fleet\` for the compact overview, and \`{{cli}} agent fleet-digest --json\` / \`agent.fleet_digest\` / \`rost_get_dogfood_fleet_health_digest\` for the daily dogfood evidence bundle. The digest returns live/idle state, 24h/7d turns, 7d/30d spend, recent failed runs, unresolved product errors, failed notifications, and a next action per seat. Fleet real-turn counts use the same seat-run association as \`agent.list_runs\`, filtered to real runs. Scheduled agents are checked in rounded five-minute buckets, so a minute-level cron inside the bucket queues one work order for that bucket rather than one order per minute. Sandbox dry runs do not count as real turns. If the agent is repeatedly blocked, revise the Charter or split the seat. If the agent is taking too much judgment, narrow its autonomous scope.`
+Review the first dry runs, fleet overview, tool-call audit rows, escalations, deliverables, and Signal impact. A seat's completed-work area combines explicit deliverables, work-log evidence, and successful run summaries into one operator-facing trail with safe links labelled as internal, Linear, GitHub, or external. The fleet view at \`/agents\` shows every staffed agent seat at a glance; the agent-native equivalents are \`{{cli}} command agent.list_fleet --json '{}'\` / \`rost_list_agent_fleet\` for the compact overview, and \`{{cli}} agent fleet-digest --json\` / \`agent.fleet_digest\` / \`rost_get_dogfood_fleet_health_digest\` for the daily dogfood evidence bundle. The digest returns live/idle state, 24h/7d turns, 7d/30d spend, recent failed runs, unresolved product errors, failed notifications, and a next action per seat. Shared system-health summaries use the same server-derived tenant, member, or seat-token scope so UI, CLI, and MCP operators see consistent stalled-work, unresolved-error, runner, and notification counts without client-supplied tenant boundaries. Fleet real-turn counts use the same seat-run association as \`agent.list_runs\`, filtered to real runs. Scheduled agents are checked in rounded five-minute buckets, so a minute-level cron inside the bucket queues one work order for that bucket rather than one order per minute. Sandbox dry runs do not count as real turns. If the agent is repeatedly blocked, revise the Charter or split the seat. If the agent is taking too much judgment, narrow its autonomous scope.`
   },
   {
     slug: "tool-access-and-vault",
@@ -42384,7 +42384,7 @@ External connectors are being rolled out provider by provider, conservatively (r
     order: 48,
     title: "CLI and MCP installation guide",
     summary: "Install the public CLI, register remote token-backed MCP clients, and find the full command and tool catalog.",
-    version: "2026-06-21.11",
+    version: "2026-06-21.13",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing"],
@@ -42443,7 +42443,12 @@ External connectors are being rolled out provider by provider, conservatively (r
       "integration.list",
       "integration.readiness",
       "integration.status",
-      "integration.test"
+      "integration.test",
+      "tenant.rename",
+      "deliverable.list",
+      "deliverable.get",
+      "deliverable.create",
+      "deliverable.attach"
     ],
     legal: {
       publicRisk: "low",
@@ -42820,7 +42825,7 @@ The signed-in app exposes the same Skill command surface under **Skills** in the
 | \`{{cli}} runner list|status|work-orders|revoke\` | \`runner.list\`, \`runner.status\`, \`work_order.list\`, \`runner.revoke\` | Inspect runners and work orders; revoke a runner. | Tenant | \`{{cli}} runner list --json\` |
 | \`{{cli}} notification settings|test|errors\` | \`notification.settings.get\`, \`notification.test\`, \`notification.list_errors\` | Read notification settings, send a test, and list failed deliveries with linked product error source, seat id, and run id when available. | Tenant | \`{{cli}} notification errors --limit 10 --json\` |
 | \`{{cli}} integration list|readiness|status|test\` | \`integration.list\`, \`integration.readiness\`, \`integration.status\`, \`integration.test\` | List connector metadata, read the setup-readiness checklist, read one connector's health, and run the provider-specific connection test without exposing credentials. | Tenant | \`{{cli}} integration readiness --provider google --json\` |
-| \`{{cli}} settings get|update|product-learning\` | \`settings.get\`, \`settings.update\`, \`settings.product_learning.get\`, \`settings.product_learning.update\` | Read tenant settings, update budget caps, and read or update product-learning participation. Product-learning updates stop at human confirmation in non-interactive CLI/MCP sessions. | Tenant / Tenant-admin for updates | \`{{cli}} settings product-learning get --json\`; \`{{cli}} settings product-learning update --mode disabled --json\` |
+| \`{{cli}} settings get|update|product-learning|rename\` | \`settings.get\`, \`settings.update\`, \`settings.product_learning.get\`, \`settings.product_learning.update\`, \`tenant.rename\` | Read tenant settings, update budget caps, read or update product-learning participation, and rename the company. Budget and product-learning updates stop at human confirmation in non-interactive CLI/MCP sessions; company rename is owner-only and human-gated. | Tenant / Tenant-admin for updates | \`{{cli}} settings product-learning get --json\`; \`{{cli}} settings product-learning update --mode disabled --json\`; \`{{cli}} settings rename --company "Acme Operations"\` |
 | \`{{cli}} member invite|update|remove\` | \`member.invite\`, \`member.update\`, \`member.remove\` | Manage tenant members. | Tenant | \`{{cli}} member invite --email ops@example.com --role member\` |
 | \`{{cli}} agent templates|create|setup|tools|dry-run|go-live|status|run-now|fleet-digest|get-run|show\` | \`agent_template.list\`, \`agent.create_from_template\`, \`agent.create_custom\`, \`agent_setup.get\`, \`agent_setup.update\`, \`agent.configure_tools\`, \`agent.run_dry_run\`, \`agent.go_live\`, \`agent.status\`, \`agent.run_now\`, \`agent.fleet_digest\`, \`agent.get_run\`, \`agent.show_markdown\` | Run the full agent setup and operation flow: list templates, create a draft from a template or guided custom answers (with \`--model\` and \`--effort\`), read or answer setup state, connect or decline tools, dry-run, go live, run on demand, capture the fleet-health digest, read one run's transcript/error diagnostics, and show a markdown readout. Human CLI dry-runs print the rehearsal transcript and, when present, the per-tool preview labels (\`Would run\`, \`Blocked\`, \`Escalated\`) before go-live. Create and go-live stop at human gates; the dry-run is ungated by human approval but requires a signed manifest first. | Tenant and seat | \`{{cli}} agent fleet-digest --json\` |
 | \`{{cli}} tools list\` | \`tool.catalog\` | List the discoverable tool catalog the builder reads (id, scope tiers, credential requirement, access policy, and execution-boundary guidance). | Tenant | \`{{cli}} tools list --json\` |
@@ -42830,6 +42835,7 @@ The signed-in app exposes the same Skill command surface under **Skills** in the
 | \`{{cli}} model list\` | \`model.catalog\` | List guided model tiers with recommendations, token prices, cost bands, best-fit work, and model ids for \`--model\`. | Tenant | \`{{cli}} model list --json\` |
 | \`{{cli}} compass show\` | \`compass.show_markdown\` | Render the current Compass as a clean markdown card for review. | Tenant | \`{{cli}} compass show --markdown\` |
 | \`{{cli}} charter show\` | \`charter.show_markdown\` | Render a seat's Charter as a clean markdown card for review. | Tenant | \`{{cli}} charter show --seat-id <id> --markdown\` |
+| \`{{cli}} deliverable list|get|create|attach\` | \`deliverable.list\`, \`deliverable.get\`, \`deliverable.create\`, \`deliverable.attach\` | List, get, create, or attach agent deliverables for a seat. Deliverables are durable work outputs visible across UI, CLI, and MCP. | Tenant (list/get), Seat (create/attach) | \`{{cli}} deliverable list --seat-id <id> --json\`; \`{{cli}} deliverable create --title "Brief" --kind brief\` |
 
 Skills wrapper help:
 
@@ -42949,6 +42955,10 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_list_agent_runs\` | \`agent.list_runs\` | Read a seat's agent run history (status, lane, model, cost, per-run Skill activation, tool-call, and guard-held counts) plus the seat's run/tool-call rollup including held-action count. | Seat or tenant-admin | Call with \`{"seat_id":"<seat-id>"}\`; pass \`limit\` for a deeper window. |
 | \`rost_get_agent_run_diagnostics\` | \`agent.get_run\` | Read one run's diagnostic record: transcript reference, token/cost usage, outcome, linked product-visible run errors, and loaded Skill activation file metadata. File hashes/sizes identify the immutable source package, while model prompt text may be bounded or truncated. | Seat or tenant-admin | Call with \`{"seat_id":"<seat-id>","run_id":"<run-id>"}\`. |
 | \`rost_list_agent_tool_calls\` | \`agent.list_tool_calls\` | Read a seat's tool-call ledger (tool name, guard result, manifest clause, outcome) with the held-action count as the hero metric. Never returns argument summaries or secret material. | Seat or tenant-admin | Call with \`{"seat_id":"<seat-id>"}\`; pass \`held_only: true\` for only guard-held calls. |
+| \`rost_list_agent_deliverables\` | \`deliverable.list\` | List durable agent deliverables for a seat, including explicit outputs and successful-run summaries. | Seat or tenant-admin | Call with \`{"seat_id":"<seat-id>"}\`. |
+| \`rost_get_agent_deliverable\` | \`deliverable.get\` | Read one durable agent deliverable by id for a seat. | Seat or tenant-admin | Call with \`{"seat_id":"<seat-id>","deliverable_id":"<id>"}\`. |
+| \`rost_create_agent_deliverable\` | \`deliverable.create\` | Create a scrubbed durable work output for the acting seat. | Seat | Call with title, kind, summary/content, and optional safe links. |
+| \`rost_attach_agent_deliverable\` | \`deliverable.attach\` | Attach a scrubbed deliverable to a source run, task, or work order after server-side seat validation. | Seat | Call with title, kind, and the source ids that belong to the acting seat. |
 | \`rost_list_agent_templates\` | \`agent_template.list\` | List stock agent templates and metadata. | Tenant | Call with \`{}\`. |
 | \`rost_create_agent_from_template\` | \`agent.create_from_template\` | Create a draft stock agent and draft Charter from a template (draft-only; occupancy needs a human steward). | Tenant | Call with \`seat_id\` and \`template_slug\`; expect human confirmation. |
 | \`rost_start_agent_setup\` | \`agent_setup.start\` | Start an agent setup draft for template, custom, or existing mode. | Tenant | Call with \`mode\` and seat placement. |
@@ -42982,6 +42992,7 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_remove_member\` | \`member.remove\` | Remove a tenant member. | Tenant | Call with \`member_id\`; blocked if it would orphan an agent steward chain. |
 | \`rost_get_tenant_settings\` | \`settings.get\` | Read tenant operating settings and integration status. | Tenant | Call with \`{}\`; metadata only. |
 | \`rost_update_tenant_settings\` | \`settings.update\` | Update tenant AI budget caps. | Tenant | Call with \`soft_cap_usd\` or \`hard_cap_usd\`; expect human confirmation. |
+| \`rost_rename_company\` | \`tenant.rename\` | Rename the current company. | Tenant-admin | Call with \`company_name\`; expect human confirmation. |
 | \`rost_get_sync_brief_scope\` | \`settings.sync_brief_scope.get\` | Read the tenant's Sync Brief scope (company_wide or per_cluster). | Tenant | Call with \`{}\`. |
 | \`rost_update_sync_brief_scope\` | \`settings.sync_brief_scope.update\` | Set the tenant's Sync Brief scope (company_wide or per_cluster). | Tenant-admin | Owner-only; call with \`{"sync_brief_scope":"company_wide"}\` or \`{"sync_brief_scope":"per_cluster"}\`. |
 | \`rost_get_product_learning_policy\` | \`settings.product_learning.get\` | Read whether product/page/recommendation analytics are allowed. | Tenant | Call with \`{}\`; audit/security logs are always enabled. |
@@ -43776,7 +43787,7 @@ Keep agent scope tight at first. Approve more autonomy only after evidence. Use
     order: 71,
     title: "Confirmations and human gates guide",
     summary: "How {{brand}} routes authority-changing work through human confirmation, and why agents never approve their own requests.",
-    version: "2026-06-20.1",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["graph_design", "charter_design", "staffing", "operating_rhythm"],
@@ -43801,7 +43812,7 @@ Keep agent scope tight at first. Approve more autonomy only after evidence. Use
 ## Confirmation levels
 
 - \`none\`: no confirmation gate \u2014 the command never returns a pending confirmation. Most are reads or reversible drafts an agent can run directly, including over MCP (graph reads, \`charter.draft\`, \`status.record\`, \`sync.brief.compile\`, \`sync.run.start\`, \`task.complete\`). A few \`none\` commands still require a human actor or an interactive channel \u2014 \`confirmation.approve\` is \`none\` (approving a gate cannot itself be gated) yet runs only as a human in the UI or CLI \u2014 so \`none\` means "no confirmation gate", not always "agent-callable".
-- \`human_required\`: a human must approve. Structural, staffing, resolution, and go-live commands (\`seat.reparent\`, \`charter.approve\`, \`goal.reparent\`, \`friction.resolve\`, \`agent.go_live\`, \`mcp_token.create\`).
+- \`human_required\`: a human must approve. Structural, staffing, resolution, tenant profile, and go-live commands (\`seat.reparent\`, \`charter.approve\`, \`goal.reparent\`, \`friction.resolve\`, \`agent.go_live\`, \`mcp_token.create\`, \`tenant.rename\`).
 - \`credential_flow\`: routes through the vault-backed credential path so a secret is captured as a vault reference, never stored or logged in the clear (\`credential.ingress\`, \`tenant.anthropic_key.save\`; \`agent.configure_tools\` is \`credential_flow\` too \u2014 it stages credential-ingress requests through the same path without ever taking raw secret material).
 - \`dangerous\`: the highest-risk human gate. Only two commands carry it \u2014 \`settings.update\` and \`agent.decommission\`.
 
@@ -43831,11 +43842,11 @@ Stop before: approving a Charter, signing a manifest, connecting a tool or crede
     order: 72,
     title: "Settings guide",
     summary: "How to use Settings as the control plane for company access, channels, providers, tokens, and operating defaults.",
-    version: "2026-06-21.2",
+    version: "2026-06-21.4",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing"],
-    relatedCommandIds: ["onboarding.create_invite", "mcp_token.create", "mcp_token.revoke", "mcp_token.list", "integration.list", "integration.readiness", "integration.status", "integration.test", "settings.get", "settings.update", "settings.sync_brief_scope.get", "settings.sync_brief_scope.update", "settings.product_learning.get", "settings.product_learning.update"],
+    relatedCommandIds: ["onboarding.create_invite", "mcp_token.create", "mcp_token.revoke", "mcp_token.list", "integration.list", "integration.readiness", "integration.status", "integration.test", "settings.get", "settings.update", "tenant.rename", "settings.sync_brief_scope.get", "settings.sync_brief_scope.update", "settings.product_learning.get", "settings.product_learning.update"],
     legal: { publicRisk: "low", notes: ["{{brand}}-native settings guidance."] },
     sources: [
       {
@@ -43854,7 +43865,7 @@ Start with members and invites, then provider and channel connections, then MCP
 
 ## What belongs in Settings
 
-- Company profile and workspace defaults.
+- Company profile and workspace defaults. Rename the company from Settings or with \`tenant.rename\` (CLI: \`{{cli}} settings rename --company "<name>"\`); the command is owner-only, human-gated, and records a rename event with old and new names.
 - Members, invites, and tenant roles.
 - Agent access tokens for local agents.
 - Provider and integration configuration.
@@ -43888,6 +43899,8 @@ Product-learning participation controls whether {{brand}} may record product/pag
 
 Read the policy with \`settings.product_learning.get\` (CLI: \`{{cli}} settings product-learning get\`). Change it with \`settings.product_learning.update\` (CLI: \`{{cli}} settings product-learning update --mode disabled\`). Analytics ingestion code should call the shared product-learning policy helper instead of reading \`tenants.settings\` directly.
 
+The product analytics foundation stores only bounded product telemetry: product events, page views by route template, command invocation metadata, onboarding milestones, and recommendation outcomes. Authenticated users can read analytics rows for their tenant, but writes are server-owned through the trusted DB helpers. The helpers and database constraints reject or redact obvious raw URLs, filesystem paths, secrets, prompt/content fields, command argument/output fields, direct contact/payment identifiers, and long prose-shaped values. These analytics rows are not audit records; operational logs and security evidence stay in their dedicated append-only or product-visible tables.
+
 ## Inference budget
 
 Agents that run on {{brand}}-managed inference draw against a tenant inference budget with a hard cap. A new company starts with a hard cap of $0, so a managed-inference run is blocked until the cap is raised. When a run hits the cap it stops with a typed budget error that names the fix; raise the cap before agents can run again.
@@ -46543,14 +46556,26 @@ var settingsWrapper = (context, args) => dispatch(context, "settings", args, {
       const spend = asRecord(asRecord(output).spend);
       return `Updated budget caps (soft=$${field(spend, "soft_cap_usd")}, hard=$${field(spend, "hard_cap_usd")}).`;
     });
+  },
+  rename: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const companyName = optionalValue(parsed, "company");
+    if (!companyName) {
+      throw new UsageError("Provide --company <name>.");
+    }
+    return execute(ctx, parsed, "tenant.rename", { company_name: companyName }, (output) => {
+      const record2 = asRecord(output);
+      return `Renamed company from ${field(record2, "previous_name")} to ${field(record2, "name")}.`;
+    });
   }
 }, settingsUsage(context.binName));
 function settingsUsage(bin) {
-  return `Usage: ${bin} settings get|update|product-learning [--json]
+  return `Usage: ${bin} settings get|update|product-learning|rename [--json]
   ${bin} settings get
   ${bin} settings update [--soft-cap-usd <n>] [--hard-cap-usd <n>]
   ${bin} settings product-learning get
-  ${bin} settings product-learning update --mode enabled|disabled|enterprise_contract`;
+  ${bin} settings product-learning update --mode enabled|disabled|enterprise_contract
+  ${bin} settings rename --company <name>`;
 }
 var memberWrapper = (context, args) => dispatch(context, "member", args, {
   invite: (ctx, rest) => {
@@ -47115,6 +47140,87 @@ function charterUsage(bin) {
   return `Usage: ${bin} charter show --seat-id <id> [--markdown] [--json]
   ${bin} charter show --seat-id <id> --markdown \u2014 render a seat's active or latest Charter as a markdown card.`;
 }
+function formatDeliverableList(output) {
+  const deliverables = asArray(asRecord(output).deliverables);
+  if (deliverables.length === 0) {
+    return "No deliverables for this seat.";
+  }
+  return deliverables.map((entry) => {
+    const r = asRecord(entry);
+    const summary = field(r, "summary") === "\u2014" ? "" : ` \u2014 ${field(r, "summary")}`;
+    return `${field(r, "id")}  [${field(r, "kind")}]  ${field(r, "title")}${summary}`;
+  }).join("\n");
+}
+function formatDeliverableDetail(output) {
+  const d = asRecord(asRecord(output).deliverable);
+  const links = asArray(d.links).map((entry) => {
+    const l = asRecord(entry);
+    return `  ${field(l, "kind")}: ${field(l, "label")} <${field(l, "url")}>`;
+  }).join("\n");
+  return [
+    `# ${field(d, "title")} [${field(d, "kind")}]`,
+    field(d, "id"),
+    field(d, "summary") === "\u2014" ? "" : field(d, "summary"),
+    field(d, "content") === "\u2014" ? "" : `content:
+${field(d, "content")}`,
+    `delivered: ${field(d, "delivered_at")}`,
+    `run: ${field(d, "source_run_status")} ${field(d, "source_run_model")}`,
+    `task: ${field(d, "source_task_title")}`,
+    links.length > 0 ? `links:
+${links}` : ""
+  ].filter((line) => line.length > 0).join("\n");
+}
+function formatDeliverableWrite(output) {
+  const record2 = asRecord(output);
+  return `deliverable ${field(record2, "deliverable_id")} recorded.`;
+}
+var deliverableWrapper = (context, args) => dispatch(context, "deliverable", args, {
+  list: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const seatId = requireValue2(parsed, "seat-id");
+    return execute(ctx, parsed, "deliverable.list", { seat_id: seatId }, formatDeliverableList);
+  },
+  get: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const body = {
+      seat_id: requireValue2(parsed, "seat-id"),
+      deliverable_id: requireValue2(parsed, "deliverable-id")
+    };
+    return execute(ctx, parsed, "deliverable.get", body, formatDeliverableDetail);
+  },
+  create: (ctx, rest) => {
+    const parsed = parseFlags(rest, /* @__PURE__ */ new Set(["json"]));
+    const body = withOptional({
+      kind: optionalValue(parsed, "kind") ?? "other",
+      title: requireValue2(parsed, "title")
+    }, {
+      summary: optionalValue(parsed, "summary"),
+      content: optionalValue(parsed, "content")
+    });
+    return execute(ctx, parsed, "deliverable.create", body, formatDeliverableWrite);
+  },
+  attach: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const body = withOptional({
+      kind: optionalValue(parsed, "kind") ?? "other",
+      title: requireValue2(parsed, "title")
+    }, {
+      run_id: optionalValue(parsed, "run-id"),
+      task_id: optionalValue(parsed, "task-id"),
+      work_order_id: optionalValue(parsed, "work-order-id"),
+      summary: optionalValue(parsed, "summary"),
+      content: optionalValue(parsed, "content")
+    });
+    return execute(ctx, parsed, "deliverable.attach", body, formatDeliverableWrite);
+  }
+}, deliverableUsage(context.binName));
+function deliverableUsage(bin) {
+  return `Usage: ${bin} deliverable list|get|create|attach [--json]
+  ${bin} deliverable list --seat-id <id>
+  ${bin} deliverable get --seat-id <id> --deliverable-id <id>
+  ${bin} deliverable create --title <text> [--kind brief|work_evidence|artifact|report|other] [--summary <text>] [--content <text>]
+  ${bin} deliverable attach --title <text> [--run-id <id>] [--task-id <id>] [--work-order-id <id>] [--kind brief|work_evidence|artifact|report|other] [--summary <text>] [--content <text>]`;
+}
 var OPERATION_GROUPS = [
   "task",
   "status",
@@ -47133,7 +47239,8 @@ var OPERATION_GROUPS = [
   "skills",
   "model",
   "compass",
-  "charter"
+  "charter",
+  "deliverable"
 ];
 var wrappers = {
   task: taskWrapper,
@@ -47153,7 +47260,8 @@ var wrappers = {
   skills: skillsWrapper,
   model: modelWrapper,
   compass: compassWrapper,
-  charter: charterWrapper
+  charter: charterWrapper,
+  deliverable: deliverableWrapper
 };
 function isOperationGroup(value) {
   return value !== void 0 && OPERATION_GROUPS.includes(value);
@@ -47176,7 +47284,8 @@ var groupUsageBuilders = {
   skills: skillsUsage,
   model: modelUsage,
   compass: compassUsage,
-  charter: charterUsage
+  charter: charterUsage,
+  deliverable: deliverableUsage
 };
 function operationGroupUsage(group, bin) {
   return usageWithSchemaFooter(groupUsageBuilders[group](bin), bin);
@@ -47200,14 +47309,15 @@ function operationUsageLines(bin) {
     `${bin} sync brief|compile|complete`,
     `${bin} runner list|status|work-orders|revoke`,
     `${bin} notification settings|test|errors`,
-    `${bin} settings get|update|product-learning`,
+    `${bin} settings get|update|product-learning|rename`,
     `${bin} member invite|update|remove`,
     `${bin} agent templates|create|setup|tools|dry-run|go-live|status|run-now|fleet-digest|get-run|show`,
     `${bin} tools list`,
     `${bin} skills list|get|file|assigned|check-dependencies`,
     `${bin} model list`,
     `${bin} compass show`,
-    `${bin} charter show`
+    `${bin} charter show`,
+    `${bin} deliverable list|get|create|attach`
   ];
 }