polygram 0.11.0-rc.5 → 0.11.0-rc.6

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.11.0-rc.5",
+  "version": "0.11.0-rc.6",
   "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. Multi-bot, multi-chat, per-topic isolation; SQLite transcripts; inline-keyboard approvals. Bundles /polygram:status|logs|pair-code|approvals admin commands plus history (transcript queries) and polygram-send (out-of-turn IPC sends with file-upload validation) skills.",
   "keywords": [
     "telegram",

package/lib/db/sessions.js

@@ -186,6 +186,34 @@ function resolveSessionForSpawn(db, sessionKey, resolved = {}) {
     return before[f] !== after[f];
   });
 
+  // 0.11.0 channels boundary (2026-05-25): SDK ↔ tmux flips remain
+  // non-invalidating per rc.32's reasoning. But channels mode is
+  // genuinely different on the claude side:
+  //
+  //   - bridge MCP server is mounted (--mcp-config + --strict-mcp-config)
+  //   - additional --append-system-prompt directive enforces the
+  //     reply-tool contract (claude must call mcp__polygram-bridge__reply
+  //     instead of writing inline). Sessions created without this
+  //     directive don't have the contract baked into their context.
+  //   - agent behavior expectations differ — same agent file, but
+  //     conversation flow is "user msg arrives via channel, reply via
+  //     tool" rather than "user msg arrives inline, reply inline."
+  //
+  // Live shumorobot 2026-05-25 incident: Music topic resumed a
+  // pre-channels session id (4837f61a-…) that had been mid-soulseek-
+  // curation. The user's "how are you" got interpreted as a continuation
+  // of THAT task; claude responded with music release info, inline,
+  // never calling the reply tool. Every turn timed out at 3min.
+  //
+  // Rule: any transition TO or FROM channels drops the prior session.
+  // XOR — flips between channels and {sdk,tmux} invalidate; sdk↔tmux
+  // flips remain free.
+  const wasChannels = before.pm_backend === 'channels';
+  const willBeChannels = after.pm_backend === 'channels';
+  if (after.pm_backend != null && wasChannels !== willBeChannels) {
+    drifted.push('pm_backend');
+  }
+
   if (drifted.length === 0) {
     return { existingSessionId: row.claude_session_id, drift: null };
   }

package/lib/process/channels-process.js

@@ -370,6 +370,14 @@ class ChannelsProcess extends Process {
     // EXISTING conversation. Lazy-respawn after bridge-disconnect must use
     // --resume so conversation history is preserved. Mirrors
     // tmux-process.js:514-518.
+    //
+    // rc.6 note: pre-channels session ids (created by sdk/tmux backends and
+    // persisted in polygram's DB) are NOT cross-backend compatible — claude
+    // indexes session files under a cwd-derived projects dir that may not
+    // match what channels-mode passes, leading to silent "No conversation
+    // found" exit. The fix lives at the data layer, not here: operator
+    // clears pre-channels session ids from polygram's sessions table before
+    // flipping a chat to channels (see ops/migrate-to-channels.sql).
     if (opts.existingSessionId) {
       claudeArgs.push('--resume', opts.existingSessionId);
     } else {
@@ -413,6 +421,42 @@ class ChannelsProcess extends Process {
     // from leaking as user-visible messages (shumorobot 2026-05-15 incident).
     claudeArgs.push('--append-system-prompt', POLYGRAM_DISPLAY_HINT);
 
+    // rc.6 (2026-05-25 shumorobot diagnosis): channels-mode contract is
+    // NOT obvious to the agent. The bridge's MCP `instructions:` field tells
+    // claude to use the reply tool, but that's seen only during MCP init and
+    // gets buried under the agent's own system prompt. Observed live: the
+    // music-curator agent received user messages via the channel and wrote
+    // replies INLINE to its TUI instead of calling `mcp__polygram-bridge__reply`,
+    // so polygram never saw them and every turn timed out after 3 minutes.
+    //
+    // Append a SECOND, explicit directive that overrides the agent's default
+    // conversational behavior. Phrased as a hard rule so it survives whatever
+    // the agent's system prompt says. Future tuning may move this to a
+    // shared lib/telegram/channels-protocol-hint.js if it grows; for now
+    // inline is fine since it's tied to the channels backend implementation.
+    claudeArgs.push('--append-system-prompt', [
+      '## polygram channels mode — HARD CONTRACT',
+      '',
+      'You are running inside polygram with the channels backend. Your stdout/TUI',
+      'output is NOT seen by the user. The user is on Telegram.',
+      '',
+      'To deliver ANY message to the user, you MUST call the MCP tool',
+      '`mcp__polygram-bridge__reply` with `chat_id` and `text` arguments.',
+      'Pass the chat_id verbatim from the channel message you received.',
+      '',
+      'Do NOT respond conversationally in-line. Do NOT assume any inline',
+      'text will reach the user. If you have ANYTHING to say to the user —',
+      'an answer, a question, a status update, an acknowledgement — it goes',
+      'through `mcp__polygram-bridge__reply`. Period.',
+      '',
+      'This applies to every turn, including the first message after',
+      '`/new` or `/reset`. Even a single-line "Hi" must be sent via the tool.',
+      '',
+      'Internal tool calls (Bash, Edit, Write, Read, etc.) are fine to use',
+      'as normal — only the FINAL user-visible message needs to go through',
+      'the reply tool.',
+    ].join('\n'));
+
     // Parity audit P6: honor isolateUserConfig — mirrors tmux pattern at
     // lib/process/tmux-process.js:502-505,543-546. Channels ALWAYS uses
     // --strict-mcp-config (the bridge requires it), so the MCP half is

package/package.json

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