dsh-im-ops/test/channels
evanfang0054 3b810fea6b fix(feishu): present Harness questions as threaded replies in topic groups
Regular answers reuse the stream card, which is created through the
reply API targeting the triggering message, so they land in the right
Feishu thread. Pending Harness questions (ask_user_question) were sent
through a fresh message.create with only the chat_id, so in topic
groups they appeared in the group's default area instead of the topic
the conversation belongs to.

Thread question delivery the same way as answers:

- #send accepts { replyTo } and uses im.v1.message.reply, falling back
  to a plain message when the referenced one is gone
- the triggering message id now travels into the interaction context
  and pending state, and #presentInteraction replies to it
- resolved-question notices reply to the user's answer message

- bridge.test.mjs: assert the question is delivered via the reply API
  targeting the triggering message inside a topic group
- lib/index.js: regenerated host bundle
2026-08-31 17:12:55 +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 fix(feishu): present Harness questions as threaded replies in topic groups 2026-08-31 17:12:55 +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