shivasymbl c934c533db feat(slack): opt-in Block Kit markdown block rendering for standard markdown ... Slack's Block Kit `markdown` block accepts standard markdown (tables, headers, task lists, fenced code with syntax highlighting, links) and lets Slack translate it natively — eliminating the lossy markdown→mrkdwn conversion for the rendered layout. Enable via platforms.slack.extra.markdown_blocks. Safety rails added on top of the original design: * opt-in (default off) — Slack documents the block for 'apps that use platform AI features' and does not guarantee availability across all app types / surfaces, so unconditional adoption is not safe yet * the mrkdwn-converted text field is ALWAYS kept as the notification/search/accessibility fallback * content over Slack's 12k cumulative markdown-block cap declines to the rich_blocks renderer / plain text path * the existing block-rejection retry (invalid_blocks / msg_too_long / too_many_blocks) re-sends the plain mrkdwn payload, so an unsupported surface degrades gracefully instead of dropping the message * when both modes are enabled, markdown_blocks is preferred over the local rich_blocks renderer; rich_blocks remains the fallback Adapted from #8554 by @shivasymbl — the original patched the deleted gateway/platforms/slack.py and switched unconditionally; reimplemented against the plugin adapter's _maybe_blocks/sanitize_blocks pipeline. Fixes #8552.		2026-07-23 11:50:28 -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	feat(slack): opt-in Block Kit markdown block rendering for standard markdown	2026-07-23 11:50:28 -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