/** The one gate raw errors pass on their way to the wire. Vendo's OWN errors
 *  (code + operator-crafted message) are safe and actionable, so they travel
 *  recognizably prefixed — the thread UI renders the detail line only for
 *  this shape. Anything else (provider/transport internals can carry request
 *  URLs, keys, prompts) stays the fixed generic string. Either way the REAL
 *  error lands in the server log: the operator's terminal is where the
 *  honest message belongs (field case: a dead apps-create turn surfaced as
 *  nothing but "Something went wrong" anywhere).
 *
 *  Its own module so the harness runtime raises the IDENTICAL failure
 *  affordance — banner, Retry, detail line, meter sentence — instead of
 *  inventing a second error UX.
 */
export declare function wireErrorMessage(error: unknown): string;
/** The half of {@link wireErrorMessage} that can NAME the failure, split out so
 *  a caller with its own fallback sentence can still tell the two apart —
 *  the runtime's, for a harness that threw rather than reported. Logs nothing;
 *  the caller that has the raw error owns the operator's line. */
export declare function specificWireErrorMessage(error: unknown): string | undefined;
//# sourceMappingURL=wire-error.d.ts.map