/**
 * The plugin's own configuration surface. The Host validates the profile
 * patch against {@link Config} and generates the settings page of this
 * profile entry from the same schema, so the plugin registers no settings
 * section of its own.
 *
 * Every field is `volatile`: the settings subsystem projects only volatile
 * fields into an entry's form, and a write commits the new value into the
 * running plugin's references instead of remounting the row. The runtime
 * therefore reads those references live — {@link effectiveConfig} resolves
 * them at call time — and re-derives what it registered for the row when the
 * Loader announces a committed change.
 * @module @linxin666/dsh-client-ui-git-graph/host/config
 */
import type { Volatile } from '@deepseek-ai/cordis';
import z from '@deepseek-ai/schemastery';
/** Plugin config as the runtime reads it: one live reference per field. */
export interface Config {
    /** Auto-isolate every New Session of a git workspace into a fresh managed worktree. */
    autoIsolate: Volatile<boolean>;
    /** Baseline for auto-created worktrees: the checkout's current HEAD or the remote default branch. */
    autoBaseline: Volatile<'current' | 'default'>;
    /** Register the model-facing git_worktree tool (opt-in; off keeps git off the model-visible surface). */
    agentTool: Volatile<boolean>;
}
/** Profile-patch shape of {@link Config}, before the schema turns it into live references. */
export interface ConfigInput {
    /** Auto-isolate every New Session of a git workspace into a fresh managed worktree. */
    autoIsolate?: boolean;
    /** Baseline for auto-created worktrees: the checkout's current HEAD or the remote default branch. */
    autoBaseline?: 'current' | 'default';
    /** Register the model-facing git_worktree tool (opt-in; off keeps git off the model-visible surface). */
    agentTool?: boolean;
}
/** Config values with schema defaults applied. */
export type ResolvedConfig = Required<ConfigInput>;
/** Schemastery schema backing the profile patch values and the generated settings page. */
export declare const Config: z<ConfigInput, Config>;
/**
 * Resolve the effective config with schema defaults applied. Volatile fields
 * arrive as live references, so this reads the value the settings subsystem
 * last committed rather than a snapshot taken at mount.
 * @param config - the config the Host handed to the plugin row.
 * @returns the resolved values.
 */
export declare function effectiveConfig(config?: Config): ResolvedConfig;
//# sourceMappingURL=config.d.ts.map