/**
 * Crewly home directory resolution utility.
 *
 * Single source of truth for resolving the path the Crewly backend
 * should treat as `~/.crewly` for the current process. Honours the
 * `CREWLY_HOME` environment variable so test profiles, dry-run kits,
 * and ESTestNode acceptance harnesses can isolate their state from a
 * developer's real home directory.
 *
 * Why this exists
 * ---------------
 * Several callers used to inline `path.join(os.homedir(), '.crewly')`
 * directly. That pattern silently ignores `CREWLY_HOME`, so a test
 * harness that exports `CREWLY_HOME=/tmp/...` would still write into
 * the developer's real `~/.crewly`. That broke:
 *   - ESTestNode acceptance path
 *   - Mia's KR3 walkthrough on a `/tmp/...` profile (P0 surfaced
 *     2026-05-05 during the live walk-through pre-flight)
 *
 * Use this helper everywhere the backend needs the Crewly home path.
 * Do NOT re-implement the env read inline — that is the same
 * anti-pattern the bug above targeted.
 *
 * @module services/core/crewly-home.utils
 */
/**
 * Resolve the Crewly home directory for the current process.
 *
 * Priority order:
 * 1. `process.env.CREWLY_HOME` (highest — for test profiles, dry-run
 *    kits, and ESTestNode acceptance harnesses).
 * 2. `path.join(os.homedir(), '.crewly')` (default for normal
 *    developer / production usage).
 *
 * An empty-string `CREWLY_HOME` is treated as unset (returns the
 * default). A whitespace-only value is treated as set (returned as-is)
 * — callers that care about that should validate the path themselves.
 *
 * @returns Absolute path to the Crewly home directory.
 *
 * @example
 * ```ts
 * import { getCrewlyHomePath } from './crewly-home.utils.js';
 *
 * const teamsDir = path.join(getCrewlyHomePath(), 'teams');
 * // CREWLY_HOME=/tmp/foo  → /tmp/foo/teams
 * // CREWLY_HOME unset      → /Users/<user>/.crewly/teams
 * ```
 */
export declare function getCrewlyHomePath(): string;
/**
 * A short, non-secret id for a Crewly home directory.
 *
 * The backend reports it on `/health` so a CLI can tell whether the backend
 * on a port is *its own* one. Loopback requests need no API token, so without
 * this check `crewly login` / `crewly onboard` run by one Unix user would
 * drive another user's backend that happens to hold the port (on a shared
 * server: a production Crewly running as root on 8787).
 *
 * @param home - Crewly home (defaults to {@link getCrewlyHomePath})
 * @returns First 16 hex chars of sha256(absolute home path)
 */
export declare function getCrewlyHomeId(home?: string): string;
/**
 * Whether a directory is an installed package tree — anything under a
 * `node_modules` segment. `npm install` replaces such a tree wholesale, so
 * nothing the user owns may live inside it.
 *
 * @param dir - Absolute path
 * @returns True when the path contains a `node_modules` segment
 */
export declare function isInsidePackageTree(dir: string): boolean;
/**
 * The `.crewly` data directory for a project path.
 *
 * Normally `<projectPath>/.crewly`. When the "project" is really the npm
 * package directory — the cwd of a globally installed `crewly` service —
 * the Crewly home directory is returned instead, because anything written
 * under the package tree is deleted by the next `npm i -g crewly` (observed
 * on a production server on 2026-09-18: every mission, escalation, trigger
 * and request vanished on upgrade). Every per-project store that falls back
 * to `process.cwd()` must resolve its root through this helper.
 *
 * @param projectPath - Resolved project root (often `process.cwd()`)
 * @returns Absolute directory that holds the project's `.crewly` state
 *
 * @example
 * ```ts
 * resolveProjectDataDir('/repo');                            // "/repo/.crewly"
 * resolveProjectDataDir('/usr/lib/node_modules/crewly');     // "~/.crewly"
 * ```
 */
export declare function resolveProjectDataDir(projectPath: string): string;
/**
 * Per-project stores that older versions wrote under `<cwd>/.crewly` even
 * when cwd was the npm package directory. Listed so the boot-time rescue
 * knows what to carry over; anything else under the package tree is
 * regenerable.
 */
export declare const PACKAGE_TREE_STORES: readonly ["missions", "escalations", "requests", "task-records", "triggers", "knowledge", "tasks", "goals", "agents-index.json"];
/**
 * One-time rescue for installs whose per-project state still lives inside
 * the npm package tree: copy each known store to the safe data directory
 * when the safe copy does not exist yet (or is an empty directory). Safe to
 * call at every boot — a no-op once the safe location is populated or the
 * legacy directory is gone. Never deletes the source.
 *
 * @param legacyDir - `<package>/.crewly`
 * @param safeDir - The directory returned by {@link resolveProjectDataDir}
 * @returns Names of the stores copied
 */
export declare function migrateLegacyProjectData(legacyDir: string, safeDir: string): string[];
//# sourceMappingURL=crewly-home.utils.d.ts.map