import { type HTMLAttributes } from "react";
import type { EscalationOfferSegment } from "./types/message.types";
export interface EscalationOfferMessageProps extends HTMLAttributes<HTMLDivElement> {
    data: EscalationOfferSegment['data'];
    status?: EscalationOfferSegment['status'];
    resolvedByName?: string | null;
    onApprove?: EscalationOfferSegment['onApprove'];
    onReject?: EscalationOfferSegment['onReject'];
}
/**
 * Ticket-escalation offer block.
 *
 * Renders THROUGH the client approval card rather than reimplementing it:
 * per Figma (fae chat › "escalation to admin") the offer is that exact
 * component, down to the Approve/Reject labels and the resolved
 * "Approved by {name}" pill. Only the wiring differs — approve/reject call
 * the ticket-escalation mutations, never the tool-approval endpoint — which
 * is why this is a distinct segment type with its own handlers.
 *
 * The handoff receipt that follows an approval is NOT rendered here: it is its
 * own `TICKET_ESCALATED` block on the wire, which also covers the inactivity
 * auto-escalation — a path that raises no offer to infer from.
 */
declare const EscalationOfferMessage: import("react").ForwardRefExoticComponent<EscalationOfferMessageProps & import("react").RefAttributes<HTMLDivElement>>;
export { EscalationOfferMessage };
//# sourceMappingURL=escalation-offer-message.d.ts.map