From 6146a173f19953ed765686d11e824713e62f1453 Mon Sep 17 00:00:00 2001 From: dave Date: Tue, 24 Mar 2026 21:54:19 +0000 Subject: [PATCH] storkit: done 384_story_whatsapp_markdown_to_whatsapp_formatting_conversion --- ...kdown_to_whatsapp_formatting_conversion.md | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .storkit/work/5_done/384_story_whatsapp_markdown_to_whatsapp_formatting_conversion.md diff --git a/.storkit/work/5_done/384_story_whatsapp_markdown_to_whatsapp_formatting_conversion.md b/.storkit/work/5_done/384_story_whatsapp_markdown_to_whatsapp_formatting_conversion.md new file mode 100644 index 0000000..444ef76 --- /dev/null +++ b/.storkit/work/5_done/384_story_whatsapp_markdown_to_whatsapp_formatting_conversion.md @@ -0,0 +1,23 @@ +--- +name: "WhatsApp markdown-to-WhatsApp formatting conversion" +--- + +# Story 384: WhatsApp markdown-to-WhatsApp formatting conversion + +## User Story + +As a WhatsApp user, I want bot messages to use WhatsApp-native formatting instead of raw markdown, so that headers, bold text, and links render properly. + +## Acceptance Criteria + +- [ ] Headers (# ## ### etc.) are converted to bold text (*Header*) in WhatsApp messages +- [ ] Markdown bold (**text**) is converted to WhatsApp bold (*text*) +- [ ] Markdown strikethrough (~~text~~) is converted to WhatsApp strikethrough (~text~) +- [ ] Markdown links [text](url) are converted to readable format: text (url) +- [ ] Code blocks and inline code are preserved as-is (already compatible) +- [ ] Matrix bot formatting is completely unaffected (conversion only applied in WhatsApp send paths) +- [ ] Existing WhatsApp chunking (4096 char limit) still works correctly after conversion + +## Out of Scope + +- TBD