/**
 * Shared adapter/daemon budgets for an explicit Mojo close.
 *
 * This is deliberately a dependency-free module: worker-pool tests mock the
 * Mojo backend as a process boundary, but both sides still need one source of
 * truth for the nested timeout relationship.
 */
export declare const MOJO_CLI_TIMEOUT_MS = 60000;
export declare const MOJO_DESTROY_SETTLE_MS = 8000;
export declare const MOJO_EXPLICIT_CLOSE_RESULT_TIMEOUT_MS = 75000;
/**
 * Budget for PROVING the local mojo child is gone during an explicit close.
 *
 * SIGTERM alone is not proof: a child that ignores it keeps running while the row
 * is published as closed, and a closed row is filtered out of the device-isolation
 * inventory — so the blocker disappears with the process still alive. Split as
 * SIGTERM grace, then SIGKILL, then a final wait.
 */
export declare const MOJO_CHILD_TERMINATION_PROOF_MS = 2000;
export declare const MOJO_EXPLICIT_CLOSE_HEADROOM_MS: number;
//# sourceMappingURL=mojo-budgets.d.ts.map