Observed

The platform count has exceeded the marketed "22" (Photon iMessage, WhatsApp Business Cloud API, SimpleX, Raft added in v0.17.0); exact recount not done this pass. Six adapters are natively maintained (rest community, no SLA), and all platforms still share a single event loop — one network flake can cascade (#21026, OPEN). Confirmed history: Slack cross-channel send fixed (PR #16198 / #15927); Discord non-response (#16744) closed not-planned/implemented-on-main.

1. UPDATE 2026-07-09(v0.18.2): #21026 still OPEN (stale since 2026-05-08); Telegram pool-timeout silent-drop path addressed by PR #54121 (#53524 closed completed) but the structural single-loop root cause remains. Status remains partial.
2. UPDATE 2026-07-17(v0.18.2, tag v2026.7.7.2): #21026 (root-cause single-event-loop issue) and #13281 (Weixin cross-loop send) both CLOSED 2026-07-12 by an automated vendor triage bot (hermes-sweeper, verdict not_planned/implemented_on_main). #21026's cited fix, commit 1011c07966 ("use owned executor for agent work"), is confirmed via `gh api` to already be included in the v0.18.2 release lineage (merged in v2026.7.1) — agent turns now run off the asyncio loop, a real architecture change. However, #21026's own follow-up comments (from the original reporter, after the fix window) report Feishu+QQ disconnects persisting on a 2-platform-only setup, suspecting a websocket keepalive/ping regression unrelated to agent-work blocking — the closure's root-cause attribution is contested by the reporter and not independently re-verified by TD via soak test. #13281's cited fix commit (d7f44faa4) has a diverged git history relative to the v0.18.2 tag (not a clean ancestor), lowering confidence it is cleanly present in the release under test. Net: all issues HM-04 originally tracked are now closed on the tracker and one real architecture change did ship, but TD treats the closure as partial/contested rather than verified. Status remains partial.