import type { TrackerConfig } from './types.js';
import type { CoreRoot, Preset } from './core/engine.js';
export declare function noTrackerValidation(value: string | undefined): never;
export declare function ztrackResolvableFrom(root: string): boolean;
/** Cheap, NON-EXECUTING health probe of the validation oracle: `null` when `check`/`loop` should
 *  be able to run here (or when there is nothing to probe — no tracker, no configured
 *  entrypoint), else one sentence naming what is broken and how to fix it. Deliberately never
 *  imports the preset: read-only commands must not execute repo code (the preset runs as code —
 *  SECURITY.md), so this checks only environment facts (file exists, runtime can type-strip,
 *  ztrack resolvable as a dependency). Used to warn on commands that SUCCEED without the preset
 *  (issue list/view, import, loop status …), which otherwise leave the tracker looking healthy
 *  right up until the first `check`/`loop`/`--actionable` dies. */
export declare function oracleUnavailableReason(projectRoot: string): string | null;
/** Resolve the active preset — a standalone core `Preset` exported by the repo-local
 *  `validation.entrypoint` (its own schema/parser/rules; see ARCHITECTURE.md §3), OR, when
 *  `presetPath` is given (operator `--preset <path>`, `check` only — see cliCheck.ts), that
 *  module instead. One pipeline; there is no separate snapshot runtime. This is the SINGLE
 *  resolution point shared by checkTracker/checkTrackerRoot/checkFile (check.ts) and
 *  exportTrackerRoot (export.ts) — no per-caller duplication. */
export declare function resolveTrackerValidation(config: TrackerConfig, projectRoot?: string, presetPath?: string): Promise<Preset<CoreRoot>>;
export declare function issueStatusEnumOf(preset: Preset<CoreRoot>): string[] | null;
/** The active preset's issue status vocabulary, for write-time validation — `null` means "no
 *  write-time check should engage" (config unreadable, no validation entrypoint configured, the
 *  entrypoint fails to load, or its schema exposes no plain-enum `status` field). Always resolves
 *  the REPO's configured entrypoint (never an operator `--preset` override — that flag is a
 *  `check`-only escape hatch, see loadOperatorPreset above); this never throws. */
export declare function activeStatusEnum(projectRoot: string): Promise<string[] | null>;