polygram 0.12.1 → 0.12.3

package/lib/process/channels-bridge.mjs

@@ -322,7 +322,7 @@ mcp.setRequestHandler(ListToolsRequestSchema, async () => {
         // (P0 spike Q-B: claude echoes only the trigger id) — this array can.
         consumed_turn_ids: {
           type: 'array', items: { type: 'string' },
-          description: 'turn_id of EVERY <channel> message this reply answers or has absorbed since your last reply (including mid-turn follow-ups). Always set it.',
+          description: 'turn_id of EVERY <channel> message this reply answers or has absorbed since your last reply, including mid-turn follow-ups. Set it on EVERY reply, even short one-line ones; if you answered two messages in one reply, list BOTH turn_ids. Omitting a folded follow-up makes polygram treat it as dropped.',
         },
       },
       required: ['chat_id', 'text'],

package/lib/process/cli-process.js

@@ -754,11 +754,14 @@ class CliProcess extends Process {
       'as normal — only the FINAL user-visible message needs to go through',
       'the reply tool.',
       '',
-      'When you call `reply`, ALWAYS set `consumed_turn_ids` to the turn_id',
-      'attribute of EVERY <channel> message you are answering or have received',
-      'since your last reply — including mid-turn follow-ups you absorbed into',
-      'the current answer. polygram uses it to confirm follow-up delivery;',
-      'omitting it can cause a follow-up to be re-sent to you.',
+      'When you call `reply`, ALWAYS set `consumed_turn_ids` to the turn_id of',
+      'EVERY <channel> message this reply answers or folds in — every mid-turn',
+      'follow-up you absorbed since your last reply. This applies to EVERY reply,',
+      'including SHORT one-line ones: if two messages arrived and you answered both',
+      'in one reply, list BOTH turn_ids (e.g. consumed_turn_ids: ["<original-id>",',
+      '"<follow-up-id>"]). Omitting a folded follow-up makes polygram read it as',
+      'DROPPED — it gets re-sent to you or flagged as a lost message. When unsure,',
+      'include the id.',
       '',
       '### Staying responsive on a long task',
       '',
@@ -2129,6 +2132,22 @@ class CliProcess extends Process {
           backend: this.backend,
         });
         this._logEvent('turn-timeout', { turnTimeoutMs, reason });
+        // 0.12.3 wedge characterization (docs/0.13-turn-wedge-autorecovery-spec.md):
+        // a zero-reply turn hit the ceiling = claude wedged (no hooks AND no
+        // "esc to interrupt" the whole window). Capture the TUI pane tail + busy
+        // flags to learn WHAT state claude is stuck in (a tool, an unrecognized
+        // prompt, the idle ❯, blank). Fire-and-forget: never blocks or changes
+        // the kill path; the tmux session is still alive at this point.
+        this.probeBusyState().then((probe) => {
+          this._logEvent('turn-timeout-pane', {
+            reason,
+            streaming: probe.streaming,
+            background_shell: probe.backgroundShell,
+            shell_count: probe.shellCount,
+            captured: probe.captured,
+            pane_tail: probe.paneTail,
+          });
+        }).catch(() => { /* telemetry best-effort — never throws into the kill path */ });
         this.emit('idle');
         const err = new Error(`turn timeout (${turnTimeoutMs}ms, reason=${reason})`);
         err.code = 'TURN_TIMEOUT';

package/package.json

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