/**
 * Path resolution utilities for VALORA package
 *
 * Provides functions to locate:
 * - Package built-in resources (data/ directory shipped with the npm package)
 * - Project-level overrides (.valora/ directory in the user's project)
 * - Global user configuration (~/.valora/)
 * - Runtime data directories (sessions, logs, cache)
 */
/**
 * Get the root directory of the installed VALORA package.
 * Resolves from the compiled module location up to the directory containing
 * package.json with name "valora" AND a data/ directory (to distinguish from dist/ copy).
 */
export declare function getPackageRoot(): string;
/**
 * Get the path to the package's built-in data directory.
 * Contains agents, commands, prompts, templates, hooks, and default configs.
 */
export declare function getPackageDataDir(): string;
/**
 * Get the project-level .valora/ configuration directory.
 * Walks up from process.cwd() looking for a .valora/ directory.
 * Returns null if not found (not in a project context).
 */
export declare function getProjectConfigDir(): null | string;
/**
 * Get the global user configuration directory.
 * Returns ~/.valora/ on Unix or %APPDATA%/valora/ on Windows.
 * Override with VALORA_GLOBAL_CONFIG_DIR for testing or custom deployments.
 */
export declare function getGlobalConfigDir(): string;
/**
 * Get the runtime data directory for sessions, logs, cache, etc.
 * Uses .valora/ in project context, or ~/.valora/ globally.
 */
export declare function getRuntimeDataDir(): string;
/**
 * Resolve the project root to check `isWorkspaceTrusted()` against: the
 * nearest ancestor containing `.valora/`, or `process.cwd()` if none exists.
 * Single source of truth for every `isWorkspaceTrusted()` caller — before
 * this existed, `hook-execution.service.ts` walked up to find the `.valora/`
 * ancestor while other consumers used raw `process.cwd()` with no walk-up,
 * so running `valora` from a subdirectory of an already-trusted project
 * would silently deny trust for the consumers that didn't walk up. Fails
 * closed either way (never grants trust it shouldn't), but was a real,
 * confusing functional inconsistency across consumers of the same primitive.
 */
export declare function getWorkspaceTrustCheckRoot(): string;
/**
 * Get the package's built-in plugins directory.
 */
export declare function getPackagePluginsDir(): string;
/**
 * Get the path to the shipped plugin registry JSON file.
 */
export declare function getPluginRegistryPath(): string;
/**
 * Get the global user plugins directory (~/.valora/plugins/).
 */
export declare function getGlobalPluginsDir(): string;
/**
 * Get the system-wide plugins directory, accessible to all users on the machine.
 * Override with VALORA_SYSTEM_PLUGINS_DIR for testing or custom deployments.
 * Defaults: /usr/local/share/valora/plugins (Unix/macOS), %PROGRAMDATA%\valora\plugins (Windows).
 */
export declare function getSystemPluginsDir(): string;
/**
 * Get the project-level plugins directory (.valora/plugins/).
 * Returns null if not in a project context.
 */
export declare function getProjectPluginsDir(): null | string;
/**
 * Get the current package version from package.json at the package root.
 */
export declare function getValoraVersion(): string;
/**
 * Returns true if a Valora configuration directory exists in any scope
 * (project, user, or system). Used to detect a first-time install.
 */
export declare function hasAnyValoraConfig(): boolean;
//# sourceMappingURL=paths.d.ts.map