/**
 * The eval shadow tree, re-exported from `@auden.to/projections`.
 *
 * The derivation moved there when the **server** needed it too: a guide pull has
 * to tell every client where that guide's criteria belong, and deriving it
 * per-client is the divergence `unified-item-sync` removes. See that module for
 * why `projections` was the right home.
 *
 * `resolveEvalShadowPath` stays here because it is the only part that touches
 * `node:path` — it turns the scope-relative rule into an absolute path on this
 * machine, which is a CLI concern and not something the server ever asks.
 */
export { EVAL_SHADOW_DIR, classifyLocalItemPath, evalShadowPath, guidePathFromEvalShadow, type LocalItemClassification, } from '@auden.to/projections';
/**
 * Absolute path of a guide's criteria under `scopeRoot` — the repo checkout for
 * a `project` guide, the homedir for a `global` one. `null` for the same guide
 * paths `evalShadowPath` refuses.
 */
export declare function resolveEvalShadowPath(scopeRoot: string, guidePath: string): string | null;
//# sourceMappingURL=eval-path.d.ts.map