/** One doctor check result, structurally identical to `DoctorCheck`. */
interface FreshnessCheck {
    name: string;
    status: "ok" | "warn" | "fail";
    detail: string;
}
/**
 * Report whether template application is current for this checkout.
 * @param targetPath - Project path to inspect
 * @returns Doctor check result
 */
export declare function checkApplyFreshness(targetPath: string): Promise<FreshnessCheck>;
/**
 * Report whether the js-yaml this install resolved can actually be driven.
 *
 * Separate from the freshness check because it answers the follow-up question:
 * *why* has nothing applied? A host `overrides`/`resolutions` entry collapses
 * Lisa's own js-yaml onto the host's pin, and an incompatible pin used to kill
 * the CLI at module-load time with a bare stack trace. Lisa now links against
 * any js-yaml shape and reports the incompatibility in plain language here.
 *
 * `fail`, not `warn`: nothing that parses YAML works in this state — Codex and
 * OpenCode artifact generation, CI workflow readiness, and the console's deploy
 * pipeline all stop — and the remedy is a one-line manifest edit.
 * @returns Doctor check result
 */
export declare function checkYamlRuntime(): FreshnessCheck;
export {};
//# sourceMappingURL=doctor-apply-freshness.d.ts.map