jonah.fu 81884173df feat(qq): render answers as markdown ... Deliver final Harness answers to QQ as msg_type=2 markdown so bold, headings, code blocks, lists, and tables render natively in QQ. - add markdown-reply.mjs: chunk long answers at code-fence/table boundaries (4500-char limit) and send each chunk with a unique msg_seq to avoid passive-reply dedup (40054005) - fall back to plain text per chunk when the platform rejects markdown, so bots without markdown capability keep working - route the non-stream final answer path in qq-bridge through the markdown sender; streaming replies already use markdown content type, and command/notice texts stay plain		2026-08-23 21:59:06 +08:00
..
bridge.test.mjs	feat(qq): render answers as markdown	2026-08-23 21:59:06 +08:00
client-api.test.mjs	fix: remember direct recipients for connection tests	2026-08-19 11:24:50 +08:00
client-ui.test.mjs	feat(ui): compact bot connection metadata	2026-08-23 01:20:58 +08:00
config-and-qr.test.mjs	Add QQ bot channel	2026-08-15 17:51:48 +08:00
controller-and-rpc.test.mjs	feat: send test messages during bot connection checks	2026-08-19 03:52:52 +08:00
markdown-reply.test.mjs	feat(qq): render answers as markdown	2026-08-23 21:59:06 +08:00
production.test.mjs	feat: add native result-file delivery	2026-08-23 20:02:06 +08:00
runtime.test.mjs	feat: add native result-file delivery	2026-08-23 20:02:06 +08:00