/**
 * T-CODEX-HOST-SHELL CHS.2 — codex `apply_patch` envelope parsing.
 *
 * Codex's file-edit tool reports `tool_name: "apply_patch"` with the patch
 * text in `tool_input.command`; no pack rule matches that name, so without
 * normalization a codex file write sails past every coding-flow gate (the
 * post-trust CHS.1 live spike proved it). The hook bin normalizes each
 * touched path into ONE synthesized single-path `Write` event — every PATH
 * predicate dialect (contains/endsWith/startsWith/==) sees a normal
 * file_path. Content: `Add File` sections carry the FULL final content as
 * `+` lines (true artifact for the content audits); `Update`/`Delete`
 * sections become a first-line-LABELED hunk diff — explicit, never
 * silently-stale (the effective_content failure mode the design review
 * caught). Zero markers parsed → [] → the caller passes the event through
 * untouched (fail-open for unknown envelope variants).
 *
 * Imports from: (none — pure).
 * Imported by: src/runtime/hooks/pre-tool-use.ts.
 */
export interface PatchedFile {
    path: string;
    kind: 'add' | 'update' | 'delete';
    /** add: true final content; update/delete: labeled hunk diff. */
    content: string;
}
export declare function parseApplyPatch(command: string): PatchedFile[];
//# sourceMappingURL=apply_patch.d.ts.map