import type { BrowserProbe } from './web-install-types.js';
/**
 * Is the pinned browser on disk? Never throws, never spawns, never downloads.
 *
 * **It answers about the artifact `launch()` starts** (R6). `executablePath()`
 * names the `chromium` build, but `chromium.launch()` with no options and
 * `headless` defaulting true resolves `chromium-headless-shell`
 * (`registry.getExecutableName`) — a SEPARATE ~271 MiB download. Probing the
 * full chromium therefore answered "installed" for a machine on which no op
 * could launch: `launch()` failed, S1's net downloaded, the probe kept saying
 * installed, and `peaks web install` short-circuited to a no-op success. See
 * `headlessShellDir` for how the right path is obtained.
 *
 * `version` is reported even when the executable is missing, because "the
 * package is cached but its browser is not" is a different diagnosis from
 * "nothing is installed" — the first is one `peaks web install` away.
 */
export declare function probeBrowserInstalled(): Promise<BrowserProbe>;