export declare const DAEMON_ENV_KEYS: readonly ["WEB_EXTERNAL_HOST", "BOTMUX_DASHBOARD_EXTERNAL_HOST", "BOTMUX_DASHBOARD_HOST", "BOTMUX_DASHBOARD_PORT", "BOTMUX_DAEMON_IPC_BASE_PORT", "BOTMUX_DASHBOARD_PUBLIC_READONLY", "BOTMUX_PUBLIC_URL", "BOTMUX_DASHBOARD_CONTROL_AUDIT_PATH", "BOTMUX_DASHBOARD_TERMINAL_CONTROL_TTL_MS"];
export type DaemonEnvKey = (typeof DAEMON_ENV_KEYS)[number];
/**
 * Pin both PM2 apps to one deterministic ~/.botmux/.env snapshot. A restart
 * launched inside a botmux session inherited its values from the old daemon,
 * so only the persisted file is authoritative in that context.
 *
 * Every key resolves to a string, empty when neither source sets it. Each
 * consumer treats the empty string as "unset" and applies its own default
 * (h5-auth's ENABLED/BRAND/TTL/SECURE_COOKIE parsing, control-audit's path
 * fallback, terminal-control's TTL validation), so a blank baked value is
 * indistinguishable from an absent one — except for the dashboard bind host,
 * whose historical default is applied here.
 */
export declare function resolveDaemonEnv(inheritedEnv: NodeJS.ProcessEnv, envFileText?: string): Record<DaemonEnvKey, string>;
//# sourceMappingURL=daemon-lifecycle-env.d.ts.map