Doruk Ardahan e40a38aa29 fix(slack): avoid assistant status on synthetic top-level threads ... When reply_in_thread=false, top-level channel events carry their own message ts as metadata.thread_id for session keying. Calling assistant.threads.setStatus on that ts activated a Slack assistant thread ('is thinking...') before the actual response was sent, and the flat reply then never cleared it. send_typing now routes through the same _resolve_thread_ts synthetic- thread guard as message sending, and the gateway threads message_id through progress/status metadata so the adapter can distinguish real threads from synthetic top-level session keys. Reapplied from #18859-sibling PR #17184 by @dorukardahan (both commits: fix + progress-metadata test) onto current main via 3-way apply — the original patched gateway/platforms/slack.py, moved to plugins/platforms/slack/adapter.py in the plugin migration.		2026-07-23 11:36:49 -07:00
..
__init__.py	refactor(gateway): migrate slack/dingtalk/whatsapp/matrix/feishu/telegram/wecom/email/sms adapters to bundled plugins	2026-06-20 10:26:45 -07:00
adapter.py	fix(slack): avoid assistant status on synthetic top-level threads	2026-07-23 11:36:49 -07:00
block_kit.py	fix(slack): sanitize outbound Block Kit payloads at the API boundary	2026-07-22 06:58:34 -07:00
plugin.yaml	Add Slack thread mention gating	2026-07-22 21:14:44 -07:00