/**
 * Protected-path list — explicit, versioned, one place.
 *
 * Writes from `ollama_draft` that target these paths require explicit
 * `confirm_write: true`, enforced server-side (never prompt-side).
 *
 * Do NOT scatter conditionals across tool handlers. Add a new protected
 * path here, bump PROTECTED_PATHS_VERSION, and the whole system picks it up.
 */
export declare const PROTECTED_PATHS_VERSION = 1;
export interface ProtectedPathRule {
    /** Glob-ish pattern, evaluated by matchesProtectedPath(). Use POSIX separators. */
    pattern: string;
    /** Human-readable reason shown in the error. */
    reason: string;
}
/**
 * Rules — kept explicit so a reviewer can eyeball them.
 *
 * Matching is substring-against-normalized-path with "/" as separator.
 * A pattern ending in "/" matches any descendant.
 */
export declare const PROTECTED_PATHS: ProtectedPathRule[];
/**
 * Normalize a path for comparison: forward slashes, no leading ./, lowercase on
 * case-insensitive filesystems.
 *
 * On Windows (NTFS) and macOS (APFS) — case-insensitive — input is lowercased so
 * callers comparing against canonical lowercase patterns honor the platform's
 * filesystem semantics. On case-sensitive Linux, case is preserved.
 */
export declare function normalizePath(p: string): string;
export interface ProtectedMatch {
    protected: boolean;
    rule?: ProtectedPathRule;
}
export declare function matchesProtectedPath(path: string, rules?: ProtectedPathRule[]): ProtectedMatch;
//# sourceMappingURL=protectedPaths.d.ts.map