@mycadet/assistant 0.12.7 → 0.12.9

package/src/cli/commands/cloud/index.help.ts

@@ -11,11 +11,11 @@ export const cloudHelp: CliCommandHelp = {
   helpText: `
 The cloud subsystem manages the connection to Cadet Cloud. Use
 'connect', 'status', and 'disconnect' to manage cloud credentials.
-Any assistant using the managed LLM proxy can use these commands.
+Any assistant using the cloud LLM proxy can use these commands.
 
 External service callbacks (Telegram webhooks, Twilio webhooks, email,
-OAuth redirects) route through the platform's gateway proxy via
-'callback-routes'. Works for both platform-managed and self-hosted
+OAuth redirects) route through the cloud's gateway proxy via
+'callback-routes'. Works for both cloud-managed and self-hosted
 assistants.
 
 Examples:
@@ -52,16 +52,16 @@ Reads platform-related environment variables and stored credentials to report
 the current platform deployment context and connection state.
 
 Fields:
-  isPlatform          Whether IS_PLATFORM is set (boolean)
-  baseUrl             CADET_PLATFORM_URL — the platform gateway base URL
+  isPlatform          Whether IS_CLOUD is set (boolean)
+  baseUrl             CADET_CLOUD_URL — the cloud gateway base URL
   assistantId         This assistant's platform UUID
   hasAssistantApiKey  Whether a stored assistant API key is available; null
                       when the credential store could not be read
   hasWebhookSecret    Whether a stored webhook secret is available (needed
                       for email and other inbound webhook channels)
   available           Whether callback registration prerequisites are satisfied
-  organizationId      The platform organization ID (from stored credentials)
-  userId              The platform user ID (from stored credentials)
+  organizationId      The cloud organization ID (from stored credentials)
+  userId              The cloud user ID (from stored credentials)
 
 For the Tunnel state (only relevant for Twilio webhooks and live
 voice/audio), use 'assistant gateway status' instead.
@@ -76,7 +76,7 @@ Examples:
         "Show the organization's credit balance, plan-credit usage, and daily-limit state",
       helpText: `
 Fetches the org's credit balance, plan-included credit usage, extra credit,
-upcoming expiry, today's spend, and daily-limit state from the platform
+upcoming expiry, today's spend, and daily-limit state from the cloud
 billing summary.
 
 Fields:
@@ -103,14 +103,14 @@ Fields:
   credits_expiring_soon  Credit on grants expiring within 30 days, in USD
   next_credit_expiry_at  Earliest upcoming grant expiry (ISO 8601), or null
 
-Grant fields are null when the platform does not report grant figures. Plan
+Grant fields are null when the cloud does not report grant figures. Plan
 credit mixes grants with different lifetimes (only the Pro bundle turns over
 with the billing cycle), so it has no single reset date. next_credit_expiry_at
 is the earliest expiry across all grants, plan-included or not, and
 'assistant cloud subscription' gives the billing cycle boundary.
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure CADET_PLATFORM_URL is set and credentials are stored).
+ensure CADET_CLOUD_URL is set and credentials are stored).
 
 Examples:
   $ assistant cloud credits
@@ -121,7 +121,7 @@ Examples:
       description:
         "Show the organization's current plan and subscription state",
       helpText: `
-Fetches the org's plan and subscription state from the platform. Answers
+Fetches the org's plan and subscription state from the cloud. Answers
 "what plan am I on?".
 
 Fields:
@@ -130,7 +130,7 @@ Fields:
                       null on the base plan
   renewalDate         When the current period ends / the plan renews (ISO
                       8601), or null on the base plan
-  currentPeriodEnd    Same as renewalDate; mirrors the platform field
+  currentPeriodEnd    Same as renewalDate; mirrors the cloud field
   cancelAtPeriodEnd   True when the subscription is set to cancel at period end
   cancelAt            When the subscription cancels (ISO 8601), or null
   selectedCreditTier  The selected Pro credit bundle tier, or null
@@ -142,7 +142,7 @@ For the credit balance (not the plan), use 'assistant cloud credits'. For
 plan pricing, use 'assistant cloud plans'.
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure CADET_PLATFORM_URL is set and credentials are stored).
+ensure CADET_CLOUD_URL is set and credentials are stored).
 
 Examples:
   $ assistant cloud subscription
@@ -152,7 +152,7 @@ Examples:
       name: "plans",
       description: "Show the plan catalog with pricing",
       helpText: `
-Fetches the platform plan catalog. Answers "how much does each plan cost?".
+Fetches the cloud plan catalog. Answers "how much does each plan cost?".
 
 Returns a "plans" array. Each entry has an "id" ("base" or "pro"), "name",
 "billing_interval", and "included_features". The base plan carries
@@ -163,7 +163,7 @@ For the org's OWN plan (not the catalog), use 'assistant cloud
 subscription'. For the credit balance, use 'assistant cloud credits'.
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure CADET_PLATFORM_URL is set and credentials are stored).
+ensure CADET_CLOUD_URL is set and credentials are stored).
 
 Examples:
   $ assistant cloud plans
@@ -173,17 +173,17 @@ Examples:
       name: "invoices",
       description: "Read the organization's Stripe invoice history",
       helpText: `
-Invoices are read from the platform's billing invoices endpoint using this
+Invoices are read from the cloud's billing invoices endpoint using this
 assistant's platform API key. Amounts are Stripe-scaled integers; see
 'assistant cloud invoices list --help' for the scaling rules. 'created'
 is a Unix timestamp in seconds.
 
-The platform returns one page of invoices at a time (newest first). When
+The cloud returns one page of invoices at a time (newest first). When
 the response's 'has_more' is true, pass the last invoice's id via
 --starting-after to fetch the next (older) page.
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure CADET_PLATFORM_URL is set and credentials are stored).
+ensure CADET_CLOUD_URL is set and credentials are stored).
 
 Examples:
   $ assistant cloud invoices list --json
@@ -202,7 +202,7 @@ Examples:
             },
           ],
           helpText: `
-Fetches one page of the org's Stripe invoice history from the platform,
+Fetches one page of the org's Stripe invoice history from the cloud,
 newest first.
 
 Fields:
@@ -229,7 +229,7 @@ Fields:
                       fetch them with --starting-after
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure CADET_PLATFORM_URL is set and credentials are stored).
+ensure CADET_CLOUD_URL is set and credentials are stored).
 
 Examples:
   $ assistant cloud invoices list --json
@@ -246,13 +246,13 @@ Examples:
             },
           ],
           helpText: `
-The platform has no per-invoice endpoint, so the assistant pages through
+The cloud has no per-invoice endpoint, so the assistant pages through
 the org's invoice list (newest first) until the ID matches. The lookup
 searches the most recent 2,500 invoices (25 pages) and errors if the ID
 is not found within that range.
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure CADET_PLATFORM_URL is set and credentials are stored).
+ensure CADET_CLOUD_URL is set and credentials are stored).
 
 Examples:
   $ assistant cloud invoices get in_1AbCdEfGh
@@ -265,8 +265,8 @@ Examples:
       description: "Disconnect from Cadet Cloud by removing stored credentials",
       helpText: `
 Removes all stored cloud credentials from the assistant's secure
-credential store. After disconnecting, platform-managed features (managed
-proxy, managed OAuth, callback routing) will no longer be available until
+credential store. After disconnecting, cloud-managed features (managed
+proxy, cloud OAuth, callback routing) will no longer be available until
 you reconnect with 'assistant cloud connect'.
 
 Use 'assistant cloud status' to check the current connection state
@@ -280,7 +280,7 @@ Examples:
       name: "callback-routes",
       description: "Manage platform callback route registrations",
       helpText: `
-Callback routes tell the platform gateway how to forward inbound provider
+Callback routes tell the cloud gateway how to forward inbound provider
 webhooks to the correct assistant instance. Each route maps a callback path
 and type to a stable external URL that external services (Telegram, Twilio,
 email, OAuth providers) should use.
@@ -293,7 +293,7 @@ Examples:
       subcommands: [
         {
           name: "register",
-          description: "Register a callback route with the platform gateway",
+          description: "Register a callback route with the cloud gateway",
           options: [
             {
               flags: "--path <path>",
@@ -309,14 +309,14 @@ Examples:
             },
           ],
           helpText: `
-Registers a callback route with the platform's internal gateway endpoint so
-the platform knows how to forward inbound provider webhooks to this
-platform-managed assistant instance.
+Registers a callback route with the cloud's internal gateway endpoint so
+the cloud knows how to forward inbound provider webhooks to this
+cloud assistant instance.
 
 Arguments:
   --path    The path portion after the ingress base URL. Leading/trailing
-            slashes are stripped by the platform.
-  --type    The route type identifier used by the platform to classify and
+            slashes are stripped by the cloud.
+  --type    The route type identifier used by the cloud to classify and
             route the callback.
 
 Known callback path/type combinations:
@@ -328,8 +328,8 @@ Known callback path/type combinations:
   --path webhooks/email             --type email
   --path oauth/callback             --type oauth
 
-Works for both platform-managed and self-hosted assistants. Requires
-CADET_PLATFORM_URL and a platform assistant ID. Returns the platform-provided
+Works for both cloud-managed and self-hosted assistants. Requires
+CADET_CLOUD_URL and a cloud assistant ID. Returns the cloud-provided
 stable callback URL that external services should use.
 
 Examples:
@@ -340,11 +340,11 @@ Examples:
           name: "list",
           description: "List registered callback routes for this assistant",
           helpText: `
-Lists all callback routes registered with the platform for this assistant.
+Lists all callback routes registered with the cloud for this assistant.
 Shows the route type, callback URL, and path for each registered webhook.
 
 Requires cloud credentials (run 'assistant cloud connect' first or
-ensure IS_PLATFORM and CADET_PLATFORM_URL are set and credentials are stored).
+ensure IS_CLOUD and CADET_CLOUD_URL are set and credentials are stored).
 
 Examples:
   $ assistant cloud callback-routes list

package/src/cli/commands/cloud/index.ts

@@ -260,7 +260,7 @@ export function registerCloudCommand(program: Command): void {
             callbackUrl: string;
             callbackPath: string;
             type: string;
-          }>("platform_callback_routes_register", {
+          }>("cloud_callback_routes_register", {
             body: { path: opts.path, type: opts.type },
           });
           if (!r.ok) {

package/src/cli/commands/config.ts

@@ -40,7 +40,7 @@ const SERVICE_MODE_PATH_RE = /^services\.[^.]+\.mode$/;
  */
 const REMOVED_MODE_PATHS: Record<string, string> = {
   "services.web-search.mode":
-    "services.web-search.mode does not exist; web search is configured by provider alone. For managed search run `config set services.web-search.provider cadet`.",
+    "services.web-search.mode does not exist; web search is configured by provider alone. For cloud search run `config set services.web-search.provider cadet`.",
   "services.image-generation.mode":
     "services.image-generation.mode does not exist; image generation is configured by provider alone. For managed image generation run `config set services.image-generation.provider cadet`.",
 };
@@ -153,7 +153,7 @@ export function registerConfigCommand(program: Command): void {
           // the value above cannot be mistaken for the effective one.
           const { describeShadowedConfigGet, findSubstrateShadowing } =
             await import("../../config/substrate-twin-shadowing.js");
-          const shadowing = findSubstrateShadowing(raw, key);
+          const shadowing = findSubstrateShadowing(key);
           if (shadowing) {
             log.warn(describeShadowedConfigGet(shadowing, key));
           }

package/src/cli/commands/credentials.ts

@@ -59,8 +59,8 @@ function printCredentialHuman(output: Record<string, unknown>): void {
   }
 }
 
-function printManagedCredentialHuman(output: Record<string, unknown>): void {
-  log.info(`  [platform-managed] ${output.provider}`);
+function printCloudCredentialHuman(output: Record<string, unknown>): void {
+  log.info(`  [cloud-managed] ${output.provider}`);
   log.info(`    Handle:      ${output.handle}`);
   log.info(`    Status:      ${output.status}`);
   if (output.accountInfo) {
@@ -82,7 +82,7 @@ function printManagedCredentialHuman(output: Record<string, unknown>): void {
 
 interface CredentialsListResponse {
   credentials: Record<string, unknown>[];
-  managedCredentials: Record<string, unknown>[];
+  cloudCredentials: Record<string, unknown>[];
 }
 
 interface CredentialsStatusResponse {
@@ -120,16 +120,16 @@ export function registerCredentialsCommand(program: Command): void {
             );
           }
 
-          const { credentials, managedCredentials } = r.result!;
+          const { credentials, cloudCredentials } = r.result!;
 
           if (shouldOutputJson(cmd)) {
             writeOutput(cmd, {
               ok: true,
               credentials,
-              managedCredentials,
+              cloudCredentials,
             });
           } else {
-            const totalCount = credentials.length + managedCredentials.length;
+            const totalCount = credentials.length + cloudCredentials.length;
             if (totalCount === 0) {
               log.info("No credentials found");
             } else {
@@ -140,12 +140,10 @@ export function registerCredentialsCommand(program: Command): void {
                   log.info("");
                 }
               }
-              if (managedCredentials.length > 0) {
-                log.info(
-                  `${managedCredentials.length} platform-managed credential(s):\n`,
-                );
-                for (const managed of managedCredentials) {
-                  printManagedCredentialHuman(managed);
+              if (cloudCredentials.length > 0) {
+                log.info(`${cloudCredentials.length} cloud credential(s):\n`);
+                for (const managed of cloudCredentials) {
+                  printCloudCredentialHuman(managed);
                   log.info("");
                 }
               }

package/src/cli/commands/domain.ts

@@ -70,7 +70,7 @@ Examples:
           return `
 Arguments:
   subdomain   The subdomain to register (e.g. "velly" → velly.${baseDomain}).
-              If omitted, the platform derives it from the assistant's name.
+              If omitted, the cloud derives it from the assistant's name.
 
 Options:
   --email-username <username>  Also register an email address for the domain

package/src/cli/commands/email.help.ts

@@ -114,7 +114,7 @@ from the assistant's registered email address.
 
 Body source priority: --body flag > --file flag > stdin (if not a TTY).
 
-When --reply-to is provided, the platform auto-resolves In-Reply-To,
+When --reply-to is provided, the cloud auto-resolves In-Reply-To,
 References, and Subject headers from the referenced email. You can
 still override subject with -s.
 

package/src/cli/commands/email.ts

@@ -180,7 +180,7 @@ Examples:
           "after",
           () => `
 Shows the email address registered for this assistant along with
-current usage and quota information from the platform.
+current usage and quota information from the cloud.
 
 Examples:
   $ assistant email status
@@ -482,7 +482,7 @@ Examples:
           }
 
           // Read attachments and base64-encode their content for the JSON
-          // wire to the platform proxy.
+          // wire to the cloud proxy.
           let attachments:
             | { filename: string; content_type: string; content: string }[]
             | undefined;

package/src/cli/commands/gateway.help.ts

@@ -32,7 +32,7 @@ public-ingress transport (currently Tunnel).
 
 The tunnel is ONLY used to route inbound Twilio webhooks and live voice/audio
 WebSockets through to this assistant. It has nothing to do with platform
-credentials, the managed LLM proxy, or text channels. If you are not using
+credentials, the cloud LLM proxy, or text channels. If you are not using
 Twilio voice or live audio, a "not connected" tunnel is expected and harmless.
 
 JSON output (--json):

package/src/cli/commands/gateway.ts

@@ -111,7 +111,7 @@ export function registerGatewayCommand(program: Command): void {
         log.info(
           "  live voice/audio WebSockets. It is not needed for text channels or",
         );
-        log.info("  the managed LLM proxy.");
+        log.info("  the cloud LLM proxy.");
       });
 
       const logs = subcommand(gateway, "logs");

package/src/cli/commands/image-generation.help.ts

@@ -7,7 +7,7 @@ export const imageGenerationHelp: CliCommandHelp = {
   description: "AI image generation and editing",
   helpText: `
 Modes:
-  managed    — Uses platform-managed credentials (requires login to Cadet).
+  managed    — Uses cloud credentials (requires login to Cadet).
   your-own   — Uses your own Gemini or OpenAI API key depending on the configured model.
 
 Supported models: pass a tier alias, the assistant resolves it to the

package/src/cli/commands/inference-providers.ts

@@ -65,7 +65,7 @@ function formatAuth(auth: AuthInfo): string {
     case "api_key":
       return `api_key (credential: ${auth.credential})`;
     case "platform":
-      return "platform (managed proxy)";
+      return "platform (cloud proxy)";
     case "none":
       return "none";
     case "oauth_subscription":

package/src/cli/commands/inference.help.ts

@@ -204,11 +204,11 @@ Examples:
       helpText: `
 A provider entry names a model provider plus how to reach it. Auth is
 derived from the provider: keyless providers (ollama) need none, the
-Cadet entry routes through the platform's managed proxy, and everything
+Cadet entry routes through the cloud's cloud proxy, and everything
 else uses an API key referenced by --credential.
 
 Canonical entry (seeded on every boot):
-  cadet → the platform-managed provider; cannot be deleted
+  cadet → the cloud provider; cannot be deleted
 
 Examples:
   $ assistant inference providers list

package/src/cli/commands/memory/index.help.ts

@@ -739,7 +739,7 @@ only contested gate decisions — the signal relevant for threshold calibration.
 Coverage is limited to runs still pending platform flush. In a healthy system
 the outbox holds only the last few minutes to hours of events, so
 --lookback-days is an upper bound, not a guarantee; long-window aggregation
-lives on the platform side on top of flushed watchdog events.
+lives on the cloud side on top of flushed watchdog events.
 
 Reads the telemetry database directly — the assistant does not need to be
 running.

package/src/cli/commands/oauth/connect.test.ts

@@ -98,7 +98,7 @@ async function runConnectCommand(extraArgs: string[] = []): Promise<{
 }
 
 describe("oauth connect", () => {
-  test("managed provider in a conversation shell returns oauth_connect guidance without opening a browser", async () => {
+  test("cloud provider in a conversation shell returns oauth_connect guidance without opening a browser", async () => {
     const { stdout, exitCode } = await runConnectCommand();
 
     expect(exitCode).toBe(1);
@@ -116,7 +116,7 @@ describe("oauth connect", () => {
     ]);
   });
 
-  test("managed provider in a conversation shell includes requested scopes in the oauth_connect guidance", async () => {
+  test("cloud provider in a conversation shell includes requested scopes in the oauth_connect guidance", async () => {
     const { stdout, exitCode } = await runConnectCommand([
       "--scopes",
       "https://www.googleapis.com/auth/tasks",

package/src/cli/commands/oauth/connect.ts

@@ -152,7 +152,7 @@ export function registerConnectCommand(oauth: Command): void {
 
             if (opts.clientId) {
               log.info(
-                `Warning: --client-id is ignored for platform-managed providers. The platform manages OAuth apps for "${provider}".`,
+                `Warning: --client-id is ignored for cloud providers. The cloud manages OAuth apps for "${provider}".`,
               );
             }
 

package/src/cli/commands/oauth/index.help.ts

@@ -515,7 +515,7 @@ Arguments:
 
 Modes:
   managed    OAuth credentials are managed by Cadet Cloud. The
-             assistant connects via a platform-hosted authorization flow.
+             assistant connects via a cloud-hosted authorization flow.
              No local client ID or secret is needed.
   your-own   You supply your own OAuth app credentials (client ID and
              secret). The assistant runs the OAuth flow locally.
@@ -699,9 +699,9 @@ completion. Use --no-browser to print the URL instead (useful for headless
 or SSH sessions).
 
 Important for chat/UI turns: do not run this command just to let the user
-connect a managed provider. Render the first-class connect surface instead:
+connect a cloud provider. Render the first-class connect surface instead:
 call \`ui_show\` with surface_type "oauth_connect" and data.providerKey set to
-the provider (for example, "google"). That surface starts the managed OAuth UI
+the provider (for example, "google"). That surface starts the cloud OAuth UI
 and avoids pasting raw authorization links into the conversation. If the user
 needs non-default scopes, also pass data.requestedScopes as a full replacement
 set (list every scope the connection should keep, not just the new ones).
@@ -866,7 +866,7 @@ need direct access to the token (i.e. \`assistant oauth request\` is
 insufficient) and you are comfortable with the security implications.
 
 Token retrieval is only supported for providers with mode set to "your-own".
-Platform-managed providers handle tokens internally — use
+Cloud providers handle tokens internally — use
 'assistant oauth ping <provider>' to verify connectivity or
 'assistant oauth request --provider <provider> <url>' to make
 authenticated requests.
@@ -925,7 +925,7 @@ Environment variables (printed as \`export\` lines with --export):
 Use 'assistant oauth status <provider>' to find account identifiers for
 --account. Unlabeled connections can be selected by their connection ID.
 
-Managed connections forward Content-Type, Accept, User-Agent, and X-Request-Id.
+Cloud connections forward Content-Type, Accept, User-Agent, and X-Request-Id.
 Requests with unsupported headers, including If-Match and Idempotency-Key,
 are rejected before calling the provider. A connection using your own OAuth
 app can preserve those headers.

package/src/cli/commands/oauth/providers.ts

@@ -282,7 +282,7 @@ export function registerProviderCommands(oauth: Command): void {
     ) => {
       const queryParams: Record<string, string> = {};
       if (opts.supportsManaged) {
-        queryParams.supports_managed_mode = "true";
+        queryParams.supports_cloud_mode = "true";
       }
       const r = await cliIpcCall<{
         providers: Array<Record<string, unknown>>;
@@ -300,7 +300,7 @@ export function registerProviderCommands(oauth: Command): void {
         providerKey: p.provider_key as string,
         displayName: p.display_name as string | null,
         description: p.description as string | null,
-        supportsManagedMode: p.supports_managed_mode as boolean,
+        supportsManagedMode: p.supports_cloud_mode as boolean,
         managedServiceIsPaid: p.managed_service_is_paid as boolean,
         requiresClientSecret: p.requires_client_secret as boolean,
         logoUrl: p.logo_url as string | null,

package/src/cli/commands/oauth/shared.ts

@@ -15,7 +15,7 @@ import { writeOutput } from "../../output.js";
 
 /**
  * Verify that the user has connected to Cadet Cloud (has stored
- * credentials). Unlike `requirePlatformClient`, this does NOT require a
+ * credentials). Unlike `requireCloudClient`, this does NOT require a
  * platform assistant ID — it only checks that credentials exist.
  *
  * Writes an error and sets exitCode=1 when the user is not connected.
@@ -26,8 +26,8 @@ import { writeOutput } from "../../output.js";
 export async function requirePlatformConnection(
   cmd: Command,
 ): Promise<boolean> {
-  const { CadetPlatformClient } = await import("../../../platform/client.js");
-  const client = await CadetPlatformClient.create();
+  const { CadetCloudClient } = await import("../../../cloud/client.js");
+  const client = await CadetCloudClient.create();
   if (!client) {
     writeOutput(cmd, {
       ok: false,

package/src/cli/commands/plugins.help.ts

@@ -184,8 +184,7 @@ Examples:
       options: [
         {
           flags: "--print",
-          description:
-            "Print the entry JSON without submitting to the platform",
+          description: "Print the entry JSON without submitting to the cloud",
         },
         {
           flags: "--path <dir>",
@@ -205,7 +204,7 @@ Examples:
 
 Validates the plugin in the current directory (or --path), resolves the
 git commit SHA and GitHub remote, and submits the entry to the Cadet
-platform API. The platform creates a pull request against
+platform API. The cloud creates a pull request against
 vargasjr-dev/mycadet adding the plugin to the marketplace catalog.
 
 Requires a connected Cadet Cloud account (run \`assistant cloud connect\`).

package/src/cli/commands/plugins.ts

@@ -112,8 +112,8 @@ const libs = {
       "pluginInstallPlatform",
       () =>
         loadModule(
-          "../lib/install-from-platform.js",
-        ) as typeof import("../lib/install-from-platform.js"),
+          "../lib/install-from-cloud.js",
+        ) as typeof import("../lib/install-from-cloud.js"),
     );
   },
   get installed() {
@@ -209,8 +209,8 @@ export function registerPluginsCommand(program: Command): void {
         ) => {
           try {
             const direct = looksLikeGitHubSpec(nameOrUrl);
-            // A plain marketplace install by name is platform-managed: the
-            // content flows through the platform install endpoint (which
+            // A plain marketplace install by name is cloud-managed: the
+            // content flows through the cloud install endpoint (which
             // serves a verified `.tgz`), not a GitHub clone. The advanced
             // pin/ref/allow-unreviewed selectors still resolve a specific
             // reviewed revision through the marketplace-git path, and a
@@ -236,7 +236,7 @@ export function registerPluginsCommand(program: Command): void {
               // self-hosted) there is no platform to call, so resolve the pin
               // from the bundled catalog and install through the GitHub path.
               const platformEnabled =
-                libs.catalogLocal.arePlatformFeaturesEnabled();
+                libs.catalogLocal.areCloudFeaturesEnabled();
               if (platformEnabled) {
                 if (!libs.catalogLocal.isPluginCatalogEntryVisible(nameOrUrl)) {
                   console.error(

package/src/cli/commands/roadmap.help.ts

@@ -14,7 +14,7 @@ Items, upvotes, and comments filed here are attributed to the assistant, not
 to its owner: the assistant signs these calls with its own platform API key.
 The owner's own roadmap identity lives on \`cadet roadmap\`.
 
-Reads work anonymously when the assistant is not connected to the platform
+Reads work anonymously when the assistant is not connected to the cloud
 (the "upvoted" marker is then blank). Every write needs the connection, so
 run \`assistant cloud connect\` first.
 

package/src/cli/commands/telemetry.help.ts

@@ -8,9 +8,9 @@ export const telemetryHelp: CliCommandHelp = {
   subcommands: [
     {
       name: "flush",
-      description: "Force-flush all pending telemetry events to the platform",
+      description: "Force-flush all pending telemetry events to the cloud",
       helpText: `
-Reports how many events reached the platform: 'sent' (POSTed), 'persisted'
+Reports how many events reached the cloud: 'sent' (POSTed), 'persisted'
 (confirmed written), and 'dropped' (sent - persisted — server-side drops plus
 events skipped at ingest validation). When nothing ships, prints why (e.g.
 nothing pending, opted out, not signed in).

package/src/cli/commands/telemetry.ts

@@ -15,7 +15,7 @@ function describeSkip(reason: string): string {
     case "opted-out":
       return "Telemetry flush skipped: analytics sharing is opted out.";
     case "no-credentials":
-      return "Telemetry flush skipped: not signed in to the platform yet.";
+      return "Telemetry flush skipped: not signed in to the cloud yet.";
     case "unknown-consent":
       return "Telemetry flush skipped: consent not yet resolved (will retry).";
     case "checkpoint-unavailable":
@@ -23,7 +23,7 @@ function describeSkip(reason: string): string {
     case "disabled":
       return "Telemetry flush skipped: telemetry is disabled.";
     case "post-failed":
-      return "Telemetry flush failed: the platform rejected the request.";
+      return "Telemetry flush failed: the cloud rejected the request.";
     default:
       return `Telemetry flush skipped: ${reason}`;
   }

package/src/cli/commands/tts.help.ts

@@ -92,7 +92,7 @@ Examples:
         {
           name: "[id...]",
           description:
-            "Voice/model id to set (joined with spaces). ElevenLabs voice id for elevenlabs; managed voice model id (ElevenLabs id or Deepgram Aura model like aura-2-thalia-en) for cadet; Aura model id for deepgram",
+            "Voice/model id to set (joined with spaces). ElevenLabs voice id for elevenlabs; cloud voice model id (ElevenLabs id or Deepgram Aura model like aura-2-thalia-en) for cadet; Aura model id for deepgram",
         },
       ],
       options: [
@@ -105,11 +105,11 @@ Examples:
       helpText: `
 Set the assistant's TTS voice on whichever provider is currently active
 (services.tts.provider). This writes to the config key that provider actually
-reads — e.g. services.tts.providers.cadet.model for managed speech — so the
+reads — e.g. services.tts.providers.cadet.model for cloud speech — so the
 change takes effect on the next spoken turn.
 
 Prefer this over 'assistant config set services.tts.providers.elevenlabs.voiceId'
-directly: on a managed (cadet) assistant that field is ignored, so the voice
+directly: on a cloud (cadet) assistant that field is ignored, so the voice
 would silently not change.
 
 Examples: