/**
 * The bytes this session wrote to a file, for use as a diff base.
 *
 * THE BRIDGE THIS CROSSES. The hook knows the client's real `session_id` and
 * the file's content; the MCP server knows neither. They share a filesystem and
 * a project, so the hook records what it wrote and the server reads it back --
 * the same shape the legacy PowerShell path used, rather than a new invention.
 *
 * WHY A SESSION SCOPE IS NOT OPTIONAL. A diff base is only sound if the caller
 * already holds the bytes being diffed against. The knowledge-graph snapshot
 * cannot supply that: `indexFile` runs on every file either hook observes,
 * READS INCLUDED and across sessions, so it answers "what did some hook last
 * see". Using it would hand a fresh session `// No changes` for a file it has
 * never seen -- withholding content while reporting success, which is worse
 * than the full resend this replaces.
 *
 * EVERY UNCERTAINTY RESOLVES TO NULL, and null means "resend the file", which
 * is today's behaviour. So this can add a saving and can never subtract one.
 * Nothing here throws: a diff-base lookup must not be able to fail a read.
 */
/** The content this session wrote to `filePath`, or null. */
export declare function authoredBase(filePath: string): string | null;
//# sourceMappingURL=authored-base.d.ts.map