@comecaramelos/dsh-chrome-mcp 0.0.1 → 1.0.0

package/lib/host/constants.js

@@ -0,0 +1,242 @@
+/**
+ * Host-half fixed identifiers, budgets and validation patterns.
+ *
+ * The strings are a public contract — the settings namespace is both the
+ * persistence key and the Web card's slot key — and the budgets are what the
+ * README and the tests quote, so they live here once and every module imports
+ * rather than repeats them.
+ */
+/** Fixed settings namespace; also the client card's slot key. */
+export const SETTINGS_NAMESPACE = "chrome-mcp";
+/** Environment variable that seeds the launch flags for one dsh run. */
+export const FLAGS_ENV_VAR = "DSH_CHROME_MCP_FLAGS";
+/**
+ * Flag entries are appended verbatim to the bridge argv and reach Chrome via
+ * a direct execve (no shell), so shell metacharacters cannot execute here.
+ * What must never reach argv is control characters (newlines, NULs) — they
+ * corrupt the argument framing, so entries may not contain any.
+ */
+export const CONTROL_PATTERN = /[\x00-\x1f\x7f]/u;
+/** Flags every launch carries unless the user overrides them. */
+export const DEFAULT_EXTRA_FLAGS = ["--no-usage-statistics", "--no-performance-crux"];
+/**
+ * The flags the card's **Flags WSL** control appends for a WSL ↔ Windows
+ * debugging setup — a fixed recommendation, not a setting and never persisted.
+ * The shape is what makes it actually reach the browser:
+ *
+ * - the debug port travels as `--chromeArg=--remote-debugging-port=9222`:
+ *   the bridge's strict parser knows only its own option names, so a bare
+ *   `--remote-debugging-port` is reported as `Unknown arguments` and dropped
+ *   before any browser is launched; as a `chromeArg` it lands in Chrome's own
+ *   argv and the debugging port opens (see the "Browser switches" hard
+ *   constraint).
+ *
+ * A `--user-data-dir` entry is deliberately **not** recommended alongside it.
+ * The idea of carrying the profile as a project-rooted `.chrome` was measured
+ * to be impossible for the Windows executable: a Windows `chrome.exe` profile
+ * directory has to live on a Windows-local path — neither the WSL checkout
+ * nor the `\\wsl.localhost` mount can carry its locks (9P) — so the
+ * **Prelaunch Windows Chrome** run launches with its own Windows-native
+ * profile under `%LOCALAPPDATA%`, and the one entry this list recommends is
+ * the debug port the run answers on.
+ */
+export const WSL_EXTRA_FLAGS = ["--chromeArg=--remote-debugging-port=9222"];
+/** Upstream configuration docs surfaced by the client card link. */
+export const CONFIGURATION_DOCS_URL = "https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/configuration.md";
+/** Timeout for one check subprocess (chrome executable probe). */
+export const CHECK_TIMEOUT_MS = 15000;
+/**
+ * Why a Windows `chrome.exe` on a WSL host is **never probed**. The exec answers
+ * successfully — which is what makes the selection look healthy — but answering
+ * means *attaching to the Windows browser session*, and that brings a browser
+ * instance up (measured on WSL2 + Google Chrome 153: `chrome.exe --version`
+ * spawns the browser process plus its crashpad handler). No tool call could
+ * ever drive what it started (the debug pipes do not cross the interop
+ * boundary), so the probe buys nothing and costs a running browser: the check
+ * answers nothing, and the scan keeps the entry visible as `unavailable` with
+ * this reason.
+ */
+export const WSL_WINDOWS_LAUNCH_ERROR = "Windows chrome.exe cannot be launched from WSL — use connect mode (--browserUrl / --wsEndpoint) against a Chrome started with --remote-debugging-port";
+/** Max length of a reported error line. */
+export const ERROR_CAP = 240;
+/**
+ * Log lines the bridge emits after a lost connection recovered — clear
+ * the captured connection error when one shows up.
+ */
+export const BRIDGE_RECONNECTED = /reconnected and re-synced tools/u;
+/** One bridge log level: the levels the captured wrapper shadows. */
+export const LOG_LEVELS = ["trace", "debug", "info", "warn", "error", "fatal"];
+/**
+ * Bridge console-output routing modes (mirrors the reference plugin's gateway
+ * stderr modes). "log" redirects the spawned child's stderr into a log file;
+ * "console" inherits it onto the dsh console.
+ */
+export const BRIDGE_STDERR_MODES = ["log", "console"];
+/** Modes accepted by the `stderrMode` user layer: also the empty string
+ * ("" → follow the row config `bridgeStderr`). */
+export const STDERR_MODE_FIELD_PATTERN = /^(?:log|console)?$/u;
+/** Row-config `bridgeStderrLog` accepts "" (the per-spawn default) or a
+ * POSIX absolute path; nothing else. */
+export const OPTIONAL_PATH_PATTERN = /^(?:\/[^\x00-\x1f\x7f]*|)$/u;
+/**
+ * Candidate POSIX shells used only to redirect the bridge's stderr (see
+ * ./bridge.ts `buildBridgeSpawn`). None found on a bare Windows host → the
+ * redirect is impossible and the spawn stays unwrapped with `fallback:
+ * "platform"`/`"shell"`.
+ */
+export const SH_PATH_CANDIDATES = ["/bin/sh", "/usr/bin/sh"];
+/**
+ * `chromePath` user layer: a filesystem path or a PATH-resolved name. Nothing
+ * travels through a shell here either, so the only hard constraint is that no
+ * control character reaches it; the length cap keeps one absurd value out of
+ * argv and out of the settings document.
+ */
+export const CHROME_PATH_PATTERN = /^[^\x00-\x1f\x7f]{0,4096}$/u;
+/** Upper bound of the **legacy** UI-authored custom-executable MRU (oldest
+ * drops off). The MRU is the older shape of the saved-executables list: a host
+ * whose settings still carry it folds its paths into the `executables` rows the
+ * first time the picker scans (see ./catalog.ts `mergeEntries`), after which the
+ * rows are the only source of saved executables. */
+export const CUSTOM_PATHS_CAP = 10;
+/** Longest display name a saved-executable row may carry — the `name` half is
+ * UI-only (what the pill and the dropdown render), the `id` half is what goes on
+ * the wire. */
+export const CATALOG_NAME_MAX_LENGTH = 200;
+/** Upper bound of the saved-executable rows, merged-list side: the tail drops
+ * off, so a scan that keeps discovering new ids cannot grow the persisted
+ * catalog without limit. */
+export const CATALOG_MAX_LENGTH = 50;
+/**
+ * The Windows-side Chrome/Edge executables the card's **Prelaunch Windows Chrome**
+ * button locates through the WSL interop mount. They are NOT local picker
+ * candidates — the picker must never offer what cannot be launched from
+ * Linux (hard constraint) — the button exists precisely because Windows
+ * Chrome is only usable in *connect* mode. The list is host-served logic: the
+ * card carries no copy of it.
+ */
+export const WINDOWS_CHROME_CANDIDATES = [
+    "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe",
+    "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe",
+    "C:\\Program Files\\Microsoft\\Edge\\Application\\msedge.exe",
+    "C:\\Program Files (x86)\\Microsoft\\Edge\\Application\\msedge.exe"
+];
+/** The debugging port every Windows Chrome launch carries first — kept
+ * coherent with the port the **Flags WSL** control recommends. */
+export const WINDOWS_CHROME_PORT = 9222;
+/** The debugging-port pool the run falls through when the first port is already
+ * carrying a listener: [first, first+1, …]. A listener answers "reachable",
+ * which is what makes the port's own reachability sample its in-use signal. */
+export const WINDOWS_CHROME_PORT_POOL = [9222, 9223, 9224];
+/**
+ * Ports that **only Windows ever listens on** (RPC endpoint mapper, RDP). The
+ * prereq check connects one of them: on a `mirrored` networkingMode host the
+ * connect succeeds, on a NAT host it gives up — the sample must discriminate,
+ * which is exactly what makes it the prereq (measured: 135/3389 CONNECTED
+ * under mirrored, closed ports TIME OUT, never refuse). A port that WSL might
+ * hold locally (445 via Samba) must never be used: it would answer reachable
+ * even when the Windows loopback is unreachable.
+ */
+export const WINDOWS_CHROME_PREREQ_PORTS = [135, 3389];
+/** How long to wait for the launched Windows Chrome to open its port. */
+export const WINDOWS_CHROME_WAIT_MS = 10000;
+/** How long one TCP reachability sample waits before calling the port
+ * unreachable (a NAT host's closed port times out; it never refuses). */
+export const WINDOWS_CHROME_SAMPLE_MS = 1000;
+/** Poll cadence while waiting for a launched Windows Chrome to bind its port. */
+export const WINDOWS_CHROME_POLL_MS = 500;
+/**
+ * The Windows-side working directory the launch runs with. Nothing depends on
+ * it (every argument is absolute), it only keeps relative path resolution off
+ * any UNC (WSL-side) path — the shape the old `cmd.exe /c start` form needed
+ * too (measured 2026-10-04, see .probe/windows-chrome-connect-probe.log).
+ */
+export const WINDOWS_CHROME_START_CWD = "/mnt/c/Windows";
+/** The UNC root modern WSL exports to Windows-side processes. */
+export const WSL_UNC_ROOT = "\\\\wsl.localhost\\";
+/**
+ * The Windows-side directory name the run profiles under
+ * (`%LOCALAPPDATA%\dsh-chrome-mcp\<.chrome|\.chrome-<port>>`). The profile
+ * must live on the Windows filesystem: the WSL-side directories, served to
+ * Windows through 9P, cannot carry the locks Chrome's SQLite tables and its
+ * singleton socket take — a profile rooted there opens every table as a
+ * zero-byte file and shows "an error occurred while opening your profile" on
+ * every launch (measured live 2026-10-04 against Chrome 154). The workspace
+ * keeps a `.chrome` view of this directory through the link the run refreshes
+ * (see `linkWindowsChromeProfile`).
+ */
+export const WINDOWS_CHROME_PROFILE_DIRNAME = "dsh-chrome-mcp";
+/** The connect-mode flag the button writes; its value is the debugging URL. */
+export const BROWSER_URL_FLAG_PREFIX = "--browserUrl=";
+/**
+ * The flags a brand-new Windows profile is launched with, beside the port and
+ * the profile directory. A fresh `--user-data-dir` IS a first run for the
+ * browser: Windows Chrome opens the welcome tab and the default-search-engine
+ * chooser on it, and in connect mode nothing clicks through it — the debugging
+ * session is left sitting on the FRE page. Both flags suppress that
+ * experience, exactly like the manual recipe the button replaces. They travel
+ * on the **browser's own** argv (the `start` line), never as `--chromeArg=`:
+ * here it is Chrome being told at launch what not to show, not the bridge
+ * parser (see the browser-switches bullet under Hard constraints).
+ */
+export const WINDOWS_CHROME_FIRST_RUN_FLAGS = ["--no-first-run", "--no-default-browser-check"];
+/**
+ * The page the Windows launch opens, package-root-relative. It is the one asset
+ * this plugin ships outside `lib`, and it is **read host-side**: the run renders
+ * it with its own answers, writes it through the interop mount next to the
+ * profile directory (so the Windows-side browser can actually read it), and hands
+ * the browser the `file:///…` URL. It exists because the honest answer to "why
+ * did a window just open?" is prose the argv cannot carry — and the usual
+ * placeholder is not an option: `example.com` carries an explicit notice against
+ * being used for automation and tests.
+ */
+export const WINDOWS_CHROME_LANDING_ASSET = "assets/prelaunch-windows-chrome.html";
+/** The base name of the landing file written beside each profile directory
+ * (`…\dsh-chrome-mcp\prelaunch-<port>.html`) — a sibling of the profile, never a
+ * file inside it, so it never reads as profile churn. */
+export const WINDOWS_CHROME_LANDING_BASENAME = "prelaunch";
+/** What one Windows Chrome run may currently be doing (the card derives its
+ * button state, pill muting and disabled reason from this single field).
+ * `"not-applicable"` is the non-WSL answer the plan asks the button to read as
+ * disabled-off; `"launch-failed"` and the rest are the §4 failure states. */
+export const WINDOWS_CHROME_STATES = [
+    "off",
+    "launching",
+    "connected",
+    "unreachable",
+    "not-found",
+    "launch-failed",
+    "not-applicable"
+];
+/** Schema pattern for `windowsChromeStatus.state`. */
+export const WINDOWS_CHROME_STATE_PATTERN = /^(?:off|launching|connected|unreachable|not-found|launch-failed|not-applicable)$/u;
+/**
+ * The prereq answer — the one manual step that is not the button's job
+ * (configuring `~/.wslconfig` is out of scope, reading/reaching it is not).
+ */
+export const WINDOWS_CHROME_PREREQ_ERROR = "Windows Chrome needs networkingMode=mirrored in %USERPROFILE%\\.wslconfig, then wsl --shutdown: today the Windows loopback is not reachable from this WSL host";
+/** Where the effective selection came from (`effectiveSource`): a `chromePath`
+ * written by the card (or seeded once by the host) or the row config. Nothing
+ * resolves on its own, so there is no "auto". */
+export const EFFECTIVE_SOURCES = ["selected", "row-config"];
+/**
+ * Environment variables WSL exports into every distro session. Their presence
+ * answers "are we running inside WSL?" — the first one carries the distro name,
+ * `WSL_INTEROP` the interop-path directory (`/run/WSL/<pid>`).
+ */
+export const WSL_ENV_VARS = ["WSL_DISTRO_NAME", "WSL_DISTRO_LABEL", "WSL_INTEROP"];
+/**
+ * The `binfmt_misc` registration WSL installs for PE binaries: its presence
+ * marks a WSL kernel. It is only the **fallback** signal — inside a host the
+ * launch environment is authoritative, and an empty one is an answer (see
+ * ./platform.ts).
+ */
+export const WSL_INTEROP_MARKER = "/proc/sys/fs/binfmt_misc/WSLInterop";
+/** Windows executables reachable through the interop mount (`/mnt/c/...`) or by
+ * their Windows spelling (UNC, drive letter). */
+export const WINDOWS_PATH_PATTERN = /^(?:\/mnt\/[a-z]\/|\\\\[\w.-]+\\|[a-z]:[\\/])/iu;
+/** The PE suffix. WSL execve's a `.exe` from any path (the Windows loader reads
+ * the Linux filesystem over UNC), so the suffix alone marks a Windows binary. */
+export const WINDOWS_EXE_PATTERN = /\.exe$/iu;
+/** Schema pattern for `effectiveSource` ("" = nothing resolved yet). */
+export const EFFECTIVE_SOURCE_PATTERN = /^(?:selected|row-config)?$/u;
+//# sourceMappingURL=constants.js.map

package/lib/host/constants.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"constants.js","sourceRoot":"","sources":["../../src/host/constants.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,iEAAiE;AACjE,MAAM,CAAC,MAAM,kBAAkB,GAAG,YAAY,CAAC;AAE/C,wEAAwE;AACxE,MAAM,CAAC,MAAM,aAAa,GAAG,sBAAsB,CAAC;AAEpD;;;;;GAKG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,kBAAkB,CAAC;AAElD,iEAAiE;AACjE,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,uBAAuB,EAAE,uBAAuB,CAAC,CAAC;AAEtF;;;;;;;;;;;;;;;;;;;;GAoBG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,CAAC,0CAA0C,CAAC,CAAC;AAE5E,oEAAoE;AACpE,MAAM,CAAC,MAAM,sBAAsB,GAC/B,uFAAuF,CAAC;AAE5F,kEAAkE;AAClE,MAAM,CAAC,MAAM,gBAAgB,GAAG,KAAK,CAAC;AAEtC;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,wBAAwB,GACjC,uJAAuJ,CAAC;AAE5J,2CAA2C;AAC3C,MAAM,CAAC,MAAM,SAAS,GAAG,GAAG,CAAC;AAE7B;;;GAGG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,kCAAkC,CAAC;AAErE,qEAAqE;AACrE,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,OAAO,EAAE,OAAO,EAAE,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,OAAO,CAAU,CAAC;AAExF;;;;GAIG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAqC,CAAC,KAAK,EAAE,SAAS,CAAC,CAAC;AAExF;kDACkD;AAClD,MAAM,CAAC,MAAM,yBAAyB,GAAG,qBAAqB,CAAC;AAE/D;wCACwC;AACxC,MAAM,CAAC,MAAM,qBAAqB,GAAG,6BAA6B,CAAC;AAEnE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,CAAC,SAAS,EAAE,aAAa,CAAU,CAAC;AAEtE;;;;;GAKG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,6BAA6B,CAAC;AAEjE;;;;oDAIoD;AACpD,MAAM,CAAC,MAAM,gBAAgB,GAAG,EAAE,CAAC;AAEnC;;eAEe;AACf,MAAM,CAAC,MAAM,uBAAuB,GAAG,GAAG,CAAC;AAE3C;;4BAE4B;AAC5B,MAAM,CAAC,MAAM,kBAAkB,GAAG,EAAE,CAAC;AAErC;;;;;;;GAOG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG;IACrC,4DAA4D;IAC5D,kEAAkE;IAClE,6DAA6D;IAC7D,mEAAmE;CAC7D,CAAC;AAEX;kEACkE;AAClE,MAAM,CAAC,MAAM,mBAAmB,GAAG,IAAI,CAAC;AAExC;;+EAE+E;AAC/E,MAAM,CAAC,MAAM,wBAAwB,GAAG,CAAC,IAAI,EAAE,IAAI,EAAE,IAAI,CAAU,CAAC;AAEpE;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,2BAA2B,GAAG,CAAC,GAAG,EAAE,IAAI,CAAU,CAAC;AAEhE,yEAAyE;AACzE,MAAM,CAAC,MAAM,sBAAsB,GAAG,KAAK,CAAC;AAE5C;yEACyE;AACzE,MAAM,CAAC,MAAM,wBAAwB,GAAG,IAAI,CAAC;AAE7C,iFAAiF;AACjF,MAAM,CAAC,MAAM,sBAAsB,GAAG,GAAG,CAAC;AAE1C;;;;;GAKG;AACH,MAAM,CAAC,MAAM,wBAAwB,GAAG,gBAAgB,CAAC;AAEzD,iEAAiE;AACjE,MAAM,CAAC,MAAM,YAAY,GAAG,qBAAqB,CAAC;AAElD;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,8BAA8B,GAAG,gBAAgB,CAAC;AAE/D,+EAA+E;AAC/E,MAAM,CAAC,MAAM,uBAAuB,GAAG,eAAe,CAAC;AAEvD;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,8BAA8B,GAAG,CAAC,gBAAgB,EAAE,4BAA4B,CAAU,CAAC;AAExG;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,4BAA4B,GAAG,sCAAsC,CAAC;AAEnF;;yDAEyD;AACzD,MAAM,CAAC,MAAM,+BAA+B,GAAG,WAAW,CAAC;AAE3D;;;6EAG6E;AAC7E,MAAM,CAAC,MAAM,qBAAqB,GAAG;IACjC,KAAK;IACL,WAAW;IACX,WAAW;IACX,aAAa;IACb,WAAW;IACX,eAAe;IACf,gBAAgB;CACV,CAAC;AAEX,sDAAsD;AACtD,MAAM,CAAC,MAAM,4BAA4B,GAAG,mFAAmF,CAAC;AAEhI;;;GAGG;AACH,MAAM,CAAC,MAAM,2BAA2B,GACpC,gKAAgK,CAAC;AAErK;;iDAEiD;AACjD,MAAM,CAAC,MAAM,iBAAiB,GAAG,CAAC,UAAU,EAAE,YAAY,CAAU,CAAC;AAErE;;;;GAIG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,CAAC,iBAAiB,EAAE,kBAAkB,EAAE,aAAa,CAAU,CAAC;AAE5F;;;;;GAKG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,qCAAqC,CAAC;AAExE;iDACiD;AACjD,MAAM,CAAC,MAAM,oBAAoB,GAAG,iDAAiD,CAAC;AAEtF;iFACiF;AACjF,MAAM,CAAC,MAAM,mBAAmB,GAAG,UAAU,CAAC;AAE9C,wEAAwE;AACxE,MAAM,CAAC,MAAM,wBAAwB,GAAG,6BAA6B,CAAC"}

package/lib/host/controller/bridge-run.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Controller — bridge switches.
+ *
+ * How a flag, executable or stderr-mode change reaches the running bridge: the
+ * logical argv is rebuilt through `bridgeConfig` for the current state and
+ * applied as a `fiber.update()`, chained on the fiber's own readiness so a
+ * switch that lands while the first connection is still loading actually takes
+ * effect (cordis restarts a fiber only from `ACTIVE`).
+ */
+import { bridgeConfig } from "../bridge.js";
+import type { BridgeStderrMode, ChromeMcpConfig } from "../types/index.js";
+import type { Controller } from "./state.js";
+/** The row config as the bridge/config builders see it: effective executable,
+ * cleaned row flags. The logical argv shape is unchanged. */
+export declare function configForBridge(controller: Controller, flags: string[]): ChromeMcpConfig;
+/**
+ * Restart the bridge connection with one built config.
+ *
+ * A cordis fiber restarts only from `ACTIVE`: an `update` issued while the
+ * bridge's first connection is still loading is stored but never applied (the
+ * load in flight resolves with the config it started with), and the update
+ * settles `undefined` as if it had worked — so the bridge would silently keep
+ * running with the argv it first spawned with. Chaining the update onto the
+ * fiber's own readiness (the returned thenable settles with the load) is what
+ * makes the switches that land while the bridge is still starting — the first
+ * ones the saved connect-mode flags produce — actually take effect.
+ */
+export declare function restartBridge(controller: Controller, built: ReturnType<typeof bridgeConfig>, note: string): void;
+/** Re-apply the nested bridge with one flags list; failures logged, never thrown. */
+export declare function applyFlags(controller: Controller, flags: string[]): void;
+/**
+ * Switch the effective bridge stderr mode in place — the card's "Reduce log
+ * output" toggle. Only the spawn wrapper changes, but that means restarting the
+ * bridge connection (the stderr routing is fixed at spawn); the flags and the
+ * executable stay exactly as they were.
+ */
+export declare function applyStderrMode(controller: Controller, mode: BridgeStderrMode): void;
+//# sourceMappingURL=bridge-run.d.ts.map

package/lib/host/controller/bridge-run.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"bridge-run.d.ts","sourceRoot":"","sources":["../../../src/host/controller/bridge-run.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,OAAO,EAAE,YAAY,EAAE,MAAM,cAAc,CAAC;AAE5C,OAAO,KAAK,EAAE,gBAAgB,EAAE,eAAe,EAAE,MAAM,mBAAmB,CAAC;AAG3E,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,YAAY,CAAC;AAE7C;6DAC6D;AAC7D,wBAAgB,eAAe,CAAC,UAAU,EAAE,UAAU,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,eAAe,CAExF;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,aAAa,CAAC,UAAU,EAAE,UAAU,EAAE,KAAK,EAAE,UAAU,CAAC,OAAO,YAAY,CAAC,EAAE,IAAI,EAAE,MAAM,GAAG,IAAI,CAUhH;AAED,qFAAqF;AACrF,wBAAgB,UAAU,CAAC,UAAU,EAAE,UAAU,EAAE,KAAK,EAAE,MAAM,EAAE,GAAG,IAAI,CAWxE;AAED;;;;;GAKG;AACH,wBAAgB,eAAe,CAAC,UAAU,EAAE,UAAU,EAAE,IAAI,EAAE,gBAAgB,GAAG,IAAI,CAOpF"}

package/lib/host/controller/bridge-run.js

@@ -0,0 +1,69 @@
+/**
+ * Controller — bridge switches.
+ *
+ * How a flag, executable or stderr-mode change reaches the running bridge: the
+ * logical argv is rebuilt through `bridgeConfig` for the current state and
+ * applied as a `fiber.update()`, chained on the fiber's own readiness so a
+ * switch that lands while the first connection is still loading actually takes
+ * effect (cordis restarts a fiber only from `ACTIVE`).
+ */
+import { bridgeConfig } from "../bridge.js";
+import { flagsSkipCheck } from "../flags.js";
+import { noteStderr } from "./notes.js";
+/** The row config as the bridge/config builders see it: effective executable,
+ * cleaned row flags. The logical argv shape is unchanged. */
+export function configForBridge(controller, flags) {
+    return { ...controller.config, extraFlags: flags, chromePath: controller.state.runningChromePath };
+}
+/**
+ * Restart the bridge connection with one built config.
+ *
+ * A cordis fiber restarts only from `ACTIVE`: an `update` issued while the
+ * bridge's first connection is still loading is stored but never applied (the
+ * load in flight resolves with the config it started with), and the update
+ * settles `undefined` as if it had worked — so the bridge would silently keep
+ * running with the argv it first spawned with. Chaining the update onto the
+ * fiber's own readiness (the returned thenable settles with the load) is what
+ * makes the switches that land while the bridge is still starting — the first
+ * ones the saved connect-mode flags produce — actually take effect.
+ */
+export function restartBridge(controller, built, note) {
+    void Promise.resolve(controller.bridge)
+        .then(() => controller.bridge.update(built.config))
+        .then(() => {
+        controller.state.entry.lastError = "";
+        // Intentionally NOT clearing `chromeMissing`: a successful bridge
+        // update proves the flags took (clears the captured connection error)
+        // but says nothing about the executable.
+    })
+        .catch((error) => controller.ctx.logger.error(`chrome-devtools-mcp(${controller.config.serverName}): ${note}: ${String(error)}`));
+}
+/** Re-apply the nested bridge with one flags list; failures logged, never thrown. */
+export function applyFlags(controller, flags) {
+    const { state } = controller;
+    state.runningFlags = flags;
+    state.entry.carriesConnectionMode = flagsSkipCheck(flags);
+    // Connect mode launches no local executable, so the known "executable
+    // missing" state simply does not apply while it is set.
+    if (state.entry.carriesConnectionMode)
+        state.entry.chromeMissing = false;
+    controller.ctx.logger.info(`chrome-devtools-mcp(${controller.config.serverName}): relaunching bridge with flags [${flags.join(" ")}]`);
+    const built = bridgeConfig(configForBridge(controller, flags), flags, state.runningStderrMode);
+    noteStderr(controller, built);
+    restartBridge(controller, built, "flags update failed");
+}
+/**
+ * Switch the effective bridge stderr mode in place — the card's "Reduce log
+ * output" toggle. Only the spawn wrapper changes, but that means restarting the
+ * bridge connection (the stderr routing is fixed at spawn); the flags and the
+ * executable stay exactly as they were.
+ */
+export function applyStderrMode(controller, mode) {
+    const { state } = controller;
+    state.runningStderrMode = mode;
+    controller.ctx.logger.info(`chrome-devtools-mcp(${controller.config.serverName}): bridge stderr mode → "${mode}" (restarting the bridge connection)`);
+    const built = bridgeConfig(configForBridge(controller, state.runningFlags), state.runningFlags, mode);
+    noteStderr(controller, built);
+    restartBridge(controller, built, `bridge stderr mode switch to "${mode}" failed`);
+}
+//# sourceMappingURL=bridge-run.js.map

package/lib/host/controller/bridge-run.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"bridge-run.js","sourceRoot":"","sources":["../../../src/host/controller/bridge-run.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,OAAO,EAAE,YAAY,EAAE,MAAM,cAAc,CAAC;AAC5C,OAAO,EAAE,cAAc,EAAE,MAAM,aAAa,CAAC;AAG7C,OAAO,EAAE,UAAU,EAAE,MAAM,YAAY,CAAC;AAGxC;6DAC6D;AAC7D,MAAM,UAAU,eAAe,CAAC,UAAsB,EAAE,KAAe;IACnE,OAAO,EAAE,GAAG,UAAU,CAAC,MAAM,EAAE,UAAU,EAAE,KAAK,EAAE,UAAU,EAAE,UAAU,CAAC,KAAK,CAAC,iBAAiB,EAAE,CAAC;AACvG,CAAC;AAED;;;;;;;;;;;GAWG;AACH,MAAM,UAAU,aAAa,CAAC,UAAsB,EAAE,KAAsC,EAAE,IAAY;IACtG,KAAK,OAAO,CAAC,OAAO,CAAC,UAAU,CAAC,MAAM,CAAC;SAClC,IAAI,CAAC,GAAG,EAAE,CAAC,UAAU,CAAC,MAAM,CAAC,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC;SAClD,IAAI,CAAC,GAAG,EAAE;QACP,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,SAAS,GAAG,EAAE,CAAC;QACtC,kEAAkE;QAClE,sEAAsE;QACtE,yCAAyC;IAC7C,CAAC,CAAC;SACD,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,UAAU,CAAC,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,uBAAuB,UAAU,CAAC,MAAM,CAAC,UAAU,MAAM,IAAI,KAAK,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC,CAAC;AAC1I,CAAC;AAED,qFAAqF;AACrF,MAAM,UAAU,UAAU,CAAC,UAAsB,EAAE,KAAe;IAC9D,MAAM,EAAE,KAAK,EAAE,GAAG,UAAU,CAAC;IAC7B,KAAK,CAAC,YAAY,GAAG,KAAK,CAAC;IAC3B,KAAK,CAAC,KAAK,CAAC,qBAAqB,GAAG,cAAc,CAAC,KAAK,CAAC,CAAC;IAC1D,sEAAsE;IACtE,wDAAwD;IACxD,IAAI,KAAK,CAAC,KAAK,CAAC,qBAAqB;QAAE,KAAK,CAAC,KAAK,CAAC,aAAa,GAAG,KAAK,CAAC;IACzE,UAAU,CAAC,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,uBAAuB,UAAU,CAAC,MAAM,CAAC,UAAU,qCAAqC,KAAK,CAAC,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;IACvI,MAAM,KAAK,GAAG,YAAY,CAAC,eAAe,CAAC,UAAU,EAAE,KAAK,CAAC,EAAE,KAAK,EAAE,KAAK,CAAC,iBAAiB,CAAC,CAAC;IAC/F,UAAU,CAAC,UAAU,EAAE,KAAK,CAAC,CAAC;IAC9B,aAAa,CAAC,UAAU,EAAE,KAAK,EAAE,qBAAqB,CAAC,CAAC;AAC5D,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,eAAe,CAAC,UAAsB,EAAE,IAAsB;IAC1E,MAAM,EAAE,KAAK,EAAE,GAAG,UAAU,CAAC;IAC7B,KAAK,CAAC,iBAAiB,GAAG,IAAI,CAAC;IAC/B,UAAU,CAAC,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,uBAAuB,UAAU,CAAC,MAAM,CAAC,UAAU,4BAA4B,IAAI,sCAAsC,CAAC,CAAC;IACtJ,MAAM,KAAK,GAAG,YAAY,CAAC,eAAe,CAAC,UAAU,EAAE,KAAK,CAAC,YAAY,CAAC,EAAE,KAAK,CAAC,YAAY,EAAE,IAAI,CAAC,CAAC;IACtG,UAAU,CAAC,UAAU,EAAE,KAAK,CAAC,CAAC;IAC9B,aAAa,CAAC,UAAU,EAAE,KAAK,EAAE,iCAAiC,IAAI,UAAU,CAAC,CAAC;AACtF,CAAC"}

package/lib/host/controller/captures.d.ts

@@ -0,0 +1,22 @@
+import type { Controller } from "./state.js";
+/**
+ * Fold bridge log lines into the base layer. dsh-mcp-client reports connection
+ * problems only through its logger (reconnect warnings with "connection
+ * failed/lost", give-up errors, spawn failures), and a module plugin has no
+ * push channel to clients — so the newest failure line becomes `lastError`, and
+ * the "reconnected and re-synced tools" success line clears it. The wrapper
+ * lives only on the bridge scope; our own logs bypass it, so our own warns never
+ * masquerade as connection errors.
+ */
+export declare function noteBridgeLog(controller: Controller, level: string, args: unknown[]): void;
+/**
+ * Register the tool-call status capture: browser-level failures surface only as
+ * the calling agent's tool result, never on the bridge logger, so a settled
+ * result whose registered name is prefixed `mcp__<serverName>__` and carries
+ * `isError` writes the failure into the base layer; a successful chrome-tool call
+ * clears both, so the card reports current health. The body is wrapped in
+ * try/catch (warn only — a capture fault must never break a tool call) and
+ * returns `next()` unchanged.
+ */
+export declare function registerToolCapture(controller: Controller): void;
+//# sourceMappingURL=captures.d.ts.map

package/lib/host/controller/captures.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"captures.d.ts","sourceRoot":"","sources":["../../../src/host/controller/captures.ts"],"names":[],"mappings":"AAcA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,YAAY,CAAC;AAE7C;;;;;;;;GAQG;AACH,wBAAgB,aAAa,CAAC,UAAU,EAAE,UAAU,EAAE,KAAK,EAAE,MAAM,EAAE,IAAI,EAAE,OAAO,EAAE,GAAG,IAAI,CAW1F;AAED;;;;;;;;GAQG;AACH,wBAAgB,mBAAmB,CAAC,UAAU,EAAE,UAAU,GAAG,IAAI,CAgBhE"}

package/lib/host/controller/captures.js

@@ -0,0 +1,60 @@
+/**
+ * Controller — the two capture paths that reach the base layer.
+ *
+ * A module plugin has no push channel to clients, so both capture paths write
+ * straight into the base layer: the newest bridge-log failure line becomes
+ * `lastError`, and a settled browser-tool result that failed does the same (the
+ * two never duplicate — bridge logs never reach the tool surface and vice
+ * versa). Each capture is classified into the known "executable missing" flag so
+ * the single red status dot keeps its whole story.
+ */
+import { BRIDGE_RECONNECTED } from "../constants.js";
+import { firstLine, isChromeMissing, toolResultNote } from "../status.js";
+/**
+ * Fold bridge log lines into the base layer. dsh-mcp-client reports connection
+ * problems only through its logger (reconnect warnings with "connection
+ * failed/lost", give-up errors, spawn failures), and a module plugin has no
+ * push channel to clients — so the newest failure line becomes `lastError`, and
+ * the "reconnected and re-synced tools" success line clears it. The wrapper
+ * lives only on the bridge scope; our own logs bypass it, so our own warns never
+ * masquerade as connection errors.
+ */
+export function noteBridgeLog(controller, level, args) {
+    const message = args
+        .map((arg) => (arg instanceof Error ? (arg.stack ?? arg.message ?? String(arg)) : String(arg)))
+        .join(" ");
+    if (level === "error" || level === "warn") {
+        controller.state.entry.lastError = firstLine(message);
+        controller.state.entry.chromeMissing = isChromeMissing(message);
+    }
+    else if (level === "info" && BRIDGE_RECONNECTED.test(message)) {
+        controller.state.entry.lastError = "";
+        controller.state.entry.chromeMissing = false;
+    }
+}
+/**
+ * Register the tool-call status capture: browser-level failures surface only as
+ * the calling agent's tool result, never on the bridge logger, so a settled
+ * result whose registered name is prefixed `mcp__<serverName>__` and carries
+ * `isError` writes the failure into the base layer; a successful chrome-tool call
+ * clears both, so the card reports current health. The body is wrapped in
+ * try/catch (warn only — a capture fault must never break a tool call) and
+ * returns `next()` unchanged.
+ */
+export function registerToolCapture(controller) {
+    const toolPrefix = `mcp__${controller.config.serverName}__`;
+    controller.ctx.on("tools/post-execute", async (exec, result, next) => {
+        try {
+            if (typeof exec.name === "string" && exec.name.startsWith(toolPrefix)) {
+                const note = toolResultNote(exec.name, result);
+                controller.state.entry.lastError = note ?? "";
+                controller.state.entry.chromeMissing = note === null ? false : isChromeMissing(note);
+            }
+        }
+        catch (error) {
+            controller.ctx.logger.warn(`chrome-devtools-mcp(${controller.config.serverName}): tool status capture failed: ${String(error)}`);
+        }
+        return next();
+    });
+}
+//# sourceMappingURL=captures.js.map

package/lib/host/controller/captures.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"captures.js","sourceRoot":"","sources":["../../../src/host/controller/captures.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AACH,OAAO,EAAE,kBAAkB,EAAE,MAAM,iBAAiB,CAAC;AACrD,OAAO,EAAE,SAAS,EAAE,eAAe,EAAE,cAAc,EAAE,MAAM,cAAc,CAAC;AAK1E;;;;;;;;GAQG;AACH,MAAM,UAAU,aAAa,CAAC,UAAsB,EAAE,KAAa,EAAE,IAAe;IAChF,MAAM,OAAO,GAAG,IAAI;SACf,GAAG,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,CAAC,GAAG,YAAY,KAAK,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,KAAK,IAAI,GAAG,CAAC,OAAO,IAAI,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,CAAC;SAC9F,IAAI,CAAC,GAAG,CAAC,CAAC;IACf,IAAI,KAAK,KAAK,OAAO,IAAI,KAAK,KAAK,MAAM,EAAE,CAAC;QACxC,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,SAAS,GAAG,SAAS,CAAC,OAAO,CAAC,CAAC;QACtD,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,aAAa,GAAG,eAAe,CAAC,OAAO,CAAC,CAAC;IACpE,CAAC;SAAM,IAAI,KAAK,KAAK,MAAM,IAAI,kBAAkB,CAAC,IAAI,CAAC,OAAO,CAAC,EAAE,CAAC;QAC9D,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,SAAS,GAAG,EAAE,CAAC;QACtC,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,aAAa,GAAG,KAAK,CAAC;IACjD,CAAC;AACL,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,mBAAmB,CAAC,UAAsB;IACtD,MAAM,UAAU,GAAG,QAAQ,UAAU,CAAC,MAAM,CAAC,UAAU,IAAI,CAAC;IAC3D,UAAU,CAAC,GAAG,CAAC,EAA0H,CACtI,oBAAoB,EACpB,KAAK,EAAE,IAAuB,EAAE,MAAsB,EAAE,IAAmB,EAAE,EAAE;QAC3E,IAAI,CAAC;YACD,IAAI,OAAO,IAAI,CAAC,IAAI,KAAK,QAAQ,IAAI,IAAI,CAAC,IAAI,CAAC,UAAU,CAAC,UAAU,CAAC,EAAE,CAAC;gBACpE,MAAM,IAAI,GAAG,cAAc,CAAC,IAAI,CAAC,IAAI,EAAE,MAAM,CAAC,CAAC;gBAC/C,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,SAAS,GAAG,IAAI,IAAI,EAAE,CAAC;gBAC9C,UAAU,CAAC,KAAK,CAAC,KAAK,CAAC,aAAa,GAAG,IAAI,KAAK,IAAI,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,eAAe,CAAC,IAAI,CAAC,CAAC;YACzF,CAAC;QACL,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACb,UAAU,CAAC,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,uBAAuB,UAAU,CAAC,MAAM,CAAC,UAAU,kCAAkC,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;QACrI,CAAC;QACD,OAAO,IAAI,EAAE,CAAC;IAClB,CAAC,CAAC,CAAC;AACX,CAAC"}

package/lib/host/controller/commits.d.ts

@@ -0,0 +1,4 @@
+import type { Controller } from "./state.js";
+/** Route one settings commit. */
+export declare function onSettingsChange(controller: Controller): void;
+//# sourceMappingURL=commits.d.ts.map

package/lib/host/controller/commits.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"commits.d.ts","sourceRoot":"","sources":["../../../src/host/controller/commits.ts"],"names":[],"mappings":"AAmBA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,YAAY,CAAC;AAE7C,iCAAiC;AACjC,wBAAgB,gBAAgB,CAAC,UAAU,EAAE,UAAU,GAAG,IAAI,CAoD7D"}

package/lib/host/controller/commits.js

@@ -0,0 +1,75 @@
+/**
+ * Controller — settings-commit routing.
+ *
+ * One settings commit may carry any of five changes; this routes them in the
+ * reference's order: a flags drift restarts the bridge, an executable change
+ * picked by the card restarts it and re-runs the discovery, a rows change is
+ * folded into the same run (never a second one), the stderr toggle restarts the
+ * connection with/without the stderr wrapper, and the two trigger nonces (the
+ * fetch button, the Windows button) fire their runs. The first commit is the
+ * registration run — a persisted Windows trigger folds in silently so booting a
+ * host never launches a Windows browser by itself.
+ */
+import { normalizeEntries } from "../catalog.js";
+import { sameFlags } from "../flags.js";
+import { resolveEffectiveChromePath, resolveStderrMode } from "../values.js";
+import { applyFlags, applyStderrMode } from "./bridge-run.js";
+import { applyChromePath, queue, sameEntries } from "./runs.js";
+/** Route one settings commit. */
+export function onSettingsChange(controller) {
+    const { state } = controller;
+    try {
+        const current = state.source();
+        if (!sameFlags(current.extraFlags, state.runningFlags))
+            applyFlags(controller, current.extraFlags);
+        // Executable changes come from the persisted `chromePath` the card wrote
+        // (a row's `id`). They restart the bridge connection and re-run the
+        // discovery, because a different executable reads a different machine. A
+        // path the host seeded itself keeps standing until the user picks one:
+        // the seed is written into the persisted layer, and until that write is
+        // visible a commit must not resolve back to "nothing selected".
+        const userLayer = typeof current.chromePath === "string" ? current.chromePath.trim() : "";
+        if (userLayer !== "")
+            state.seenUserSelection = true;
+        const seededCarry = state.seededPath !== "" && !state.seenUserSelection ? state.seededPath : "";
+        const nextChromePath = resolveEffectiveChromePath(userLayer !== "" ? userLayer : seededCarry, controller.rowChromePath);
+        const nextSource = userLayer !== "" ? "selected" : seededCarry !== "" ? "selected" : controller.rowChromePath !== "" ? "row-config" : "";
+        if (nextChromePath !== state.runningChromePath)
+            applyChromePath(controller, nextChromePath, nextSource);
+        // Rows changes touch the list, never the connection.
+        const nextExecutables = normalizeEntries(current.executables);
+        const rowsChanged = !sameEntries(nextExecutables, state.runningExecutables);
+        // The "Reduce log output" toggle lives here too: a change of the
+        // effective stderr mode restarts the bridge connection with / without
+        // the stderr-capturing wrapper.
+        const nextStderrMode = resolveStderrMode(current.stderrMode, controller.config.bridgeStderr);
+        if (nextStderrMode !== state.runningStderrMode)
+            applyStderrMode(controller, nextStderrMode);
+        const firstCommit = state.lastRefreshNonce === void 0;
+        const refreshChanged = !firstCommit && current.refreshExecutablesNonce !== state.lastRefreshNonce;
+        const windowsChanged = !firstCommit && current.openWindowsChromeNonce !== state.lastWindowsNonce;
+        state.lastRefreshNonce = current.refreshExecutablesNonce;
+        state.lastWindowsNonce = current.openWindowsChromeNonce;
+        if (firstCommit) {
+            // The registration run: discovery + probe, no separate call. A
+            // persisted Windows trigger folds in silently — booting a host must
+            // never launch a Windows browser by itself.
+            queue(controller, "probe");
+        }
+        else {
+            // The card's **Search executables** button. A rows change is folded
+            // into the same run rather than a second one, so the client waits on
+            // exactly one revision bump.
+            if (refreshChanged || rowsChanged)
+                queue(controller, "probe");
+            // The card's **Prelaunch Windows Chrome** button: one Windows run,
+            // sharing this chain (one run at a time).
+            if (windowsChanged)
+                queue(controller, "windows");
+        }
+    }
+    catch (error) {
+        controller.ctx.logger.error(`chrome-devtools-mcp(${controller.config.serverName}): ${String(error)}`);
+    }
+}
+//# sourceMappingURL=commits.js.map

package/lib/host/controller/commits.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"commits.js","sourceRoot":"","sources":["../../../src/host/controller/commits.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AACH,OAAO,EAAE,gBAAgB,EAAE,MAAM,eAAe,CAAC;AACjD,OAAO,EAAE,SAAS,EAAE,MAAM,aAAa,CAAC;AACxC,OAAO,EAAE,0BAA0B,EAAE,iBAAiB,EAAE,MAAM,cAAc,CAAC;AAG7E,OAAO,EAAE,UAAU,EAAE,eAAe,EAAE,MAAM,iBAAiB,CAAC;AAC9D,OAAO,EAAE,eAAe,EAAE,KAAK,EAAE,WAAW,EAAE,MAAM,WAAW,CAAC;AAGhE,iCAAiC;AACjC,MAAM,UAAU,gBAAgB,CAAC,UAAsB;IACnD,MAAM,EAAE,KAAK,EAAE,GAAG,UAAU,CAAC;IAC7B,IAAI,CAAC;QACD,MAAM,OAAO,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC;QAC/B,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,UAAU,EAAE,KAAK,CAAC,YAAY,CAAC;YAAE,UAAU,CAAC,UAAU,EAAE,OAAO,CAAC,UAAU,CAAC,CAAC;QAEnG,yEAAyE;QACzE,oEAAoE;QACpE,yEAAyE;QACzE,uEAAuE;QACvE,wEAAwE;QACxE,gEAAgE;QAChE,MAAM,SAAS,GAAG,OAAO,OAAO,CAAC,UAAU,KAAK,QAAQ,CAAC,CAAC,CAAC,OAAO,CAAC,UAAU,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QAC1F,IAAI,SAAS,KAAK,EAAE;YAAE,KAAK,CAAC,iBAAiB,GAAG,IAAI,CAAC;QACrD,MAAM,WAAW,GAAG,KAAK,CAAC,UAAU,KAAK,EAAE,IAAI,CAAC,KAAK,CAAC,iBAAiB,CAAC,CAAC,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC,CAAC,EAAE,CAAC;QAChG,MAAM,cAAc,GAAG,0BAA0B,CAAC,SAAS,KAAK,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,WAAW,EAAE,UAAU,CAAC,aAAa,CAAC,CAAC;QACxH,MAAM,UAAU,GACZ,SAAS,KAAK,EAAE,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,WAAW,KAAK,EAAE,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,UAAU,CAAC,aAAa,KAAK,EAAE,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC,EAAE,CAAC;QAC1H,IAAI,cAAc,KAAK,KAAK,CAAC,iBAAiB;YAAE,eAAe,CAAC,UAAU,EAAE,cAAc,EAAE,UAAU,CAAC,CAAC;QAExG,qDAAqD;QACrD,MAAM,eAAe,GAAG,gBAAgB,CAAC,OAAO,CAAC,WAAW,CAAC,CAAC;QAC9D,MAAM,WAAW,GAAG,CAAC,WAAW,CAAC,eAAe,EAAE,KAAK,CAAC,kBAAkB,CAAC,CAAC;QAE5E,iEAAiE;QACjE,sEAAsE;QACtE,gCAAgC;QAChC,MAAM,cAAc,GAAG,iBAAiB,CAAC,OAAO,CAAC,UAAU,EAAE,UAAU,CAAC,MAAM,CAAC,YAAY,CAAC,CAAC;QAC7F,IAAI,cAAc,KAAK,KAAK,CAAC,iBAAiB;YAAE,eAAe,CAAC,UAAU,EAAE,cAAc,CAAC,CAAC;QAE5F,MAAM,WAAW,GAAG,KAAK,CAAC,gBAAgB,KAAK,KAAK,CAAC,CAAC;QACtD,MAAM,cAAc,GAAG,CAAC,WAAW,IAAI,OAAO,CAAC,uBAAuB,KAAK,KAAK,CAAC,gBAAgB,CAAC;QAClG,MAAM,cAAc,GAAG,CAAC,WAAW,IAAI,OAAO,CAAC,sBAAsB,KAAK,KAAK,CAAC,gBAAgB,CAAC;QACjG,KAAK,CAAC,gBAAgB,GAAG,OAAO,CAAC,uBAAuB,CAAC;QACzD,KAAK,CAAC,gBAAgB,GAAG,OAAO,CAAC,sBAAsB,CAAC;QACxD,IAAI,WAAW,EAAE,CAAC;YACd,+DAA+D;YAC/D,oEAAoE;YACpE,4CAA4C;YAC5C,KAAK,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;QAC/B,CAAC;aAAM,CAAC;YACJ,oEAAoE;YACpE,qEAAqE;YACrE,6BAA6B;YAC7B,IAAI,cAAc,IAAI,WAAW;gBAAE,KAAK,CAAC,UAAU,EAAE,OAAO,CAAC,CAAC;YAC9D,mEAAmE;YACnE,0CAA0C;YAC1C,IAAI,cAAc;gBAAE,KAAK,CAAC,UAAU,EAAE,SAAS,CAAC,CAAC;QACrD,CAAC;IACL,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACb,UAAU,CAAC,GAAG,CAAC,MAAM,CAAC,KAAK,CAAC,uBAAuB,UAAU,CAAC,MAAM,CAAC,UAAU,MAAM,MAAM,CAAC,KAAK,CAAC,EAAE,CAAC,CAAC;IAC1G,CAAC;AACL,CAAC"}

package/lib/host/controller/controller.d.ts

@@ -0,0 +1,40 @@
+import { type WindowsChromeRunOptions } from "../windows/index.js";
+import type { ChromeMcpConfig, PluginContext, SettingsResolved, WindowsChromeRun } from "../types/index.js";
+/** The live state one apply() keeps in memory. */
+export interface ChromeMcpController {
+    /** The composition base layer served alongside the user layer. */
+    readonly entry: SettingsResolved;
+    /** Swap the live resolved settings source (installSection hook). */
+    setSource(next: () => SettingsResolved): void;
+    /** Route one settings commit: relaunch on flag or executable drift, and run
+     * one executable refresh on the search trigger. */
+    onSettingsChange(): void;
+    /** Run one executable refresh (probe the candidates, merge what is found
+     * into the saved rows, seed a never-configured host). Runs are serialized so
+     * rapid actions never interleave. */
+    run(): Promise<unknown>;
+    /** Run the Windows Chrome path once (locate, prereq, port, launch, connect)
+     * on the same one-run-at-a-time chain the button drives through, and answer
+     * with what the run stated. This is the MCP-tool surface of the button: the
+     * trigger is the call itself — nothing is persisted, so a booting host never
+     * launches a browser on its own. Resolves after the run settles. */
+    prelaunchWindowsChrome(): Promise<string>;
+}
+/**
+ * Optional overrides for tests and diagnostics: the Windows Chrome run is the
+ * only half that reaches outside the process (it opens TCP sockets and spawns
+ * through the interop mount), so a wiring test replaces just this one — the same
+ * injectability rule every other platform half follows.
+ */
+export type ChromeMcpControllerDeps = {
+    runWindowsChrome?: (options: WindowsChromeRunOptions) => Promise<WindowsChromeRun>;
+};
+/**
+ * Build the live state for one bridge + card pairing.
+ * @param ctx - plugin context.
+ * @param config - validated row config.
+ * @param deps - optional host overrides (tests replace the Windows run;
+ * everything else resolves from this process).
+ */
+export declare function createChromeMcpController(ctx: PluginContext, config: ChromeMcpConfig, deps?: ChromeMcpControllerDeps): ChromeMcpController;
+//# sourceMappingURL=controller.d.ts.map

package/lib/host/controller/controller.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"controller.d.ts","sourceRoot":"","sources":["../../../src/host/controller/controller.ts"],"names":[],"mappings":"AA6BA,OAAO,EAA2B,KAAK,uBAAuB,EAAE,MAAM,qBAAqB,CAAC;AAE5F,OAAO,KAAK,EAER,eAAe,EAEf,aAAa,EACb,gBAAgB,EAChB,gBAAgB,EACnB,MAAM,mBAAmB,CAAC;AAS3B,kDAAkD;AAClD,MAAM,WAAW,mBAAmB;IAChC,kEAAkE;IAClE,QAAQ,CAAC,KAAK,EAAE,gBAAgB,CAAC;IACjC,oEAAoE;IACpE,SAAS,CAAC,IAAI,EAAE,MAAM,gBAAgB,GAAG,IAAI,CAAC;IAC9C;uDACmD;IACnD,gBAAgB,IAAI,IAAI,CAAC;IACzB;;yCAEqC;IACrC,GAAG,IAAI,OAAO,CAAC,OAAO,CAAC,CAAC;IACxB;;;;wEAIoE;IACpE,sBAAsB,IAAI,OAAO,CAAC,MAAM,CAAC,CAAC;CAC7C;AAED;;;;;GAKG;AACH,MAAM,MAAM,uBAAuB,GAAG;IAClC,gBAAgB,CAAC,EAAE,CAAC,OAAO,EAAE,uBAAuB,KAAK,OAAO,CAAC,gBAAgB,CAAC,CAAC;CACtF,CAAC;AAEF;;;;;;GAMG;AACH,wBAAgB,yBAAyB,CAAC,GAAG,EAAE,aAAa,EAAE,MAAM,EAAE,eAAe,EAAE,IAAI,GAAE,uBAA4B,GAAG,mBAAmB,CAwI9I"}