@comecaramelos/dsh-chrome-mcp 1.0.0 → 2.0.0

package/lib/host/schema.d.ts

@@ -1,307 +1,361 @@
 /**
- * The two zod schemas: the cordis row config and the settings section.
+ * The single zod `Config` of the plugin row.
  *
- * The row config validates what lives in the profile (one row per plugin
- * instance); the settings schema describes the namespace the Web GUI card
- * edits — the persisted user layer (flags, the executable selection, the saved
- * executable rows, the stderr toggle and the one action trigger) plus the
- * base-layer status fields served alongside it.
+ * Since dsh 0.2.0 the Web GUI card edits the **row configuration** through the
+ * profile's configuration form — there is no separate `settings.yaml` namespace
+ * and no base layer to publish state over. So one schema carries everything the
+ * card reads and writes, and every field the card touches is declared
+ * `.volatile()`: a volatile field is editable through the form without
+ * remounting the plugin, its user layer rides the profile patch instead of
+ * `settings.yaml`, and a live value the Host commits never reaches the patch
+ * (the form write strips the volatile fields out of the stored layer before
+ * merging).
+ *
+ * Ordinary fields (`serverName`, `command`, `package`, `chromePaths`, `env`,
+ * `cwd`, `toolCallTimeoutMs`, `maxInstructionBytes`, `failOnStartupError`,
+ * `reconnect`, `bridgeStderrLog`) are composition-only: the card reads them, it
+ * never edits them, and a form write naming one of them is refused by
+ * dsh-settings.
+ *
+ * Host-resolved fields carry the live value in the reference, so the Host
+ * publishes them through the live mirror (dsh-ancesters `createLiveMirror`) — never with the form.
  */
 import z from "@deepseek-ai/schemastery";
-export declare const Config: z<Schemastery.ObjectS<{
-    serverName: z<string, string>;
-    command: z<string, string>;
-    package: z<string, string>;
-    extraFlags: z<string[], string[]>;
-    chromePath: z<string, string>;
-    chromePaths: z<string[], string[]>;
-    env: z<import("@deepseek-ai/cosmokit").Dict<string, string>, import("@deepseek-ai/cosmokit").Dict<string, string>>;
-    cwd: z<string, string>;
-    toolCallTimeoutMs: z<number, number>;
-    failOnStartupError: z<boolean, boolean>;
-    reconnect: z<Schemastery.ObjectS<{
-        enabled: z<boolean, boolean>;
-        initialDelayMs: z<number, number>;
-        maxDelayMs: z<number, number>;
-        maxAttempts: z<number, number>;
-    }>, Schemastery.ObjectT<{
-        enabled: z<boolean, boolean>;
-        initialDelayMs: z<number, number>;
-        maxDelayMs: z<number, number>;
-        maxAttempts: z<number, number>;
-    }>>;
-    /** Bridge console-output routing: "log" (default) redirects the spawned
-     * npx child's inherited stderr into a per-spawn log file so its progress
-     * / startup lines stay out of the dsh console; "console" inherits it
-     * (debug). The card's "Reduce log output" toggle (`stderrMode`) overrides
-     * this. See {@link buildBridgeSpawn}. */
-    bridgeStderr: z<"log" | "console", "log" | "console">;
-    /** Log path override for "log" mode; "" = auto (see
-     * {@link bridgeStderrLogPath}). Absolute paths only. */
-    bridgeStderrLog: z<string, string>;
-}>, Schemastery.ObjectT<{
-    serverName: z<string, string>;
-    command: z<string, string>;
-    package: z<string, string>;
-    extraFlags: z<string[], string[]>;
-    chromePath: z<string, string>;
-    chromePaths: z<string[], string[]>;
-    env: z<import("@deepseek-ai/cosmokit").Dict<string, string>, import("@deepseek-ai/cosmokit").Dict<string, string>>;
-    cwd: z<string, string>;
-    toolCallTimeoutMs: z<number, number>;
-    failOnStartupError: z<boolean, boolean>;
-    reconnect: z<Schemastery.ObjectS<{
-        enabled: z<boolean, boolean>;
-        initialDelayMs: z<number, number>;
-        maxDelayMs: z<number, number>;
-        maxAttempts: z<number, number>;
-    }>, Schemastery.ObjectT<{
-        enabled: z<boolean, boolean>;
-        initialDelayMs: z<number, number>;
-        maxDelayMs: z<number, number>;
-        maxAttempts: z<number, number>;
-    }>>;
+/**
+ * The plugin row's configuration, and the configuration form the Web GUI card
+ * edits. Every `.volatile()` field below is live: a user edit lands in the
+ * profile patch and commits without a remount, and the Host's own live answers
+ * ride the same references without ever being persisted.
+ */
+export declare const Config: z<Schemastery.ObjectS<NoInfer<{
+    serverName: z<string, string, "defined">;
+    command: z<string, string, "defined">;
+    package: z<string, string, "defined">;
+    /** Flags appended after `npx -y <package>`; the card's last UI edit. The
+     * field's own pattern is what refuses them (an entry that carries a control
+     * character never resolves, so a write is refused Host-side rather than
+     * landing in argv); an executable-pinning flag is rejected by the Host fold
+     * because the executable is picked below. */
+    extraFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    chromePaths: z<string[], string[], "defined">;
+    env: z<import("@deepseek-ai/cosmokit").Dict<string, string>, import("@deepseek-ai/cosmokit").Dict<string, string>, "defined">;
+    cwd: z<string, string, "defined">;
+    toolCallTimeoutMs: z<number, number, "defined">;
+    /** Ceiling for the bridge's server instructions (UTF-8 bytes, attribution
+     * included); an oversized description rejects the connection. Mirrors
+     * `dsh-mcp-client`'s own field and default (32768) — a passthrough for a
+     * server whose instructions run longer than the cap. */
+    maxInstructionBytes: z<number, number, "defined">;
+    failOnStartupError: z<boolean, boolean, "defined">;
+    reconnect: z<Schemastery.ObjectS<NoInfer<{
+        enabled: z<boolean, boolean, "defined">;
+        initialDelayMs: z<number, number, "defined">;
+        maxDelayMs: z<number, number, "defined">;
+        maxAttempts: z<number, number, "defined">;
+    }>>, Schemastery.ObjectT<NoInfer<{
+        enabled: z<boolean, boolean, "defined">;
+        initialDelayMs: z<number, number, "defined">;
+        maxDelayMs: z<number, number, "defined">;
+        maxAttempts: z<number, number, "defined">;
+    }>>, "plain">;
     /** Bridge console-output routing: "log" (default) redirects the spawned
      * npx child's inherited stderr into a per-spawn log file so its progress
      * / startup lines stay out of the dsh console; "console" inherits it
      * (debug). The card's "Reduce log output" toggle (`stderrMode`) overrides
      * this. See {@link buildBridgeSpawn}. */
-    bridgeStderr: z<"log" | "console", "log" | "console">;
+    bridgeStderr: z<"log" | "console", "log" | "console", "defined">;
     /** Log path override for "log" mode; "" = auto (see
      * {@link bridgeStderrLogPath}). Absolute paths only. */
-    bridgeStderrLog: z<string, string>;
-}>>;
-/**
- * User-settings section served to the Web GUI card.
- *
- * Persisted (user layer in `$DSH_HOME/settings.yaml`): `extraFlags`,
- * `chromePath` (the executable the picker selected — or that the host seeded
- * once), `executables` (the saved-executables rows: `id` = path, `name` = UI
- * label), `refreshExecutablesNonce` (the card's **Search executables**
- * trigger), `openWindowsChromeNonce` (the card's **Prelaunch Windows Chrome**
- * trigger), `chromeCustomPaths` (the **legacy** hand-typed MRU: folded into the
- * rows once by the first scan, never written again) and `stderrMode` (the
- * "Reduce log output" toggle: "log" captures the bridge's stderr into a
- * per-spawn log file, "console" echoes it, "" follows the row-config
- * `bridgeStderr`).
- * Served but never persisted (composition base layer held in memory by the
- * host): `lastError`, `executableDiscoveryRevision`, `chromeVersion`,
- * `executableStatus`, `chromeMissing`, `effectiveChromePath`,
- * `effectiveSource`, `wslWindowsExecutable`, `windowsChromeStatus`,
- * `carriesConnectionMode`, the static `rowStderr` mirror, the static
- * `defaultExtraFlags` mirror (the canonical defaults list the card's
- * **Restore defaults** control appends) and the static `wslExtraFlags` mirror
- * (the recommended WSL ↔ Windows flags the card's **Flags WSL** control
- * appends) — the client's polls stop when the served revision advances past its
- * action-time value.
- */
-export declare const SettingsSchema: z<Schemastery.ObjectS<{
-    /** Flags appended after `npx -y <package>`; persisted last UI edit. An
-     * executable-pinning flag is rejected: the executable is picked below. */
-    extraFlags: z<string[], string[]>;
-    /** Written by the UI **Search executables** button; the host reacts to it by
-     * re-probing the saved rows and merging what it finds back into them. */
-    refreshExecutablesNonce: z<number, number>;
-    /** Written by the UI **Prelaunch Windows Chrome** button; the host reacts to it
-     * by running the Windows launch: locate the Windows Chrome, prove the
-     * mirrored-loopback prereq, launch it with a debugging port, and write the
-     * `--browserUrl` connect entry that leaves the bridge in connect mode. */
-    openWindowsChromeNonce: z<number, number>;
+    bridgeStderrLog: z<string, string, "defined">;
     /**
      * The executable the bridge launches with: picked in the picker (a saved
-     * row's `id`) or seeded once by the host's first scan. "" = nothing resolved
-     * yet — there is no auto state to fall back to.
+     * row's `id`) or seeded once by the Host's first scan. "" = nothing
+     * resolved yet — there is no auto state to fall back to.
      */
-    chromePath: z<string, string>;
+    chromePath: z<string, string, "volatile-defined">;
     /** The picker's saved rows — `{ id: path, name: label }`, user-authored. The
-     * host re-normalizes (trim, dedupe, caps) on every read, and a scan merges
+     * Host re-normalizes (trim, dedupe, caps) on every read, and a scan merges
      * what it discovers into them without dropping a name the user chose. */
-    executables: z<({
+    executables: z<NoInfer<({
         id?: string | null | undefined;
         name?: string | null | undefined;
-    } & import("@deepseek-ai/cosmokit").Dict)[], Schemastery.ObjectT<{
-        id: z<string, string>;
-        name: z<string, string>;
-    }>[]>;
+    } & import("@deepseek-ai/cosmokit").Dict)[]>, NoInfer<Schemastery.ObjectT<NoInfer<{
+        id: z<string, string, "defined">;
+        name: z<string, string, "defined">;
+    }>>[]>, "volatile-defined">;
+    /** The ids of saved rows the user dropped. Every run folds what it found
+     * back into the rows, and the found list keeps answering a path the user
+     * just deleted, so without this record a dropped row stood back up on the
+     * very run the deletion queued (measured live 2026-10-12: the (x86)
+     * Windows-executable row read as a delete that never landed). Merge steps
+     * skip every id standing here; a list write carrying the id again clears
+     * it. Host-authored: the card never edits this field. */
+    droppedExecutables: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
     /**
      * **Legacy** MRU of hand-typed executables, newest first. The saved rows
-     * replace it: a host whose settings still carry it folds its paths into the
-     * rows during the first scan (see ./catalog.ts `mergeEntries`), so the field
-     * is read once and never written again.
+     * replace it: a Host whose profile still carries it folds its paths into
+     * the rows during the first scan (see ./catalog.ts `mergeEntries`), so the
+     * field is read once and never written again.
      */
-    chromeCustomPaths: z<string[], string[]>;
+    chromeCustomPaths: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
     /**
-     * Persisted UI "Reduce log output" toggle: "log" captures the bridge's
+     * The card's "Reduce log output" toggle: "log" captures the bridge's
      * stderr into the log file, "console" echoes it (debug). "" follows the
-     * row-config `bridgeStderr` (mirrored into `rowStderr`).
+     * row-config `bridgeStderr`.
      */
-    stderrMode: z<string, string>;
+    stderrMode: z<string, string, "volatile-defined">;
+    /** The mode the bridge actually routes console output through — the UI
+     * toggle when it states one, else the row config. Mirrored live so the
+     * toggle never reads a phantom state (see `resolveStderrMode`). */
+    stderrEffective: z<"log" | "console", "log" | "console", "volatile-defined">;
+    /** Written by the card's **Fetch executables** button; the Host reacts by
+     * re-probing the saved rows and merging what it finds back into them. */
+    refreshExecutablesNonce: z<number, number, "volatile-defined">;
+    /** Written by the card's **Prelaunch Windows Chrome** button; the Host
+     * reacts by running the Windows launch: locate the Windows Chrome, prove
+     * the mirrored-loopback prereq, launch it with a debugging port, and write
+     * the `--browserUrl` connect entry that leaves the bridge in connect mode. */
+    openWindowsChromeNonce: z<number, number, "volatile-defined">;
+    /**
+     * Whether the translation of this row's **standalone** configuration was
+     * offered and turned down. Host-authored:
+     * the card never edits it — only the proposal's dismiss action does.
+     */
+    migrationDismissed: z<boolean, boolean, "volatile-defined">;
     /** Last check/connection failure, human-readable; empty when healthy. */
-    lastError: z<string, string>;
+    lastError: z<string, string, "volatile-defined">;
     /** Known error: the last failure was "no Chrome executable detected". */
-    chromeMissing: z<boolean, boolean>;
+    chromeMissing: z<boolean, boolean, "volatile-defined">;
     /** Executable-run counter (success or failure); completion signal for every
      * executable action the card can take. */
-    executableDiscoveryRevision: z<number, number>;
+    executableDiscoveryRevision: z<number, number, "volatile-defined">;
     /** The version the **selected** executable answered with; "" when nothing
      * answered — nothing picked, a connect mode, or a blocked path. */
-    chromeVersion: z<string, string>;
+    chromeVersion: z<string, string, "volatile-defined">;
     /** Per-row probe status keyed by path: the version the row answered with,
-     * and the failure for a row that is present but not runnable (or blocked).
-     * Base layer, never persisted — the rows themselves live in the user
-     * layer. */
-    executableStatus: z<({
+     * and the failure for a row that is present but not runnable (or blocked). */
+    executableStatus: z<NoInfer<({
         path?: string | null | undefined;
         version?: string | null | undefined;
         error?: string | null | undefined;
-    } & import("@deepseek-ai/cosmokit").Dict)[], Schemastery.ObjectT<{
-        path: z<string, string>;
-        version: z<string, string>;
-        error: z<string, string>;
-    }>[]>;
-    /** The path the bridge actually launches with ("" when nothing is fixed).
-     * Base layer, never persisted. */
-    effectiveChromePath: z<string, string>;
+        note?: string | null | undefined;
+    } & import("@deepseek-ai/cosmokit").Dict)[]>, NoInfer<Schemastery.ObjectT<NoInfer<{
+        path: z<string, string, "defined">;
+        version: z<string, string, "defined">;
+        error: z<string, string, "defined">;
+        note: z<string, string, "defined">;
+    }>>[]>, "volatile-defined">;
+    /** The path the bridge actually launches with ("" when nothing is fixed). */
+    effectiveChromePath: z<string, string, "volatile-defined">;
     /** Where `effectiveChromePath` came from — picked (`"selected"`), row config
-     * (`"row-config"`) or nothing yet (""). Base layer, never persisted. */
-    effectiveSource: z<string, string>;
-    /** Row-config `bridgeStderr` in effect (static base layer; never
-     * persisted) — the fallback when `stderrMode` is "". */
-    rowStderr: z<"log" | "console", "log" | "console">;
-    /** The canonical default extra-flags list (static base layer; never
-     * persisted) — the list the card's **Restore defaults** control appends to
-     * what the editor holds. Mirror of `DEFAULT_EXTRA_FLAGS`. */
-    defaultExtraFlags: z<string[], string[]>;
-    /** The recommended WSL ↔ Windows extra-flags list (static base layer;
-     * never persisted) — the list the card's **Flags WSL** control appends to
-     * what the editor holds, missing entries only. Mirror of
-     * `WSL_EXTRA_FLAGS`. */
-    wslExtraFlags: z<string[], string[]>;
-    /** True while this host runs under WSL and the selected executable is a
-     * Windows binary — the state the card's notice explains. Base layer, never
-     * persisted (see ./platform.ts). */
-    wslWindowsExecutable: z<boolean, boolean>;
-    /** What the **Prelaunch Windows Chrome** run is doing (base layer; never
-     * persisted) — the single field the card derives the button's state, its
-     * disabled reason and the pill's connect-mode muting from. The locate,
-     * prereq, launch and port answers all live host-side (./windows/), so
-     * the card never carries a list of Windows paths or reachability rules. */
-    windowsChromeStatus: z<Schemastery.ObjectS<{
-        state: z<string, string>;
-        port: z<number, number>;
-        error: z<string, string>;
-    }>, Schemastery.ObjectT<{
-        state: z<string, string>;
-        port: z<number, number>;
-        error: z<string, string>;
-    }>>;
-    /** True while the bridge launches with a connect-mode flag
-     * (`--browserUrl` / `--wsEndpoint`): no local executable is then launched
-     * or probed, so the card mutes the picker. Base layer, never persisted. */
-    carriesConnectionMode: z<boolean, boolean>;
-}>, Schemastery.ObjectT<{
-    /** Flags appended after `npx -y <package>`; persisted last UI edit. An
-     * executable-pinning flag is rejected: the executable is picked below. */
-    extraFlags: z<string[], string[]>;
-    /** Written by the UI **Search executables** button; the host reacts to it by
-     * re-probing the saved rows and merging what it finds back into them. */
-    refreshExecutablesNonce: z<number, number>;
-    /** Written by the UI **Prelaunch Windows Chrome** button; the host reacts to it
-     * by running the Windows launch: locate the Windows Chrome, prove the
-     * mirrored-loopback prereq, launch it with a debugging port, and write the
-     * `--browserUrl` connect entry that leaves the bridge in connect mode. */
-    openWindowsChromeNonce: z<number, number>;
+     * (`"row-config"`) or nothing yet (""). */
+    effectiveSource: z<string, string, "volatile-defined">;
+    /** The canonical default extra-flags list — the list the card's **Restore
+     * defaults** control appends to what the editor holds. Mirror of
+     * `DEFAULT_EXTRA_FLAGS`, served so the card carries no copy of it. */
+    defaultExtraFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    /** The recommended WSL ↔ Windows extra-flags list — the list the card's
+     * **Flags WSL** control appends, missing entries only. Mirror of
+     * `WSL_EXTRA_FLAGS`, served so the card carries no copy of it. */
+    wslExtraFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    /** True while this Host runs under WSL and the selected executable is a
+     * Windows binary — the state the card's notice explains (see ./platform.ts). */
+    wslWindowsExecutable: z<boolean, boolean, "volatile-defined">;
+    /** What the **Prelaunch Windows Chrome** run is doing — the single field
+     * the card derives the button's state, its disabled reason and the pill's
+     * connect-mode muting from. Every half (locate, prereq, launch, port) lives
+     * Host-side (./windows/), so the card carries no list of Windows paths or
+     * reachability rules. */
+    windowsChromeStatus: z<NoInfer<Schemastery.ObjectS<NoInfer<{
+        state: z<string, string, "defined">;
+        port: z<number, number, "defined">;
+        error: z<string, string, "defined">;
+    }>>>, NoInfer<Schemastery.ObjectT<NoInfer<{
+        state: z<string, string, "defined">;
+        port: z<number, number, "defined">;
+        error: z<string, string, "defined">;
+    }>>>, "volatile-defined">;
+    /** True while the bridge launches with a connect-mode flag (`--browserUrl`
+     * / `--wsEndpoint`): no local executable is then launched or probed, so the
+     * card mutes the picker. */
+    carriesConnectionMode: z<boolean, boolean, "volatile-defined">;
+    /** The flags a live connection of this component's own kinds actually
+     * launches with — mirrored from the last `resolve`, not from any layer, so
+     * the machine page states what is running rather than what was last
+     * configured. Empty while nothing resolves. */
+    runningFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    /** The note the last live connection answered with — where its console
+     * output goes, or the Windows URL it connected to. "" when the answer was
+     * silent. */
+    runningNote: z<string, string, "volatile-defined">;
+}>>, Schemastery.ObjectT<NoInfer<{
+    serverName: z<string, string, "defined">;
+    command: z<string, string, "defined">;
+    package: z<string, string, "defined">;
+    /** Flags appended after `npx -y <package>`; the card's last UI edit. The
+     * field's own pattern is what refuses them (an entry that carries a control
+     * character never resolves, so a write is refused Host-side rather than
+     * landing in argv); an executable-pinning flag is rejected by the Host fold
+     * because the executable is picked below. */
+    extraFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    chromePaths: z<string[], string[], "defined">;
+    env: z<import("@deepseek-ai/cosmokit").Dict<string, string>, import("@deepseek-ai/cosmokit").Dict<string, string>, "defined">;
+    cwd: z<string, string, "defined">;
+    toolCallTimeoutMs: z<number, number, "defined">;
+    /** Ceiling for the bridge's server instructions (UTF-8 bytes, attribution
+     * included); an oversized description rejects the connection. Mirrors
+     * `dsh-mcp-client`'s own field and default (32768) — a passthrough for a
+     * server whose instructions run longer than the cap. */
+    maxInstructionBytes: z<number, number, "defined">;
+    failOnStartupError: z<boolean, boolean, "defined">;
+    reconnect: z<Schemastery.ObjectS<NoInfer<{
+        enabled: z<boolean, boolean, "defined">;
+        initialDelayMs: z<number, number, "defined">;
+        maxDelayMs: z<number, number, "defined">;
+        maxAttempts: z<number, number, "defined">;
+    }>>, Schemastery.ObjectT<NoInfer<{
+        enabled: z<boolean, boolean, "defined">;
+        initialDelayMs: z<number, number, "defined">;
+        maxDelayMs: z<number, number, "defined">;
+        maxAttempts: z<number, number, "defined">;
+    }>>, "plain">;
+    /** Bridge console-output routing: "log" (default) redirects the spawned
+     * npx child's inherited stderr into a per-spawn log file so its progress
+     * / startup lines stay out of the dsh console; "console" inherits it
+     * (debug). The card's "Reduce log output" toggle (`stderrMode`) overrides
+     * this. See {@link buildBridgeSpawn}. */
+    bridgeStderr: z<"log" | "console", "log" | "console", "defined">;
+    /** Log path override for "log" mode; "" = auto (see
+     * {@link bridgeStderrLogPath}). Absolute paths only. */
+    bridgeStderrLog: z<string, string, "defined">;
     /**
      * The executable the bridge launches with: picked in the picker (a saved
-     * row's `id`) or seeded once by the host's first scan. "" = nothing resolved
-     * yet — there is no auto state to fall back to.
+     * row's `id`) or seeded once by the Host's first scan. "" = nothing
+     * resolved yet — there is no auto state to fall back to.
      */
-    chromePath: z<string, string>;
+    chromePath: z<string, string, "volatile-defined">;
     /** The picker's saved rows — `{ id: path, name: label }`, user-authored. The
-     * host re-normalizes (trim, dedupe, caps) on every read, and a scan merges
+     * Host re-normalizes (trim, dedupe, caps) on every read, and a scan merges
      * what it discovers into them without dropping a name the user chose. */
-    executables: z<({
+    executables: z<NoInfer<({
         id?: string | null | undefined;
         name?: string | null | undefined;
-    } & import("@deepseek-ai/cosmokit").Dict)[], Schemastery.ObjectT<{
-        id: z<string, string>;
-        name: z<string, string>;
-    }>[]>;
+    } & import("@deepseek-ai/cosmokit").Dict)[]>, NoInfer<Schemastery.ObjectT<NoInfer<{
+        id: z<string, string, "defined">;
+        name: z<string, string, "defined">;
+    }>>[]>, "volatile-defined">;
+    /** The ids of saved rows the user dropped. Every run folds what it found
+     * back into the rows, and the found list keeps answering a path the user
+     * just deleted, so without this record a dropped row stood back up on the
+     * very run the deletion queued (measured live 2026-10-12: the (x86)
+     * Windows-executable row read as a delete that never landed). Merge steps
+     * skip every id standing here; a list write carrying the id again clears
+     * it. Host-authored: the card never edits this field. */
+    droppedExecutables: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
     /**
      * **Legacy** MRU of hand-typed executables, newest first. The saved rows
-     * replace it: a host whose settings still carry it folds its paths into the
-     * rows during the first scan (see ./catalog.ts `mergeEntries`), so the field
-     * is read once and never written again.
+     * replace it: a Host whose profile still carries it folds its paths into
+     * the rows during the first scan (see ./catalog.ts `mergeEntries`), so the
+     * field is read once and never written again.
      */
-    chromeCustomPaths: z<string[], string[]>;
+    chromeCustomPaths: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
     /**
-     * Persisted UI "Reduce log output" toggle: "log" captures the bridge's
+     * The card's "Reduce log output" toggle: "log" captures the bridge's
      * stderr into the log file, "console" echoes it (debug). "" follows the
-     * row-config `bridgeStderr` (mirrored into `rowStderr`).
+     * row-config `bridgeStderr`.
+     */
+    stderrMode: z<string, string, "volatile-defined">;
+    /** The mode the bridge actually routes console output through — the UI
+     * toggle when it states one, else the row config. Mirrored live so the
+     * toggle never reads a phantom state (see `resolveStderrMode`). */
+    stderrEffective: z<"log" | "console", "log" | "console", "volatile-defined">;
+    /** Written by the card's **Fetch executables** button; the Host reacts by
+     * re-probing the saved rows and merging what it finds back into them. */
+    refreshExecutablesNonce: z<number, number, "volatile-defined">;
+    /** Written by the card's **Prelaunch Windows Chrome** button; the Host
+     * reacts by running the Windows launch: locate the Windows Chrome, prove
+     * the mirrored-loopback prereq, launch it with a debugging port, and write
+     * the `--browserUrl` connect entry that leaves the bridge in connect mode. */
+    openWindowsChromeNonce: z<number, number, "volatile-defined">;
+    /**
+     * Whether the translation of this row's **standalone** configuration was
+     * offered and turned down. Host-authored:
+     * the card never edits it — only the proposal's dismiss action does.
      */
-    stderrMode: z<string, string>;
+    migrationDismissed: z<boolean, boolean, "volatile-defined">;
     /** Last check/connection failure, human-readable; empty when healthy. */
-    lastError: z<string, string>;
+    lastError: z<string, string, "volatile-defined">;
     /** Known error: the last failure was "no Chrome executable detected". */
-    chromeMissing: z<boolean, boolean>;
+    chromeMissing: z<boolean, boolean, "volatile-defined">;
     /** Executable-run counter (success or failure); completion signal for every
      * executable action the card can take. */
-    executableDiscoveryRevision: z<number, number>;
+    executableDiscoveryRevision: z<number, number, "volatile-defined">;
     /** The version the **selected** executable answered with; "" when nothing
      * answered — nothing picked, a connect mode, or a blocked path. */
-    chromeVersion: z<string, string>;
+    chromeVersion: z<string, string, "volatile-defined">;
     /** Per-row probe status keyed by path: the version the row answered with,
-     * and the failure for a row that is present but not runnable (or blocked).
-     * Base layer, never persisted — the rows themselves live in the user
-     * layer. */
-    executableStatus: z<({
+     * and the failure for a row that is present but not runnable (or blocked). */
+    executableStatus: z<NoInfer<({
         path?: string | null | undefined;
         version?: string | null | undefined;
         error?: string | null | undefined;
-    } & import("@deepseek-ai/cosmokit").Dict)[], Schemastery.ObjectT<{
-        path: z<string, string>;
-        version: z<string, string>;
-        error: z<string, string>;
-    }>[]>;
-    /** The path the bridge actually launches with ("" when nothing is fixed).
-     * Base layer, never persisted. */
-    effectiveChromePath: z<string, string>;
+        note?: string | null | undefined;
+    } & import("@deepseek-ai/cosmokit").Dict)[]>, NoInfer<Schemastery.ObjectT<NoInfer<{
+        path: z<string, string, "defined">;
+        version: z<string, string, "defined">;
+        error: z<string, string, "defined">;
+        note: z<string, string, "defined">;
+    }>>[]>, "volatile-defined">;
+    /** The path the bridge actually launches with ("" when nothing is fixed). */
+    effectiveChromePath: z<string, string, "volatile-defined">;
     /** Where `effectiveChromePath` came from — picked (`"selected"`), row config
-     * (`"row-config"`) or nothing yet (""). Base layer, never persisted. */
-    effectiveSource: z<string, string>;
-    /** Row-config `bridgeStderr` in effect (static base layer; never
-     * persisted) — the fallback when `stderrMode` is "". */
-    rowStderr: z<"log" | "console", "log" | "console">;
-    /** The canonical default extra-flags list (static base layer; never
-     * persisted) — the list the card's **Restore defaults** control appends to
-     * what the editor holds. Mirror of `DEFAULT_EXTRA_FLAGS`. */
-    defaultExtraFlags: z<string[], string[]>;
-    /** The recommended WSL ↔ Windows extra-flags list (static base layer;
-     * never persisted) — the list the card's **Flags WSL** control appends to
-     * what the editor holds, missing entries only. Mirror of
-     * `WSL_EXTRA_FLAGS`. */
-    wslExtraFlags: z<string[], string[]>;
-    /** True while this host runs under WSL and the selected executable is a
-     * Windows binary — the state the card's notice explains. Base layer, never
-     * persisted (see ./platform.ts). */
-    wslWindowsExecutable: z<boolean, boolean>;
-    /** What the **Prelaunch Windows Chrome** run is doing (base layer; never
-     * persisted) — the single field the card derives the button's state, its
-     * disabled reason and the pill's connect-mode muting from. The locate,
-     * prereq, launch and port answers all live host-side (./windows/), so
-     * the card never carries a list of Windows paths or reachability rules. */
-    windowsChromeStatus: z<Schemastery.ObjectS<{
-        state: z<string, string>;
-        port: z<number, number>;
-        error: z<string, string>;
-    }>, Schemastery.ObjectT<{
-        state: z<string, string>;
-        port: z<number, number>;
-        error: z<string, string>;
-    }>>;
-    /** True while the bridge launches with a connect-mode flag
-     * (`--browserUrl` / `--wsEndpoint`): no local executable is then launched
-     * or probed, so the card mutes the picker. Base layer, never persisted. */
-    carriesConnectionMode: z<boolean, boolean>;
-}>>;
+     * (`"row-config"`) or nothing yet (""). */
+    effectiveSource: z<string, string, "volatile-defined">;
+    /** The canonical default extra-flags list — the list the card's **Restore
+     * defaults** control appends to what the editor holds. Mirror of
+     * `DEFAULT_EXTRA_FLAGS`, served so the card carries no copy of it. */
+    defaultExtraFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    /** The recommended WSL ↔ Windows extra-flags list — the list the card's
+     * **Flags WSL** control appends, missing entries only. Mirror of
+     * `WSL_EXTRA_FLAGS`, served so the card carries no copy of it. */
+    wslExtraFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    /** True while this Host runs under WSL and the selected executable is a
+     * Windows binary — the state the card's notice explains (see ./platform.ts). */
+    wslWindowsExecutable: z<boolean, boolean, "volatile-defined">;
+    /** What the **Prelaunch Windows Chrome** run is doing — the single field
+     * the card derives the button's state, its disabled reason and the pill's
+     * connect-mode muting from. Every half (locate, prereq, launch, port) lives
+     * Host-side (./windows/), so the card carries no list of Windows paths or
+     * reachability rules. */
+    windowsChromeStatus: z<NoInfer<Schemastery.ObjectS<NoInfer<{
+        state: z<string, string, "defined">;
+        port: z<number, number, "defined">;
+        error: z<string, string, "defined">;
+    }>>>, NoInfer<Schemastery.ObjectT<NoInfer<{
+        state: z<string, string, "defined">;
+        port: z<number, number, "defined">;
+        error: z<string, string, "defined">;
+    }>>>, "volatile-defined">;
+    /** True while the bridge launches with a connect-mode flag (`--browserUrl`
+     * / `--wsEndpoint`): no local executable is then launched or probed, so the
+     * card mutes the picker. */
+    carriesConnectionMode: z<boolean, boolean, "volatile-defined">;
+    /** The flags a live connection of this component's own kinds actually
+     * launches with — mirrored from the last `resolve`, not from any layer, so
+     * the machine page states what is running rather than what was last
+     * configured. Empty while nothing resolves. */
+    runningFlags: z<NoInfer<string[]>, NoInfer<string[]>, "volatile-defined">;
+    /** The note the last live connection answered with — where its console
+     * output goes, or the Windows URL it connected to. "" when the answer was
+     * silent. */
+    runningNote: z<string, string, "volatile-defined">;
+}>>, "plain">;
+/** What one row's configuration **form** answers with — every field resolved to a
+ * plain, nullable value (`TypeS`, not `TypeT`: the volatile fields stay plain here,
+ * they are not wrapped references). This is the stored/described shape: what a
+ * described settings row carries, and what the card reads out of its snapshot.
+ * What `apply` receives is **not** this shape — every `.volatile()` field of it
+ * arrives as a reference instead, which is why the host half carries its own
+ * runtime view in ./types/config.ts (`ChromeMcpConfig`). */
+export type ConfigFormValues = Schemastery.TypeS<typeof Config>;
 //# sourceMappingURL=schema.d.ts.map