switchroom 0.19.36 → 0.19.37

package/dist/cli/switchroom.js

@@ -2120,7 +2120,7 @@ var init_esm = __esm(() => {
 });
 
 // src/build-info.ts
-var VERSION = "0.19.36", COMMIT_SHA = "ba505b15";
+var VERSION = "0.19.37", COMMIT_SHA = "5d2f9a17";
 
 // src/cli/resolve-version.ts
 import { existsSync, readFileSync } from "node:fs";
@@ -31355,8 +31355,8 @@ into your system prompt every session; this is the conversational summary.
   Kicking off a worker to crawl the changelog.
 
   **What it'll do**
-  \u2022 pull every entry since v0.14
-  \u2022 flag anything user-facing
+  - pull every entry since v0.14
+  - flag anything user-facing
 
   **Back in** ~2 min with a synthesized summary.
 - Use backtick-wrapped \`inline code\` for filenames, commands, and
@@ -31540,7 +31540,8 @@ You're writing for a phone screen in Telegram. Every reply renders as rich Markd
   fenced code blocks ALWAYS with a language
   hint (\`\`\`diff, \`\`\`json, \`\`\`bash \u2014 bare fence only for non-code fixed-width output);
   and the flagship \u2014 the **expandable blockquote** \`**> first line\` + \`> continuation\`
-  for a long quote, stack trace, or detailed aside the reader can collapse. Use it
+  for a long quote, stack trace, or detailed aside the reader can collapse. The \`**>\`
+  opener must be at the line start (column 0) \u2014 never indented \u2014 or it won't parse. Use it
   whenever a bulky supporting block would otherwise dominate the message.
 
 Renders wrong on this path \u2014 never emit: underline (\`__x__\` renders as bold),
@@ -31623,6 +31624,8 @@ var init_scaffold = __esm(() => {
     "mcp__hindsight__list_banks",
     "mcp__hindsight__get_memory",
     "mcp__hindsight__list_memories",
+    "mcp__hindsight__invalidate_memory",
+    "mcp__hindsight__update_memory",
     "mcp__hindsight__get_document",
     "mcp__hindsight__list_documents",
     "mcp__hindsight__delete_document",

package/dist/host-control/main.js

@@ -21311,7 +21311,7 @@ function allocateAgentUid(name) {
 }
 
 // src/build-info.ts
-var VERSION = "0.19.36";
+var VERSION = "0.19.37";
 
 // src/setup/hindsight-recall-tunables.ts
 var RECALL_DEADLINE_HEADROOM_SECONDS = 2;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "switchroom",
   "//version": "NOT the release version — source of truth is the git tag, resolved by scripts/build.mjs:resolveVersion() (see CLAUDE.md > Standard release process). This field is stale by design and only the Layer-4 dev/non-tag fallback for build.mjs + src/cli/resolve-version.ts; do NOT bump it expecting a release to pick it up. npm-pack tarball naming needs a real version — do that as an UNCOMMITTED pack-time bump (see release step 6), never a committed one.",
-  "version": "0.19.36",
+  "version": "0.19.37",
   "description": "Run Claude Code 24/7 on your Claude Pro/Max subscription over Telegram. Open-source alternative to OpenClaw and NanoClaw — no API keys.",
   "type": "module",
   "bin": {

package/telegram-plugin/bridge/bridge.ts

@@ -94,7 +94,7 @@ const TOOL_SCHEMAS = [
       // client and this detail was being silently truncated away.
       'FORUM TOPICS: a reply is auto-routed back to the topic the question came from, so do NOT pass message_thread_id on a normal reply — pass the inbound\'s origin_turn_id instead, so the answer lands in the right topic even if a message from another topic arrived while you were working. message_thread_id is only for deliberately posting into a topic that is not the one you were asked in. ' +
       // Format modes: likewise moved out of the truncated instructions string.
-      'FORMAT: the default format is "html" — write natural markdown and it is auto-converted to Telegram HTML (bold, italic, code, links, code blocks). Pass format: "markdownv2" for MarkdownV2 with auto-escaping, or "text" for plain text sent verbatim.',
+      'FORMAT: by default your text is rendered as rich GFM markdown (Bot API 10.1) — write natural markdown (bold, italic, code, links, code blocks, lists, tables) and it renders as-is. Pass format: "text" to send plain text verbatim with no rendering. "html" and "markdownv2" are accepted legacy aliases that route through the exact same single rich GFM path — there is no separate HTML engine and no auto-escaping.',
     inputSchema: {
       type: 'object',
       properties: {
@@ -105,7 +105,7 @@ const TOOL_SCHEMAS = [
         message_thread_id: { type: 'string', description: 'Forum topic thread ID. Auto-applied from the last inbound message in the same chat if not specified.' },
         origin_turn_id: { type: 'string', description: 'In a forum supergroup, pass back the origin_turn_id attribute from the <channel> message you are answering. It pins the reply to that message\'s topic even if another topic\'s turn started meanwhile. Omit in DMs / single-topic chats.' },
         files: { type: 'array', items: { type: 'string' }, description: 'Absolute file paths to attach. Images send as photos; other types as documents. Max 50MB each. Telegram rejects photos with extreme dimensions (aspect ratio over ~10:1, width+height over 10000px, or over 10MB) — very tall images like full-page screenshots are auto-rerouted as documents; crop or split them first if the user should see them inline as photos.' },
-        format: { type: 'string', enum: ['html', 'markdownv2', 'text'], description: "Rendering mode. 'html' (default) converts markdown to Telegram HTML." },
+        format: { type: 'string', enum: ['html', 'markdownv2', 'text'], description: "Rendering mode. Default renders your text as rich GFM markdown (Bot API 10.1). 'text' sends plain text verbatim. 'html' and 'markdownv2' are legacy aliases that route through the same single rich GFM path — no separate HTML engine, no auto-escaping." },
         disable_web_page_preview: { type: 'boolean', description: 'Disable link preview thumbnails. Default: true.' },
         protect_content: { type: 'boolean', description: 'When true, Telegram prevents the message from being forwarded or saved.' },
         quote_text: { type: 'string', description: 'Surgical quote: specific text to highlight from the reply_to message. Requires reply_to.' },
@@ -180,7 +180,7 @@ const TOOL_SCHEMAS = [
         chat_id: { type: 'string' },
         message_id: { type: 'string' },
         text: { type: 'string' },
-        format: { type: 'string', enum: ['html', 'markdownv2', 'text'], description: "Rendering mode. 'html' (default) converts markdown to Telegram HTML." },
+        format: { type: 'string', enum: ['html', 'markdownv2', 'text'], description: "Rendering mode. Default renders your text as rich GFM markdown (Bot API 10.1). 'text' sends plain text verbatim. 'html' and 'markdownv2' are legacy aliases that route through the same single rich GFM path — no separate HTML engine, no auto-escaping." },
       },
       required: ['chat_id', 'message_id', 'text'],
     },
@@ -341,7 +341,7 @@ const TOOL_SCHEMAS = [
       type: 'object',
       properties: {
         chat_id: { type: 'string', description: 'Chat that should receive the question. Pass from inbound meta.' },
-        question: { type: 'string', description: 'The question text. Plain text or HTML. Keep it short — buttons render below.' },
+        question: { type: 'string', description: 'The question text. Plain text or GFM markdown (rendered through the same rich path as replies). Keep it short — buttons render below.' },
         options: {
           type: 'array',
           items: { type: 'string' },

package/telegram-plugin/dist/bridge/bridge.js

@@ -25061,7 +25061,7 @@ var mcp = new Server({ name: "telegram", version: "1.0.0" }, {
 var TOOL_SCHEMAS = [
   {
     name: "reply",
-    description: "Reply on Telegram. Pass chat_id from the inbound message. By default the reply is a quote-reply to the latest inbound user message in this chat+thread \u2014 pass quote:false to opt out, or pass an explicit reply_to to thread under a specific earlier message. files (absolute paths) attach images or documents. inline_keyboard adds tappable buttons (URL or callback) under the message \u2014 single-tap actions beat asking the user to type YES. " + "FORUM TOPICS: a reply is auto-routed back to the topic the question came from, so do NOT pass message_thread_id on a normal reply \u2014 pass the inbound's origin_turn_id instead, so the answer lands in the right topic even if a message from another topic arrived while you were working. message_thread_id is only for deliberately posting into a topic that is not the one you were asked in. " + 'FORMAT: the default format is "html" \u2014 write natural markdown and it is auto-converted to Telegram HTML (bold, italic, code, links, code blocks). Pass format: "markdownv2" for MarkdownV2 with auto-escaping, or "text" for plain text sent verbatim.',
+    description: "Reply on Telegram. Pass chat_id from the inbound message. By default the reply is a quote-reply to the latest inbound user message in this chat+thread \u2014 pass quote:false to opt out, or pass an explicit reply_to to thread under a specific earlier message. files (absolute paths) attach images or documents. inline_keyboard adds tappable buttons (URL or callback) under the message \u2014 single-tap actions beat asking the user to type YES. " + "FORUM TOPICS: a reply is auto-routed back to the topic the question came from, so do NOT pass message_thread_id on a normal reply \u2014 pass the inbound's origin_turn_id instead, so the answer lands in the right topic even if a message from another topic arrived while you were working. message_thread_id is only for deliberately posting into a topic that is not the one you were asked in. " + 'FORMAT: by default your text is rendered as rich GFM markdown (Bot API 10.1) \u2014 write natural markdown (bold, italic, code, links, code blocks, lists, tables) and it renders as-is. Pass format: "text" to send plain text verbatim with no rendering. "html" and "markdownv2" are accepted legacy aliases that route through the exact same single rich GFM path \u2014 there is no separate HTML engine and no auto-escaping.',
     inputSchema: {
       type: "object",
       properties: {
@@ -25072,7 +25072,7 @@ var TOOL_SCHEMAS = [
         message_thread_id: { type: "string", description: "Forum topic thread ID. Auto-applied from the last inbound message in the same chat if not specified." },
         origin_turn_id: { type: "string", description: "In a forum supergroup, pass back the origin_turn_id attribute from the <channel> message you are answering. It pins the reply to that message's topic even if another topic's turn started meanwhile. Omit in DMs / single-topic chats." },
         files: { type: "array", items: { type: "string" }, description: "Absolute file paths to attach. Images send as photos; other types as documents. Max 50MB each. Telegram rejects photos with extreme dimensions (aspect ratio over ~10:1, width+height over 10000px, or over 10MB) \u2014 very tall images like full-page screenshots are auto-rerouted as documents; crop or split them first if the user should see them inline as photos." },
-        format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. 'html' (default) converts markdown to Telegram HTML." },
+        format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. Default renders your text as rich GFM markdown (Bot API 10.1). 'text' sends plain text verbatim. 'html' and 'markdownv2' are legacy aliases that route through the same single rich GFM path \u2014 no separate HTML engine, no auto-escaping." },
         disable_web_page_preview: { type: "boolean", description: "Disable link preview thumbnails. Default: true." },
         protect_content: { type: "boolean", description: "When true, Telegram prevents the message from being forwarded or saved." },
         quote_text: { type: "string", description: "Surgical quote: specific text to highlight from the reply_to message. Requires reply_to." },
@@ -25146,7 +25146,7 @@ var TOOL_SCHEMAS = [
         chat_id: { type: "string" },
         message_id: { type: "string" },
         text: { type: "string" },
-        format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. 'html' (default) converts markdown to Telegram HTML." }
+        format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. Default renders your text as rich GFM markdown (Bot API 10.1). 'text' sends plain text verbatim. 'html' and 'markdownv2' are legacy aliases that route through the same single rich GFM path \u2014 no separate HTML engine, no auto-escaping." }
       },
       required: ["chat_id", "message_id", "text"]
     }
@@ -25303,7 +25303,7 @@ var TOOL_SCHEMAS = [
       type: "object",
       properties: {
         chat_id: { type: "string", description: "Chat that should receive the question. Pass from inbound meta." },
-        question: { type: "string", description: "The question text. Plain text or HTML. Keep it short \u2014 buttons render below." },
+        question: { type: "string", description: "The question text. Plain text or GFM markdown (rendered through the same rich path as replies). Keep it short \u2014 buttons render below." },
         options: {
           type: "array",
           items: { type: "string" },

package/telegram-plugin/dist/gateway/gateway.js

@@ -6923,7 +6923,11 @@ function normalizePunctuation(text) {
   const escNonce = nonce.replace(/[.*+?^${}()|[\]\\]/g, "\\$&");
   const linkRestoreRe = new RegExp(`\x00RML${escNonce}_(\\d+)\x00`, "g");
   const restoreLinks = (s) => s.replace(linkRestoreRe, (_m, idx) => linkMasks[Number(idx)] ?? _m);
-  let out = maskedAutolinks.replace(/(\S)[ \t][\u2014\u2013][ \t](?=(\S))/g, (_m, a, b) => /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `).replace(/(\w)\u2014(?=(\w))/g, (_m, a, b) => /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `).replace(/(\w)\u2013(?=\w)/g, "$1-");
+  const rewriteDashes = (line) => line.replace(/(\S)[ \t][\u2014\u2013][ \t](?=(\S))/g, (_m, a, b) => /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `).replace(/(\w)\u2014(?=(\w))/g, (_m, a, b) => /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `).replace(/(\w)\u2013(?=\w)/g, "$1-");
+  const isQuotedLine = (line) => isBlockquoteLine(line) || line.trimStart().startsWith("**>");
+  let out = maskedAutolinks.split(`
+`).map((line) => isQuotedLine(line) ? line : rewriteDashes(line)).join(`
+`);
   out = restoreLinks(out);
   out = out.split(`
 `).map((line) => line.replace(/^([ \t]*)[\u2022\u00b7][ \t]+/, "$1- ")).join(`
@@ -13607,7 +13611,7 @@ function guardUnsupportedTokens(text) {
 var CARET_PAIR, FOOTNOTE_MARKER, DETAILS_BLOCK, ORPHAN_TAGS;
 var init_unsupported_token_guard = __esm(() => {
   CARET_PAIR = /\^([A-Za-z0-9]+)\^/g;
-  FOOTNOTE_MARKER = /\[\^\d+\](?!:)/g;
+  FOOTNOTE_MARKER = /\[\^[A-Za-z0-9]{1,10}\](?!:)/g;
   DETAILS_BLOCK = /<details[^>]*>\s*(?:<summary[^>]*>([\s\S]*?)<\/summary>)?([\s\S]*?)<\/details>/gi;
   ORPHAN_TAGS = /<\/?(?:details|summary)[^>]*>/gi;
 });
@@ -99668,10 +99672,10 @@ function startOutboxSweep(deps) {
 }
 
 // ../src/build-info.ts
-var VERSION2 = "0.19.36";
-var COMMIT_SHA = "ba505b15";
-var COMMIT_DATE = "2026-07-30T07:53:24Z";
-var LATEST_PR = 4019;
+var VERSION2 = "0.19.37";
+var COMMIT_SHA = "5d2f9a17";
+var COMMIT_DATE = "2026-07-30T08:57:38Z";
+var LATEST_PR = 4023;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts

package/telegram-plugin/dist/server.js

@@ -24827,7 +24827,7 @@ var init_bridge = __esm(async () => {
   TOOL_SCHEMAS = [
     {
       name: "reply",
-      description: "Reply on Telegram. Pass chat_id from the inbound message. By default the reply is a quote-reply to the latest inbound user message in this chat+thread \u2014 pass quote:false to opt out, or pass an explicit reply_to to thread under a specific earlier message. files (absolute paths) attach images or documents. inline_keyboard adds tappable buttons (URL or callback) under the message \u2014 single-tap actions beat asking the user to type YES. " + "FORUM TOPICS: a reply is auto-routed back to the topic the question came from, so do NOT pass message_thread_id on a normal reply \u2014 pass the inbound's origin_turn_id instead, so the answer lands in the right topic even if a message from another topic arrived while you were working. message_thread_id is only for deliberately posting into a topic that is not the one you were asked in. " + 'FORMAT: the default format is "html" \u2014 write natural markdown and it is auto-converted to Telegram HTML (bold, italic, code, links, code blocks). Pass format: "markdownv2" for MarkdownV2 with auto-escaping, or "text" for plain text sent verbatim.',
+      description: "Reply on Telegram. Pass chat_id from the inbound message. By default the reply is a quote-reply to the latest inbound user message in this chat+thread \u2014 pass quote:false to opt out, or pass an explicit reply_to to thread under a specific earlier message. files (absolute paths) attach images or documents. inline_keyboard adds tappable buttons (URL or callback) under the message \u2014 single-tap actions beat asking the user to type YES. " + "FORUM TOPICS: a reply is auto-routed back to the topic the question came from, so do NOT pass message_thread_id on a normal reply \u2014 pass the inbound's origin_turn_id instead, so the answer lands in the right topic even if a message from another topic arrived while you were working. message_thread_id is only for deliberately posting into a topic that is not the one you were asked in. " + 'FORMAT: by default your text is rendered as rich GFM markdown (Bot API 10.1) \u2014 write natural markdown (bold, italic, code, links, code blocks, lists, tables) and it renders as-is. Pass format: "text" to send plain text verbatim with no rendering. "html" and "markdownv2" are accepted legacy aliases that route through the exact same single rich GFM path \u2014 there is no separate HTML engine and no auto-escaping.',
       inputSchema: {
         type: "object",
         properties: {
@@ -24838,7 +24838,7 @@ var init_bridge = __esm(async () => {
           message_thread_id: { type: "string", description: "Forum topic thread ID. Auto-applied from the last inbound message in the same chat if not specified." },
           origin_turn_id: { type: "string", description: "In a forum supergroup, pass back the origin_turn_id attribute from the <channel> message you are answering. It pins the reply to that message's topic even if another topic's turn started meanwhile. Omit in DMs / single-topic chats." },
           files: { type: "array", items: { type: "string" }, description: "Absolute file paths to attach. Images send as photos; other types as documents. Max 50MB each. Telegram rejects photos with extreme dimensions (aspect ratio over ~10:1, width+height over 10000px, or over 10MB) \u2014 very tall images like full-page screenshots are auto-rerouted as documents; crop or split them first if the user should see them inline as photos." },
-          format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. 'html' (default) converts markdown to Telegram HTML." },
+          format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. Default renders your text as rich GFM markdown (Bot API 10.1). 'text' sends plain text verbatim. 'html' and 'markdownv2' are legacy aliases that route through the same single rich GFM path \u2014 no separate HTML engine, no auto-escaping." },
           disable_web_page_preview: { type: "boolean", description: "Disable link preview thumbnails. Default: true." },
           protect_content: { type: "boolean", description: "When true, Telegram prevents the message from being forwarded or saved." },
           quote_text: { type: "string", description: "Surgical quote: specific text to highlight from the reply_to message. Requires reply_to." },
@@ -24912,7 +24912,7 @@ var init_bridge = __esm(async () => {
           chat_id: { type: "string" },
           message_id: { type: "string" },
           text: { type: "string" },
-          format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. 'html' (default) converts markdown to Telegram HTML." }
+          format: { type: "string", enum: ["html", "markdownv2", "text"], description: "Rendering mode. Default renders your text as rich GFM markdown (Bot API 10.1). 'text' sends plain text verbatim. 'html' and 'markdownv2' are legacy aliases that route through the same single rich GFM path \u2014 no separate HTML engine, no auto-escaping." }
         },
         required: ["chat_id", "message_id", "text"]
       }
@@ -25069,7 +25069,7 @@ var init_bridge = __esm(async () => {
         type: "object",
         properties: {
           chat_id: { type: "string", description: "Chat that should receive the question. Pass from inbound meta." },
-          question: { type: "string", description: "The question text. Plain text or HTML. Keep it short \u2014 buttons render below." },
+          question: { type: "string", description: "The question text. Plain text or GFM markdown (rendered through the same rich path as replies). Keep it short \u2014 buttons render below." },
           options: {
             type: "array",
             items: { type: "string" },

package/telegram-plugin/format.ts

@@ -718,21 +718,37 @@ export function normalizePunctuation(text: string): string {
   const restoreLinks = (s: string): string =>
     s.replace(linkRestoreRe, (_m, idx: string) => linkMasks[Number(idx)] ?? _m)
 
+  // The dash rewrite runs per line so blockquote lines can be exempted:
+  // `>` blockquotes are reserved for VERBATIM quoted text, and rewriting an
+  // author's ` — ` to `, ` inside a quotation would corrupt what they quoted.
+  // The expandable-blockquote opener `**>` is a blockquote line too even though
+  // isBlockquoteLine (which keys on a leading `>`) doesn't catch the `**`
+  // prefix, so exempt it explicitly. Code spans and link hrefs stay masked
+  // throughout, so their dashes are already protected on every line.
+  const rewriteDashes = (line: string): string =>
+    line
+      // 1. Space-flanked em/en dash. Numeric range keeps a hyphen. The right
+      //    flank is a LOOKAHEAD (captured, not consumed) so consecutive spaced
+      //    dashes ("a — b — c") all normalize in one pass — a consumed \S would
+      //    swallow the char that anchors the next match.
+      .replace(/(\S)[ \t][—–][ \t](?=(\S))/g, (_m, a: string, b: string) =>
+        /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `,
+      )
+      // 2. Bare em-dash between word chars. Numeric range keeps a hyphen.
+      //    Right flank is a lookahead for the same consecutive-match reason.
+      .replace(/(\w)—(?=(\w))/g, (_m, a: string, b: string) =>
+        /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `,
+      )
+      // 3. Bare en-dash between word chars → hyphen (ranges: 2019–2024).
+      .replace(/(\w)–(?=\w)/g, '$1-')
+
+  const isQuotedLine = (line: string): boolean =>
+    isBlockquoteLine(line) || line.trimStart().startsWith('**>')
+
   let out = maskedAutolinks
-    // 1. Space-flanked em/en dash. Numeric range keeps a hyphen. The right
-    //    flank is a LOOKAHEAD (captured, not consumed) so consecutive spaced
-    //    dashes ("a — b — c") all normalize in one pass — a consumed \S would
-    //    swallow the char that anchors the next match.
-    .replace(/(\S)[ \t][—–][ \t](?=(\S))/g, (_m, a: string, b: string) =>
-      /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `,
-    )
-    // 2. Bare em-dash between word chars. Numeric range keeps a hyphen.
-    //    Right flank is a lookahead for the same consecutive-match reason.
-    .replace(/(\w)—(?=(\w))/g, (_m, a: string, b: string) =>
-      /\d/.test(a) && /\d/.test(b) ? `${a}-` : `${a}, `,
-    )
-    // 3. Bare en-dash between word chars → hyphen (ranges: 2019–2024).
-    .replace(/(\w)–(?=\w)/g, '$1-')
+    .split('\n')
+    .map((line) => (isQuotedLine(line) ? line : rewriteDashes(line)))
+    .join('\n')
 
   // Restore link hrefs now that the dash passes are done — before the bullet
   // pass and the code restore.

package/telegram-plugin/render/unsupported-token-guard.ts

@@ -59,12 +59,16 @@ import { splitProtectedSegments } from "./code-segments.js";
  *  `a^2+b^2=c^2`, `2^8`, and `x^n` all pass through untouched. */
 const CARET_PAIR = /\^([A-Za-z0-9]+)\^/g;
 
-/** Footnote reference marker `[^N]` (digits only) NOT immediately followed by
- *  `:` (which would make it a footnote DEFINITION line we leave intact). Removed
- *  entirely. Restricting the id to digits keeps this off in-prose bracket
- *  literals like `array[^index]` and regex-ish `[^/]`, which are NOT footnotes
- *  and would otherwise be silently eaten. */
-const FOOTNOTE_MARKER = /\[\^\d+\](?!:)/g;
+/** Footnote reference marker `[^id]` where the id is a short alphanumeric run
+ *  (`[^1]`, `[^note]`, `[^ref]`) NOT immediately followed by `:` (which would
+ *  make it a footnote DEFINITION line we leave intact). Removed entirely.
+ *  Requiring the id to be 1–10 ALPHANUMERIC chars keeps this off regex-ish
+ *  literals like `[^/]`, `[^\s]`, `[^-a-z]`, whose bodies contain punctuation
+ *  and so never match. In-prose subscript-ish `array[^i]` outside a code span
+ *  is a rare theoretical false positive (an `i` id matches); code spans are
+ *  masked upstream by splitProtectedSegments so real code is safe, and prose
+ *  that writes a literal `[^i]` reads as footnote noise anyway. */
+const FOOTNOTE_MARKER = /\[\^[A-Za-z0-9]{1,10}\](?!:)/g;
 
 /** `<details>…</details>` with an optional leading `<summary>…</summary>`.
  *  Dot-all via `[\s\S]`; non-greedy so adjacent blocks don't merge. */

package/telegram-plugin/tests/format-consistency.test.ts

@@ -245,6 +245,24 @@ describe('normalizePunctuation', () => {
     expect(normalizePunctuation('<not—a—url>')).toBe('<not, a, url>')
   })
 
+  test('does NOT rewrite a dash inside a `>` blockquote (verbatim quote)', () => {
+    // `>` blockquotes hold quoted text the author is reproducing verbatim;
+    // rewriting their em-dash to `, ` corrupts the quotation.
+    expect(normalizePunctuation('> she said — plainly — no')).toBe(
+      '> she said — plainly — no',
+    )
+    // Indented blockquote line is still a blockquote.
+    expect(normalizePunctuation('  > quoted — text')).toBe('  > quoted — text')
+    // The expandable-blockquote opener `**>` is a blockquote line too.
+    expect(normalizePunctuation('**> first — line\n> continues — here')).toBe(
+      '**> first — line\n> continues — here',
+    )
+    // Prose OUTSIDE the quote still normalizes; only the quoted line is spared.
+    expect(normalizePunctuation('intro — here\n> quote — verbatim\nafter — end')).toBe(
+      'intro, here\n> quote — verbatim\nafter, end',
+    )
+  })
+
   test('idempotent', () => {
     const once = normalizePunctuation('a — b\n• c\nd—e\n1–2')
     expect(normalizePunctuation(once)).toBe(once)

package/telegram-plugin/tests/mcp-instructions-budget.test.ts

@@ -162,8 +162,15 @@ describe("moved instruction content landed in tool descriptions", () => {
 
   it("format modes landed in the reply description", () => {
     expect(bridgeCode).toContain("FORMAT:");
-    expect(bridgeCode).toMatch(/default format is "html"/);
+    // The description must describe the ONE real render path (rich GFM), and
+    // still name the legacy aliases so the enum values stay documented. It must
+    // NOT resurrect the deleted-engine claims (html→HTML conversion, MarkdownV2
+    // auto-escaping) — those are false at HEAD (single GFM path, no escaping).
+    expect(bridgeCode).toMatch(/rich GFM markdown/);
     expect(bridgeCode).toContain("markdownv2");
+    expect(bridgeCode).not.toMatch(/default format is "html"/);
+    expect(bridgeCode).not.toMatch(/auto-converted to Telegram HTML/);
+    expect(bridgeCode).not.toMatch(/MarkdownV2 with auto-escaping/);
   });
 
   it("history-buffer rationale landed in get_recent_messages", () => {

package/telegram-plugin/tests/render/unsupported-token-guard.test.ts

@@ -71,15 +71,46 @@ describe("guardUnsupportedTokens — deterministic send-time repair", () => {
     expect(guardUnsupportedTokens("x^2^ metres")).toBe("x2 metres");
   });
 
-  it("leaves in-prose bracket literals intact, repairs real numeric footnotes", () => {
-    // `array[^index]` is a negated-char-class / index literal, not a footnote.
-    expect(guardUnsupportedTokens("array[^index] lookup")).toBe(
-      "array[^index] lookup",
+  it("repairs alphanumeric footnote markers, not just numeric", () => {
+    // POLISH-4: widened from digits-only so `[^note]`/`[^ref]` no longer ship
+    // as literal bracket noise. Each would survive UNTOUCHED on origin/main.
+    expect(guardUnsupportedTokens("see the note[^note] here")).toBe(
+      "see the note here",
+    );
+    expect(guardUnsupportedTokens("as shown[^ref] above")).toBe(
+      "as shown above",
+    );
+    expect(guardUnsupportedTokens("point[^fn1] made")).toBe("point made");
+    // A single-letter id is a footnote too.
+    expect(guardUnsupportedTokens("claim[^a] holds")).toBe("claim holds");
+    // Definition lines with an alphanumeric id are still left intact (`(?!:)`).
+    expect(guardUnsupportedTokens("[^note]: the definition")).toBe(
+      "[^note]: the definition",
     );
+  });
+
+  it("leaves regex-literal negated char classes intact", () => {
+    // Real negated char classes contain punctuation / ranges / escapes, so the
+    // alphanumeric-only id requirement excludes them — these stay verbatim.
     expect(guardUnsupportedTokens("use [^/] to match")).toBe(
       "use [^/] to match",
     );
-    // A real numeric footnote marker is still stripped.
+    expect(guardUnsupportedTokens("strip [^a-z] chars")).toBe(
+      "strip [^a-z] chars",
+    );
+    expect(guardUnsupportedTokens('match [^"] here')).toBe('match [^"] here');
+    // Accepted tradeoff (task POLISH-4): a PURE-alphanumeric negated class in
+    // BARE prose like `array[^index]` is now treated as a footnote and stripped.
+    // This is rare — regex/index literals in real prose live in code spans,
+    // which splitProtectedSegments masks (see code-span test below).
+    expect(guardUnsupportedTokens("array[^index] lookup")).toBe("array lookup");
+    // …but inside a code span the same literal is untouched.
+    expect(guardUnsupportedTokens("`array[^index]` lookup")).toBe(
+      "`array[^index]` lookup",
+    );
+  });
+
+  it("repairs a real numeric footnote marker", () => {
     expect(guardUnsupportedTokens("see the note[^1] here")).toBe(
       "see the note here",
     );