Repository navigation
What this is
A self-hosted IM transport layer. It holds platform credentials and connections, verifies signatures, decrypts payloads, and normalizes seven platforms into one envelope. It does not know what a room, a seat or an invoice is — that belongs to the caller.
First release — verified on real platforms, not on mocks
WeCom gets a leg that cannot be broken by an egress change. After moving the intelligent-robot leg onto the official SDK's long connection, proactive send works with no prior inbound (measured: errcode 0 in 360 / 308 / 291 ms across three runs and two groups). The old HTTP-callback leg could only reply inside a one-hour passive window and was gated by 企业可信IP. That leg is now honestly declared url-keyed, and the declaration is asserted by a test that names the evidence.
A real image came through decrypted. A message with a photo produced an envelope whose media address returned a 234,816-byte JPEG — magic ffd8ffe0 → JFIF. A tampered ticket and a malformed one both answer 410.
A pod roll loses nothing. Deleting the running pod brought up a new one that re-established both long connections unattended; bindings came back from Postgres and the acceptance queue replayed what had arrived.
Fixed because the live run found them
- The envelope was missing
chatType. A group message and a direct message both collapsed to one bare string inchatKey, and the platform answers them through different APIs. - There was no way to list or retire a binding. A WeCom long connection allows exactly one live connection per bot, so duplicate bindings actively disconnected each other — and the deployed service had four of them with no route to remove any.
- A 10-second outbound timeout was a guaranteed failure from a China egress. A real call to slack.com measured 10,971 ms. It is now one shared 30-second constant instead of eight literals.
Also in this release
Seven adapters (WeCom intelligent robot, WeCom self-built app, WeCom group robot, WeChat official account, Feishu/Lark, Slack, Telegram), a durable acceptance queue that persists before acking the platform, HMAC-signed media tickets with a 5-minute TTL, and a capability gate that refuses to boot an adapter that does not declare its outbound shape.
Full operations manual: docs/OPERATIONS.md.