@mycadet/assistant 0.12.7 → 0.12.8

package/src/workspace/migrations/109-swap-quality-profile-to-glm-5p2.ts

@@ -4,26 +4,26 @@ import { join } from "node:path";
 import type { WorkspaceMigration } from "./types.js";
 
 // Bring an existing workspace's managed inference config in line with the
-// current code templates: the managed `quality-optimized` profile runs GLM 5.2
-// (Fireworks), and the default advisor points at the managed `frontier` (Opus)
+// current code templates: the cloud `quality-optimized` profile runs GLM 5.2
+// (Fireworks), and the default advisor points at the cloud `frontier` (Opus)
 // profile.
 //
-// A migration is needed even though the seeder reconciles managed-profile
+// A migration is needed even though the seeder reconciles cloud-profile
 // content from the templates on every boot, because the seeder only consults a
 // template when it reseeds that profile. Off-platform installs reseed every
-// boot, but a platform workspace keeps the profile it was hatched with (the
+// boot, but a cloud workspace keeps the profile it was hatched with (the
 // seeder skips overlay-supplied profiles, and the overlay is consumed once). A
 // platform workspace whose `quality-optimized` profile resolves to Opus
 // therefore relies on this migration to move it to GLM 5.2.
 //
-// Scope: only the managed `quality-optimized` profile is rewritten — the
+// Scope: only the cloud `quality-optimized` profile is rewritten — the
 // user-owned `custom-quality-optimized` copy is theirs to manage, and an
 // explicitly user-owned `quality-optimized` is left alone. A profile matches
 // only when its model is an Opus id (the OpenRouter-prefixed id included);
 // absent `source` on this canonical name means legacy managed (migration 052
 // seeds it source-less), so it counts as ours.
 //
-// The managed `frontier` profile is materialized by the boot seeder (it is a
+// The cloud `frontier` profile is materialized by the boot seeder (it is a
 // managed template), so this migration only points the default advisor at it,
 // and only when the workspace still carries the seeded `quality-optimized`
 // default and no user-owned `frontier` profile exists.
@@ -38,7 +38,7 @@ const GLM_52_MODEL = "accounts/fireworks/models/glm-5p2";
 export const swapQualityProfileToGlm52Migration: WorkspaceMigration = {
   id: "109-swap-quality-profile-to-glm-5p2",
   description:
-    "Set the managed quality-optimized profile to GLM 5.2 and point the default advisor at frontier",
+    "Set the cloud quality-optimized profile to GLM 5.2 and point the default advisor at frontier",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {
@@ -66,7 +66,7 @@ export const swapQualityProfileToGlm52Migration: WorkspaceMigration = {
     const profiles = readObject(llm.profiles);
     if (profiles !== null) {
       const profile = readObject(profiles["quality-optimized"]);
-      // Only the managed profile is ours to migrate. `quality-optimized` is a
+      // Only the cloud profile is ours to migrate. `quality-optimized` is a
       // canonical name reserved since migration 052, which seeded it source-less,
       // so absent `source` means legacy managed — treat it as ours. Only an
       // explicit `source: "user"` (a profile the user took ownership of) is left
@@ -90,15 +90,15 @@ export const swapQualityProfileToGlm52Migration: WorkspaceMigration = {
       }
     }
 
-    // Move the default advisor pointer to the new strongest managed profile.
+    // Move the default advisor pointer to the new strongest cloud profile.
     // Only the seeded default (`quality-optimized`) is rewritten; a workspace
     // that picked its own advisor profile keeps it. Skip the rewrite when a
     // user already owns a profile named `frontier`: the seeder leaves that
-    // user profile in place rather than materializing the managed Opus one, so
+    // user profile in place rather than materializing the cloud Opus one, so
     // pointing the advisor at it would consult an arbitrary user model. Leaving
     // the advisor on `quality-optimized` (now managed GLM 5.2) is the safe
     // fallback in that collision case. Any `frontier` present at migration time
-    // is user-owned (the managed one is materialized later, at seed time);
+    // is user-owned (the cloud one is materialized later, at seed time);
     // treat anything not explicitly `source: "managed"` as theirs, since the
     // settings UI saves custom profiles without a `source`.
     const existingFrontier = readObject(profiles?.frontier);

package/src/workspace/migrations/110-flip-balanced-profile-to-together.ts

@@ -3,18 +3,18 @@ import { join } from "node:path";
 
 import type { WorkspaceMigration } from "./types.js";
 
-// Move the managed `balanced` profile from Fireworks MiniMax M3 to Together AI.
+// Move the cloud `balanced` profile from Fireworks MiniMax M3 to Together AI.
 //
 // Together serves MiniMax M3 with correct forced-`tool_choice` and object-typed
 // tool-arg handling; the Fireworks copy collapses object args to `{}`. The boot
-// seeder reconciles managed-profile content from the templates, but only when
-// it reseeds a profile: off-platform installs reseed every boot, while a
+// seeder reconciles cloud-profile content from the templates, but only when
+// it reseeds a profile: off-cloud installs reseed every boot, while a
 // platform workspace keeps the profile it was hatched with (the seeder skips
 // overlay-supplied profiles, and the overlay is consumed once). A platform
 // workspace whose `balanced` profile still resolves to Fireworks MiniMax M3
 // therefore relies on this migration to move it to Together.
 //
-// Scope: only the managed `balanced` profile still on the Fireworks MiniMax M3
+// Scope: only the cloud `balanced` profile still on the Fireworks MiniMax M3
 // default is rewritten. A user-owned `balanced` (`source: "user"`) or one whose
 // model the user changed is left alone. Migration 052 seeds `balanced`
 // source-less, so absent `source` means legacy managed — treat it as ours. The
@@ -27,7 +27,7 @@ const NEW_MODEL = "MiniMaxAI/MiniMax-M3";
 export const flipBalancedProfileToTogetherMigration: WorkspaceMigration = {
   id: "110-flip-balanced-profile-to-together",
   description:
-    "Move the managed balanced profile from Fireworks to Together AI (MiniMax M3)",
+    "Move the cloud balanced profile from Fireworks to Together AI (MiniMax M3)",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {
@@ -56,7 +56,7 @@ export const flipBalancedProfileToTogetherMigration: WorkspaceMigration = {
     }
 
     const profile = readObject(profiles["balanced"]);
-    // Only the managed profile still on the Fireworks MiniMax M3 default is
+    // Only the cloud profile still on the Fireworks MiniMax M3 default is
     // ours to migrate. `balanced` is seeded source-less by migration 052, so
     // absent `source` means legacy managed; only an explicit `source: "user"`
     // is left untouched. Matching on the old model id leaves a user-retargeted

package/src/workspace/migrations/113-swap-balanced-profile-to-glm-5p2.ts

@@ -5,18 +5,18 @@ import type { WorkspaceMigration } from "./types.js";
 
 // Bring an existing workspace's managed `balanced` profile in line with the
 // current code template: it now runs GLM 5.2 (Fireworks) at effort `high`,
-// taking over the model the managed `quality-optimized` profile used to serve.
+// taking over the model the cloud `quality-optimized` profile used to serve.
 // The slot keeps its own `label` and `description`.
 //
-// A migration is needed even though the seeder reconciles managed-profile
+// A migration is needed even though the seeder reconciles cloud-profile
 // content from the templates on every boot, because the seeder only consults a
 // template when it reseeds that profile. Off-platform installs reseed every
-// boot, but a platform workspace keeps the profile it was hatched with (the
+// boot, but a cloud workspace keeps the profile it was hatched with (the
 // seeder skips overlay-supplied profiles, and the overlay is consumed once). A
 // platform workspace whose `balanced` profile still resolves to Together
 // MiniMax M3 therefore relies on this migration to move it to GLM 5.2.
 //
-// Scope: only the managed `balanced` profile is rewritten. `balanced` is a
+// Scope: only the cloud `balanced` profile is rewritten. `balanced` is a
 // canonical name reserved since migration 052, which seeded it source-less, so
 // absent `source` means legacy managed — treat it as ours. An explicit
 // `source: "user"` (a profile the user took ownership of) or one whose model the
@@ -43,7 +43,7 @@ const SEEDED_TOP_P = 0.95;
 
 export const swapBalancedProfileToGlm52Migration: WorkspaceMigration = {
   id: "113-swap-balanced-profile-to-glm-5p2",
-  description: "Set the managed balanced profile to GLM 5.2 (Fireworks)",
+  description: "Set the cloud balanced profile to GLM 5.2 (Fireworks)",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {

package/src/workspace/migrations/114-swap-quality-profile-to-opus.ts

@@ -9,15 +9,15 @@ import type { WorkspaceMigration } from "./types.js";
 // managed `balanced` profile takes over the GLM 5.2 model `quality-optimized`
 // used to serve (migration 113).
 //
-// A migration is needed even though the seeder reconciles managed-profile
+// A migration is needed even though the seeder reconciles cloud-profile
 // content from the templates on every boot, because the seeder only consults a
 // template when it reseeds that profile. Off-platform installs reseed every
-// boot, but a platform workspace keeps the profile it was hatched with (the
+// boot, but a cloud workspace keeps the profile it was hatched with (the
 // seeder skips overlay-supplied profiles, and the overlay is consumed once). A
 // platform workspace whose `quality-optimized` profile resolves to GLM 5.2
 // therefore relies on this migration to move it to Opus.
 //
-// Scope: only the managed `quality-optimized` profile still on the GLM 5.2
+// Scope: only the cloud `quality-optimized` profile still on the GLM 5.2
 // default is rewritten. `quality-optimized` is a canonical name reserved since
 // migration 052, which seeded it source-less, so absent `source` means legacy
 // managed — treat it as ours. An explicit `source: "user"` (a profile the user
@@ -32,7 +32,7 @@ const NEW_MODEL = "claude-opus-4-8";
 export const swapQualityProfileToOpusMigration: WorkspaceMigration = {
   id: "114-swap-quality-profile-to-opus",
   description:
-    "Set the managed quality-optimized profile to Anthropic Opus (matching frontier)",
+    "Set the cloud quality-optimized profile to Anthropic Opus (matching frontier)",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {

package/src/workspace/migrations/115-drop-frontier-profile.ts

@@ -3,11 +3,11 @@ import { join } from "node:path";
 
 import type { WorkspaceMigration } from "./types.js";
 
-// Reclaim the managed `frontier` inference profile. It ran Anthropic Opus on
-// `anthropic-managed` — the same model and config as the managed
+// Reclaim the cloud `frontier` inference profile. It ran Anthropic Opus on
+// `anthropic-managed` — the same model and config as the cloud
 // `quality-optimized` profile, which the seeder reconciles from the templates
 // on every boot. The seeder never deletes a profile, so this migration deletes
-// the managed `frontier` object and repoints every reference to it — its
+// the cloud `frontier` object and repoints every reference to it — its
 // `profileOrder` entry, the `activeProfile` and `advisorProfile` selections,
 // call-site `profile` overrides, and mix-profile arms — onto `quality-optimized`,
 // which resolves to the same Opus route. A `frontier` profile that the user owns
@@ -19,7 +19,7 @@ const REPLACEMENT = "quality-optimized";
 export const dropFrontierProfileMigration: WorkspaceMigration = {
   id: "115-drop-frontier-profile",
   description:
-    "Remove the managed Frontier profile and repoint its references to Quality",
+    "Remove the cloud Frontier profile and repoint its references to Quality",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {
@@ -46,7 +46,7 @@ export const dropFrontierProfileMigration: WorkspaceMigration = {
     const frontier = profiles !== null ? readObject(profiles[FRONTIER]) : null;
 
     // A user-owned profile that happens to use this name keeps everything,
-    // references included — only the managed profile is reclaimed.
+    // references included — only the cloud profile is reclaimed.
     if (frontier !== null && frontier.source !== "managed") {
       return;
     }

package/src/workspace/migrations/123-swap-quality-profile-to-fable.ts

@@ -3,17 +3,17 @@ import { join } from "node:path";
 
 import type { WorkspaceMigration } from "./types.js";
 
-// Move the managed quality-optimized profile from Anthropic Opus 4.8 back to
+// Move the cloud quality-optimized profile from Anthropic Opus 4.8 back to
 // Claude Fable 5, reversing migration 114.
 //
 // The quality-optimized intent maps to claude-fable-5, but the intent map is
-// only consulted when a profile is seeded: off-platform installs reseed managed
-// profiles on every boot, while on-platform workspaces keep the profile they
+// only consulted when a profile is seeded: off-cloud installs reseed managed
+// profiles on every boot, while on-cloud workspaces keep the profile they
 // were hatched with — the seeder skips existing profiles there, and the hatch
 // overlay is consumed exactly once. A platform workspace holding an Opus 4.8
 // quality-optimized profile therefore keeps it until a migration rewrites it.
 //
-// Only the managed quality-optimized profile is touched — the user-owned
+// Only the cloud quality-optimized profile is touched — the user-owned
 // custom-quality-optimized copy is theirs to manage. Within it, only a profile
 // still on the Opus default is rewritten — matching by model value also covers
 // the OpenRouter-prefixed id. A profile whose model the user changed to
@@ -30,7 +30,7 @@ const MODEL_SWAPS: Record<string, string> = {
 export const swapQualityProfileToFableMigration: WorkspaceMigration = {
   id: "123-swap-quality-profile-to-fable",
   description:
-    "Move the managed quality-optimized profile from Anthropic Opus 4.8 to Claude Fable 5",
+    "Move the cloud quality-optimized profile from Anthropic Opus 4.8 to Claude Fable 5",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {

package/src/workspace/migrations/125-repoint-managed-connections-to-cadet.ts

@@ -7,10 +7,10 @@ import type { WorkspaceMigration } from "./types.js";
 // `*-managed` connection onto the single provider-agnostic `cadet`
 // connection.
 //
-// The five managed connections (anthropic/openai/gemini/fireworks/together)
+// The five cloud connections (anthropic/openai/gemini/fireworks/together)
 // are collapsed into one `cadet` row and are no longer seeded (a follow-up
 // migration deletes the orphaned rows), so any config still pointing at them
-// would fail to resolve. Managed profiles also self-heal via the boot-time
+// would fail to resolve. Cloud profiles also self-heal via the boot-time
 // template reconcile, but `llm.default`, per-call-site overrides, and
 // user-owned copies are rewritten here.
 //
@@ -31,7 +31,7 @@ const CADET_CONNECTION = "cadet";
 export const repointManagedConnectionsToCadetMigration: WorkspaceMigration = {
   id: "125-repoint-managed-connections-to-cadet",
   description:
-    "Repoint provider_connection from the per-provider *-managed connections to the single cadet connection",
+    "Repoint provider_connection from the per-provider *-cloud connections to the single cadet connection",
   run(workspaceDir: string): void {
     const configPath = join(workspaceDir, "config.json");
     if (!existsSync(configPath)) {

package/src/workspace/migrations/126-strip-managed-profile-bodies.ts

@@ -9,7 +9,7 @@ import type { WorkspaceMigration } from "./types.js";
 // into workspace config, so this migration strips the previously seeded
 // managed entries down to thin stubs holding only the workspace-owned
 // overlay fields (`source`, plus `label`/`status`/`topP` by key-presence —
-// the exact whitelist the effective view reads off a managed-source entry).
+// the exact whitelist the effective view reads off a cloud-source entry).
 //
 // A same-named entry the user explicitly owns (a non-managed `source` tag)
 // is left fully intact — user profiles shadow the code defaults by design.
@@ -29,7 +29,7 @@ const DEFAULT_PROFILE_NAMES = [
 
 const WORKSPACE_OWNED_FIELDS = ["label", "status", "topP"];
 
-export const stripManagedProfileBodiesMigration: WorkspaceMigration = {
+export const stripCloudProfileBodiesMigration: WorkspaceMigration = {
   id: "126-strip-managed-profile-bodies",
   description:
     "Strip seeded managed default-profile bodies down to thin workspace-owned stubs (content is code-owned)",

package/src/workspace/migrations/127-backfill-default-provider.ts

@@ -5,7 +5,7 @@ import type { WorkspaceMigration } from "./types.js";
 
 // Backfill `llm.defaultProvider` for installs that never ran the hatch flow
 // (which sets it directly) from deterministic, synchronously-readable
-// signals: `IS_PLATFORM`, a legacy `llm.default.provider`, or a personal
+// signals: `IS_CLOUD`, a legacy `llm.default.provider`, or a personal
 // `custom-*` profile's provider.
 //
 // Platform installs resolve to "cadet" before the legacy field is
@@ -16,7 +16,7 @@ import type { WorkspaceMigration } from "./types.js";
 // value). This mirrors the hatch precedence, where platform outranks the
 // BYOK provider signal.
 //
-// The same schema-default echo affects the off-platform legacy read:
+// The same schema-default echo affects the off-cloud legacy read:
 // `LLMConfigBase.provider` defaults to "anthropic" and the first-launch
 // seed persists it, so a bare "anthropic" is ambiguous. Disambiguating it
 // requires an async vault read that this sync migration cannot perform, so
@@ -115,10 +115,10 @@ function isValidDefaultProvider(value: unknown): boolean {
   );
 }
 
-// Frozen copy of config/env-registry.ts's IS_PLATFORM read — migration
+// Frozen copy of config/env-registry.ts's IS_CLOUD read — migration
 // modules must not import from config modules (workspace/migrations/AGENTS.md).
 function isPlatform(): boolean {
-  return process.env.IS_PLATFORM === "true" || process.env.IS_PLATFORM === "1";
+  return process.env.IS_CLOUD === "true" || process.env.IS_CLOUD === "1";
 }
 
 function resolveProviderSignal(

package/src/workspace/migrations/130-speech-mode-to-provider.ts

@@ -6,11 +6,11 @@ import type { WorkspaceMigration } from "./types.js";
 /**
  * Fold `services.stt.mode` / `services.tts.mode` into the provider field.
  *
- * Managed speech used to be a second axis: `mode: "managed"` routed to Cadet
+ * Cloud speech used to be a second axis: `mode: "managed"` routed to Cadet
  * while `provider` held the untouched BYOK choice. Provider is now the only
- * axis, with `"cadet"` meaning managed, so a managed service must be rewritten
+ * axis, with `"cadet"` meaning managed, so a cloud service must be rewritten
  * to `provider: "cadet"` before the new schema reads it — otherwise the
- * lingering BYOK provider would be taken at face value and a managed user would
+ * lingering BYOK provider would be taken at face value and a cloud user would
  * silently fall back to a provider they have no key for.
  *
  * Idempotent: a config with no `mode` key is left untouched.
@@ -88,7 +88,7 @@ export const speechModeToProviderMigration: WorkspaceMigration = {
         continue;
       }
 
-      // What a managed service had chosen for BYOK before is not
+      // What a cloud service had chosen for BYOK before is not
       // recoverable — it was overwritten on the way up.
       service.mode = service.provider === "cadet" ? "managed" : "your-own";
       changed = true;

package/src/workspace/migrations/131-drop-web-fetch-mode.ts

@@ -5,7 +5,7 @@ import type { WorkspaceMigration } from "./types.js";
 
 /**
  * Strip the now-removed `services.web-fetch.mode` field from existing
- * `config.json` files. Web fetch has no managed proxy, so the field never
+ * `config.json` files. Web fetch has no cloud proxy, so the field never
  * governed anything — provider is the only axis — and the schema no longer
  * recognizes it.
  *

package/src/workspace/migrations/132-web-search-mode-to-provider.ts

@@ -9,15 +9,15 @@ import type { WorkspaceMigration } from "./types.js";
  * Configs written by older versions carry two axes: `mode: "managed"` routes
  * search through the Cadet Cloud proxy while `provider` holds an
  * untouched BYOK choice. The schema treats `provider` as the only axis, with
- * `"cadet"` meaning managed, so this migration rewrites a managed service to
+ * `"cadet"` meaning managed, so this migration rewrites a cloud service to
  * `provider: "cadet"` — otherwise the lingering BYOK provider would be taken
- * at face value and a managed user would silently land on a provider they
+ * at face value and a cloud user would silently land on a provider they
  * hold no key for.
  *
  * `inference-provider-native` is the exception: it is a distinct user-facing
- * option (the inference model runs its own hosted search), so a managed
+ * option (the inference model runs its own hosted search), so a cloud
  * service on that provider keeps it verbatim rather than becoming `cadet`.
- * Its managed fallback (platform proxy when the model has no native search
+ * Its cloud fallback (cloud proxy when the model has no native search
  * and no user key exists) works without a `mode`.
  *
  * Idempotent: a config with no `mode` key is left untouched.
@@ -91,8 +91,8 @@ export const webSearchModeToProviderMigration: WorkspaceMigration = {
     }
 
     // Schemas that predate this migration accept provider "cadet" alongside
-    // mode "managed", so the managed pair round-trips exactly. The BYOK
-    // provider a managed service holds before `run()` is not recoverable —
+    // mode "managed", so the cloud pair round-trips exactly. The BYOK
+    // provider a cloud service holds before `run()` is not recoverable —
     // `run()` overwrites it. Likewise `inference-provider-native` rolls back
     // to `your-own`: dropping `mode` erases any pairing with `managed`.
     service.mode = service.provider === "cadet" ? "managed" : "your-own";

package/src/workspace/migrations/133-collapse-provider-connections.ts

@@ -11,7 +11,7 @@ const log = getLogger("migrations/133-collapse-provider-connections");
 //
 // - `provider_connection: "cadet"` entries become `provider: "cadet"` (the
 //   routing identity) and lose the connection field — dispatch derives the
-//   managed upstream from the model.
+//   cloud upstream from the model.
 // - `provider_connection: "chatgpt-subscription"` entries become
 //   `provider: "chatgpt"` when their model is a Codex subscription model.
 // - The conventional `<provider>-personal` reference is dropped: the
@@ -178,7 +178,7 @@ export const collapseProviderConnectionsMigration: WorkspaceMigration = {
     // the field is stripped on read, so any raw value is dead weight the
     // resolver has never honored. It is deleted verbatim, never used as a
     // rewrite signal: flipping a call site's provider from a schema-dead
-    // "cadet" string would move a BYOK call site onto the managed route.
+    // "cadet" string would move a BYOK call site onto the cloud route.
     const callSites = readObject(llm.callSites);
     if (callSites !== null) {
       for (const key of Object.keys(callSites)) {
@@ -309,7 +309,7 @@ function rewriteEntry(entry: Record<string, unknown>, label: string): boolean {
  * Decode an encoded `<managed-provider>/<model>` routing string to its native
  * model id, or null when the value is not an encoded id for a known managed
  * model. Fireworks/together native ids contain slashes but their prefixes
- * ("accounts", "MiniMaxAI") are not managed provider names, so they pass
+ * ("accounts", "MiniMaxAI") are not cloud provider names, so they pass
  * through untouched.
  */
 function decodeRoutedModel(value: unknown): string | null {

package/src/workspace/migrations/134-image-generation-mode-to-provider.ts

@@ -11,10 +11,10 @@ import type { WorkspaceMigration } from "./types.js";
  * names the backend the proxy fronts (gemini or openai). The schema treats
  * `provider` as the only axis, with `"cadet"` meaning managed and the
  * backend derived from the selected model's prefix at request time, so this
- * migration rewrites every managed service to `provider: "cadet"`. There is
+ * migration rewrites every cloud service to `provider: "cadet"`. There is
  * no per-provider exemption: the stored backend value under managed mode is
  * itself derived from the model on every model write, so replacing it loses
- * nothing — `model` is preserved verbatim and keeps routing the managed
+ * nothing — `model` is preserved verbatim and keeps routing the cloud
  * request to the same backend.
  *
  * Idempotent: a config with no `mode` key is left untouched.
@@ -97,8 +97,8 @@ export const imageGenerationModeToProviderMigration: WorkspaceMigration = {
     }
 
     // Schemas that predate this migration accept provider "cadet" alongside
-    // mode "managed", so the managed pair round-trips exactly. The backend
-    // provider a managed service holds before `run()` is not recoverable —
+    // mode "managed", so the cloud pair round-trips exactly. The backend
+    // provider a cloud service holds before `run()` is not recoverable —
     // `run()` overwrites it with "cadet". That value is derived from the
     // model prefix, so it re-derives on the next model write.
     service.mode = service.provider === "cadet" ? "managed" : "your-own";

package/src/workspace/migrations/136-repair-stale-fireworks-kimi-model-id.ts

@@ -17,9 +17,9 @@ import type { WorkspaceMigration } from "./types.js";
  * Fireworks latency-intent model.
  *
  * Provider guard: the stale ID belongs to the `fireworks` provider and
- * also appears in managed profiles stamped
+ * also appears in cloud profiles stamped
  * `provider: "cadet"` (which route Fireworks-account model IDs through
- * the managed proxy). A fragment is repaired when its `provider` is
+ * the cloud proxy). A fragment is repaired when its `provider` is
  * `"fireworks"`, `"cadet"`, or absent; an explicit other provider (e.g.
  * an `openai-compatible` endpoint serving a model by the same name) is
  * left untouched.

package/src/workspace/migrations/137-repair-retired-fireworks-minimax-model-id.ts

@@ -21,8 +21,8 @@ import type { WorkspaceMigration } from "./types.js";
  * would make it read as unedited to `ensureByokDefaultProfiles`.
  *
  * Provider guard: the retired ID belongs to the `fireworks` provider and
- * also appears in managed profiles stamped `provider: "cadet"` (which
- * route Fireworks-account model IDs through the managed proxy). A fragment
+ * also appears in cloud profiles stamped `provider: "cadet"` (which
+ * route Fireworks-account model IDs through the cloud proxy). A fragment
  * is repaired when its `provider` is `"fireworks"`, `"cadet"`, or absent;
  * an explicit other provider (e.g. an `openai-compatible` endpoint serving
  * a model by the same name) is left untouched.

package/src/workspace/migrations/139-clear-renamed-cost-profile-label.ts

@@ -7,7 +7,7 @@ import type { WorkspaceMigration } from "./types.js";
  * Clear the machinery-written `"Speed"` label off the `cost-optimized`
  * profile so the code catalog's new label ("Cost") reaches existing installs.
  *
- * `label` is workspace-owned overlay state: a managed-source entry's label
+ * `label` is workspace-owned overlay state: a cloud-source entry's label
  * wins over the code default (`WORKSPACE_OWNED_DEFAULT_FIELDS` in
  * `config/default-profile-catalog.ts`). Migration 082 and the pre-catalog
  * seeder both wrote `"Speed"` onto `cost-optimized`, and migration 126
@@ -67,7 +67,7 @@ export const clearRenamedCostProfileLabelMigration: WorkspaceMigration = {
     if (entry === null) {
       return;
     }
-    // Only a managed-source entry carries a machinery-written label. Anything
+    // Only a cloud-source entry carries a machinery-written label. Anything
     // else, a source-less legacy entry included, shadows the default outright
     // (see `getEffectiveProfile`), so its label is the user's.
     if (entry.source !== "managed") {

package/src/workspace/migrations/141-stt-english-default-to-multilingual.ts

@@ -5,7 +5,7 @@ import type { WorkspaceMigration } from "./types.js";
 
 /**
  * Put existing assistants on code-switching by writing
- * `services.stt.language: "multi"` on Deepgram and the managed relay,
+ * `services.stt.language: "multi"` on Deepgram and the cloud relay,
  * covering both an accepted English default and a language that was never
  * set at all.
  *
@@ -14,7 +14,7 @@ import type { WorkspaceMigration } from "./types.js";
  * exist before the language picker shipped (#39546, released 2026-07-31), and
  * on these two providers that picker never offered English and Multilingual
  * as peers. The only English row was the default row, labelled "English
- * (default)". So an `"en"` on Deepgram or the managed relay records "I
+ * (default)". So an `"en"` on Deepgram or the cloud relay records "I
  * accepted the default", not "I want English rather than code-switching", and
  * the default it accepted has since changed.
  *
@@ -22,7 +22,7 @@ import type { WorkspaceMigration } from "./types.js";
  *
  *   - Only `"en"` and absent. Any other language is a real choice from a list
  *     where it was the only way to get that language.
- *   - Only Deepgram and the managed relay (`mode: "managed"` routes there
+ *   - Only Deepgram and the cloud relay (`mode: "managed"` routes there
  *     while `provider` holds the bring-your-own restore value). xAI has
  *     offered an explicit English row since the picker shipped, so an `"en"`
  *     there is deliberate, and code-switching is a Deepgram mode its adapter
@@ -38,7 +38,7 @@ const MULTI_DEFAULT_PROVIDERS = new Set(["deepgram", "cadet"]);
 export const sttEnglishDefaultToMultilingualMigration: WorkspaceMigration = {
   id: "141-stt-english-default-to-multilingual",
   description:
-    "Move services.stt.language from the accepted English default to multilingual on Deepgram and managed speech",
+    "Move services.stt.language from the accepted English default to multilingual on Deepgram and cloud speech",
   run(workspaceDir: string): void {
     if (process.env.CADET_DEFAULT_WORKSPACE_CONFIG_PATH) {
       return;

package/src/workspace/migrations/144-convert-stranded-subscription-openai-profiles.ts

@@ -34,7 +34,7 @@ const log = getLogger("migration-144");
  * `llm.defaultProvider` of "openai" converts the same way: it anchors the
  * code-owned default profiles and background call sites, which are equally
  * stranded. Fragments with a `provider_connection` pin, a pinned
- * defaultProvider connectionName, any other provider, or a managed source
+ * defaultProvider connectionName, any other provider, or a cloud source
  * are left untouched. `llm.default` is not swept: migration 133 drops that
  * legacy blob and runs earlier in the chain.
  */

package/src/workspace/migrations/145-collapse-profile-bindings-to-entries.ts

@@ -42,7 +42,7 @@ const log = getLogger("migrations/145-collapse-profile-bindings-to-entries");
 // conservative keep-provider path.
 
 const ROUTING_IDENTITIES = new Set(["cadet", "chatgpt"]);
-const MANAGED_ROUTABLE = new Set([
+const CLOUD_ROUTABLE = new Set([
   "openai",
   "anthropic",
   "gemini",
@@ -294,7 +294,7 @@ function kindAgrees(rowKind: string, provider: string | undefined): boolean {
     return provider === "openai";
   }
   if (rowKind === "cadet") {
-    return MANAGED_ROUTABLE.has(provider);
+    return CLOUD_ROUTABLE.has(provider);
   }
   return false;
 }

package/src/workspace/migrations/146-repair-retired-fireworks-deepseek-flash-model-id.ts

@@ -19,8 +19,8 @@ import type { WorkspaceMigration } from "./types.js";
  * dated ID.
  *
  * Provider guard: the stale ID belongs to the `fireworks` provider and also
- * appears in managed profiles stamped `provider: "cadet"` (which route
- * Fireworks-account model IDs through the managed proxy). Under the entries
+ * appears in cloud profiles stamped `provider: "cadet"` (which route
+ * Fireworks-account model IDs through the cloud proxy). Under the entries
  * model (migration 145) `provider` can also hold a `provider_connections`
  * entry name whose row kind drives dispatch. A fragment is repaired when
  * its `provider` is `"fireworks"`, `"cadet"`, absent, or an entry name

package/src/workspace/migrations/148-strip-unsupported-fallback-profiles.ts

@@ -4,7 +4,7 @@
  * Automatic model fallbacks are code-owned metadata on the four managed
  * default profiles. Earlier builds accepted custom `fallbackProfile` values
  * in raw workspace config, including pointers rewritten by migration 147.
- * Those values cannot be executed under the managed-only fallback contract
+ * Those values cannot be executed under the cloud-only fallback contract
  * and would make later config writes fail validation.
  *
  * This migration removes every persisted pointer except the exact managed
@@ -35,7 +35,7 @@ const CODE_OWNED_FALLBACKS: Record<string, string> = {
 export const stripUnsupportedFallbackProfilesMigration: WorkspaceMigration = {
   id: "148-strip-unsupported-fallback-profiles",
   description:
-    "Remove custom fallback profile pointers outside the managed default contract",
+    "Remove custom fallback profile pointers outside the cloud default contract",
   // A transient config write failure must not leave an unsupported pointer
   // behind permanently; the next boot can safely repeat this idempotent pass.
   retryFailedCheckpoint: true,

package/src/workspace/migrations/150-stt-flux-provider-to-model-family.ts

@@ -16,7 +16,7 @@ import type { WorkspaceMigration } from "./types.js";
  *   provider: "deepgram-flux"  ->  provider: "deepgram"
  *                                  providers.deepgram.model: "flux"
  *
- * The same rewrite applies to the managed pair. Any other provider value is
+ * The same rewrite applies to the cloud pair. Any other provider value is
  * left untouched, and an existing `providers.<parent>` entry keeps every key
  * it already had.
  *

package/src/workspace/migrations/151-repair-renamed-fireworks-deepseek-pro-model-id.ts

@@ -19,8 +19,8 @@ import type { WorkspaceMigration } from "./types.js";
  * dated ID.
  *
  * Provider guard: the stale ID belongs to the `fireworks` provider and also
- * appears in managed profiles stamped `provider: "cadet"` (which route
- * Fireworks-account model IDs through the managed proxy). Under the entries
+ * appears in cloud profiles stamped `provider: "cadet"` (which route
+ * Fireworks-account model IDs through the cloud proxy). Under the entries
  * model (migration 145) `provider` can also hold a `provider_connections`
  * entry name whose row kind drives dispatch. A fragment is repaired when
  * its `provider` is `"fireworks"`, `"cadet"`, absent, or an entry name

package/src/workspace/migrations/152-repair-retired-fireworks-minimax-m2p7-model-id.ts

@@ -23,8 +23,8 @@ import type { WorkspaceMigration } from "./types.js";
  * to the same model this migration writes.
  *
  * Provider guard: the stale ID belongs to the `fireworks` provider and also
- * appears in managed profiles stamped `provider: "cadet"` (which route
- * Fireworks-account model IDs through the managed proxy). Under the entries
+ * appears in cloud profiles stamped `provider: "cadet"` (which route
+ * Fireworks-account model IDs through the cloud proxy). Under the entries
  * model (migration 145) `provider` can also hold a `provider_connections`
  * entry name whose row kind drives dispatch. A fragment is repaired when
  * its `provider` is `"fireworks"`, `"cadet"`, absent, or an entry name