export interface AftRequest {
    id: string;
    command: string;
    [key: string]: unknown;
}
export interface AftResponse {
    id: string;
    success: boolean;
    code?: string;
    message?: string;
    [key: string]: unknown;
}
export declare function sendAftRequest(binaryPath: string, request: AftRequest): Promise<AftResponse>;
/**
 * Send NDJSON requests to a long-running `aft` binary and collect
 * matching responses.
 *
 * The contract is forgiving by design: any stdout line that isn't valid
 * JSON is treated as binary noise (panic message, banner from a wrapper
 * script, log line that escaped to stdout, etc.) and remembered for
 * diagnostics rather than crashing the caller. We only report failure
 * when the binary exits without producing the expected number of valid
 * responses — and when we do, the error message names the specific
 * binary path, the noise we observed, and the stderr tail so the user
 * gets actionable context (issue #29 was a raw `SyntaxError` stack from
 * `JSON.parse` on the first leaked stdout line, with no hint what to
 * try next).
 */
export declare function sendAftRequests(binaryPath: string, requests: AftRequest[]): Promise<AftResponse[]>;
//# sourceMappingURL=aft-bridge.d.ts.map