import { type RuntimeConfig } from "./validate.js";
import { type InstanceRef } from "./instances.js";
export declare const defaultConfigPath: () => string;
/**
 * Works out which credentials file to use when nobody said.
 *
 * `NANDI_PROXMOX_CONFIG` is still the explicit answer and always wins. Without
 * it, the server used to look only at the legacy `config.json` name, which the
 * multi-instance layout stopped writing -- so any launcher that could not
 * hardcode an absolute path (a published client plugin, for one) simply failed
 * to start. Discovering the instance instead is what lets a client config be
 * portable between machines.
 *
 * Ambiguity is an error rather than a guess: picking one of two Proxmox
 * clusters on the model's behalf is exactly the decision that must not be made
 * silently.
 */
export declare const chooseConfigPath: (instances: InstanceRef[]) => string;
export declare const discoverConfigPath: (cwd?: string) => Promise<string>;
export declare const loadFileConfig: (explicitPath?: string) => Promise<RuntimeConfig>;
//# sourceMappingURL=fileConfig.d.ts.map