/**
 * The ONE per-project docs-root resolution every interactive route shares (crew#472).
 *
 * The proxy, the governed doc delete, and the attributed docs list all answer under
 * `/projects/:projectId/interactive/...`, and all three must agree on which directory — and so
 * which bridge — a project id means. Before this module each route carried its own copy of the
 * existence check + resolution; the partitioning fix touched the resolution, and three copies of
 * a rule that decides which project sees which documents is two too many.
 *
 * This is also where a partition is MATERIALIZED and containment-checked on real paths
 * (`ensureProjectInteractiveRoot`): a symbolic link planted at `projects/<id>` is refused here,
 * before any route hands the path to a bridge, by throwing `InteractivePartitionRefusedError` —
 * which fastify answers as a 500 naming the path. Fail closed: the one answer this seam must
 * never give is some other directory.
 */
import type { CoreAdapter } from '../core/adapter.js';
import type { ProjectSettingsStore } from '../projects/settings.js';
/** The injectable halves of the resolution — a test harness points them away from the real
 *  machine. Every interactive route's deps object satisfies this structurally, so a route passes
 *  its deps. Since crew 0.7.35 (D-L7-1) the DEFAULT root hangs off the daemon STATE HOME, not HOME:
 *  `stateHome` places it (and the partitions under it); `home` only expands `~` in an explicit
 *  `interactiveRoot` setting. */
export interface ProjectRootOptions {
    env?: NodeJS.ProcessEnv;
    /** The daemon state home the default docs root resolves under; default `crewStateHome()`. */
    stateHome?: string;
    /** The HOME a leading `~` in an EXPLICIT setting expands against; default `homedir()`. */
    home?: string;
}
/**
 * The resolved docs root for a project, or null when no such project exists. Throws
 * `InteractivePartitionRefusedError` when the project's partition is not a real directory
 * under `projects/` (see the module header).
 *
 * `default` is SYNTHESIZED by the route layer (DES-PROJECT-001 §7) — the engine has no row for
 * it, so an existence check there would 404 the one project every operator starts with. A
 * pre-0.6.0 engine has no project surface at all: `default` is the only project such a deployment
 * can have, so its legacy shared root is the truthful answer for whatever id was asked —
 * partitioning by an id that cannot name a project there would only manufacture an empty root.
 */
export declare function projectDocsRoot(adapter: CoreAdapter, settings: ProjectSettingsStore, projectId: string, opts?: ProjectRootOptions): Promise<string | null>;
//# sourceMappingURL=project-root.d.ts.map