switchroom 0.21.10 → 0.21.12

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

@@ -20,10 +20,62 @@ import {
   escapeMarkdown,
   splitMarkdownChunks,
   addParagraphSpacers,
+  codeFenceFor,
   PARAGRAPH_SPACER,
   RICH_MESSAGE_MAX_CHARS,
 } from '../format.js'
 
+// ---------------------------------------------------------------------------
+// codeFenceFor — the single shared fence-width rule (#4702 follow-up)
+// ---------------------------------------------------------------------------
+
+describe('codeFenceFor', () => {
+  test('defaults to three backticks when the body carries no long run', () => {
+    expect(codeFenceFor('')).toBe('```')
+    expect(codeFenceFor('plain body')).toBe('```')
+    expect(codeFenceFor('a ` b `` c')).toBe('```')
+  })
+
+  test('widens to one longer than the longest run in the body', () => {
+    expect(codeFenceFor('a\n```\nb')).toBe('````')
+    expect(codeFenceFor('a\n````\nb')).toBe('`````')
+    expect(codeFenceFor('` `` ``` ````')).toBe('`````')
+    expect(codeFenceFor('x```y')).toBe('````')
+  })
+
+  test('the delimiter is strictly longer than every run in the body', () => {
+    // The property the wire depends on: with the open/close pair the only
+    // runs of that width, nothing in the body can close the fence early or
+    // leave one open.
+    for (const body of ['no ticks', '`', '```', '``````', 'a ``` b ````` c']) {
+      const fence = codeFenceFor(body)
+      for (const run of body.match(/`+/g) ?? []) {
+        expect(run.length).toBeLessThan(fence.length)
+      }
+    }
+  })
+
+  test('does not blow the stack on a body with very many backtick runs', () => {
+    // The former `Math.max(0, ...runs.map(…))` form passed one argument per
+    // run and threw `RangeError: Maximum call stack size exceeded` past the
+    // engine's argument limit, from inside the render path.
+    //
+    // THE COUNT IS LOAD-BEARING and has to clear the argument limit of EVERY
+    // engine that runs this file, because the limit is engine-dependent and
+    // this file is collected by BOTH runners: `bun test` (the shipping
+    // runtime, via the `tests/` positional in scripts/bun-test-ci.sh) and
+    // vitest/Node. Measured on the pinned toolchain by bisecting the former
+    // spread form on this exact body shape — highest surviving run count is
+    // 638,621 on Bun 1.3.13 and 125,289 on Node 22.23.2. So the 200_000 this
+    // started at passed on Bun WITH the bug reinstated: it asserted nothing
+    // in the shipping runtime. 1M is ~1.57x the higher (Bun) limit, and the
+    // shipping loop scans the resulting 2.9 MB body in single-digit
+    // milliseconds, so the margin is nearly free.
+    const body = 'x `'.repeat(1_000_000)
+    expect(codeFenceFor(body)).toBe('```')
+  })
+})
+
 // ---------------------------------------------------------------------------
 // escapeMarkdown — narrowed inline-special escaper (#2669)
 // ---------------------------------------------------------------------------

package/telegram-plugin/tests/turn-supersede-finalizes-prior-card.test.ts

@@ -7,7 +7,7 @@
  * card was never finalized, never unpinned (`fg:<statusKey>` stayed claimed
  * forever), froze on its last landed edit, and left NO `turn-lifecycle clear`
  * line to explain it. Proof from the field: carrie's turn
- * `-1004223464247:_#1078` has a `turn-lifecycle set reason=enqueue` at
+ * `-1004444444444:_#1078` has a `turn-lifecycle set reason=enqueue` at
  * 2026-07-28T18:13:37.554Z and no `clear` anywhere in the log; its stale pinned
  * card was still on screen in the operator's screenshot.
  *

package/telegram-plugin/tests/worker-origin-gap-dispatch.test.ts

@@ -47,7 +47,7 @@ import { decideSubagentHandback } from '../gateway/subagent-handback-inbound-bui
 
 type Db = ReturnType<typeof openTurnsDbInMemory>
 
-const TOPIC_CHAT = '-1004223464247'
+const TOPIC_CHAT = '-1004444444444'
 const TOPIC_THREAD = '77'
 const OWNER_DM = '555'
 

package/telegram-plugin/uat/scenarios/jtbd-supergroup-reply-channel.test.ts

@@ -35,7 +35,7 @@ import { expectMessage } from "../assertions.js";
 
 const AGENT = "test-harness";
 
-/** Bot API marked id of the test supergroup, e.g. -1005164217975. */
+/** Bot API marked id of the test supergroup, e.g. -1006666666666. */
 const SUPERGROUP_ID = Number.parseInt(process.env.SWITCHROOM_UAT_CHAT_ID ?? "", 10);
 
 /** A supergroup turn is a full inbound→claude→outbound round-trip; give

package/telegram-plugin/worker-activity-feed.ts

@@ -850,8 +850,8 @@ export function createWorkerActivityFeed(opts: WorkerActivityFeedOpts): WorkerAc
    *
    * The separator and the topic-less sentinel are both load-bearing. This used
    * to be `` `${chatId} ${threadId ?? ''}` ``, which for a topic-less group
-   * rendered as `-1004223464247 ` — a key ending in a bare space. On disk that
-   * became `"pinKey": "wk:group:-1004223464247 "`: trailing whitespace that
+   * rendered as `-1004444444444 ` — a key ending in a bare space. On disk that
+   * became `"pinKey": "wk:group:-1004444444444 "`: trailing whitespace that
    * survives JSON round-trips, is invisible in every log line and grep, and
    * cannot be distinguished by eye from the same chat WITH a topic. Any operator
    * or tool reconciling rows by chat would silently treat the two as one.