/**
 * The per-checkout files under `<root>/.vigiles/` that git tracks, as
 * repo-relative paths from `root`. Empty when nothing is tracked, when `root` is
 * not in a git work tree, or when `git` is missing — silence is the answer to
 * every "cannot tell".
 */
export declare function trackedLocalFiles(root: string): string[];
/**
 * Does the COMMITTED `.vigiles/.gitignore` (the one at `HEAD`) lack entries
 * vigiles needs — i.e. will vigiles' additions show up as a change to a tracked
 * file until someone commits them.
 *
 * The question is asked of `HEAD`, not of the worktree's dirtiness, and that
 * is the point (Codex review on #275, third pass). "The file is modified" was
 * the earlier predicate; it could not tell vigiles' additions from the owner's
 * own unrelated edit, and then advised committing work in progress. Reading the
 * committed copy answers only for vigiles' entries, staged or not, and says
 * nothing once they are committed, whatever else the owner is editing.
 * `HEAD:./path`, not `HEAD:path`: without `./` git resolves the path from the
 * REPOSITORY root, so a package nested in a larger worktree read the wrong file
 * — or none — and stayed silent (Codex review on #275, gitrevisions(7)).
 * Silent on every "cannot tell": not in a repo, no `HEAD`, file not committed.
 */
export declare function committedIgnoreFileLacksEntries(root: string): boolean;
/**
 * The one-line warning for {@link trackedLocalFiles}, or `null` when there is
 * nothing to say. Files inside a tracked local DIRECTORY (`state/`,
 * `eval-cache/`) are named by that directory, so one line stays one line and the
 * command it prints untracks all of them.
 */
export declare function formatTrackedLocalFiles(tracked: readonly string[], committedLacksEntries?: boolean): string | null;
/** Print the warning for `root` to stderr when there is one. CLI-only. */
export declare function warnTrackedLocalFiles(root: string): void;
//# sourceMappingURL=local-files-tracked.d.ts.map