polygram 0.10.0-rc.35 → 0.10.0-rc.37

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.10.0-rc.35",
+  "version": "0.10.0-rc.37",
   "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/turn-phase.js

@@ -109,7 +109,15 @@ function isTerminal(phase) {
  * doesn't gate any transitions; future commits MAY tighten this.
  */
 const ALLOWED_TRANSITIONS = Object.freeze({
-  [TurnPhase.QUEUED]:             new Set([TurnPhase.PASTED_UNCONFIRMED, TurnPhase.FAILED]),
+  // PASTE_PARKED is reachable directly from QUEUED on cold-start +
+  // stacked-message flows: claude TUI emits `queue-operation:enqueue`
+  // before the corresponding `user-message` when it is still
+  // cold-starting or finishing a prior turn. The predicate sees the
+  // enqueue first and sets PASTE_PARKED without ever observing the
+  // PASTED_UNCONFIRMED intermediate. rc.35 production caught this as
+  // log noise once Commit 3 (`_awaitSettle`) started consuming
+  // predicate fields more strictly.
+  [TurnPhase.QUEUED]:             new Set([TurnPhase.PASTED_UNCONFIRMED, TurnPhase.PASTE_PARKED, TurnPhase.FAILED]),
   [TurnPhase.PASTED_UNCONFIRMED]: new Set([TurnPhase.PASTE_PARKED, TurnPhase.SUBMITTED, TurnPhase.STREAMING, TurnPhase.TOOL_RUNNING, TurnPhase.SUBAGENT_RUNNING, TurnPhase.APPROVAL_PENDING, TurnPhase.QUIET, TurnPhase.DONE, TurnPhase.FAILED]),
   [TurnPhase.PASTE_PARKED]:       new Set([TurnPhase.SUBMITTED, TurnPhase.STREAMING, TurnPhase.TOOL_RUNNING, TurnPhase.SUBAGENT_RUNNING, TurnPhase.APPROVAL_PENDING, TurnPhase.QUIET, TurnPhase.DONE, TurnPhase.FAILED]),
   [TurnPhase.SUBMITTED]:          new Set([TurnPhase.STREAMING, TurnPhase.TOOL_RUNNING, TurnPhase.SUBAGENT_RUNNING, TurnPhase.APPROVAL_PENDING, TurnPhase.QUIET, TurnPhase.DONE, TurnPhase.FAILED]),

package/lib/telegram/display-hint.js

@@ -57,6 +57,17 @@ const POLYGRAM_DISPLAY_HINT = [
   '- Headers `#`, `##`, `###` render as plain text — use **bold** for emphasis.',
   '- Horizontal rules render as a thin divider line.',
   '- Long replies stream in chunks; prefer concise structure over walls of text.',
+  '',
+  '### NEVER emit shell-context canned strings — HARD RULE',
+  '',
+  'You are running as a Telegram chat bot, NOT as a script being piped into a shell. Certain phrases are CLI-context boilerplate from the underlying environment and MUST NEVER appear in a reply, because the user sees them as a literal message from you and they look like a system error:',
+  '',
+  '- `No response requested.`',
+  '- `No response needed.`',
+  '- `Continuing...` as a standalone reply',
+  '- Any other shell-prompt-style filler that acknowledges silence',
+  '',
+  'If a user message is short, ambiguous, or feels like a no-op acknowledgement (e.g. `okay`, `ok`, `yes`, `got it`, `thanks`), reply with a brief substantive line — acknowledge what you understood and what (if anything) you will do next. If you genuinely have nothing useful to say, ask ONE specific clarifying question. NEVER emit a placeholder or a shell-style canned string — the chat surface has no silent-no-op state. Every reply must be intentional content.',
 ].join('\n');
 
 /**

package/package.json

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