/**
 * daemon-config-tier.ts, the daemon's own config store.
 *
 * Every daemon-owned key (see config-ownership.ts) lives in exactly one file,
 * `<daemonHome>/settings.json`, which defaults to `~/.goodvibes/daemon/
 * settings.json`, the same directory that already holds the daemon's identity
 * state (operator-tokens.json, detached-daemon.json). One writer, one reader of
 * record, therefore nothing to sync and nothing to drift.
 *
 * The old arrangement put these keys in `~/.goodvibes/tui/settings.json` for no
 * reason other than the daemon binary being the TUI binary, so every other
 * product had to know that "tui" secretly meant "daemon". It no longer does.
 *
 * Resolution order for a daemon-owned key: defaults < global surface < project
 * surface < shared tier < DAEMON TIER < CLI overrides. The daemon tier overlays
 * last so a stale value left behind in a surface silo can never win.
 */
import { isDaemonOwnedConfigKey, type DaemonOwnedConfigPath } from './config-ownership.js';
/** Directory name of the daemon's own state root under `~/.goodvibes/`. */
export declare const DAEMON_CONFIG_ROOT = "daemon";
/** File name of the daemon's settings store within the daemon home. */
export declare const DAEMON_SETTINGS_FILE = "settings.json";
/** Absolute path of the daemon config store for a given daemon home directory. */
export declare function daemonConfigPathForHome(daemonHomeDir: string): string;
/**
 * Absolute path of the daemon config store derived from a user home directory:
 * `<homeDir>/.goodvibes/daemon/settings.json`. Callers that honor
 * `GOODVIBES_DAEMON_HOME` should resolve the daemon home first and use
 * {@link daemonConfigPathForHome} instead.
 */
export declare function daemonConfigPath(homeDir: string): string;
/** Read the daemon config store as a plain object ({} when it does not exist). */
export declare function readDaemonTierFile(path: string): Record<string, unknown>;
/** Persist one daemon-owned key, merging with whatever else is already stored. */
export declare function persistDaemonKey(path: string, key: string, value: unknown): void;
/** Remove one daemon-owned key so it falls back to its default. */
export declare function removeDaemonKey(path: string, key: string): void;
/** A daemon-owned key found in a settings object, with its stored value. */
export interface DaemonTierEntry {
    readonly key: DaemonOwnedConfigPath;
    readonly value: unknown;
}
/**
 * Every daemon-owned path explicitly present in a parsed settings object. Used
 * both to overlay the daemon tier at load and to find what a surface silo is
 * still holding that should have moved.
 *
 * Walks `listDaemonOwnedConfigPaths`, not the schema-key list: an array-valued
 * daemon setting stored here would otherwise be written by `set` and then never
 * read back, so the daemon would keep running on the default.
 */
export declare function collectDaemonOwnedEntries(parsed: unknown): readonly DaemonTierEntry[];
/**
 * Overlay the daemon tier onto a resolved config. `assign` receives each
 * daemon-owned key that the store explicitly carries; keys absent from the
 * store keep whatever the lower tiers resolved to.
 *
 * Returns the keys that were overlaid, so `describeConfigKeySource` can report
 * the daemon tier honestly rather than guessing.
 */
export declare function overlayDaemonTier(path: string, assign: (key: DaemonOwnedConfigPath, value: unknown) => void): readonly DaemonOwnedConfigPath[];
/**
 * The same overlay against an ALREADY-PARSED store.
 *
 * ConfigManager screens a settings file before it merges any of it (see
 * settings-ingestion.ts), which means the object it overlays is not the one on
 * disk: a key that could not be ingested has been removed from it, loudly. If
 * the overlay re-read the file it would put that key straight back, which is
 * the quarantine defeating itself.
 */
export declare function overlayDaemonTierFrom(stored: Record<string, unknown>, assign: (key: DaemonOwnedConfigPath, value: unknown) => void): readonly DaemonOwnedConfigPath[];
/**
 * Drop daemon-store values as part of a config reset, returning the paths
 * cleared so the caller can forget them as a source.
 *
 * `key === undefined` means a full reset. Without this the daemon tier would
 * re-overlay on the next load and quietly defeat the reset.
 */
export declare function clearDaemonTierForReset(path: string, key: string | undefined): readonly DaemonOwnedConfigPath[];
/** Re-exported for callers that hold a raw key string rather than a ConfigKey. */
export { isDaemonOwnedConfigKey };
//# sourceMappingURL=daemon-config-tier.d.ts.map