import { DefaultLogger } from './infrastructure/logger.js';
import { DefaultPathResolver } from './infrastructure/path-resolver.js';
import { DefaultSecretVault } from './security/secret-vault.js';
import { type Config } from './types/config.js';
import { type WstackPaths } from './utils/wstack-paths.js';
/**
 * Options for {@link bootConfig}. Both the CLI and the WebUI server boot the
 * same way; the only intentional differences are the label used in the
 * plaintext-secret migration notice and whether CLI flags are supplied.
 */
export interface BootConfigOptions {
    /**
     * Parsed CLI flags. `cwd` relocates path resolution; `provider`/`model`/
     * `log-level`/`verbose`/`trace`/`yolo`/`no-features` are patched into the
     * loaded config (see {@link flagsToConfigPatch}). Defaults to `{}` (the
     * WebUI server passes no flags).
     */
    flags?: Record<string, string | boolean>;
    /**
     * Label shown in the `[<label>] Encrypted N plaintext secret(s) in FILE`
     * stderr notice emitted when legacy plaintext secrets get auto-encrypted.
     * The CLI passes `wstack`; the WebUI server passes `WebUI`. Default
     * `wstack`.
     */
    appLabel?: string | undefined;
    /**
     * Load the active profile's `sync.json` and merge it into `config.sync` so the
     * ConfigStore starts with the correct CloudSync state. Default `true`.
     */
    loadSyncConfig?: boolean | undefined;
    /**
     * Skip the provider/model identity validation during config load. When
     * `true`, a missing provider or model in config does NOT throw — the
     * boot caller is responsible for handling the missing-provider case
     * (e.g. showing a setup screen). Used by `--webui` mode so the WebUI
     * can boot without a configured provider and show the setup screen.
     */
    skipIdentityValidation?: boolean | undefined;
}
/**
 * Everything the boot phase resolves before DI-container wiring. Superset of
 * what the CLI and WebUI server each consumed previously, so both can pick the
 * fields they need from a single canonical result.
 */
export interface BootConfigResult {
    cwd: string;
    projectRoot: string;
    userHome: string;
    wpaths: WstackPaths;
    pathResolver: DefaultPathResolver;
    config: Config;
    vault: DefaultSecretVault;
    logger: DefaultLogger;
    /** Convenience alias for `wpaths.globalConfig`. */
    globalConfigPath: string;
}
/**
 * Canonical boot routine shared by `@wrongstack/cli` and `@wrongstack/webui`.
 * Resolves paths, creates the real AES-GCM secret vault, migrates any
 * plaintext secrets, loads + merges config (with CLI-flag overrides and an
 * optional sync overlay), and builds a logger.
 *
 * The per-package `bootConfig()` wrappers re-shape this result into their own
 * legacy return types for backward compatibility — keep this the single source
 * of boot behavior so the two consumers can't drift.
 */
export declare function bootConfig(options?: BootConfigOptions): Promise<BootConfigResult>;
/**
 * Translate parsed CLI flags into a partial Config patch applied on top of the
 * file-loaded config. Explicit `--log-level` wins over `--verbose`/`--trace`.
 */
export declare function flagsToConfigPatch(flags: Record<string, string | boolean>): Partial<Config>;
/**
 * Refuse to boot when the resolved project root lives inside
 * `<globalRoot>/projects` — the per-project state namespace WrongStack itself
 * owns (`~/.wrongstack/projects/<slug>`, or under `WRONGSTACK_HOME`).
 *
 * When this happens it means a caller spawned a WrongStack process with a
 * state path as its cwd; `DefaultPathResolver` then finds no project marker,
 * walks up, hits the home-directory stop, and falls back to cwd — so the state
 * directory itself becomes the "project". Boot would go on to register a
 * nested slug (`<slug>-<hash>`) with its own `meta.json`, `projects.json`
 * entry, mailbox lock and token, splitting coordination state across two
 * namespaces — with the nested one always winning `lastSeen`.
 *
 * Deliberately scoped to `projects/` rather than all of `globalRoot`: a user
 * may legitimately point `WRONGSTACK_HOME` at a directory that also contains
 * real repositories (our own bridge tests do exactly this), and refusing those
 * would be a false positive. Nothing under `projects/` is ever a real repo, so
 * the narrow check has no such ambiguity.
 *
 * Loud on purpose — the symptom is far harder to diagnose than a refused boot
 * that names the offending directory.
 */
export declare function assertProjectRootOutsideStateDir(projectRoot: string, globalRoot: string): void;
//# sourceMappingURL=boot.d.ts.map