/** File name of the owner profile within the daemon home. */
export declare const OWNER_PROFILE_FILE = "owner-profile.md";
/** Absolute path of the profile for a given daemon home directory. */
export declare function ownerProfilePathForHome(daemonHomeDir: string): string;
/**
 * Absolute path derived from a user home directory:
 * `<homeDir>/.goodvibes/daemon/owner-profile.md`. Callers honouring
 * `GOODVIBES_DAEMON_HOME` should use {@link resolveOwnerProfilePath} instead.
 */
export declare function ownerProfilePath(homeDir: string): string;
export interface OwnerProfilePathOptions {
    /**
     * `profile.path` from config. Empty means the default; a non-empty value is an
     * explicit override for a non-default daemon home and wins outright.
     */
    readonly override?: string | undefined;
    /** Value of the `--daemon-home` CLI flag, when the host parsed one. */
    readonly daemonHomeArg?: string | undefined;
    /** Override `process.env`, for tests. */
    readonly env?: NodeJS.ProcessEnv | undefined;
    /** Override the home directory, for tests. */
    readonly homeDir?: string | undefined;
}
/**
 * Resolve the profile path, first match wins:
 *   1. an explicit `profile.path` override
 *   2. `--daemon-home`
 *   3. `GOODVIBES_DAEMON_HOME`
 *   4. `<tree root>/.goodvibes/daemon/`, an injected `homeDir` when a caller
 *      supplied one, else the tree root `GOODVIBES_HOME` names, else the login
 *      home.
 *
 * A relative path in any of the overrides resolves against the current working
 * directory, matching `resolveDaemonHomeDir` so the two cannot disagree about
 * what a relative daemon home means.
 */
export declare function resolveOwnerProfilePath(options?: OwnerProfilePathOptions): string;
//# sourceMappingURL=paths.d.ts.map