LangBot/docs/event-based-agents/adapters/00-index.md

EBA Adapter Migration Records

This directory records adapter-level migration details for the Event-Based Agents architecture. Each adapter document should be kept close to the implementation and must answer four questions:

1. What changed in the adapter structure.
2. Which configuration fields are required.
3. Which events and APIs are supported.
4. What has been verified end to end.

Adapter Documents

General acceptance checklist: EBA Adapter Acceptance Checklist

Current acceptance report: EBA Adapter Acceptance Report

Adapter	Status	Document
Telegram	Migrated; partial plugin E2E, real UI inbound image/file verified	Telegram
Discord	Migrated; partial plugin E2E, media-inbound gaps remain	Discord
OneBot v11 / aiocqhttp	Migrated; Matcha UI plus protocol-level multi-component coverage	OneBot v11 / aiocqhttp
DingTalk	Migrated; partial plugin E2E, real UI inbound image/file verified; group gap remains	DingTalk
Lark / Feishu	Migrated; partial live text E2E, media-inbound gap remains	Lark / Feishu
WeCom	Migrated; private text plugin E2E verified, media/group gaps remain	WeCom
WeComBot	Migrated; private text and outbound/API plugin E2E verified, feedback/group gaps remain	WeComBot
Official Account	Migrated; private text plugin E2E verified, proactive outbound not supported	Official Account
QQ Official API	Migrated; WebSocket inbound reached LangBot, model config blocked reply	QQ Official API
Slack	Migrated; private text and outbound/API plugin E2E verified	Slack

Documentation Checklist

When migrating a new adapter, add one document here with:

• Configuration table matching the adapter manifest.
• Supported event list.
• Supported common API list.
• Supported call_platform_api action list.
• Known unsupported APIs and the reason.
• Live test notes, including platform, channel type, destructive operations, and residual risks.
• A clear distinction between real UI inbound media, protocol-level injected inbound media, and bot outbound media.