/**
 * Static config validation beyond what zod parsing gives us.
 *
 * The config schemas are deliberately non-strict (unknown TOML keys are
 * ignored at load time so old servers tolerate new keys) — which turns a
 * typo like `auto_copu = true` into silently-dropped intent. `config
 * validate` closes that gap: unknown keys are found by walking the parsed
 * TOML against the zod schema tree itself (no hand-maintained key lists,
 * so new settings are covered automatically), plus cross-setting
 * consistency checks for the mistakes a schema cannot see.
 */
import type { RawAppConfig } from './schema.js';
export interface UnknownKey {
    /** Dotted path of the unrecognized key, e.g. `settings.verification.auto_copu`. */
    path: string;
    /** Closest known key at that level, when one is plausibly meant. */
    suggestion?: string;
}
export interface ConsistencyIssue {
    severity: 'error' | 'warning';
    message: string;
}
/** Keys present in the parsed TOML that no schema knows about. */
export declare function findUnknownKeys(raw: unknown): UnknownKey[];
/** Cross-setting mistakes a per-field schema cannot see. */
export declare function findConsistencyIssues(raw: RawAppConfig): ConsistencyIssue[];
//# sourceMappingURL=validate.d.ts.map