import type { Command } from 'commander';
import { type CommandIO, type CommandResult } from '../../services/io.js';
/**
 * `cadence config explain [field]` — render the active config in plain language
 * (phase 92). Loads the config, gathers the impure {@link gatherExplainContext},
 * builds the explanation with the phase-91 pure core, and renders text / JSON.
 * Pure over its `io` sink; the CLI action wires real streams + exit code.
 *
 * Complements `cadence config doctor` (config-conflict pairs) and `cadence
 * doctor` (structural host/state health): this surface *explains* what the
 * config does and flags config-semantic foot-guns, pointing at those for the
 * full checks.
 */
export declare function runConfigExplain(root: string, args: {
    field?: string | undefined;
    all?: boolean | undefined;
    json?: boolean | undefined;
}, io: CommandIO): Promise<CommandResult>;
/**
 * `cadence config edit [field]` — guided TTY wizard over the curated config
 * keys. Refuses in a non-TTY (points to `config set`), walks the curated set
 * (or one resolved field), writes once atomically behind a confirm, then prints
 * the slice-A `config explain` effect. Pure logic lives in `config-edit/`; this
 * wires the real readline prompts + the single write.
 */
export declare function runConfigEdit(root: string, args: {
    field?: string | undefined;
    isTty: boolean;
}, io: CommandIO): Promise<CommandResult>;
export declare function registerConfigCommand(program: Command): void;
//# sourceMappingURL=config.d.ts.map