/**
 * Turn a driver-start/prompt failure into a friendly, actionable message when the
 * cause is a missing/unusable agent binary; otherwise return `null` so the caller
 * surfaces the raw error unchanged.
 *
 * The bridge classifies these as `category: "config"` and carries a `hint`, but the
 * shape reaching the CLI varies: omp's `start()` rejects with the raw spawn error
 * (`code === "ENOENT"`), while the subprocess CLI drivers reject with the classified
 * `AgentError` attached under `.detail`. Duck-type across all of them.
 */
export declare function friendlyDriverError(err: unknown): string | null;
//# sourceMappingURL=driver-error.d.ts.map