/**
 * The LIVE installed wicked-garden plugin, as the catalog reports it (wicked-studio#388).
 *
 * The daemon-owned root holds a BASELINE — a content-addressed copy of the plugin as it was when
 * `refresh-baseline` last captured it — and publishes immutable snapshots from it. Nothing said
 * whether the plugin ON DISK had moved since. In the MCP S8 dogfood the published snapshot was
 * generation 5, captured before wicked-garden#1192 added `scripts/mcp/shim.py`, so the first
 * governed run failed with `scripts/mcp/shim.py: not found under the plugin root
 * …/snapshots/000005`. The remedy (Refresh baseline → Publish) worked, but nothing on the page had
 * told the operator the root was behind their install — and every MCP call a worker makes goes
 * through that shim.
 *
 * The comparison is the CONTENT HASH, the same identity `refresh-baseline` decides on
 * (`hashFileSet` over the dependency closure). Not the version string: two installs of one version
 * with different bytes are two baselines, and a checkout that moved without a version bump is the
 * dogfood's exact case. The runtime shares a background probe across catalog and diagnostics reads (crew#1021).
 */
import { type FileRecord } from './tree.js';
import { type PluginSource } from './plugin-source.js';
import type { SkillSourceKind } from '../core/types.js';
/** What `GET /skills` reports about the installed plugin (`SkillsManifestResponse.installed`). */
export interface InstalledPluginState {
    source: {
        kind: SkillSourceKind;
        path: string;
        plugin_version: string;
    };
    /** HEAD sha for a `checkout` source; `null` otherwise (or when git could not answer). */
    git_sha: string | null;
    /**
     * The content hash of the installed bundle — comparable with `SkillManifest.baseline`. `null`
     * when the bundle could not be read, and then `unreadable` says why: a comparison crew could not
     * make is stated, never reported as agreement.
     */
    baseline: string | null;
    unreadable: string | null;
}
/**
 * The installed plugin's identity, or `null` when no plugin is installed at all (the unseeded case
 * the catalog's own 503 already covers). `discover` / `bundle` / `hash` are injectable so a test
 * never reads the developer's own config dir.
 */
export declare function installedPluginState(opts?: {
    discover?: () => PluginSource | null;
    bundle?: (root: string) => FileRecord[];
    hash?: (files: FileRecord[]) => string;
    git?: (source: PluginSource) => {
        git_sha: string | null;
    };
}): InstalledPluginState | null;
/**
 * crew#1021: the background probe yields before discovery, paces bundle enumeration, and uses
 * asynchronous file and git reads. The synchronous entry point remains for boot/CLI callers.
 */
export declare function installedPluginStateAsync(opts?: {
    discover?: () => PluginSource | null;
}): Promise<InstalledPluginState | null>;
//# sourceMappingURL=installed.d.ts.map