/**
 * Everything the CLI keeps: ~/.vana, or VANA_HOME when set. VANA_HOME moves
 * only the CLI's own folder, so a second, isolated CLI state (a demo, a test
 * account) keeps the real HOME and with it the macOS keychain that Chrome
 * and the owner secret store need.
 */
export declare function getVanaHome(): string;
/**
 * Ensure ~/.vana and ~/.dataconnect both resolve to the same directory.
 *
 * Cases:
 * 1. ~/.dataconnect exists, ~/.vana doesn't → rename + symlink old path
 * 2. ~/.vana exists, ~/.dataconnect doesn't → create symlink at old path
 * 3. Both exist (no symlink) → leave as-is (user manages manually)
 *
 * The symlink at ~/.dataconnect ensures vana-com/data-connect (DataConnect
 * desktop app) keeps working. DataConnect hardcodes ~/.dataconnect in
 * src-tauri/src/commands/connector.rs:66. It should adopt ~/.vana upstream.
 *
 * Returns "migrated" when legacy data was actually moved, "symlinked" when
 * only the compat symlink was created (typical first run of a fresh
 * install), and null when nothing changed.
 */
export declare function migrateLegacyDataHome(): "migrated" | "symlinked" | null;
export declare function getConnectorCacheDir(): string;
export declare function getBrowserProfilesDir(): string;
export declare function getCliStatePath(): string;
export declare function getResultsDir(): string;
export declare function getSourceResultPath(source: string): string;
export declare function getPreviousResultPath(source: string): string;
/** Rotate current result to .previous before overwriting. */
export declare function rotateResult(source: string): Promise<void>;
export declare function getSessionsDir(): string;
export declare function getLogsDir(): string;
export declare function getTelemetryDir(): string;
export declare function getTelemetryOutboxDir(): string;
export declare function getTimestampedLogPath(prefix: string): string;
//# sourceMappingURL=paths.d.ts.map