polygram 0.8.0-rc.35 → 0.8.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.8.0-rc.35",
+  "version": "0.8.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 and a history skill.",
   "keywords": [
     "telegram",

package/lib/autosteer-buffer.js

@@ -91,10 +91,18 @@ function createAutosteerBuffer() {
  *     non-empty output, with kind='autosteer-hook-drained'.
  * @param {string|null} [opts.chatId] — for the logEvent payload only.
  * @param {object} [opts.logger]      — for error logging (must have .error).
+ * @param {(sessionKey: string, drainedCount: number) => void} [opts.onDrained]
+ *   — fired AFTER the hook successfully injects additionalContext.
+ *     rc.37 wires this to clearAutosteeredReactions so the ✍ reaction
+ *     fades the moment the agent absorbs the follow-up — not at SDK
+ *     turn-end, which under autosteer can stretch tens of minutes
+ *     (one SDK turn keeps absorbing follow-ups via additionalContext
+ *     and never emits result, so the old turn-end-only cleanup left
+ *     ✍ stuck across many user messages).
  *
  * @returns {async () => Promise<HookJSONOutput>}
  */
-function makePostToolBatchHook({ buffer, sessionKey, logEvent = null, chatId = null, logger = console } = {}) {
+function makePostToolBatchHook({ buffer, sessionKey, logEvent = null, chatId = null, logger = console, onDrained = null } = {}) {
   if (!buffer) throw new TypeError('buffer required');
   if (!sessionKey) throw new TypeError('sessionKey required');
   return async () => {
@@ -111,6 +119,10 @@ function makePostToolBatchHook({ buffer, sessionKey, logEvent = null, chatId = n
           });
         } catch { /* logger errors must not break the hook */ }
       }
+      if (typeof onDrained === 'function') {
+        try { onDrained(sessionKey, drained.length); }
+        catch (err) { logger?.error?.(`[${sessionKey}] onDrained: ${err?.message || err}`); }
+      }
       return {
         continue: true,
         hookSpecificOutput: {

package/lib/status-reactions.js

@@ -39,7 +39,13 @@ const STATES = {
   // All three emoji on Telegram's curated standard reaction list.
   THINKING:         { label: 'thinking',         chain: ['🤔']             },
   THINKING_DEEPER:  { label: 'thinking-deeper',  chain: ['🤨', '🤔']       },
-  THINKING_DEEPEST: { label: 'thinking-deepest', chain: ['🧐', '🤓', '🤔'] },
+  // rc.37: 🧐 (face with monocle) is REACTION_INVALID for bots — only
+  // Telegram Premium users can pick arbitrary emoji; bots are limited
+  // to ~70 standard reactions and 🧐 isn't on the list. Production
+  // log: `reaction apply failed (THINKING_DEEPEST → 🧐): 400: Bad
+  // Request: REACTION_INVALID`. 🤓 (nerd face, intellectual focus) is
+  // on the list and reads as "deeper than skeptical-eyebrow".
+  THINKING_DEEPEST: { label: 'thinking-deepest', chain: ['🤓', '🤔'] },
   CODING:           { label: 'coding',           chain: ['👨‍💻', '✍', '🤔'] },
   WEB:              { label: 'web',              chain: ['⚡', '🔥', '🤔']  },
   TOOL:             { label: 'tool',             chain: ['🔥', '🤔']       },
@@ -81,12 +87,17 @@ const DEFAULT_STALL_MS = 45_000;
 const DEFAULT_FREEZE_MS = 180_000;
 // rc.32: thinking-deepening cascade thresholds. Calibrated to Ivan DM
 // 14-day production data (445 turns) — 8% finish <5s, 33% in 5-15s,
-// 25% in 15-30s. 8s catches the meaty band, 20s catches the
-// mid-bracket. STALL still fires at 45s for the genuinely-long 17%.
+// 25% in 15-30s. rc.35 bump: 8s→12s, 20s→30s. User feedback after
+// rc.32 deploy was that the cascade kicked in too eagerly — most
+// 5-15s turns showed 🤨 briefly before resolving, and the resulting
+// emoji churn felt noisy rather than informative. Bumping deeper to
+// 12s lets the entire 5-15s bracket (33%) resolve on plain 🤔, and
+// deepest to 30s lets the 15-30s bracket (25%) resolve on 🤨 without
+// cascading. STALL still fires at 45s for the genuinely-long 17%.
 // CODING / TOOL / WEB / WRITING reset the cascade (any state-change
 // in setState clears the deepening timers).
-const DEFAULT_THINKING_DEEPER_MS = 8_000;
-const DEFAULT_THINKING_DEEPEST_MS = 20_000;
+const DEFAULT_THINKING_DEEPER_MS = 12_000;
+const DEFAULT_THINKING_DEEPEST_MS = 30_000;
 
 // Tool name → state classifier. Case-insensitive substring match so we
 // don't have to enumerate every existing or future tool. Order matters:
@@ -219,8 +230,8 @@ function createReactionManager({
   };
 
   // rc.32: thinking-deepening cascade. When state is THINKING, schedule
-  // auto-promotion at 8s (→ THINKING_DEEPER, 🤨) and 20s (→ THINKING_DEEPEST,
-  // 🧐). Any other setState (CODING / TOOL / WEB / WRITING / terminal) clears
+  // auto-promotion at 12s (→ THINKING_DEEPER, 🤨) and 30s (→ THINKING_DEEPEST,
+  // 🤓). Any other setState (CODING / TOOL / WEB / WRITING / terminal) clears
   // these. heartbeat() does NOT re-arm them — heartbeat is for keeping
   // STALL/TIMEOUT at bay during silent activity, not for resetting
   // visible deepening progression.

package/package.json

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

package/polygram.js

@@ -931,6 +931,18 @@ function buildSdkOptions(sessionKey, ctx) {
     chatId: ctx?.chatId ?? null,
     logEvent,
     logger: console,
+    // rc.37: clear ✍ reactions when the hook ABSORBS follow-ups, not
+    // at SDK turn-end. Under autosteer one SDK "turn" can stretch
+    // tens of minutes — every drain feeds more user text via
+    // additionalContext, the agent keeps reasoning, no `result` event
+    // fires, inFlight stays true, ✍ stays stuck on every drained
+    // follow-up. Clearing at drain time matches user perception
+    // ("the bot got my message → ✍ goes away").
+    onDrained: (key) => {
+      clearAutosteeredReactions(key).catch((err) => {
+        console.error(`[${BOT_NAME}] autosteer-hook clearReactions: ${err.message}`);
+      });
+    },
   });
 
   // 0.8.0-rc.21: SessionStart hook preloads recent polygram-DB