import type { LTApiResult, LTApiAuth } from '../../types/sdk';
/**
 * Resolve a pending escalation with a human-provided payload.
 *
 * Handles multiple resolution paths:
 * 1. **Condition signal** — lightweight `conditionLT` signal via metadata.signal_id
 * 2. **Signal-routed** — full signal_routing via YAML engine or Durable handle
 * 3. **Strategy triage** — escalation strategy redirects to a triage workflow
 * 4. **Notification-only** — no workflow_type; acknowledge and close
 * 5. **Re-run** — restart the original workflow with resolver data injected
 *
 * Password fields in the resolver payload are replaced with ephemeral
 * tokens (15-minute TTL) so plaintext never enters the signal store.
 */
export declare function resolveEscalation(input: {
    id: string;
    resolverPayload: Record<string, any>;
}, _auth: LTApiAuth): Promise<LTApiResult>;
/**
 * Resolve an efficient (atomic) escalation directly by its `signal_key` and
 * resume the waiting workflow in place. For webhook callers that know the
 * deterministic signal id (e.g. `signal-scan-ar-${orderId}`) and want to skip
 * the id lookup. RBAC-scoped to the caller's visible roles.
 */
export declare function resolveBySignalKey(input: {
    signalKey: string;
    resolverPayload: Record<string, any>;
}, auth: LTApiAuth): Promise<LTApiResult>;