export interface CmdGuardStatus {
    supported: boolean;
    installed: boolean;
    autorunValue?: string;
    rulesPresent: boolean;
    ruleCount?: number;
    mode?: string;
}
export declare function isCmdGuardInstalled(): boolean;
export declare function getCmdGuardStatus(): CmdGuardStatus;
export interface InstallCmdGuardArgs {
    /** Reserved for future use. */
    profiles?: string;
}
/** `fullcourtdefense install-cmd-guard` — enable interactive cmd.exe blocking. */
export declare function installCmdGuardCommand(_args?: InstallCmdGuardArgs): Promise<void>;
/** `fullcourtdefense uninstall-cmd-guard` */
export declare function uninstallCmdGuardCommand(): Promise<void>;
/** Refresh shared rules JSON when cmd guard is installed. */
export declare function refreshCmdGuardRules(): void;
/**
 * Self-heal a stale/broken cmd-guard AutoRun. Two failure shapes are covered:
 *
 *  1. Registry references our autorun bat but the FILE was deleted (manual
 *     cleanup, interrupted uninstall) — every cmd.exe errors on startup and
 *     poisons `cmd /c` exit codes to 1.
 *  2. The bat EXISTS but its doskey macros point at a node.exe or checker
 *     script that no longer exists (uninstall/upgrade removed the install
 *     root but left the per-user bat) — every wrapped command (docker, git,
 *     kubectl, …) fails with "cannot find the path specified".
 *
 * In both cases: strip OUR fragment from AutoRun (a customer's own entries
 * survive) and delete our orphaned guard files. Returns true when repaired.
 */
export declare function repairStaleCmdAutorun(): boolean;