polygram 0.18.1 → 0.18.2

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.18.1",
+  "version": "0.18.2",
   "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. Multi-bot, multi-chat, per-topic isolation; SQLite transcripts; inline-keyboard approvals. Bundles /polygram:status|logs|pair-code|approvals admin commands plus history (transcript queries) and polygram-send (out-of-turn IPC sends with file-upload validation) skills.",
   "keywords": [
     "telegram",

package/lib/telegram/display-hint.js

@@ -63,13 +63,39 @@ const TABLES_AND_HEADERS_SECTION_PLAIN = [
 const TABLES_AND_HEADERS_SECTION_RICH = [
   '### Rich formatting is available in this chat',
   '',
-  'This chat has rich-text rendering enabled. Real Telegram markdown tables, headings (`#`/`##`/etc.), task lists, and collapsible `<details>` blocks now render as an actual structured message, not flattened text — use them when they make an answer clearer or easier to scan (a comparison, a set of steps, a key/value summary, a checklist tracking progress). No character-width budget applies to tables here; write a normal markdown table.',
+  'This chat has rich-text rendering enabled. Real Telegram markdown tables, headings (`#`/`##`/etc.), task lists, collapsible `<details>` blocks, blockquotes (`>`), and dividers (`---`) now render as an actual structured message, not flattened text. No character-width budget applies to tables here; write a normal markdown table.',
   '',
-  '**Task lists for progress:** `- [ ] pending step` / `- [x] done step` renders as a real checkbox list — the natural way to show multi-step progress as it happens.',
+  '**Use the real construct instead of faking it with bold text and emoji.** In plain-mode chats you had to fake structure with **bold** pseudo-headers, emoji bullets (✅ ❓ 🕓, •, etc.), and plain-text separator lines, because headings and checkboxes rendered as flattened text there. That workaround is unnecessary here and looks worse than the real thing. When you catch yourself about to write a bold pseudo-heading or an emoji-bulleted list, use the actual construct instead:',
+  '',
+  '- A named group of items (e.g. "ready to apply" / "needs your input" / "deferred") → a real heading (`## Ready to apply`), not `**Ready to apply:**`.',
+  '- A list of items each with a yes/no/pending state (approve this? confirm that?) → a real task list (`- [ ] item`), not `• item` with an emoji glued on.',
+  '- A comparison or key/value summary → a real markdown table.',
+  '- A quoted aside, caveat, or callout you want visually set apart → a real blockquote (`> like this`), not a bold prefix.',
+  '- A visual break between distinct sections of a long reply → a real divider (`---` on its own line), the same way you already reach for it, but now it renders as a divider instead of literal dashes.',
+  '- Verbose supporting detail (a diff, a log, raw output) you want available but not front-and-center → `<details><summary>Label</summary>...</details>`.',
+  '',
+  'Worked example — triaging a batch of items into groups, each item with its own state:',
+  '',
+  '```',
+  '## Ready to apply',
+  '',
+  '- [ ] Merge the two lists into one (#18)',
+  '- [ ] Fix the delivery-time wording (#4)',
+  '',
+  '## Need your input',
+  '',
+  '- [ ] Hemming service — confirm we can offer it (#11)',
+  '',
+  '## Deferred to v2',
+  '',
+  '- [ ] Size-guide page (#16)',
+  '```',
+  '',
+  '**Task lists for progress:** `- [ ] pending step` / `- [x] done step` renders as a real checkbox list — the natural way to show multi-step progress, a batch of items awaiting confirmation, or anything else with a per-item done/pending state.',
   '',
   '**Collapsible detail:** wrap verbose logs/diffs/output you want available but not front-and-center in `<details><summary>Label</summary>...</details>`.',
   '',
-  'Not every reply needs this — plain prose is still right for a normal conversational answer. Reach for structure when the CONTENT is structured, not by default.',
+  'Not every reply needs this — plain prose is still right for a normal conversational answer with no distinct items or sections. Reach for structure when the CONTENT is structured, not by default.',
   '',
   '### Other Telegram quirks',
   '',

package/lib/telegram/rich.js

@@ -3,9 +3,10 @@
  *
  * Companion to format.js's markdown→HTML pipeline, not a replacement:
  * this only runs when needsRichRendering() finds a construct (task list,
- * table, <details>, heading) that the plain HTML pipeline can't express
- * natively, AND the chat has opted in (config.richText). Everything else
- * stays on the existing toTelegramHtml() path.
+ * table, <details>, heading, blockquote, divider) that the plain HTML
+ * pipeline can't express natively, AND the chat has opted in
+ * (config.richText). Everything else stays on the existing
+ * toTelegramHtml() path.
  *
  * Block text fields carry plain strings only. Inline bold, italic, and
  * links are flattened rather than mapped to an unverified nested schema.
@@ -61,6 +62,8 @@ const TASK_ITEM_RE = /^[ \t]{0,3}[-*+][ \t]+\[[ xX]\][ \t]+/m;
 const TABLE_ROW_RE = /^[ \t]{0,3}\|?[ \t]*:?-{2,}:?[ \t]*\|/m;
 const DETAILS_RE = /<details[ \t>]/i;
 const HEADING_RE = /^#{1,6}[ \t]+\S/m;
+const BLOCKQUOTE_RE = /^[ \t]{0,3}>[ \t]?\S/m;
+const DIVIDER_RE = /^[ \t]{0,3}(-{3,}|\*{3,}|_{3,})[ \t]*$/m;
 const FENCE_LINE_RE = /^[ \t]{0,3}(`{3,}|~{3,})/;
 
 // Code-fence content renders literally, so heading, checklist, and table
@@ -109,7 +112,9 @@ function needsRichRendering(markdown) {
   return TASK_ITEM_RE.test(scoped)
       || TABLE_ROW_RE.test(scoped)
       || DETAILS_RE.test(scoped)
-      || HEADING_RE.test(scoped);
+      || HEADING_RE.test(scoped)
+      || BLOCKQUOTE_RE.test(scoped)
+      || DIVIDER_RE.test(scoped);
 }
 
 // ─── marked instance for block-level tokenization ────────────────────

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.18.1",
+  "version": "0.18.2",
   "description": "Telegram daemon for Claude Code that preserves the OpenClaw per-chat session model. Migration path for OpenClaw users moving to Claude Code.",
   "main": "lib/ipc/client.js",
   "bin": {