I would like to add a multi-bot feature，multi-bot routing multi-agent

[lessthink]

Description

I would like to add a multi-bot feature where each bot corresponds to a unique agent. For example, TG_BOT_01 maps to agent_01, TG_BOT_02 to agent_02, SLACK_BOT to agent_03, and SLACK_BOT2 to agent_04.

Requesting multi-bot support with a 1-to-1 mapping between bots and agents:

TG_BOT_01 ⮕ agent_01

TG_BOT_02 ⮕ agent_02

SLACK_BOT ⮕ agent_03

SLACK_BOT2 ⮕ agent_04"

Alternatives Considered

No response

Additional Context

No response

[lessthink]

@huoko 干的漂亮

[jaberjaber23]

The infrastructure for this partially exists. The binding system supports account_id matching in BindingMatchRule, and the router has resolve_with_context() that evaluates account_id rules. What's missing is config support for multiple bots per channel type (currently one TelegramConfig, not a Vec) and adapter identity tracking to populate account_id in dispatch context. This is a multi-session feature that requires config schema changes, adapter trait updates, and bridge wiring. Leaving open for future implementation.