/**
 * Integrity check: verify a compiled markdown file hasn't been hand-edited.
 *
 * Every compiled file has a SHA-256 hash in its first line:
 *   <!-- vigiles:sha256:<hash> compiled from CLAUDE.md.spec.ts -->
 *
 * If the body content's hash no longer matches what's recorded, someone
 * edited the compiled output directly. The check is one-pass and ~free.
 *
 * This is the entire freshness story now: no input fingerprinting, no
 * recompile diffing. Those responsibilities belong elsewhere:
 *
 * - Hand-edit detection → this module
 * - "Did the spec change?" → guard() rules emitting compile hooks
 * - "Are referenced linter rules / files / scripts still valid?"
 *   → enforce() / file() / cmd() catch this at compile time
 * - "Are committed compiled files actually fresh?"
 *   → CI runs `vigiles compile` then `git diff --exit-code`
 */
export { splitFrontmatter, findIntegrityHeader, REQUIRE_INSTRUCTIONS_SPEC_DISABLE, instructionSpecState, type InstructionSpecState, } from "./integrity-header.js";
/** Render the header in its correct position for this content. */
export declare function placeIntegrityHeader(content: string, hash: string, specFile: string): string;
export interface IntegrityResult {
    intact: boolean;
    reason?: string;
}
/**
 * Check whether the compiled markdown's SHA-256 hash matches its body.
 * Files without a hash header are treated as hand-written (intact).
 */
export declare function checkIntegrity(content: string): IntegrityResult;
/**
 * Parse the `vigiles:sha256 … compiled from <spec>` integrity header, if the
 * file carries one. Returns the referenced spec path and the body below the
 * header; `null` when the file is plain markdown (no header).
 */
export declare function parseIntegrityHeader(content: string): {
    specFile: string;
    body: string;
} | null;
/**
 * "Eject" a compiled instruction file to plain, hand-owned markdown: strip the
 * integrity header so the file is no longer spec-managed, and prepend a
 * `require-instructions-spec` disable marker so `vigiles lint` won't ask for a
 * spec back. Pure — the caller writes the file and removes the spec. Returns
 * `null` when there is no header to strip (nothing to eject). Idempotent: a body
 * that already carries the marker is not double-marked.
 *
 * The disable marker is added ONLY for instruction-file bodies. A compiled
 * SKILL.md / subagent body begins with YAML frontmatter (`---`) that MUST stay in
 * first position — prepending an HTML comment there would push the frontmatter
 * out of the lead block and the harness would lose the skill's name/description/
 * tools. The marker is also meaningless for those surfaces (require-instructions-
 * spec doesn't apply to them), so a frontmatter-led body is ejected as-is.
 */
export declare function ejectMarkdown(content: string): {
    markdown: string;
    specFile: string;
} | null;
//# sourceMappingURL=integrity.d.ts.map