export interface SideChannelResult {
    outputPath: string;
    /** Set when a pre-existing file for this tag was stale vs the current model. */
    staleWarning?: string;
}
/**
 * Shared side-channel writer for the query family (extracted from A5's inspect
 * so inspect/impact/plan/scenario/evidence don't each re-implement it). Writes
 * `<targetDir>/.loopgraph/ws/<fileTag>.md`, stamped with a staleness banner,
 * and — before overwriting — reads any prior file and warns if it was stale
 * (Decision 004 技术点 4 consumer). `buildBody` receives the banner to place it
 * wherever the body wants (top, by convention).
 *
 * Concurrency: the side-channel file is a regenerated-on-demand ADVISORY
 * artifact, not source data — the model YAML is never touched here, only this
 * derived output. The read→judge→write is deliberately NOT locked: the worst
 * case under a race is a spurious/missed staleness *warning* plus one of two
 * near-identical regenerations winning; no model data is at risk, so a file
 * lock is not pulled in for a local dev tool. The write itself IS atomic — a
 * uniquely-named temp (`randomUUID`, so two concurrent writers in the SAME
 * process, e.g. two MCP tool calls for the same id, never collide on the temp)
 * then `rename`, so a reader never observes a half-written file.
 */
export declare function writeSideChannel(targetDir: string, fileTag: string, buildBody: (banner: string) => string): Promise<SideChannelResult>;
//# sourceMappingURL=side-channel.d.ts.map