polygram 0.11.0-rc.6 → 0.11.0-rc.7

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.6",
+  "version": "0.11.0-rc.7",
   "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/process/channels-process.js

@@ -416,25 +416,19 @@ class ChannelsProcess extends Process {
       claudeArgs.push('--dangerously-skip-permissions');
     }
 
-    // Parity audit P3: append display-hint so Claude knows it's replying
-    // through Telegram. Prevents canned strings like "No response requested."
-    // 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.
+    // Parity audit P3 + rc.7 (2026-05-26 shumorobot diagnosis): combined
+    // system-prompt suffix carrying BOTH the Telegram display rules AND the
+    // channels-mode reply-tool contract. Merged into a single
+    // --append-system-prompt block — passing two separate
+    // --append-system-prompt flags caused MCP server registration to fail
+    // (live shumorobot tmux banner: "server:polygram-bridge · no MCP server
+    // configured with that name"; claude received no channel messages).
+    // Suspected: --append-system-prompt is variadic in claude's CLI and the
+    // second flag was eating the subsequent --setting-sources / --mcp-config
+    // arguments. Single combined block sidesteps the issue.
     claudeArgs.push('--append-system-prompt', [
+      POLYGRAM_DISPLAY_HINT,
+      '',
       '## polygram channels mode — HARD CONTRACT',
       '',
       'You are running inside polygram with the channels backend. Your stdout/TUI',

package/package.json

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