/**
 * Mission Paths
 *
 * Single source of truth for WHERE Mission and Key Result documents live on
 * disk. Before this module existed, seven services and controllers each
 * carried their own `getMissionsDir()` and resolved the project root
 * differently (`process.cwd()` here, `CREWLY_PROJECT_PATH` there,
 * `CREWLY_MISSIONS_DIR` in exactly one place). Any deployment where those
 * three disagree would have the reminder sweep, the review service and the
 * REST controller reading three different stores — which is one of the
 * reasons the OKR loop never closed at runtime.
 *
 * Precedence (highest first):
 *   1. `CREWLY_MISSIONS_DIR`  — absolute override of the store itself
 *      (used by tests to isolate a temp dir; may also be used by ops).
 *   2. `CREWLY_PROJECT_PATH`  — project root; store is `<root>/.crewly/missions`.
 *   3. `process.cwd()`        — legacy default; store is `<cwd>/.crewly/missions`.
 *
 * Every function here re-reads the environment on each call (no module-level
 * caching) so tests that override `process.cwd` / env in `beforeEach` see the
 * change without a module reload.
 *
 * @module services/v3/mission-paths
 */
import { isInsidePackageTree } from '../core/crewly-home.utils.js';
export { isInsidePackageTree };
/** Env var that overrides the missions store directory outright. */
export declare const MISSIONS_DIR_ENV = "CREWLY_MISSIONS_DIR";
/** Folder under `.crewly` that holds one JSON file per Mission. */
export declare const MISSIONS_FOLDER = "missions";
/** Folder under `<missionsDir>/<missionId>/` that holds one JSON per KR. */
export declare const KEY_RESULTS_FOLDER = "key-results";
/**
 * Resolve the project root the mission store hangs off.
 *
 * @returns `CREWLY_PROJECT_PATH` when set, otherwise `process.cwd()`
 */
export declare function getMissionProjectPath(): string;
/**
 * Where missions live when nothing explicit is configured.
 *
 * Until 2026-09-18 this was `<cwd>/.crewly/missions`. On a server install the
 * service's cwd is the npm package directory, so `npm i -g crewly@next`
 * replaced the directory and deleted every mission with it (observed on
 * steamfun-ops: the day's OKRs vanished on upgrade). A cwd inside
 * `node_modules` therefore falls back to `CREWLY_HOME/missions`; a real
 * project cwd keeps the per-project location so local development is
 * unchanged.
 *
 * @param projectPath - The resolved project path
 * @returns Absolute missions directory
 */
export declare function defaultMissionsDir(projectPath: string): string;
/**
 * Resolve the absolute missions directory.
 *
 * @param projectPath - Optional explicit project root. When given it is used
 *   instead of `CREWLY_PROJECT_PATH` / `process.cwd()`, but the
 *   `CREWLY_MISSIONS_DIR` override still wins so a test-isolated store is
 *   honoured by every caller (including services constructed with an
 *   explicit project path such as {@link EscalationService}).
 * @returns Absolute path to the directory holding `<missionId>.json` files
 *
 * @example
 * ```ts
 * getMissionsDir(); // "/repo/.crewly/missions"
 * ```
 */
export declare function getMissionsDir(projectPath?: string): string;
/**
 * Absolute path of a single mission document.
 *
 * @param missionId - Mission id
 * @param projectPath - Optional explicit project root (see {@link getMissionsDir})
 * @returns `<missionsDir>/<missionId>.json`
 */
export declare function getMissionPath(missionId: string, projectPath?: string): string;
/**
 * Absolute path of the directory holding a mission's Key Result documents.
 *
 * @param missionId - Mission id
 * @param projectPath - Optional explicit project root (see {@link getMissionsDir})
 * @returns `<missionsDir>/<missionId>/key-results`
 */
export declare function getKeyResultsDir(missionId: string, projectPath?: string): string;
//# sourceMappingURL=mission-paths.d.ts.map