switchroom 0.14.20 → 0.14.21

package/dist/agent-scheduler/index.js

@@ -11070,10 +11070,10 @@ var TelegramChannelSchema = exports_external.object({
   }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default — content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
   coalesce: exports_external.object({
     window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 — a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, …). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 — a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, …). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
   }).optional().describe("Inbound coalescing — how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
   interrupt: exports_external.object({
-    safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false — the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+    safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
     max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short — the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
   }).optional().describe("Interrupt timing — how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
   webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default — webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 — see #577.)"),

package/dist/auth-broker/index.js

@@ -11070,10 +11070,10 @@ var TelegramChannelSchema = exports_external.object({
   }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default — content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
   coalesce: exports_external.object({
     window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 — a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, …). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 — a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, …). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
   }).optional().describe("Inbound coalescing — how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
   interrupt: exports_external.object({
-    safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false — the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+    safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
     max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short — the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
   }).optional().describe("Interrupt timing — how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
   webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default — webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 — see #577.)"),

package/dist/cli/notion-write-pretool.mjs

@@ -11817,10 +11817,10 @@ var TelegramChannelSchema = exports_external.object({
   }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default \u2014 content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
   coalesce: exports_external.object({
     window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 \u2014 a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, \u2026). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 \u2014 a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, \u2026). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
   }).optional().describe("Inbound coalescing \u2014 how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
   interrupt: exports_external.object({
-    safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false \u2014 the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+    safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
     max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short \u2014 the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
   }).optional().describe("Interrupt timing \u2014 how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
   webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default \u2014 webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 \u2014 see #577.)"),

package/dist/cli/switchroom.js

@@ -13634,10 +13634,10 @@ var init_schema = __esm(() => {
     }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default \u2014 content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
     coalesce: exports_external.object({
       window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 \u2014 a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, \u2026). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 \u2014 a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, \u2026). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
     }).optional().describe("Inbound coalescing \u2014 how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
     interrupt: exports_external.object({
-      safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false \u2014 the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+      safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
       max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short \u2014 the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
     }).optional().describe("Interrupt timing \u2014 how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
     webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default \u2014 webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 \u2014 see #577.)"),
@@ -49421,8 +49421,8 @@ var {
 } = import__.default;
 
 // src/build-info.ts
-var VERSION = "0.14.20";
-var COMMIT_SHA = "c8b965b2";
+var VERSION = "0.14.21";
+var COMMIT_SHA = "62ddded0";
 
 // src/cli/agent.ts
 init_source();

package/dist/host-control/main.js

@@ -13805,10 +13805,10 @@ var TelegramChannelSchema = exports_external.object({
   }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default — content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
   coalesce: exports_external.object({
     window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 — a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, …). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+    max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 — a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, …). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
   }).optional().describe("Inbound coalescing — how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
   interrupt: exports_external.object({
-    safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false — the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+    safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
     max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short — the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
   }).optional().describe("Interrupt timing — how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
   webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default — webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 — see #577.)"),

package/dist/vault/approvals/kernel-server.js

@@ -11385,10 +11385,10 @@ var init_schema = __esm(() => {
     }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default — content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
     coalesce: exports_external.object({
       window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 — a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, …). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 — a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, …). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
     }).optional().describe("Inbound coalescing — how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
     interrupt: exports_external.object({
-      safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false — the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+      safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
       max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short — the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
     }).optional().describe("Interrupt timing — how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
     webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default — webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 — see #577.)"),

package/dist/vault/broker/server.js

@@ -11385,10 +11385,10 @@ var init_schema = __esm(() => {
     }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default — content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
     coalesce: exports_external.object({
       window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 — a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, …). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 — a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, …). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
     }).optional().describe("Inbound coalescing — how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
     interrupt: exports_external.object({
-      safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false — the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+      safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
       max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short — the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
     }).optional().describe("Interrupt timing — how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
     webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default — webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 — see #577.)"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "switchroom",
-  "version": "0.14.20",
+  "version": "0.14.21",
   "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": {
@@ -25,7 +25,7 @@
     "pretest": "npm run build",
     "test": "vitest run && bun test telegram-plugin/tests/history.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/silent-reply-guard.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/registry/api-registry.test.ts telegram-plugin/registry/turns-schema.test.ts telegram-plugin/tests/idle-footer-wiring.test.ts telegram-plugin/tests/subagent-tracker-hooks.test.ts telegram-plugin/tests/resolve-calling-subagent.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts",
     "test:vitest": "vitest run",
-    "test:bun": "bun test src/watchdog/state.test.ts src/watchdog/policy.test.ts src/vault/grants.test.ts src/vault/write-grants.test.ts src/vault/broker/server-grants.test.ts src/vault/broker/server-write-grants.test.ts src/vault/broker/server-mint-grant-passphrase-attest.test.ts src/vault/broker/server-passphrase-attest.test.ts src/vault/broker/server-mint-grant-posture-attest.test.ts src/vault/broker/client-token.test.ts src/vault/broker/server-unlock.test.ts src/vault/broker/auto-unlock.test.ts src/vault/broker/drift-detection.test.ts tests/vault-broker-passphrase.test.ts src/cli/vault-get-broker.test.ts src/vault/resolver-via-broker.test.ts src/vault/broker/scope.test.ts src/vault/broker/server.test.ts src/drive/disconnect.test.ts src/drive/grants.test.ts src/drive/oauth.test.ts src/drive/onboarding.test.ts src/drive/reconciler.test.ts src/drive/vault-slots.test.ts src/drive/wrapper.test.ts src/vault/approvals/kernel.test.ts src/vault/approvals/schema-idempotent.test.ts src/vault/broker/server-approvals.test.ts telegram-plugin/tests/boot-probes.test.ts telegram-plugin/tests/boot-version-string.test.ts telegram-plugin/tests/history.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/silent-reply-guard.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/tests/resolve-calling-subagent.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/uat/load-env.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts",
+    "test:bun": "bun test src/watchdog/state.test.ts src/watchdog/policy.test.ts src/vault/grants.test.ts src/vault/write-grants.test.ts src/vault/broker/server-grants.test.ts src/vault/broker/server-write-grants.test.ts src/vault/broker/server-mint-grant-passphrase-attest.test.ts src/vault/broker/server-passphrase-attest.test.ts src/vault/broker/server-mint-grant-posture-attest.test.ts src/vault/broker/client-token.test.ts src/vault/broker/server-unlock.test.ts src/vault/broker/auto-unlock.test.ts src/vault/broker/drift-detection.test.ts tests/vault-broker-passphrase.test.ts src/cli/vault-get-broker.test.ts src/vault/resolver-via-broker.test.ts src/vault/broker/scope.test.ts src/vault/broker/server.test.ts src/drive/disconnect.test.ts src/drive/grants.test.ts src/drive/oauth.test.ts src/drive/onboarding.test.ts src/drive/reconciler.test.ts src/drive/vault-slots.test.ts src/drive/wrapper.test.ts src/vault/approvals/kernel.test.ts src/vault/approvals/schema-idempotent.test.ts src/vault/broker/server-approvals.test.ts telegram-plugin/tests/boot-probes.test.ts telegram-plugin/tests/boot-version-string.test.ts telegram-plugin/tests/history.test.ts telegram-plugin/tests/history-reaper.test.ts telegram-plugin/tests/ipc-server-client.test.ts telegram-plugin/tests/ipc-server-race.test.ts telegram-plugin/tests/gateway-bridge.test.ts telegram-plugin/tests/gateway-startup-mutex.test.ts telegram-plugin/tests/gateway-clean-shutdown-marker.test.ts telegram-plugin/tests/boot-card-dedupe.test.ts telegram-plugin/tests/boot-card-reason.test.ts telegram-plugin/tests/progress-update.test.ts telegram-plugin/tests/quota-cache.test.ts telegram-plugin/tests/silent-reply-guard.test.ts telegram-plugin/tests/unhandled-rejection-policy.test.ts telegram-plugin/tests/registry-turns.test.ts telegram-plugin/registry/subagents.test.ts telegram-plugin/tests/turns-writer.test.ts telegram-plugin/tests/resolve-calling-subagent.test.ts telegram-plugin/tests/gateway-update-placeholder-dispatch.test.ts telegram-plugin/tests/reaction-trigger.test.ts telegram-plugin/tests/reaction-trigger-flow.test.ts telegram-plugin/uat/load-env.test.ts telegram-plugin/uat/feed-matcher.test.ts telegram-plugin/gateway/webhook-ingest-server.test.ts",
     "test:watch": "vitest",
     "lint": "tsc --noEmit && node scripts/check-plugin-references.mjs && bash scripts/check-bot-api-wrapping.sh && node scripts/check-bun-test-imports.mjs && node scripts/check-no-pii-secrets.mjs && node scripts/check-vault-test-hermeticity.mjs && node scripts/check-no-broadcast-delivery.mjs",
     "lint:tsc": "tsc --noEmit",

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

@@ -23739,10 +23739,10 @@ var init_schema = __esm(() => {
     }).optional().describe("Long-reply publishing via Telegraph (#579). When enabled, replies " + "above the threshold publish as a Telegraph article rendered in " + "Telegram via native Instant View. Off by default \u2014 content " + "residency is real for some personas (lawyer, health-coach with PHI). " + "Cascades from defaults.channels.telegram.telegraph. " + "(Migrated from per-agent root in #596.)"),
     coalesce: exports_external.object({
       window_ms: exports_external.number().int().nonnegative().optional().describe("Sliding-window (ms) for merging consecutive inbound messages from " + "the same sender+topic into ONE Claude turn. Each new message resets " + "the timer; the turn starts once the sender pauses for this long. " + "Catches forwarded bursts, pasted text the Telegram client split " + "into several messages, and mixed text+media forwards. Default 500. " + "Set 0 to disable (every message becomes its own turn). Raise for " + "users who think in multiple short messages; the trade-off is the " + "single-message turn start is delayed by this much (the \uD83D\uDC40 ack still " + "fires immediately, so perceived latency is unchanged)."),
-      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 1 \u2014 a second photo/document/voice within the " + "coalesce window (or an album / media_group_id) starts its own turn, " + "preserving the historical single-attachment behaviour. Raise to let " + "a forwarded album or a text+multi-image burst arrive as one turn; " + "the agent then sees numbered attachment fields (image_path, " + "image_path_2, \u2026). Excess attachments beyond the cap spill into the " + "next turn. Each attachment is downloaded, so a high cap on a slow " + "link delays turn start.")
+      max_attachments: exports_external.number().int().positive().optional().describe("Maximum number of media attachments carried into ONE coalesced " + "Claude turn. Default 10 \u2014 a full Telegram album (media_group caps " + "at 10) or a text+multi-image forwarded burst arrives as a single " + "turn; the agent sees numbered attachment fields (image_path, " + "image_path_2, \u2026). Set 1 to restore the historical " + "single-attachment-per-turn behaviour. Excess attachments beyond " + "the cap spill into the next turn. Each attachment is downloaded, " + "so a high cap on a slow link delays turn start.")
     }).optional().describe("Inbound coalescing \u2014 how the gateway groups rapid consecutive messages " + "into a single turn so a forwarded album or split paste doesn't fan out " + "into N separate turns. Cascades from defaults.channels.telegram.coalesce."),
     interrupt: exports_external.object({
-      safe_boundary: exports_external.boolean().optional().describe("When true, a `!`-prefix interrupt that arrives while the agent is " + "mid-tool-call is DEFERRED: the SIGINT and the replacement turn wait " + "until the in-flight tool call finishes (a clean boundary) instead of " + "C-c'ing the agent mid-write/mid-bash. If no tool is in flight the " + "interrupt still fires immediately. Bounded by max_wait_ms so a long " + "tool never strands the user. Default false \u2014 the interrupt fires " + "synchronously the moment `!` is received (historical behaviour). " + "Rapid repeated `!` while one is pending coalesce into a single " + "deferred interrupt carrying the latest body."),
+      safe_boundary: exports_external.boolean().optional().describe("When true (the default), a `!`-prefix interrupt that arrives while " + "the agent is mid-tool-call is DEFERRED: the SIGINT and the " + "replacement turn wait until the in-flight tool call finishes (a " + "clean boundary) instead of C-c'ing the agent mid-write/mid-bash. If " + "no tool is in flight the interrupt still fires immediately. Bounded " + "by max_wait_ms so a long tool never strands the user. Set false to " + "fire synchronously the moment `!` is received (historical " + "behaviour). Rapid repeated `!` while one is pending coalesce into a " + "single deferred interrupt carrying the latest body."),
       max_wait_ms: exports_external.number().int().positive().optional().describe("Upper bound (ms) the gateway waits for a safe boundary before firing " + "a deferred `!` interrupt anyway. Only consulted when safe_boundary is " + "true. Default 8000. Keep it short \u2014 the user explicitly asked to " + "interrupt, so a long in-flight tool shouldn't ghost them; the cap " + "trades a tiny risk of a mid-tool C-c for a guaranteed response.")
     }).optional().describe("Interrupt timing \u2014 how a `!`-prefix interrupt behaves when it lands " + "mid-tool-call. Off by default (fire immediately). Cascades from " + "defaults.channels.telegram.interrupt."),
     webhook_sources: exports_external.array(exports_external.enum(["github", "generic"])).optional().describe("External webhook sources allowed to ingest events into this agent's " + "log. POST /webhook/<agent>/<source> on the switchroom web server. " + "Each source has its own signature verification ('github' = " + "X-Hub-Signature-256 HMAC-SHA256, 'generic' = Bearer token). " + "Per-source secret read from ~/.switchroom/webhook-secrets.json " + "keyed by [agent][source]. Verified events append to " + "<agent>/telegram/webhook-events.jsonl for the agent to read on " + "demand. Off by default \u2014 webhook is the only untrusted-inbound " + "surface in the system, so opt-in is mandatory. " + "Cascades from defaults.channels.telegram.webhook_sources. " + "(Migrated from per-agent root in #596 \u2014 see #577.)"),
@@ -31074,6 +31074,9 @@ function resolveInterruptMaxWaitMs(configured) {
     return configured;
   return DEFAULT_INTERRUPT_MAX_WAIT_MS;
 }
+function resolveSafeBoundaryEnabled(configured) {
+  return configured !== false;
+}
 
 // sticker-aliases.ts
 function looksLikeFileId(s) {
@@ -31613,6 +31616,10 @@ function inboundCoalesceKey(chatId, threadId, userId) {
 }
 
 // gateway/coalesce-attachments.ts
+var DEFAULT_MAX_ATTACHMENTS = 10;
+function resolveCoalesceMaxAttachments(configured) {
+  return Math.max(1, configured ?? DEFAULT_MAX_ATTACHMENTS);
+}
 function splitCoalescedAttachments(entries, hasAttachment, maxAttachments) {
   const withAttachment = entries.filter(hasAttachment);
   const capped = withAttachment.slice(0, Math.max(1, maxAttachments));
@@ -31956,6 +31963,9 @@ class DeferredDoneReactions {
 }
 
 // worker-activity-feed.ts
+function isWorkerActivityFeedEnabled(envVal) {
+  return envVal !== "0";
+}
 var DESC_MAX = 80;
 var TOOL_ARG_MAX = 64;
 var SUMMARY_MAX = 100;
@@ -51360,10 +51370,10 @@ function sweepStaleTurnActiveMarker(stateDir, opts) {
 }
 
 // ../src/build-info.ts
-var VERSION = "0.14.20";
-var COMMIT_SHA = "c8b965b2";
-var COMMIT_DATE = "2026-05-31T01:51:10Z";
-var LATEST_PR = 2018;
+var VERSION = "0.14.21";
+var COMMIT_SHA = "62ddded0";
+var COMMIT_DATE = "2026-05-31T02:54:29Z";
+var LATEST_PR = 2024;
 var COMMITS_AHEAD_OF_TAG = 0;
 
 // gateway/boot-version.ts
@@ -53118,7 +53128,7 @@ function looksLikeAuthCode(text) {
 }
 var bufferedAttachmentKeys = new Map;
 function coalesceMaxAttachments() {
-  return Math.max(1, loadAccess().coalesceMaxAttachments ?? 1);
+  return resolveCoalesceMaxAttachments(loadAccess().coalesceMaxAttachments);
 }
 var inboundCoalescer = createInboundCoalescer({
   gapMs: () => loadAccess().coalescingGapMs ?? 500,
@@ -56407,7 +56417,7 @@ async function handleInbound(ctx, text, downloadImage, attachment, extraAttachme
     const agentName3 = process.env.SWITCHROOM_AGENT_NAME;
     const access2 = loadAccess();
     deferInterrupt = !interrupt.emptyBody && decideInterruptTiming({
-      safeBoundaryEnabled: access2.interruptSafeBoundary === true,
+      safeBoundaryEnabled: resolveSafeBoundaryEnabled(access2.interruptSafeBoundary),
       midToolCall: toolFlightTracker.isMidToolCall()
     }) === "defer";
     process.stderr.write(`telegram gateway: interrupt-marker received chat_id=${chat_id} agent=${agentName3 ?? "-"} body_len=${interrupt.body.length} empty=${interrupt.emptyBody} defer=${deferInterrupt} in_flight=${toolFlightTracker.inFlightCount()}
@@ -61654,7 +61664,7 @@ var didOneTimeSetup = false;
         if (streamMode === "checklist") {
           const watcherAgentDir = resolveAgentDirFromEnv();
           if (watcherAgentDir != null) {
-            const workerFeedEnabled = process.env.SWITCHROOM_WORKER_ACTIVITY_FEED === "1";
+            const workerFeedEnabled = isWorkerActivityFeedEnabled(process.env.SWITCHROOM_WORKER_ACTIVITY_FEED);
             const workerActivityFeed = createWorkerActivityFeed({
               bot: {
                 sendMessage: async (cid, text, sendOpts) => {

package/telegram-plugin/gateway/coalesce-attachments.ts

@@ -36,6 +36,15 @@ export interface ResolvedExtraAttachment {
  * `maxAttachments` is floored at 1 — a cap of 0 or negative would strip the
  * primary, silently dropping the only attachment.
  */
+/** Default attachments folded into one coalesced turn: a full Telegram album
+ *  (media_group caps at 10). Floored at 1 so the only attachment is never
+ *  stripped. Set channels.telegram.coalesce.max_attachments to override. */
+export const DEFAULT_MAX_ATTACHMENTS = 10
+
+export function resolveCoalesceMaxAttachments(configured: number | undefined): number {
+  return Math.max(1, configured ?? DEFAULT_MAX_ATTACHMENTS)
+}
+
 export function splitCoalescedAttachments<T>(
   entries: T[],
   hasAttachment: (e: T) => boolean,

package/telegram-plugin/gateway/gateway.ts

@@ -39,6 +39,7 @@ import {
   ToolFlightTracker,
   decideInterruptTiming,
   resolveInterruptMaxWaitMs,
+  resolveSafeBoundaryEnabled,
 } from './interrupt-defer.js'
 import {
   resolveStickerSendArgs,
@@ -56,10 +57,14 @@ import {
 } from '../telegraph.js'
 import { OutboundDedupCache } from '../recent-outbound-dedup.js'
 import { createInboundCoalescer, inboundCoalesceKey } from './inbound-coalesce.js'
-import { splitCoalescedAttachments, buildExtraAttachmentMeta } from './coalesce-attachments.js'
+import {
+  splitCoalescedAttachments,
+  buildExtraAttachmentMeta,
+  resolveCoalesceMaxAttachments,
+} from './coalesce-attachments.js'
 import { StatusReactionController } from '../status-reactions.js'
 import { DeferredDoneReactions } from '../reaction-defer.js'
-import { createWorkerActivityFeed } from '../worker-activity-feed.js'
+import { createWorkerActivityFeed, isWorkerActivityFeedEnabled } from '../worker-activity-feed.js'
 import { isTelegramReplyTool, isTelegramSurfaceTool } from '../tool-names.js'
 import { appendActivityLabel } from '../tool-activity-summary.js'
 import { toolLabel } from '../tool-labels.js'
@@ -776,14 +781,15 @@ type Access = {
   parseMode?: 'html' | 'markdownv2' | 'text'
   disableLinkPreview?: boolean
   coalescingGapMs?: number
-  /** A2: max media attachments folded into one coalesced turn. Default 1
-   *  (single-attachment behaviour). Projected from
+  /** A2: max media attachments folded into one coalesced turn. Default 10
+   *  (a full Telegram album / forwarded burst arrives as one turn). Set 1 to
+   *  restore single-attachment behaviour. Projected from
    *  channels.telegram.coalesce.max_attachments by scaffold. */
   coalesceMaxAttachments?: number
-  /** Problem B: when true, a `!` interrupt that lands mid-tool-call is
-   *  deferred until the in-flight tool finishes (bounded by
-   *  interruptMaxWaitMs) before SIGINT + resume. Default false (fire
-   *  synchronously). Projected from channels.telegram.interrupt.safe_boundary. */
+  /** Problem B: when true (the default), a `!` interrupt that lands
+   *  mid-tool-call is deferred until the in-flight tool finishes (bounded by
+   *  interruptMaxWaitMs) before SIGINT + resume. Set false to fire
+   *  synchronously. Projected from channels.telegram.interrupt.safe_boundary. */
   interruptSafeBoundary?: boolean
   /** Upper bound (ms) to wait for a safe boundary before firing a deferred
    *  interrupt anyway. Default 8000. Projected from
@@ -3137,13 +3143,13 @@ type CoalescePayload = {
 
 // Count of attachment-bearing entries currently buffered per coalesce key.
 // A new attachment for a key whose count has reached the per-agent cap
-// (coalesce.max_attachments, default 1) bypasses coalescing (see
+// (coalesce.max_attachments, default 10) bypasses coalescing (see
 // handleInboundCoalesced) so no media is dropped past the cap. Cleared on
 // flush (below) and on the synchronous bypass path.
 const bufferedAttachmentKeys = new Map<string, number>()
 
 function coalesceMaxAttachments(): number {
-  return Math.max(1, loadAccess().coalesceMaxAttachments ?? 1)
+  return resolveCoalesceMaxAttachments(loadAccess().coalesceMaxAttachments)
 }
 
 const inboundCoalescer = createInboundCoalescer<CoalescePayload>({
@@ -8727,11 +8733,11 @@ async function handleInboundCoalesced(
   const maxAttachments = coalesceMaxAttachments()
 
   // Albums (media_group_id): coalesce only when the cap allows >1 attachment
-  // (A2). At the default cap of 1 each album part keeps its own turn exactly
-  // as before — the single-attachment merge can't carry sibling photos, so
-  // bypassing avoids dropping them. With a raised cap the parts share the
-  // coalesce key and fold into one multi-attachment turn (the cap-overflow
-  // bypass below catches parts past the cap).
+  // (A2). At the default cap of 10 the parts share the coalesce key and fold
+  // into one multi-attachment turn (the cap-overflow bypass below catches
+  // parts past the cap). With the cap lowered to 1 each album part keeps its
+  // own turn — the single-attachment merge can't carry sibling photos, so
+  // bypassing avoids dropping them.
   if (hasAttachment && ctx.message?.media_group_id != null && maxAttachments <= 1) {
     return handleInbound(ctx, text, downloadImage, attachment)
   }
@@ -8741,7 +8747,8 @@ async function handleInboundCoalesced(
 
   // An attachment past the per-agent cap would be dropped by the capped merge.
   // Bypass it to its own turn so no media is silently lost. At the default
-  // cap of 1 this fires on the SECOND attachment, preserving A1 behaviour.
+  // cap of 10 this fires on the 11th attachment; with the cap lowered to 1 it
+  // fires on the SECOND, preserving A1 behaviour.
   if (hasAttachment) {
     const probeKey = inboundCoalesceKey(
       String(ctx.chat!.id),
@@ -8785,9 +8792,9 @@ async function handleInboundCoalesced(
   // Coalescing disabled (window <= 0): flush immediately, preserving any
   // media this message carried.
   if (result.bypass) return handleInbound(ctx, text, downloadImage, attachment)
-  // Count the open window's attachments so a third+ (or second, at the
-  // default cap) bypasses rather than overflows the capped merge (cleared
-  // in onFlush).
+  // Count the open window's attachments so any part past the cap (the 11th
+  // at the default cap of 10, or the second when lowered to 1) bypasses
+  // rather than overflows the capped merge (cleared in onFlush).
   if (hasAttachment) bufferedAttachmentKeys.set(key, (bufferedAttachmentKeys.get(key) ?? 0) + 1)
 }
 
@@ -8998,7 +9005,7 @@ async function handleInbound(
     deferInterrupt =
       !interrupt.emptyBody &&
       decideInterruptTiming({
-        safeBoundaryEnabled: access.interruptSafeBoundary === true,
+        safeBoundaryEnabled: resolveSafeBoundaryEnabled(access.interruptSafeBoundary),
         midToolCall: toolFlightTracker.isMidToolCall(),
       }) === 'defer'
     process.stderr.write(
@@ -17565,10 +17572,11 @@ void (async () => {
             // and edits it in place as work happens (current tool + elapsed),
             // finalizing on completion — the same "live, growing message"
             // shape the main agent's answer uses, NOT card chrome (the pinned
-            // card was deleted in #1126). Flag-gated; when ON it also
+            // card was deleted in #1126). On by default (set
+            // SWITCHROOM_WORKER_ACTIVITY_FEED=0 to disable); when ON it also
             // supersedes the coarse 5-min bucket relay below to avoid
             // double-surfacing the same progress beat.
-            const workerFeedEnabled = process.env.SWITCHROOM_WORKER_ACTIVITY_FEED === '1'
+            const workerFeedEnabled = isWorkerActivityFeedEnabled(process.env.SWITCHROOM_WORKER_ACTIVITY_FEED)
             const workerActivityFeed = createWorkerActivityFeed({
               bot: {
                 sendMessage: async (cid, text, sendOpts) => {

package/telegram-plugin/gateway/interrupt-defer.ts

@@ -98,3 +98,9 @@ export function resolveInterruptMaxWaitMs(configured: number | undefined): numbe
   if (typeof configured === 'number' && configured > 0) return configured
   return DEFAULT_INTERRUPT_MAX_WAIT_MS
 }
+
+/** safe_boundary defaults ON: a `!` mid-tool-call is deferred to a clean
+ *  boundary unless the operator explicitly sets it false. */
+export function resolveSafeBoundaryEnabled(configured: boolean | undefined): boolean {
+  return configured !== false
+}

package/telegram-plugin/tests/coalesce-attachments.test.ts

@@ -2,22 +2,40 @@
  * Unit tests for the A2 multi-attachment helpers
  * (telegram-plugin/gateway/coalesce-attachments.ts).
  *
- * These pin the two pure pieces of the multi-attachment fold-in that live
+ * These pin the pure pieces of the multi-attachment fold-in that live
  * outside gateway.ts so they can be exercised without loadAccess()/IPC:
- *   1. splitCoalescedAttachments — primary + capped extras, arrival order.
- *   2. buildExtraAttachmentMeta — numbered meta fields starting at _2.
+ *   1. resolveCoalesceMaxAttachments — the runtime cap default (10).
+ *   2. splitCoalescedAttachments — primary + capped extras, arrival order.
+ *   3. buildExtraAttachmentMeta — numbered meta fields starting at _2.
  *
- * The default cap (1) MUST reproduce the historical single-attachment shape:
- * primary only, no extras, no numbered meta.
+ * A cap of 1 reproduces the historical single-attachment shape: primary
+ * only, no extras, no numbered meta.
  */
 
 import { describe, expect, it } from 'vitest'
 import {
   splitCoalescedAttachments,
   buildExtraAttachmentMeta,
+  resolveCoalesceMaxAttachments,
+  DEFAULT_MAX_ATTACHMENTS,
   type ResolvedExtraAttachment,
 } from '../gateway/coalesce-attachments.js'
 
+describe('resolveCoalesceMaxAttachments (default 10 = full album)', () => {
+  it('defaults to 10 when unset', () => {
+    expect(resolveCoalesceMaxAttachments(undefined)).toBe(10)
+    expect(DEFAULT_MAX_ATTACHMENTS).toBe(10)
+  })
+  it('honours an explicit operator cap', () => {
+    expect(resolveCoalesceMaxAttachments(1)).toBe(1)
+    expect(resolveCoalesceMaxAttachments(25)).toBe(25)
+  })
+  it('floors a 0 / negative cap at 1 (never strips the only attachment)', () => {
+    expect(resolveCoalesceMaxAttachments(0)).toBe(1)
+    expect(resolveCoalesceMaxAttachments(-5)).toBe(1)
+  })
+})
+
 interface Entry {
   text: string
   att?: string
@@ -26,7 +44,7 @@ interface Entry {
 const has = (e: Entry): boolean => e.att != null
 
 describe('splitCoalescedAttachments', () => {
-  it('default cap 1: keeps only the first attachment as primary, no extras', () => {
+  it('cap 1: keeps only the first attachment as primary, no extras', () => {
     const entries: Entry[] = [
       { text: 'a', att: 'photo-1' },
       { text: 'b', att: 'photo-2' },

package/telegram-plugin/tests/interrupt-defer.test.ts

@@ -15,6 +15,7 @@ import {
   ToolFlightTracker,
   decideInterruptTiming,
   resolveInterruptMaxWaitMs,
+  resolveSafeBoundaryEnabled,
   DEFAULT_INTERRUPT_MAX_WAIT_MS,
 } from '../gateway/interrupt-defer.js'
 
@@ -119,6 +120,18 @@ describe('decideInterruptTiming', () => {
   })
 })
 
+describe('resolveSafeBoundaryEnabled (default ON)', () => {
+  it('defaults to true when unset', () => {
+    expect(resolveSafeBoundaryEnabled(undefined)).toBe(true)
+  })
+  it('stays true when explicitly true', () => {
+    expect(resolveSafeBoundaryEnabled(true)).toBe(true)
+  })
+  it('only an explicit false opts out', () => {
+    expect(resolveSafeBoundaryEnabled(false)).toBe(false)
+  })
+})
+
 describe('resolveInterruptMaxWaitMs', () => {
   it('uses the configured value when positive', () => {
     expect(resolveInterruptMaxWaitMs(3000)).toBe(3000)

package/telegram-plugin/tests/permission-verdict-resume-guard.test.ts

@@ -0,0 +1,86 @@
+/**
+ * Structural pin for the permission-card resume beat.
+ *
+ * What broke (and the bug this guards against): when the operator
+ * answers a permission card, the suspended `claude` turn un-parks and
+ * resumes the SAME turn — the gateway must flip the awaiting glyph
+ * (🙏) back to a working glyph so the operator sees progress instead
+ * of a stuck card. That flip is `resumeReactionAfterVerdict()`.
+ *
+ * The verdict can arrive down several independent paths (button tap,
+ * always-allow, `/allow`·`/deny`, TTL auto-deny, free-text `y <id>`/
+ * `no <id>` reply, …). Every one of them calls
+ * `dispatchPermissionVerdict(...)` to un-park the turn — but the resume
+ * glyph flip is a *separate* call right next to it. The free-text-reply
+ * path shipped the dispatch WITHOUT the resume (fixed in v0.14.19), so
+ * answering via a text reply left the card frozen on 🙏 even though the
+ * turn was running. The controller-level behaviour is covered by
+ * `status-reactions.test.ts` ("setAwaiting" + watchdog re-arm); mtcute
+ * UAT cannot observe reactions at all, so this static pin is the only
+ * thing that catches a verdict path forgetting the resume.
+ *
+ * This guard fails loudly if any `dispatchPermissionVerdict(...)`
+ * callsite is not paired with a `resumeReactionAfterVerdict()` within a
+ * few lines — i.e. a new (or refactored) verdict path drops the resume.
+ */
+
+import { describe, it, expect } from 'vitest'
+import { readFileSync } from 'node:fs'
+import { fileURLToPath } from 'node:url'
+import { dirname, resolve } from 'node:path'
+
+const __dirname = dirname(fileURLToPath(import.meta.url))
+const GATEWAY_SRC = readFileSync(
+  resolve(__dirname, '..', 'gateway', 'gateway.ts'),
+  'utf8',
+)
+
+const LINES = GATEWAY_SRC.split('\n')
+
+// A `dispatchPermissionVerdict(` occurrence is a CALLSITE unless it's the
+// function definition itself.
+const isDefinition = (line: string) =>
+  /\bfunction\s+dispatchPermissionVerdict\b/.test(line)
+
+const dispatchCallsites = LINES.flatMap((line, i) =>
+  /\bdispatchPermissionVerdict\s*\(/.test(line) && !isDefinition(line)
+    ? [i]
+    : [],
+)
+
+// How far below the dispatch the resume call is allowed to live. The
+// widest real gap today is ~9 lines (the slash-command path); 15 gives
+// refactor headroom without letting an unrelated resume "cover" a
+// dispatch from a different block.
+const RESUME_WINDOW = 15
+
+describe('permission verdict → resume reaction wiring', () => {
+  it('there is at least one verdict-dispatch path to guard', () => {
+    expect(dispatchCallsites.length).toBeGreaterThan(0)
+  })
+
+  it('every dispatchPermissionVerdict() callsite flips the awaiting glyph back via resumeReactionAfterVerdict()', () => {
+    const unpaired: number[] = []
+    for (const idx of dispatchCallsites) {
+      const window = LINES.slice(idx, idx + RESUME_WINDOW + 1).join('\n')
+      if (!/\bresumeReactionAfterVerdict\s*\(\s*\)/.test(window)) {
+        // 1-based line number for a human-readable failure.
+        unpaired.push(idx + 1)
+      }
+    }
+    expect(
+      unpaired,
+      `dispatchPermissionVerdict() at gateway.ts line(s) ` +
+        `${unpaired.join(', ')} has no resumeReactionAfterVerdict() within ` +
+        `${RESUME_WINDOW} lines — that verdict path leaves the permission ` +
+        `card stuck on 🙏 after the operator answers. Add the resume call ` +
+        `(see the sibling paths and v0.14.19 / the free-text-reply fix).`,
+    ).toEqual([])
+  })
+
+  it('the resume helper still exists (the pairing is meaningless if it was deleted)', () => {
+    expect(/function\s+resumeReactionAfterVerdict\s*\(/.test(GATEWAY_SRC)).toBe(
+      true,
+    )
+  })
+})

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

@@ -2,10 +2,24 @@ import { describe, it, expect } from 'vitest'
 import {
   renderWorkerActivity,
   createWorkerActivityFeed,
+  isWorkerActivityFeedEnabled,
   type WorkerActivityView,
   type BotApiForWorkerFeed,
 } from '../worker-activity-feed.js'
 
+describe('isWorkerActivityFeedEnabled (default ON)', () => {
+  it('defaults to true when the env var is unset', () => {
+    expect(isWorkerActivityFeedEnabled(undefined)).toBe(true)
+  })
+  it('stays on for any value other than "0"', () => {
+    expect(isWorkerActivityFeedEnabled('1')).toBe(true)
+    expect(isWorkerActivityFeedEnabled('')).toBe(true)
+  })
+  it('only "0" disables it', () => {
+    expect(isWorkerActivityFeedEnabled('0')).toBe(false)
+  })
+})
+
 function view(partial: Partial<WorkerActivityView> = {}): WorkerActivityView {
   return {
     description: 'research competitors',

package/telegram-plugin/uat/assertions.ts

@@ -11,6 +11,59 @@
 
 import type { Driver, ObservedMessage, ObservedReaction } from "./driver.js";
 
+/**
+ * Canonical shape of a worker-activity-feed message (#2000) as rendered
+ * in Telegram: a running header `🔧 Worker · …` that edits in place and
+ * finalizes to `✅ Worker done · …` / `⚠️ Worker failed · …`. The feed is
+ * default-on fleet-wide as of v0.14.19, so background sub-agent activity
+ * now surfaces as its own bot message in any chat — including DMs whose
+ * scenario only cares about the agent's conversational reply.
+ *
+ * Single source of truth; the worker-feed scenario asserts against this,
+ * and recall/reply scenarios exclude it via {@link isWorkerFeedMessage}.
+ */
+export const WORKER_FEED_RE = /🔧\s*Worker|✅\s*Worker done|⚠️\s*Worker failed|Worker (?:done|failed)/i;
+
+/**
+ * True when `m` is a worker-activity-feed message rather than the agent's
+ * own reply. Use it to skip feed noise when matching for a turn's actual
+ * answer — without it, an `expectMessage(/\S/)` can latch onto the feed's
+ * first paint and miss (or mis-time) the real reply. See #2000 / the
+ * memory-survives-restart recall scenario.
+ */
+export function isWorkerFeedMessage(m: ObservedMessage): boolean {
+  return WORKER_FEED_RE.test(m.text);
+}
+
+/**
+ * A single tool-activity-feed line as rendered by
+ * `renderActivityFeed` (telegram-plugin/tool-activity-summary.ts): the
+ * in-progress step is `→ <label>`, finished steps are `✓ <label>`, and a
+ * long turn gets a `✓ +N earlier…` header. Telegram strips the bold/italic
+ * wrapping, so the observed text is just the marker glyph + label.
+ */
+const ACTIVITY_FEED_LINE_RE = /^[→✓]\s/u;
+
+/**
+ * True when `m` is the live tool-activity feed (the one-message list of
+ * "what the agent is doing this turn") rather than the agent's reply. A
+ * message qualifies only when EVERY non-empty line is an activity line —
+ * so a real reply that merely contains an arrow is never misclassified.
+ *
+ * Recall/reply scenarios must skip this in addition to
+ * {@link isWorkerFeedMessage}: on a turn that uses tools, the feed paints
+ * `→ Finding the right tool` as its own bot message before the real answer
+ * lands, and an `expectMessage(/\S/)` would otherwise latch onto it.
+ */
+export function isActivityFeedMessage(m: ObservedMessage): boolean {
+  const lines = m.text
+    .split("\n")
+    .map((l) => l.trim())
+    .filter((l) => l.length > 0);
+  if (lines.length === 0) return false;
+  return lines.every((l) => ACTIVITY_FEED_LINE_RE.test(l));
+}
+
 export interface PollOptions {
   /** Hard deadline; the predicate must resolve truthy before this. */
   timeout: number;

package/telegram-plugin/uat/driver.ts

@@ -646,6 +646,34 @@ export class Driver {
     return { messageId: sent.id };
   }
 
+  /**
+   * Send a photo album (Telegram media_group) — multiple photos posted as
+   * one group, the way a forwarded album or a multi-image paste arrives.
+   * Exercises the gateway's A2 multi-attachment coalescing: with
+   * coalesce.max_attachments default 10, the whole album folds into ONE
+   * Claude turn (the agent sees image_path, image_path_2, …). The optional
+   * caption rides on the first item, matching Telegram client behaviour.
+   * Returns every sent message id (one per album item).
+   */
+  async sendAlbum(
+    chatId: number,
+    photoPaths: string[],
+    caption?: string,
+    opts?: SendTextOptions,
+  ): Promise<{ messageIds: number[] }> {
+    const c = this.requireClient();
+    const replyTo = opts?.replyTo ?? opts?.messageThreadId;
+    const medias = photoPaths.map((p, i) =>
+      InputMedia.photo(p, i === 0 && caption ? { caption } : undefined),
+    );
+    const sent = await c.sendMediaGroup(
+      chatId,
+      medias,
+      replyTo ? { replyTo } : undefined,
+    );
+    return { messageIds: sent.map((m) => m.id) };
+  }
+
   /**
    * Send or remove an emoji reaction on a target message. Used by the
    * UAT reaction-trigger scenario (#1074) to exercise the gateway's

package/telegram-plugin/uat/feed-matcher.test.ts

@@ -0,0 +1,80 @@
+import { describe, expect, it } from "bun:test";
+import {
+  isActivityFeedMessage,
+  isWorkerFeedMessage,
+  WORKER_FEED_RE,
+} from "./assertions.js";
+
+// Pins the worker-activity-feed detector (#2000) used by recall/reply
+// scenarios to skip feed noise. The live UAT it guards can't run in CI
+// (needs sudo + a real Telegram session), so this is the CI-verifiable
+// floor for the matcher's behavior.
+const feed = (text: string) => ({ text }) as Parameters<typeof isWorkerFeedMessage>[0];
+
+describe("isWorkerFeedMessage", () => {
+  it("matches the running feed header", () => {
+    expect(isWorkerFeedMessage(feed("🔧 Worker · crawling changelog · 0:12"))).toBe(true);
+  });
+
+  it("matches the terminal done/failed recaps", () => {
+    expect(isWorkerFeedMessage(feed("✅ Worker done · 10 tools · 1:03"))).toBe(true);
+    expect(isWorkerFeedMessage(feed("⚠️ Worker failed · 3 tools"))).toBe(true);
+  });
+
+  it("matches a done/failed header even without the leading emoji", () => {
+    expect(isWorkerFeedMessage(feed("Worker done · 2 tools"))).toBe(true);
+    expect(isWorkerFeedMessage(feed("Worker failed mid-step"))).toBe(true);
+  });
+
+  it("does NOT match an ordinary agent reply", () => {
+    expect(isWorkerFeedMessage(feed("on it, pulling the logs now"))).toBe(false);
+    expect(
+      isWorkerFeedMessage(feed("SWITCHROOM_UAT_MEM_DEADBEEFCAFE1234")),
+    ).toBe(false);
+  });
+
+  it("does NOT match a reply that merely mentions the word worker", () => {
+    expect(
+      isWorkerFeedMessage(feed("I'll dispatch a worker to handle the crawl.")),
+    ).toBe(false);
+  });
+
+  it("exposes the regex for scenarios that assert on the feed directly", () => {
+    expect(WORKER_FEED_RE.test("🔧 Worker · x")).toBe(true);
+  });
+});
+
+describe("isActivityFeedMessage", () => {
+  it("matches the in-progress step line", () => {
+    expect(isActivityFeedMessage(feed("→ Finding the right tool"))).toBe(true);
+  });
+
+  it("matches a multi-line feed (done steps + in-progress)", () => {
+    expect(
+      isActivityFeedMessage(feed("✓ Reading CLAUDE.md\n→ Searching memory")),
+    ).toBe(true);
+  });
+
+  it("matches the +N earlier header", () => {
+    expect(
+      isActivityFeedMessage(feed("✓ +3 earlier…\n✓ Reading CLAUDE.md\n→ Searching memory")),
+    ).toBe(true);
+  });
+
+  it("does NOT match an ordinary agent reply", () => {
+    expect(isActivityFeedMessage(feed("on it, pulling the logs now"))).toBe(false);
+    expect(
+      isActivityFeedMessage(feed("SWITCHROOM_UAT_MEM_DEADBEEFCAFE1234")),
+    ).toBe(false);
+  });
+
+  it("does NOT match a reply that merely contains an arrow mid-text", () => {
+    expect(
+      isActivityFeedMessage(feed("The flow is request → response → render.")),
+    ).toBe(false);
+  });
+
+  it("does NOT match an empty message", () => {
+    expect(isActivityFeedMessage(feed("   "))).toBe(false);
+  });
+});

package/telegram-plugin/uat/scenarios/jtbd-album-coalescing-dm.test.ts

@@ -0,0 +1,136 @@
+/**
+ * Album-coalescing scenario — driver sends a 3-photo Telegram album
+ * (media_group) in one shot; the gateway's A2 multi-attachment
+ * coalescing (coalesce.max_attachments, default 10 since v0.14.21)
+ * MUST fold all three into a SINGLE Claude turn, so the agent sees
+ * image_path + image_path_2 + image_path_3 together and can report a
+ * count of 3.
+ *
+ * Regression gate for the default-on flip (#2021): before max_attachments
+ * defaulted to 10, an album bypassed coalescing (each part its own turn),
+ * so the agent would only ever see ONE image per turn and answer "1".
+ * A reply of "3" proves the album coalesced.
+ *
+ * Part of: https://github.com/switchroom/switchroom/issues/865
+ *
+ * ## How the signal is read robustly
+ *
+ * The agent's answer is a bare count, which would collide with incidental
+ * digits the chat is now full of by default: the pinned progress card's
+ * timer (`00:03`) and — since the worker feed went default-on fleet-wide
+ * (#2009 / v0.14.19) — worker-feed lines like `🔧 Worker · … · 0:12`.
+ * A "first bot message containing a digit" matcher would latch onto one of
+ * those and false-fail even when coalescing is healthy (see the
+ * memory-survives-restart matcher-flake note + `isWorkerFeedMessage`).
+ *
+ * Two defences, mirroring the sibling `jtbd-forwarded-burst-dm` gate:
+ *   1. Anchor the answer on a distinctive token — the agent is told to
+ *      reply `IMAGECOUNT=<n>`. "IMAGECOUNT" never appears in a card or a
+ *      worker-feed line, so the matcher cannot collide with their digits.
+ *   2. Drain observed messages into a per-id map (collapsing streamed
+ *      edits to latest text), skip our own sends + worker-feed noise, and
+ *      poll until the ANSWER token appears — rather than returning the
+ *      first message that happens to match.
+ *
+ *   - Coalesced   → one turn sees 3 images → `IMAGECOUNT=3`.
+ *   - Non-coalesced → the turn carrying the caption/question sees only its
+ *     own (first) image → `IMAGECOUNT=1`. Surfaced as an explicit failure.
+ *
+ * Fixtures: three tiny solid-colour JPEGs under fixtures/album/, committed
+ * so the gate runs without a generation step. (Regenerate with
+ * `ffmpeg -f lavfi -i color=c=red:s=320x240 -frames:v 1 red.jpg`.)
+ */
+
+import path from "node:path";
+import { existsSync } from "node:fs";
+import { describe, expect, it } from "vitest";
+import { spinUp } from "../harness.js";
+import { pollUntil, isWorkerFeedMessage } from "../assertions.js";
+import type { ObservedMessage } from "../driver.js";
+
+const AGENT = "test-harness";
+
+const FIXTURE_DIR = path.resolve(__dirname, "..", "fixtures", "album");
+const PHOTOS = ["red.jpg", "green.jpg", "blue.jpg"].map((f) =>
+  path.join(FIXTURE_DIR, f),
+);
+
+const CAPTION =
+  "I just sent you a photo album in a single message. Count the separate " +
+  "image files you received in THIS ONE incoming message and reply with " +
+  "ONLY the token IMAGECOUNT=<n> (e.g. IMAGECOUNT=3). Nothing else.";
+
+// Warm TTFO on test-harness is ~7s; an album adds the (sub-second)
+// coalesce window plus the model looking at three images.
+const ANSWER_TIMEOUT_MS = 90_000;
+
+// Pull the count out of an `IMAGECOUNT=<n>` token, tolerating "= : whitespace".
+function imageCountIn(text: string): number | undefined {
+  const m = text.match(/IMAGECOUNT\s*[:=]?\s*(\d+)/i);
+  return m ? Number.parseInt(m[1], 10) : undefined;
+}
+
+describe("uat: album-coalescing DM round-trip", () => {
+  it(
+    "a 3-photo album folds into ONE turn — agent reports seeing 3 images",
+    async () => {
+      for (const p of PHOTOS) {
+        if (!existsSync(p)) {
+          throw new Error(
+            `album fixture missing at ${p} — see scenario header to regenerate`,
+          );
+        }
+      }
+      const sc = await spinUp({ agent: AGENT });
+      try {
+        // Observe BEFORE sending — observeMessages only sees live updates.
+        // Drain into a per-id map so streamed edits collapse to latest text;
+        // skip our own sends and worker-feed noise so neither can satisfy
+        // the count matcher.
+        const latestById = new Map<number, ObservedMessage>();
+        const stream = sc.driver.observeMessages(sc.botUserId);
+        const consume = (async () => {
+          for await (const m of stream) {
+            if (m.senderUserId === sc.driverUserId) continue;
+            if (isWorkerFeedMessage(m)) continue;
+            latestById.set(m.messageId, m);
+          }
+        })();
+
+        await sc.driver.sendAlbum(sc.botUserId, PHOTOS, CAPTION);
+
+        // Poll until a bot message carries an IMAGECOUNT token.
+        const answer = await pollUntil(
+          () => {
+            for (const m of latestById.values()) {
+              if (imageCountIn(m.text) !== undefined) return m;
+            }
+            return undefined;
+          },
+          { timeout: ANSWER_TIMEOUT_MS, interval: 500 },
+        ).catch(() => undefined);
+
+        await stream[Symbol.asyncIterator]().return?.(undefined as never);
+        await consume;
+
+        if (!answer) {
+          const seen = [...latestById.values()]
+            .map((m) => `#${m.messageId}=${JSON.stringify(m.text.slice(0, 60))}`)
+            .join(" ");
+          throw new Error(
+            `[album-coalescing] No bot reply carried an IMAGECOUNT token ` +
+              `within ${ANSWER_TIMEOUT_MS}ms. Bot messages seen: ${seen || "(none)"}.`,
+          );
+        }
+
+        const count = imageCountIn(answer.text);
+        // Coalesced => 3. A non-coalescing gateway answers 1 (the question
+        // rides photo #1; the other two parts spill to their own turns).
+        expect(count).toBe(3);
+      } finally {
+        await sc.tearDown();
+      }
+    },
+    ANSWER_TIMEOUT_MS + 30_000,
+  );
+});

package/telegram-plugin/uat/scenarios/jtbd-memory-survives-restart-dm.test.ts

@@ -53,9 +53,24 @@ import { describe, it, expect, beforeAll } from "vitest";
 import { execSync } from "node:child_process";
 import { randomBytes } from "node:crypto";
 import { spinUp } from "../harness.js";
+import { isActivityFeedMessage, isWorkerFeedMessage } from "../assertions.js";
+import type { ObservedMessage } from "../driver.js";
 
 const AGENT = "test-harness";
 
+// Two classes of bot message are NOT the agent's reply and must be
+// skipped, or a bare `/\S/` matcher latches onto them and the
+// verbatim-token check fails against noise instead of catching a real
+// memory miss:
+//   1. The worker-activity feed (#2000, default-on since v0.14.19) — a
+//      stray background sub-agent posts `🔧 Worker · …` into this DM.
+//   2. The tool-activity feed — on a turn that uses tools (memory recall
+//      does), `→ Finding the right tool` paints as its own message before
+//      the real answer lands.
+// Match the first non-empty bot reply that is neither.
+const isReply = (m: ObservedMessage): boolean =>
+  /\S/.test(m.text) && !isWorkerFeedMessage(m) && !isActivityFeedMessage(m);
+
 const RESTART_BUDGET_MS = 90_000;
 const CAPTURE_REPLY_BUDGET_MS = 60_000;
 const RECALL_REPLY_BUDGET_MS = 120_000;
@@ -139,7 +154,7 @@ const sudoOk = canShellSudo();
             `(This is a memory-survival UAT — store it via hindsight.)`,
           );
 
-          const captureReply = await sc1.expectMessage(/\S/, {
+          const captureReply = await sc1.expectMessage(isReply, {
             from: "bot",
             timeout: CAPTURE_REPLY_BUDGET_MS,
           });
@@ -180,7 +195,7 @@ const sudoOk = canShellSudo();
             `Reply with the token only, no extra text.`,
           );
 
-          const recallReply = await sc2.expectMessage(/\S/, {
+          const recallReply = await sc2.expectMessage(isReply, {
             from: "bot",
             timeout: RECALL_REPLY_BUDGET_MS + 5_000,
           });

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

@@ -25,15 +25,21 @@
  *   - 429 cooldown + message_id drift resilience (re-post on stale edit),
  *   - a forced terminal edit on `finish` regardless of throttle.
  *
- * The feed is gated to BACKGROUND workers and lives behind the
- * `SWITCHROOM_WORKER_ACTIVITY_FEED` flag — see the gateway wiring. The
- * watcher already drives the cues (it polls the worker jsonl directly,
- * so it keeps firing after the parent turn ends), which is why the feed
- * is fed from watcher callbacks rather than the bridge event stream.
+ * The feed is gated to BACKGROUND workers and is ON by default; set
+ * `SWITCHROOM_WORKER_ACTIVITY_FEED=0` to disable it — see the gateway
+ * wiring. The watcher already drives the cues (it polls the worker jsonl
+ * directly, so it keeps firing after the parent turn ends), which is why
+ * the feed is fed from watcher callbacks rather than the bridge event stream.
  */
 
 import { escapeHtml, formatDuration, truncate } from './card-format.js'
 
+/** Worker-activity feed is ON by default; an operator opts out with
+ *  SWITCHROOM_WORKER_ACTIVITY_FEED=0. */
+export function isWorkerActivityFeedEnabled(envVal: string | undefined): boolean {
+  return envVal !== '0'
+}
+
 export type WorkerActivityState = 'running' | 'done' | 'failed'
 
 /** The render-relevant snapshot of a worker at one instant. */