/**
 * The AICOMMANDER_CONFIG_DIR override, if it is one the agent would accept.
 *
 * `null` covers both "not set" and "set to something the agent refuses to start
 * with" (a relative path) — the latter is not silently substituted, it is
 * REPORTED by storage.ts's `config.override` check, which is the one place that
 * verdict belongs.
 */
export declare function doctorConfigDirOverride(): string | null;
/**
 * The jobs root, resolved as job-manager.ts's `resolveJobsRoot` resolves it —
 * with the env override read read-only, and the rest delegated so the ladder
 * below it (a root service's /var/lib, the per-user data dir, the Windows
 * LOCALAPPDATA shape) has exactly one implementation. `doctor-paths.test.ts`
 * pins the two against each other.
 *
 * `null` when AICOMMANDER_CONFIG_DIR is set to something the agent refuses to
 * start with: there is then no jobs directory on this machine to measure, and
 * the checks that wanted one report themselves `skipped` pointing at the
 * `config.override` check, rather than probing a path nothing would ever use.
 */
export declare function doctorJobsRoot(configDir?: string): string | null;
/** The reason a check has no jobs root to look at, in one sentence. */
export declare const NO_JOBS_ROOT_REASON: string;
/**
 * The diagnostic log directory, resolved as diag-log.ts's `resolveDiagLogDir`
 * resolves it — and, unlike it, without `envConfigDir()` underneath.
 *
 * The one behaviour deliberately reproduced rather than "fixed" is the fallback
 * for an override the agent refuses: `resolveDiagLogDir` catches the throw and
 * lands on the platform default, so that IS where the logs of such a machine
 * are, and a doctor that pointed somewhere else would send the user to an empty
 * directory. (`doctorJobsRoot` answers `null` in the same case because there the
 * agent genuinely never gets that far — it will not start at all.)
 */
export declare function doctorDiagLogDir(configDir?: string): string;