dsh-im-ops/test/channels
evanfang0054 fd6e0af81b feat(feishu): thread command replies, cards, and approvals to the triggering message
Plain command replies (menu cards, session/workspace/watch lists, /new,
/status, /compact, /archived, model and preset commands) and Harness
approval prompts were sent as fresh messages keyed only by chat_id, so
in topic groups they landed in the group's default area instead of the
topic the conversation belongs to.

Deliver them as replies to the triggering message, mirroring how stream
answers already thread:

- #sendCard accepts { replyTo } and replies interactively, falling back
  to a plain card when the referenced message is gone
- command replies, status text, menu/session/workspace/watch cards,
  approval prompts and resolved-question notices all carry the
  triggering message id
- batch-input failure notices follow the same rule

- bridge.test.mjs: /new in a topic group must thread the confirmation
  text and the menu card to the command message
- lib/index.js: regenerated host bundle
2026-08-31 20:06:04 +08:00
..
dingtalk feat: add stable proactive delivery 2026-08-30 11:24:53 +08:00
discord feat: add stable proactive delivery 2026-08-30 11:24:53 +08:00
feishu feat(feishu): thread command replies, cards, and approvals to the triggering message 2026-08-31 20:06:04 +08:00
office fix(office): use a neutral base URL example 2026-08-21 03:57:59 +08:00
qq feat(qq): parse inbound QQ face/emoji tags into readable text 2026-08-31 09:07:55 +08:00
shared feat: add message source context enhancement 2026-08-29 10:46:06 +08:00
slack feat: add stable proactive delivery 2026-08-30 11:24:53 +08:00
telegram fix(telegram): isolate long polling transport 2026-08-31 03:31:07 +08:00
wecom feat: add stable proactive delivery 2026-08-30 11:24:53 +08:00
weixin feat: add stable proactive delivery 2026-08-30 11:24:53 +08:00
whatsapp feat: add stable proactive delivery 2026-08-30 11:24:53 +08:00