/**
 * WeChat capability for the workflow progress broker.
 *
 * WeChat (ilink/personal account) does not expose an "edit message" API for
 * bot replies, so live edit-in-place — what Telegram and Feishu do — is
 * structurally impossible. Trying to fake it with a `append` mode would
 * spam the chat with one message per tick, which violates the social
 * properties of the surface ("Don't @ me twenty times").
 *
 * Strategy: **final-only**. The broker silently drops every mid-run update;
 * when `tool_end` fires, the broker calls us once with `isFinal: true` and
 * the full final snapshot rendered as text. The user sees a single
 * tasteful summary at the end.
 *
 * Routing: sessionKey `agent:main:weixin:<accountId>:direct:<ilinkUserId>`. We need a
 * valid `contextToken` for the recipient — which requires the user to have
 * recently messaged the bot (the token is harvested from inbound). If
 * missing, we throw and the broker logs; the run still completes, just
 * without a WeChat notification. This is consistent with how other WeChat
 * outbound paths behave.
 */
import type { ChannelProgressCapability } from '@xopcai/xopc/agent/workflow/channel-capability.js';
import type { Config } from '@xopcai/xopc/config/schema.js';
export declare function createWeixinWorkflowProgressCapability(opts: {
    getConfig: () => Config | undefined;
}): ChannelProgressCapability;