/**
 * Where a registered repo's artifacts live — resolved from the engine's record, not re-derived here.
 *
 * # What this replaces
 *
 * The code-graph path used to be spelled `join(repo.root_path, '.codegraph', 'estate.db')` in five
 * places in this package, against a sixth spelling inside wicked-core (`.wicked/code-graph.db`). Both
 * halves were individually correct and nothing failed when they disagreed: onboarding indexed 185 MB
 * into crew's path, and the governed worker's estate MCP was pointed at core's — a database nothing
 * had ever written. Every graph query the worker made answered "nothing found" about a repo full of
 * code, which is indistinguishable from a real empty result (FINDING-069, wicked-core#170).
 *
 * The fix is not "spell it the same in six places". The engine now publishes the resolved path on the
 * repo record that this package already reads, and this module is the only thing that touches that
 * field. One producer, one consumer, nothing to keep in step.
 */
import type { RepoEntry, RepoFinding } from './types.js';
/**
 * The ABSOLUTE path of a repo's code graph, as resolved by the engine.
 *
 * Throws — never falls back to the old hand-join, which is what this module exists to delete (it
 * would restore the exact divergence above and hide it behind a path that looks plausible) — in two
 * DISTINCT situations with different remedies, told apart by the error class:
 *
 * - {@link CodeGraphRootUnresolvableError}: the engine is CURRENT and resolved no repo-graph root
 *   (no `WICKED_ESTATE_REPO_GRAPH_ROOT`, no state home, no `HOME`/`USERPROFILE`), so it published an
 *   EMPTY `code_graph_db` together with a `code_graph_root_unresolvable` finding (wicked-core#406).
 *   The remedy is the daemon's environment; the finding's message says so. Callers that classify
 *   "engine too old" must let this one through (`projects/graph.ts assertEngineFresh`).
 * - a plain `Error` naming wicked-core#170: the field is ABSENT (or empty with no such finding),
 *   which means the running `wicked-core` addon predates it. The remedy is a rebuild/reinstall.
 *
 * Loud is correct in both: every graph-backed surface would otherwise report an empty repo.
 */
export declare function codeGraphDb(repo: RepoEntry): string;
/** The engine's finding code for "no repo-graph root resolves" (`RepoEntry.findings[]`, wicked-core#406). */
export declare const CODE_GRAPH_ROOT_UNRESOLVABLE = "code_graph_root_unresolvable";
/**
 * The ONE HTTP mapping every code-graph consumer shares for a `codeGraphDb()` failure this daemon
 * can classify: **503** for {@link CodeGraphRootUnresolvableError} — a CURRENT engine resolved no
 * repo-graph root, a daemon-environment fault (neither a bad request nor Fastify's generic 500) —
 * and `null` for anything else, which the caller maps itself (501 for the stale-addon case on the
 * project routes; the default elsewhere). Applied on the project-graph routes, the repo surfaces
 * (`/repos/:id/{graph,graph/blast-radius,domain-graph,requirements…}`) and nowhere else.
 */
export declare function codeGraphErrorStatus(err: unknown): number | null;
/**
 * A CURRENT engine resolved no repo-graph root for this repo (wicked-core#406) — see
 * {@link codeGraphDb}. Distinct from the stale-addon `Error` on purpose: `projects/graph.ts` turns
 * every other `codeGraphDb` throw into `ProjectGraphEngineTooOldError` (501, "reinstall the
 * addon"), which is the wrong remedy here; this class is what lets it tell the two apart.
 */
export declare class CodeGraphRootUnresolvableError extends Error {
    readonly repoId: string;
    readonly finding: RepoFinding;
    constructor(repoId: string, finding: RepoFinding);
}
/**
 * The requirements artifacts a repo's domain extraction writes.
 *
 * A DIFFERENT path family from the code graph (`.wicked-estate/requirements/`, written by
 * `wicked-core domain-graph`) and still derived here, because the engine does not publish it. Same
 * hazard, smaller blast radius: it is written and read by this package plus one core subcommand whose
 * `--out` this package passes. Tracked with the rest of the cross-repo path pins.
 */
export declare function requirementsGraph(repo: RepoEntry): string;
export declare function requirementsOverrides(repo: RepoEntry): string;
//# sourceMappingURL=repoPaths.d.ts.map