import { type PlumbEvent } from "oh-my-plumb-schema";
/** Best effort. The log must never take the hook down with it, or hold it. */
export declare const appendEvent: (root: string, event: PlumbEvent) => void;
/**
 * Keeps the event log at a bounded size: past the cap, session start rewrites
 * it to its newest cap-sized window, cut on a line boundary, keeping only
 * lines the schema still accepts. One pass lands under the cap whatever the
 * log had grown to, and what report and tune read — recent checks — stays.
 * The rename is atomic and any check appended mid-trim is telemetry, safe to
 * lose. Best effort, like every reader and writer of this file.
 */
export declare const trimEvents: (root: string, maxBytes?: number) => void;
/**
 * A payload the schema rejected, kept as a name only — never its input, its
 * output, or its content — so `report` can count host drift instead of showing
 * silence. The per-turn cap stops a host stuck in a loop from filling the log.
 * Like appendEvent, best effort: this signal must never fail the hook.
 */
export declare const appendUnknownPayload: (payload: unknown) => void;
export declare const readEvents: (root: string) => PlumbEvent[];
//# sourceMappingURL=events.d.ts.map