/**
 * Telegram capability for the {@link WorkflowProgressBroker}.
 *
 * Strategy: send the first progress update as a fresh message, then edit it in
 * place on every subsequent update. The broker enforces per-channel throttle
 * (default 5 s) and bypasses it for key events (phase change / new error /
 * tool_end), so users always see milestones promptly without us hammering
 * Telegram's edit rate limit.
 *
 * Failure handling is intentionally narrow:
 *   - `message is not modified` from `editMessageText` → swallow (it's a
 *     no-op the broker shouldn't retry).
 *   - Lost / inaccessible message during edit → fall back to a new send so
 *     the user always sees the latest snapshot.
 *   - 429 / network → bubble up, broker logs and drops the update; the next
 *     scheduled (or key) tick will retry.
 *
 * We deliberately use plain text (no parse_mode) — the snapshot renderer
 * emits ASCII-friendly output and we don't want HTML/markdown surprises with
 * `<` in agent labels or shell-style payloads.
 */
import type { ChannelProgressCapability } from '@xopcai/xopc/agent/workflow/index.js';
import type { TelegramAccountManager } from './account-manager.js';
export declare function createTelegramWorkflowProgressCapability(accountManager: TelegramAccountManager): ChannelProgressCapability;
