polygram 0.12.0-rc.13 → 0.12.0-rc.14

package/lib/process/cli-process.js

@@ -120,16 +120,17 @@ const STREAMING_HINT_RE = /esc to interrupt/i;
 // — false positives surface as no-op telemetry, false negatives surface
 // as the idle-ceiling timeout (~10min).
 const UNKNOWN_PROMPT_HEURISTIC_RE = /(\?\s*$|\(y\/N\)|Yes\/No|❯\s|^\s*[12345]\.\s)/im;
-// Dead-bridge signal. Claude Code prints "<source>  no MCP server configured
-// with that name" when a channel source references an MCP server that isn't
-// registered. Music topic incident (2026-06-01): seen mid-turn after an
-// auto-/compact of a large resumed session redrew the TUI and dropped the
-// `server:polygram-bridge` binding — the turn could no longer deliver its
-// reply and hung. The bridge name precedes the error on the same line, so
-// anchor on it: matching the bare phrase risks a false hit on prose that
-// merely quotes the error, while the healthy "polygram-bridge: <polygram-info>
-// …" connection line never contains "no MCP server configured".
-const BRIDGE_DEAD_RE = /polygram-bridge[^\n]*no MCP server configured/i;
+// rc.14: a previous rc (rc.11) had a BRIDGE_DEAD_RE here that matched the pane
+// line "server:polygram-bridge  no MCP server configured with that name" and
+// treated it as a dead bridge to recover from. That was a MISDIAGNOSIS: this
+// line is a BENIGN, persistent banner that `--dangerously-load-development-
+// channels` + `--strict-mcp-config` prints on EVERY healthy session — the
+// channel still delivers messages and the reply tool still works (reproduced
+// 2026-06-01 with a test MCP server that demonstrably functions). The pane
+// matcher therefore false-fired ~5s into every channels turn and KILLED
+// healthy sessions (the Music-topic "mid-turn detach" regression). Real bridge
+// loss is caught by the socket-close path (bridgeServer 'bridge-disconnected'
+// → _handleBridgeDisconnected). There is no reliable pane signal — removed.
 // Per-pattern rate limit so a dialog that lingers across multiple polls
 // doesn't spam sendControl/event emissions. Aligned with the 5s poll cadence.
 const MID_TURN_DEDUP_WINDOW_MS = 30_000;
@@ -2411,35 +2412,14 @@ class CliProcess extends Process {
     }
     if (!pane) return;
 
-    // Wedge recovery (Music topic incident, 2026-06-01). Claude Code's
-    // channel source can lose its MCP-server registration mid-turn — most
-    // often after an auto-/compact of a large resumed session redraws the
-    // TUI and the `server:polygram-bridge` binding fails to re-resolve
-    // ("polygram-bridge  no MCP server configured with that name"). The
-    // bridge SOCKET stays up, so the socket-close path
-    // (bridgeServer 'bridge-disconnected' → _handleBridgeDisconnected) never
-    // fires — but claude can no longer deliver the reply, so the turn
-    // orphans and would hang until the wall-clock cap while this watchdog
-    // logged cli-mid-turn-unknown-prompt every 30s and recovered nothing.
-    // Detect it from the pane and route through the SAME recovery as a real
-    // socket disconnect: reject pending turns (user gets the 🔌 resend
-    // message via BRIDGE_DISCONNECTED) and emit 'bridge-disconnected' so
-    // process-manager kills + lazy-respawns the dead instance (next msg
-    // recovers the conversation via `claude --resume`). Gated on
-    // pendingTurns.size>0 by the early return above, so it can't fire on an
-    // idle session that merely has the string in scrollback.
-    if (BRIDGE_DEAD_RE.test(pane)) {
-      this.logger.warn?.(
-        `[${this.label}] cli: channels MCP registration lost mid-turn ` +
-        `(pane-detected) — recovering ${this.pendingTurns.size} orphaned turn(s)`,
-      );
-      this._logEvent('cli-bridge-detached-midturn', {
-        pending_count: this.pendingTurns.size,
-        session_id: this.claudeSessionId,
-      });
-      this._handleBridgeDisconnected('mcp-registration-lost');
-      return;
-    }
+    // rc.14: removed the rc.11 pane-based "dead bridge" detection here. It
+    // matched the BENIGN banner "server:polygram-bridge  no MCP server
+    // configured with that name" — a cosmetic line that
+    // `--dangerously-load-development-channels` + `--strict-mcp-config` prints
+    // on EVERY healthy session (channel still delivers; reply tool still
+    // works). The matcher false-fired ~5s into every channels turn and killed
+    // healthy sessions. Real bridge loss is the socket-close path
+    // (_handleBridgeDisconnected), not anything observable in the pane.
 
     const now = Date.now();
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "polygram",
-  "version": "0.12.0-rc.13",
+  "version": "0.12.0-rc.14",
   "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": {