@mycadet/assistant 0.12.7 → 0.12.8

package/README.md

@@ -181,7 +181,7 @@ Internal forwarding routes (`/v1/internal/twilio/*`) are unaffected — these ac
 The `/channels/inbound` endpoint requires a JWT with the `svc_gateway` principal type and `ingress.write` scope to prove the request originated from the gateway. This ensures channel messages can only arrive via the gateway (which performs webhook-level verification) and not via direct HTTP calls that bypass signature checks.
 
 - **JWT-based enforcement:** The route policy in `route-policy.ts` restricts `/channels/inbound` to the `svc_gateway` principal type with `ingress.write` scope. Actor and local principals are rejected with 403.
-- **Auth bypass:** When `DISABLE_HTTP_AUTH=true` is set (platform-managed deployments), a request that supplies no `Authorization` header gets a synthetic context. A request that supplies one is verified normally, and a token that fails verification is rejected.
+- **Auth bypass:** When `DISABLE_HTTP_AUTH=true` is set (cloud-managed deployments), a request that supplies no `Authorization` header gets a synthetic context. A request that supplies one is verified normally, and a token that fails verification is rejected.
 
 ## Twilio Setup Primitive
 

package/docs/activation-funnel-telemetry.md

@@ -56,7 +56,7 @@ Flow, end to end:
      `assistant/src/telemetry/activation-funnel.ts`;
    - emission is best-effort (wrapped in try/catch) and never blocks or alters
      the surface-action flow;
-   - `recordActivationEvent` respects the platform `share_analytics` consent gate
+   - `recordActivationEvent` respects the cloud `share_analytics` consent gate
      via `getRawShareAnalytics()`: only a confirmed opt-out (`false`) drops the
      event; an `"unknown"` state (cold cache, no platform session) records and
      lets the flush/ingest gates enforce consent before anything ships.
@@ -101,7 +101,7 @@ All five steps are recorded deterministically on surface commit. The north star
 a materialized activation event (see §1).
 
 On the wire, each onboarding event also sets `screen = step_name` (to satisfy
-the platform's legacy-path validation), and `completed_at` is the ISO-8601
+the cloud's legacy-path validation), and `completed_at` is the ISO-8601
 record time.
 
 ---
@@ -189,7 +189,7 @@ whether those rows reach BigQuery (flush gate, dev-disabled).
    (it reads `getRawShareAnalytics()`); an `"unknown"` state records, but the
    flush defers until consent resolves. So for rows to actually SHIP, the dev
    session must be signed in to
-   the platform with `share_analytics` consent enabled, or no rows reach
+   the cloud with `share_analytics` consent enabled, or no rows reach
    SQLite. The consent cache is refreshed by `startConsentRefresh()` in
    `assistant/src/daemon/lifecycle.ts`, which runs **regardless of dev mode** — so
    a dev session signed in with `share_analytics` consent enabled writes
@@ -242,7 +242,7 @@ A successful flush POSTs the unreported onboarding rows to
 
 ### 5.6 Verify in BigQuery
 
-Wait for the platform → GCS NDJSON → BigQuery pipeline to land the events, then
+Wait for the cloud → GCS NDJSON → BigQuery pipeline to land the events, then
 run the query in §6.
 
 ---
@@ -292,7 +292,7 @@ collapses it earliest-wins).
 > `session_id` is the rail conversation's id. The **north star** ("≥5 user
 > messages within 24h per LD variant") is **not** a funnel event — compute it
 > downstream by joining the existing `turn` telemetry events (`turn_index` per
-> conversation) to the platform's `flag_assignment_raw` cohort-assignment table.
+> conversation) to the cloud's `flag_assignment_raw` cohort-assignment table.
 > **Dedup contract:** each row's `daemon_event_id` is deterministic,
 > `${funnel_version}:${session_id}:${step_name}`, keyed on the row's stored
 > `funnel_version`; the existing dbt earliest-wins dedup on `daemon_event_id`
@@ -314,7 +314,7 @@ collapses it earliest-wins).
   emission to a genuine user action, resolving the naming-check open
   interpretation.
 - **Stream B (multivariate cohort flag conversion) is NOT in this work.** It is
-  gated on the platform team's in-flight string-flag serving — until the platform
+  gated on the cloud team's in-flight string-flag serving — until the cloud
   can serve string/multivariate flags, flipping
   `experiment-activation-flow-2026-06-03` boolean→multivariate client-side would
   silently disable the live allowlisted rail. Until then, `ab_variant` is the

package/docs/cadet-doctor.md

@@ -1,8 +1,8 @@
 # Cadet Doctor
 
-Cadet Doctor is a platform-hosted diagnostic tool for investigating problems with a Cadet assistant.
+Cadet Doctor is a cloud-hosted diagnostic tool for investigating problems with a Cadet assistant.
 
-> **Status:** Beta. Cadet Doctor is available in the web client for platform-hosted assistants; it is not available for self-hosted assistants.
+> **Status:** Beta. Cadet Doctor is available in the web client for cloud-hosted assistants; it is not available for self-hosted assistants.
 
 ## What it does
 
@@ -79,7 +79,7 @@ A persisted session includes:
 - Tool calls and tool results.
 - Approval, backup, feedback, status, and error entries.
 - Message timestamps and counts.
-- Token and estimated-cost totals returned by the platform API.
+- Token and estimated-cost totals returned by the cloud API.
 
 The **Copy Session** action serializes the visible session into text. Doctor's idle panel also warns that Doctor logs may be temporarily stored, so guardians should avoid entering secrets that are not necessary for diagnosis.
 
@@ -91,7 +91,7 @@ Sharing feedback is separate from approving a Doctor operation. A guardian can c
 
 ## API reference
 
-The platform API exposes Doctor under the assistant-scoped routes below. Requests use the same authentication options as the surrounding platform API.
+The cloud API exposes Doctor under the assistant-scoped routes below. Requests use the same authentication options as the surrounding platform API.
 
 | Operation        | Route                                                                           | Purpose                                                    |
 | ---------------- | ------------------------------------------------------------------------------- | ---------------------------------------------------------- |
@@ -164,15 +164,15 @@ Doctor cannot start without an active assistant. Hatch or select an assistant, t
 
 ### Doctor is unavailable
 
-Doctor is platform-hosted. Self-hosted assistants do not expose the Doctor tab or the `/doctor` command.
+Doctor is cloud-hosted. Self-hosted assistants do not expose the Doctor tab or the `/doctor` command.
 
 ### Monthly session limit
 
-The platform can reject session creation when the available Doctor sessions for the month have been used. The web client tells the guardian to try again next month.
+The cloud can reject session creation when the available Doctor sessions for the month have been used. The web client tells the guardian to try again next month.
 
 ### Service or connection failure
 
-Session creation, message delivery, and event streaming can fail when the Doctor service or platform proxy is unavailable. The panel surfaces the returned error and ends the session when it cannot recover.
+Session creation, message delivery, and event streaming can fail when the Doctor service or cloud proxy is unavailable. The panel surfaces the returned error and ends the session when it cannot recover.
 
 The event stream retries recoverable interruptions with a bounded reconnect policy. If the session has expired, its event history cannot be replayed, or the stream remains idle, the panel asks the guardian to start a new session.
 

package/docs/desktop-browser-cli.md

@@ -1,10 +1,10 @@
 # Virtual desktop browser CLI
 
-`assistant browser --virtual-desktop` uses the browser CLI's shared operation handlers against the Chrome process owned by `DesktopSessionManager`. It requires a platform-hosted container, the `assistant-desktop` flag, image-provided desktop components and an identified guardian conversation. Availability is checked before starting or reusing control and after asynchronous startup; losing readiness or the feature flag cancels active control. The first eligible browser command starts Chrome and executes its action without downloading or installing dependencies. Opening the picture-in-picture panel checks readiness and starts the viewer directly. The persistent profile remains `data/desktop-profile`.
+`assistant browser --virtual-desktop` uses the browser CLI's shared operation handlers against the Chrome process owned by `DesktopSessionManager`. It requires a cloud-hosted container, the `assistant-desktop` flag, image-provided desktop components and an identified guardian conversation. Availability is checked before starting or reusing control and after asynchronous startup; losing readiness or the feature flag cancels active control. The first eligible browser command starts Chrome and executes its action without downloading or installing dependencies. Opening the picture-in-picture panel checks readiness and starts the viewer directly. The persistent profile remains `data/desktop-profile`.
 
 The assistant Dockerfile installs desktop system packages, pinned WezTerm and pinned Google Chrome before Bun and application source. Architecture-specific SHA-256 checksums verify both downloads. Chrome is extracted to `/opt/google/chrome` without running package scripts or registering its repository. Missing components require replacing the assistant image. Runtime code only checks readiness. `POST /v1/desktop/setup` remains a read-only compatibility endpoint for released clients; current clients only use GET.
 
-Automatic browser selection in platform-hosted web conversations uses the streamed Chrome when the desktop flag is enabled and the actor is an identified guardian. The macOS and Windows apps keep their existing browser selection and fallback behavior; they use the streamed desktop only with explicit `--virtual-desktop`. Their shared renderer reports a `web` transport, so selection also reads the active turn's frozen `clientOs`; it does not change transport identity or host capability checks. Explicit `--virtual-desktop`, `--browser-mode`, `--target-client-id` and active-tab requests override the default. Existing personal-browser sessions and tab pins remain on their selected browser. Tab commands use the same streamed-browser default as page commands. `--browser-mode local` selects assistant-side Playwright, not the user's Chrome.
+Automatic browser selection in cloud-hosted web conversations uses the streamed Chrome when the desktop flag is enabled and the actor is an identified guardian. The macOS and Windows apps keep their existing browser selection and fallback behavior; they use the streamed desktop only with explicit `--virtual-desktop`. Their shared renderer reports a `web` transport, so selection also reads the active turn's frozen `clientOs`; it does not change transport identity or host capability checks. Explicit `--virtual-desktop`, `--browser-mode`, `--target-client-id` and active-tab requests override the default. Existing personal-browser sessions and tab pins remain on their selected browser. Tab commands use the same streamed-browser default as page commands. `--browser-mode local` selects assistant-side Playwright, not the user's Chrome.
 
 The legacy `--desktop` option remains an alias. The deployment flag key `assistant-desktop`, API paths, sync tags and persistent profile path are unchanged for compatibility. The shared `isVirtualDesktopEnabled` gate rejects self-hosted assistants, including local Docker, for setup, streaming and control.
 
@@ -18,11 +18,11 @@ flowchart LR
   Chrome --> Stream[Existing desktop stream]
 ```
 
-The Terminal dock launcher opens [WezTerm](https://wezterm.org/), with a plain dark native title bar, minimize/maximize/close controls, a new-tab button and split panes. Use Ctrl+Shift+T for a tab, Ctrl+Shift+D to split side by side, and Ctrl+Shift+E to split top and bottom. The desktop seeds an editable `data/desktop-panel/wezterm/wezterm.lua` configuration with software rendering and a dark theme. The managed launcher keeps its stable `data/desktop-panel/applications/xterm.desktop` path so existing dock pins remain valid. The image includes an exact-version, SHA-256-verified WezTerm package for Linux x64 or ARM64, plus its rendering libraries.
+The Terminal dock launcher opens [WezTerm](https://wezterm.org/), with a plain dark native title bar, minimize/maximize/close controls, a new-tab button and split panes. Use Ctrl+Shift+T for a tab, Ctrl+Shift+D to split side by side, and Ctrl+Shift+E to split top and bottom. The desktop seeds an editable `data/desktop-panel/wezterm/wezterm.lua` configuration with software rendering and a dark theme. The cloud launcher keeps its stable `data/desktop-panel/applications/xterm.desktop` path so existing dock pins remain valid. The image includes an exact-version, SHA-256-verified WezTerm package for Linux x64 or ARM64, plus its rendering libraries.
 
 Chrome and WezTerm use explicit desktop window classes shared with their launcher entries. The desktop session bus and Plank share `XDG_DATA_HOME` so the D-Bus-activated window matcher can resolve the generated launchers and group running windows under their pinned icons.
 
-Chrome and its dock launcher share the managed profile and loopback debug port. For Chrome reopened from the dock, the profile singleton lock identifies a candidate PID, validated against the installed executable, profile and loopback debug arguments. Discovery checks `/proc` socket ownership against that browser PID, refuses redirects and validates the returned browser WebSocket endpoint. The connection stays within the container. No CDP endpoint or token is exposed to the renderer.
+Chrome and its dock launcher share the cloud profile and loopback debug port. For Chrome reopened from the dock, the profile singleton lock identifies a candidate PID, validated against the installed executable, profile and loopback debug arguments. Discovery checks `/proc` socket ownership against that browser PID, refuses redirects and validates the returned browser WebSocket endpoint. The connection stays within the container. No CDP endpoint or token is exposed to the renderer.
 
 The desktop client bypasses personal-browser discovery, extension reconnect waits and backend fallback. It reuses the existing AX snapshot, DOM element resolution, mouse, keyboard, extraction and credential-fill implementations. Operation-scoped clients borrow the lease's connection; disposing one does not release the lease. `detach`, `close`, turn completion, cancellation, errors and idle expiry release control. Turn completion clears the activity indicator immediately and queues browser cleanup before the next automation session; it leaves Chrome and the current page open for the user. Only `tabs close` closes a Chrome tab.
 
@@ -44,11 +44,11 @@ Desktop streaming checks the current in-memory gateway feature flags during conn
 
 ## Computer use on the same desktop
 
-The existing `computer-use` skill defaults to this desktop in platform-hosted
+The existing `computer-use` skill defaults to this desktop in cloud-hosted
 web conversations. Native desktop clients, including the Mac app connected to a
-platform-hosted assistant, keep the connected-computer default and require
+cloud-hosted assistant, keep the connected-computer default and require
 `target: "assistant-desktop"` to select the virtual desktop explicitly.
-Non-platform assistants keep their connected-computer behavior.
+Non-cloud assistants keep their connected-computer behavior.
 
 Explicit `target: "connected-computer"` or `target_client_id` selects a connected
 computer on every client. The selected target never falls back to another

package/docs/skills.md

@@ -4,7 +4,7 @@ This document describes the security model for the Cadet Assistant skill system,
 
 ## Overview
 
-Skills extend the assistant's capabilities by providing instructions (via `SKILL.md`) and optional custom tools (via `TOOLS.json`). Skills can be **bundled** (shipped with the application), **managed** (user-installed via `scaffold_managed_skill`), **workspace** (project-local), or **extra** (additional directories configured by the user).
+Skills extend the assistant's capabilities by providing instructions (via `SKILL.md`) and optional custom tools (via `TOOLS.json`). Skills can be **bundled** (shipped with the application), **managed** (user-installed via `scaffold_cloud_skill`), **workspace** (project-local), or **extra** (additional directories configured by the user).
 
 For managed skills, the installed source of truth is a valid directory at `$CADET_WORKSPACE_DIR/skills/<id>/` containing a top-level `SKILL.md` with standardized frontmatter. The assistant parses that frontmatter at startup and when skill directories change, then seeds Memory V2 skill entries under `skills/<id>` so the assistant can discover available skills from memory. The legacy `SKILLS.md` index is removed by workspace migration and is no longer created by install or scaffold paths.
 
@@ -54,7 +54,7 @@ The `computeSkillVersionHash(directoryPath)` function computes a deterministic S
 
 When a skill's source files change (any file added, removed, or modified), the hash changes. Version-specific trust rules with the old hash no longer match, and the user is re-prompted. This protects against:
 
-- **Supply-chain attacks**: A malicious update to a managed or workspace skill cannot silently inherit previous approvals.
+- **Supply-chain attacks**: A malicious update to a cloud or workspace skill cannot silently inherit previous approvals.
 - **Accidental drift**: Editing a skill's tool scripts invalidates stale approvals, ensuring the user reviews the new behavior.
 
 ### Choosing between version-specific and any-version rules

package/docs/voice-input-diagnostics.md

@@ -49,7 +49,7 @@ While closed, the gate holds the most recent 200 ms before deciding whether to s
 
 Flux `StartOfTurn` owns hands-free interruption, independently of the provider end-of-turn setting. Above-threshold microphone audio alone cannot pause playback, cancel a reply, or trigger a speech-start screenshot. A provider turn start emits `speech_started` immediately, without the local sustained-speech delay, and cancels an active reply through the shared interruption path. Duplicate or older provider turn indices are ignored within a stream. Other providers retain the local guard. This waits for provider recognition and does not guarantee rejection of playback echo or background speech that Flux transcribes.
 
-Managed Flux maps provider turn indices into one continuous sequence across transparent relay reconnects. A new relay connection restarting at zero therefore cannot make fresh speech look like a duplicate. If connection setup falls back to a provider without native turn detection, the suppressed local onset is replayed through the local interruption path, preserving its sustained-speech guard result even if the utterance ended during the dial.
+Cloud Flux maps provider turn indices into one continuous sequence across transparent relay reconnects. A new relay connection restarting at zero therefore cannot make fresh speech look like a duplicate. If connection setup falls back to a provider without native turn detection, the suppressed local onset is replayed through the local interruption path, preserving its sustained-speech guard result even if the utterance ended during the dial.
 
 The gate shares the existing adaptive energy classifier. Quiet speech within the one-second tail passes through; quiet onset in the 200 ms buffer is preserved if followed by detected speech. Sustained speech entirely below the local threshold can be suppressed, and noise classified as speech can reopen the gate. This limits background exposure rather than guaranteeing that every false transcript is eliminated.
 

package/eslint-rules/__tests__/cli-no-daemon-internals.test.ts

@@ -99,10 +99,10 @@ tester.run("cli/no-daemon-internals", rule, {
       code: `import { conversations } from "../../persistence/schema/conversations.js";`,
       errors: [{ messageId: "hoistedDaemonImport" }],
     },
-    // Hoisting the platform client.
+    // Hoisting the cloud client.
     {
       filename: NESTED,
-      code: `import { CadetPlatformClient } from "../../../platform/client.js";`,
+      code: `import { CadetCloudClient } from "../../../cloud/client.js";`,
       errors: [{ messageId: "hoistedDaemonImport" }],
     },
     // A non-leaf module under providers/ is daemon-internal (only util/ etc.

package/node_modules/@mycadet/avatar-manifest/src/__tests__/notification-avatar.test.ts

@@ -246,7 +246,7 @@ describe("notificationAvatarGeometry", () => {
 });
 
 describe("the transport contract", () => {
-  test("caps a notification PNG at 128 KB for the platform sync", () => {
+  test("caps a notification PNG at 128 KB for the cloud sync", () => {
     expect(NOTIFICATION_AVATAR_MAX_BYTES).toBe(128 * 1024);
   });
 

package/node_modules/@mycadet/avatar-manifest/src/notification-avatar.ts

@@ -30,7 +30,7 @@ export const NOTIFICATION_AVATAR_FALLBACK_DISC_HEX = "#ECEFEA";
 const ACCENT_MIX = 0.14;
 
 /**
- * Largest notification PNG the platform sync ships, in bytes. It bounds the
+ * Largest notification PNG the cloud sync ships, in bytes. It bounds the
  * `notification_avatar_base64` field of the PATCH that uploads the disc, which
  * is what APNs and FCM later hand their clients a URL and a hash for. A
  * photographic avatar is quantised (or dropped) to fit.
@@ -118,7 +118,7 @@ function px(value: number): string {
  * edge is the hard boundary no matter how far a cover-crop overflows.
  *
  * The `<image href="data:...">` shape is the one `downscaleRaster()` in
- * `assistant/src/platform/sync-avatar.ts` already feeds resvg, so the daemon's
+ * `assistant/src/cloud/sync-avatar.ts` already feeds resvg, so the daemon's
  * rasterizer is known to render it.
  */
 export function notificationAvatarSvg({

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/package.json

@@ -26,7 +26,7 @@
     "./error": "./src/error.ts",
     "./reactions": "./src/reactions.ts",
     "./guardian-requests": "./src/guardian-requests.ts",
-    "./platform-credential": "./src/platform-credential.ts",
+    "./cloud-credential": "./src/cloud-credential.ts",
     "./plan-credit": "./src/plan-credit.ts",
     "./integration-categories": "./src/integration-categories.ts",
     "./mcp-oauth": "./src/mcp-oauth.ts"

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/{platform-credential.ts → cloud-credential.ts}

@@ -1,10 +1,10 @@
 /**
- * Wire contract for asking an assistant whether its stored platform-managed
+ * Wire contract for asking an assistant whether its stored cloud-managed
  * credential still authenticates.
  *
  * The daemon route is the authoritative serving side:
  *   - `POST /v1/platform/verify-credential`
- *       (`assistant/src/runtime/routes/platform-routes.ts`)
+ *       (`assistant/src/runtime/routes/cloud-routes.ts`)
  *
  * The daemon's platform client produces the verdict, the route reports it,
  * and the `cadet` CLI reads it before deciding whether a stored key can be
@@ -15,26 +15,26 @@
 import { z } from "zod";
 
 /**
- * What the platform said about the stored credential, right now.
+ * What the cloud said about the stored credential, right now.
  *
- *   - `valid`: the platform accepted it.
- *   - `rejected`: the platform refused it (unauthorized or forbidden); the
+ *   - `valid`: the cloud accepted it.
+ *   - `rejected`: the cloud refused it (unauthorized or forbidden); the
  *     credential needs replacing.
  *   - `unknown`: the check itself could not run (no credential stored, the
  *     platform unreachable, a server error). Not evidence either way.
  */
-export const PlatformCredentialVerificationStatusSchema = z.enum([
+export const CloudCredentialVerificationStatusSchema = z.enum([
   "valid",
   "rejected",
   "unknown",
 ]);
-export type PlatformCredentialVerificationStatus = z.infer<
-  typeof PlatformCredentialVerificationStatusSchema
+export type CloudCredentialVerificationStatus = z.infer<
+  typeof CloudCredentialVerificationStatusSchema
 >;
 
 /** `POST /v1/platform/verify-credential` response body. */
 export const PlatformVerifyCredentialResponseSchema = z.object({
-  status: PlatformCredentialVerificationStatusSchema,
+  status: CloudCredentialVerificationStatusSchema,
 });
 export type PlatformVerifyCredentialResponse = z.infer<
   typeof PlatformVerifyCredentialResponseSchema

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/handles.ts

@@ -15,9 +15,9 @@
  *    Format: `local_oauth:<providerKey>/<connectionId>` where providerKey
  *    is the bare provider name (e.g. `google`).
  *
- * 3. **Managed OAuth** — references an OAuth connection managed by the
+ * 3. **Cloud OAuth** — references an OAuth connection managed by the
  *    platform. Format: `platform_oauth:<connectionId>` where connectionId
- *    is the platform-assigned connection identifier.
+ *    is the cloud-assigned connection identifier.
  */
 
 import { z } from "zod";
@@ -96,7 +96,7 @@ export function localOAuthHandle(
 }
 
 /**
- * Build a managed (platform) OAuth credential handle from a connection ID.
+ * Build a cloud (platform) OAuth credential handle from a connection ID.
  */
 export function platformOAuthHandle(connectionId: string): string {
   return `${HandleType.PlatformOAuth}:${connectionId}`;

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/index.ts

@@ -31,7 +31,7 @@ export * from "./no-response.js";
 export * from "./plan-credit.js";
 export * from "./integration-categories.js";
 export * from "./mcp-oauth.js";
-export * from "./platform-credential.js";
+export * from "./cloud-credential.js";
 export * from "./remote-web-pairing.js";
 export * from "./twilio-ingress.js";
 export * from "./url-normalization.js";

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/ingress.ts

@@ -4,7 +4,7 @@
  * `{env}-cloud.mycadet.ai` → `tunnel-{env}.mycadet.ai`). Returns null for
  * hosts outside that convention (localhost, custom domains). Shared by the
  * gateway speech relay and the web live-voice client so the two ends of the
- * managed-speech transport can't drift.
+ * cloud-speech transport can't drift.
  */
 export function tunnelHostForPlatformHost(host: string): string | null {
   if (host === "cloud.mycadet.ai") {
@@ -100,11 +100,17 @@ export const INGRESS_PAIRING_TUNNEL_KEY = "pairingTunnel";
 export const INGRESS_ASSISTANT_ID_KEY = "assistantId";
 
 /**
- * The local tunnel providers the CLI can start, in the order they are offered.
- * `cadet tunnel`'s accepted `--provider` values and the persisted-record
- * validation below both derive from it.
+ * The tunnel providers the CLI offers, in the order they are presented —
+ * the managed `cadet` tunnel first (listed, not yet implemented), then the
+ * local ones. `cadet tunnel`'s accepted `--provider` values and the
+ * persisted-record validation below both derive from it.
  */
-export const TUNNEL_PROVIDERS = ["ngrok", "cloudflare", "tailscale"] as const;
+export const TUNNEL_PROVIDERS = [
+  "cadet",
+  "ngrok",
+  "cloudflare",
+  "tailscale",
+] as const;
 
 export type TunnelProviderName = (typeof TUNNEL_PROVIDERS)[number];
 

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/remote-web-pairing.ts

@@ -152,7 +152,7 @@ export const DEFAULT_REMOTE_WEB_PAIRING_PLATFORM: RemoteWebPairingPlatform =
 
 /**
  * A requested platform coerced to a known value. The pairing-token route is
- * publicly reachable and the platform renders verbatim in the host's
+ * publicly reachable and the cloud renders verbatim in the host's
  * paired-devices list, so an unrecognized value never reaches the DB.
  */
 export function resolveRemoteWebPairingPlatform(

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/rpc.ts

@@ -34,7 +34,7 @@ import { RpcErrorSchema } from "./error.js";
 
 export const CesRpcMethod = {
   /** Push an updated assistant credential to CES after post-hatch provisioning. */
-  UpdateManagedCredential: "update_managed_credential",
+  UpdateCloudCredential: "update_managed_credential",
   /** Retrieve a single credential by account name. */
   GetCredential: "get_credential",
   /** Store or update a credential by account name. */
@@ -63,7 +63,7 @@ export type CesRpcMethod = (typeof CesRpcMethod)[keyof typeof CesRpcMethod];
 // update_managed_credential
 // ---------------------------------------------------------------------------
 
-export const UpdateManagedCredentialSchema = z.object({
+export const UpdateCloudCredentialSchema = z.object({
   /** The assistant API key to push to CES for platform credential materialization. */
   assistantApiKey: z.string(), // nosemgrep: not-a-secret
   /**
@@ -72,16 +72,16 @@ export const UpdateManagedCredentialSchema = z.object({
    */
   assistantId: z.string().optional(),
 });
-export type UpdateManagedCredential = z.infer<
-  typeof UpdateManagedCredentialSchema
+export type UpdateCloudCredential = z.infer<
+  typeof UpdateCloudCredentialSchema
 >;
 
-export const UpdateManagedCredentialResponseSchema = z.object({
-  /** Whether the managed credential was successfully updated. */
+export const UpdateCloudCredentialResponseSchema = z.object({
+  /** Whether the cloud credential was successfully updated. */
   updated: z.boolean(),
 });
-export type UpdateManagedCredentialResponse = z.infer<
-  typeof UpdateManagedCredentialResponseSchema
+export type UpdateCloudCredentialResponse = z.infer<
+  typeof UpdateCloudCredentialResponseSchema
 >;
 
 // ---------------------------------------------------------------------------
@@ -311,9 +311,9 @@ export type BulkSetCredentialRecordsResponse = z.infer<
  * schemas. Useful for building type-safe RPC dispatch layers.
  */
 export interface CesRpcContract {
-  [CesRpcMethod.UpdateManagedCredential]: {
-    request: UpdateManagedCredential;
-    response: UpdateManagedCredentialResponse;
+  [CesRpcMethod.UpdateCloudCredential]: {
+    request: UpdateCloudCredential;
+    response: UpdateCloudCredentialResponse;
   };
   [CesRpcMethod.GetCredential]: {
     request: GetCredential;
@@ -361,9 +361,9 @@ export interface CesRpcContract {
  * Schema lookup map for runtime validation of RPC payloads.
  */
 export const CesRpcSchemas = {
-  [CesRpcMethod.UpdateManagedCredential]: {
-    request: UpdateManagedCredentialSchema,
-    response: UpdateManagedCredentialResponseSchema,
+  [CesRpcMethod.UpdateCloudCredential]: {
+    request: UpdateCloudCredentialSchema,
+    response: UpdateCloudCredentialResponseSchema,
   },
   [CesRpcMethod.GetCredential]: {
     request: GetCredentialSchema,

package/node_modules/@mycadet/ces-client/node_modules/@mycadet/service-contracts/src/trust-rules.ts

@@ -15,7 +15,7 @@
  * - **URL**: tools whose candidates include a URL (`web_fetch`,
  *   `network_request`).
  * - **Managed skill**: tools that manage first-party skill packages
- *   (`scaffold_managed_skill`, `delete_managed_skill`).
+ *   (`scaffold_cloud_skill`, `delete_cloud_skill`).
  * - **Skill load**: the `skill_load` tool, which uses a distinct candidate
  *   namespace (`skill_load:selector` or `skill_load_dynamic:selector`).
  * - **Generic**: everything else (computer-use tools, UI surface tools,
@@ -58,8 +58,8 @@ export const URL_TOOLS = ["web_fetch", "network_request"] as const;
  * Tools that manage first-party skill packages (scaffold/delete).
  */
 export const MANAGED_SKILL_TOOLS = [
-  "scaffold_managed_skill",
-  "delete_managed_skill",
+  "scaffold_cloud_skill",
+  "delete_cloud_skill",
 ] as const;
 
 /**
@@ -89,8 +89,8 @@ export function isUrlRule(rule: { tool: string }): boolean {
   return URL_TOOLS_SET.has(rule.tool);
 }
 
-/** Returns true when the rule's tool belongs to the managed-skill-tool family. */
-export function isManagedSkillRule(rule: { tool: string }): boolean {
+/** Returns true when the rule's tool belongs to the cloud-skill-tool family. */
+export function isCloudSkillRule(rule: { tool: string }): boolean {
   return MANAGED_SKILL_TOOLS_SET.has(rule.tool);
 }
 

package/node_modules/@mycadet/ces-client/src/rpc-client.ts

@@ -416,7 +416,7 @@ export function createCesRpcClient(
       assistantApiKey: string,
       assistantId?: string,
     ): Promise<{ updated: boolean }> {
-      return call(CesRpcMethod.UpdateManagedCredential, {
+      return call(CesRpcMethod.UpdateCloudCredential, {
         assistantApiKey,
         ...(assistantId ? { assistantId } : {}),
       });

package/node_modules/@mycadet/credential-storage/src/oauth-runtime.ts

@@ -11,7 +11,7 @@
  *
  * It has NO dependency on the assistant daemon, SQLite, Drizzle, or any
  * service-specific module. The assistant's token-manager.ts and
- * token-persistence.ts wire in the platform-specific backends and
+ * token-persistence.ts wire in the cloud-specific backends and
  * delegate here for shared logic.
  */
 

package/node_modules/@mycadet/credential-storage/src/static-credentials.ts

@@ -6,7 +6,7 @@
  * platform helpers, or any service-specific code — callers supply the file
  * path and this module handles versioned JSON persistence with atomic writes.
  *
- * The assistant's `metadata-store.ts` wires in the platform-specific data
+ * The assistant's `metadata-store.ts` wires in the cloud-specific data
  * directory and re-exports convenience functions that delegate here.
  */
 

package/node_modules/@mycadet/environments/src/seeds.ts

@@ -64,12 +64,12 @@ export function cloudAssistantHubUrl(envName: string | undefined): string {
 export const SEEDS: Record<string, EnvironmentDefinition> = {
   production: {
     name: "production",
-    platformUrl: "https://cloud.mycadet.ai",
+    cloudUrl: "https://cloud.mycadet.ai",
     webUrl: "https://mycadet.ai",
   },
   staging: {
     name: "staging",
-    platformUrl: "https://staging-cloud.mycadet.ai",
+    cloudUrl: "https://staging-cloud.mycadet.ai",
     webUrl: "https://staging.mycadet.ai",
     portsOverride: portBlock(17000),
   },
@@ -77,21 +77,21 @@ export const SEEDS: Record<string, EnvironmentDefinition> = {
     name: "test",
     // Non-functional URL — used only by unit tests for URL resolution, never
     // hit in production.
-    platformUrl: "https://test-cloud.mycadet.ai",
+    cloudUrl: "https://test-cloud.mycadet.ai",
     webUrl: "https://dev.mycadet.ai",
     portsOverride: portBlock(19000),
   },
   dev: {
     name: "dev",
-    platformUrl: "https://dev-cloud.mycadet.ai",
+    cloudUrl: "https://dev-cloud.mycadet.ai",
     webUrl: "https://dev.mycadet.ai",
     portsOverride: portBlock(18000),
   },
   local: {
     name: "local",
-    platformUrl: "http://localhost:8000",
+    cloudUrl: "http://localhost:8000",
     webUrl: "http://localhost:3000",
-    // assistantPlatformUrl: "http://host.docker.internal:8000",
+    // assistantCloudUrl: "http://host.docker.internal:8000",
     // ^ uncomment this once dockerized hatch path is live.
     // The assistant runs in a different network namespace than the host.
     portsOverride: portBlock(20000),

package/node_modules/@mycadet/environments/src/shell.test.ts

@@ -72,7 +72,7 @@ describe("buildShellSpawnFlags", () => {
 });
 
 describe("path list handling", () => {
-  test("uses the platform delimiter", () => {
+  test("uses the cloud delimiter", () => {
     expect(pathListDelimiter("win32")).toBe(";");
     expect(pathListDelimiter("linux")).toBe(":");
   });

package/node_modules/@mycadet/environments/src/types.ts

@@ -21,14 +21,14 @@ export interface PortMap {
 
 /**
  * A resolved environment definition. Required fields are `name` and
- * `platformUrl`. All other fields are optional and declared upfront — new
+ * `cloudUrl`. All other fields are optional and declared upfront — new
  * fields are additive, never breaking. `name` is intentionally typed as
  * `string` (not `keyof SEEDS`) so custom environments can be represented by
  * future layers (user config file, ad-hoc env vars, etc.).
  */
 export interface EnvironmentDefinition {
   name: string;
-  platformUrl: string;
+  cloudUrl: string;
 
   /**
    * The web app (Next.js) base URL for browser-facing pages like
@@ -41,13 +41,13 @@ export interface EnvironmentDefinition {
   webUrl: string;
 
   /**
-   * Override for the platform URL the assistant process itself uses. Only
-   * differs from `platformUrl` when the assistant runs in a different network
+   * Override for the cloud URL the assistant process itself uses. Only
+   * differs from `cloudUrl` when the assistant runs in a different network
    * namespace than the host (e.g. Docker on macOS, where the host's localhost
-   * is reached via `host.docker.internal`). Falls back to `platformUrl` when
+   * is reached via `host.docker.internal`). Falls back to `cloudUrl` when
    * unset.
    */
-  assistantPlatformUrl?: string;
+  assistantCloudUrl?: string;
 
   /** Human-readable label for UI surfaces. */
   displayName?: string;

package/node_modules/@mycadet/gateway-client/node_modules/@mycadet/service-contracts/package.json

@@ -26,7 +26,7 @@
     "./error": "./src/error.ts",
     "./reactions": "./src/reactions.ts",
     "./guardian-requests": "./src/guardian-requests.ts",
-    "./platform-credential": "./src/platform-credential.ts",
+    "./cloud-credential": "./src/cloud-credential.ts",
     "./plan-credit": "./src/plan-credit.ts",
     "./integration-categories": "./src/integration-categories.ts",
     "./mcp-oauth": "./src/mcp-oauth.ts"