import type { Employee, Engine, JinnConfig } from "../shared/types.js";
/**
 * Can this built-in employee actually run, and if not, which setting fixes it?
 *
 * The Todo Dispatcher and the Todo Shaper ask exactly this before spending
 * anything, and both have to answer with the knob the operator would turn: a
 * system employee that cannot attach the company tools is a session that will
 * burn a turn and achieve nothing, and one whose engine is missing never starts
 * at all. Sharing the answer keeps the two routes from drifting into two
 * different explanations of the same broken configuration.
 */
export type SystemEmployeePreflight = {
    ok: true;
    engine: Engine;
} | {
    ok: false;
    status: number;
    error: string;
};
export declare function preflightSystemEmployee(opts: {
    employee: Employee;
    /** How the employee is named the first time, e.g. "Todo Dispatcher". */
    label: string;
    /** How its engine override is named, e.g. "Dispatcher". */
    settingLabel: string;
    engineName: string;
    globalMcp: JinnConfig["mcp"];
    getEngine: (name: string) => Engine | undefined;
}): SystemEmployeePreflight;
//# sourceMappingURL=system-employee-spawn.d.ts.map