import type { DiagnosticSection } from "./_types.js";
/** Setup-progress guide: detects which of the documented one-time setup steps
 *  are complete and names the one next command. Guidance only — never emits
 *  errors, so it cannot change the report's pass/fail verdict. */
export declare function checkSetupProgress(cwd: string): DiagnosticSection;
/**
 * Report the project-wide run lock state. The lock is held by
 * `/senai-approve` and `/senai-brainstorm-approve` for the duration of
 * their mutation. A held lock with a live pid means another Pi session is
 * mid-flight; a held lock with a dead pid or stale heartbeat is recovered
 * automatically by the next acquire call.
 */
export declare function checkLock(cwd: string): DiagnosticSection;
/** Reports the adaptive spawn cadence for the Plan stage. Tells the user
 *  which dispatch tier (A/B/C/D) is currently in effect, when the last
 *  rate-limit error fired, and whether the floor (tier D) has been stuck
 *  long enough to deserve a manual reset. */
export declare function checkCadence(cwd: string): DiagnosticSection;
export declare function checkRunArtifacts(cwd: string): DiagnosticSection;
/** Discussion checks:
 *  1. For each run directory containing a discussions/ folder, validate that
 *     exactly one discussion transcript subfolder is active — multiple active
 *     subfolders → warning naming the run id.
 *  2. For every existing mission-brief.md (pre-run and per-run), validate
 *     that all required sections for the brief's own mission type are
 *     present, in order (base 6 plus pack sections — a bugfix brief must
 *     carry its 4 extra sections). Missing sections → warning naming the
 *     file and the missing section.
 *  3. Orphan pre-run discussion folder with no mission-brief.md → info
 *     (the user started a discussion but never wrote the brief). */
export declare function checkDiscussions(cwd: string): DiagnosticSection;