polygram 0.8.0-rc.9 → 0.8.0

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
   "plugins": [
     {
       "name": "polygram",
-      "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. Bundles /polygram:status|logs|pair-code|approvals admin commands and a history skill.",
+      "description": "Telegram integration for Claude Code that preserves the OpenClaw per-chat session model. Migration target for OpenClaw users. 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.",
       "category": "integration",
       "source": "./",
       "homepage": "https://github.com/shumkov/polygram"

package/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.8.0-rc.9",
-  "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.",
+  "version": "0.8.0",
+  "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",
     "openclaw",

package/config.example.json

@@ -98,9 +98,17 @@
       "cwd": "/Users/you/admin-agent",
       "requireMention": true,
       "isolateTopics": true,
+      "_comment_topics": "rc.48: each topic entry is EITHER a string (legacy: just a label) OR an object with optional fields {name, agent, cwd, model, effort, permissionMode}. Object form lets a topic override chat-level config. Per-topic permissionMode overrides chat-level — typical use: scope one topic to permissionMode:'default' (so settings.json gates apply) while the rest of the chat stays on bypassPermissions. Object form requires isolateTopics: true (each topic gets its own SDK Query); polygram emits a startup warning otherwise.",
       "topics": {
         "100": "Customer A",
-        "200": "Customer B"
+        "200": {
+          "name": "Customer B",
+          "agent": "customer-b-helper",
+          "cwd": "/Users/you/customer-b-projects",
+          "model": "opus",
+          "effort": "high",
+          "permissionMode": "default"
+        }
       }
     },
 

package/lib/abort-detector.js

@@ -2,35 +2,72 @@
  * Detect "stop working on the current turn" signals in natural language.
  *
  * Mirrors OpenClaw's isAbortRequestText semantics: users should be able to
- * say "stop" / "подожди" / "cancel" / or just `/stop` and have polygram
+ * say "stop" / "стоп" / "cancel" / or just `/stop` and have polygram
  * interrupt the in-flight turn instead of queueing the message behind it.
  *
  * Conservative on purpose. False positives hijack user intent — "stop using
  * emoji" should NOT abort. So we require ONE of:
  *   1. The whole message (after stripping leading @-mention + trailing
- *      punctuation) is an exact match against a known abort phrase, OR
+ *      punctuation) is an exact match against a known abort phrase
+ *      (HARD or SOFT phrases — see below), OR
  *   2. It starts with an explicit slash command: /stop, /abort, /cancel, OR
- *   3. The FIRST SENTENCE (split on . ! ?) is an exact abort phrase. This
- *      catches "Stop. I'll ask in another session." — clear abort intent
- *      with continuation explaining what comes next. Comma is not a split
- *      character ("Stop, look here" is ambiguous and stays non-abort).
+ *   3. The FIRST SENTENCE (split on . ! ?) is an exact match against the
+ *      HARD phrases ONLY. Catches "Stop. I'll ask in another session." —
+ *      clear abort intent with continuation. Does NOT trigger on
+ *      "Wait? Something is off..." (rc.41 false-positive fix — soft words
+ *      like "wait" / "hold on" are too conversational to abort on
+ *      first-sentence alone).
+ *
+ * Hard phrases (whole-message OR first-sentence trigger):
+ *   English: stop, cancel, abort, halt
+ *   Russian: стоп, остановись, остановить, отмена, прекрати, прекращай,
+ *            хватит, отставить
+ *
+ * Soft phrases (whole-message ONLY):
+ *   English: wait, hold on, hold up, nevermind, never mind, nvm,
+ *            forget it, forget that
+ *   Russian: подожди, подожди-ка, забей, не надо, отмени
+ *
+ * The split exists because "wait", "hold on", "подожди" are commonly used
+ * as conversational openers ("Wait? There is something wrong..." — Ivan DM
+ * 2026-05-01 19:01) where the user is NOT asking the bot to stop, they're
+ * flagging an issue. Hard phrases ("stop", "cancel", "abort") are
+ * unambiguously about ending the current task.
  *
  * Not detected (on purpose):
  *   - "stop using markdown" → first sentence is the whole thing, not exact
  *   - "I said stop" → not at start / not exact match
+ *   - "Wait? Something is wrong..." (rc.41) — soft word, multi-sentence
+ *   - "Hold on, let me think" — same shape
  */
 
-const ABORT_PHRASES = new Set([
+'use strict';
+
+// HARD phrases: unambiguous abort intent. Trigger on whole-message OR
+// first-sentence match.
+const HARD_ABORT_PHRASES = new Set([
   // English
-  'stop', 'wait', 'cancel', 'abort', 'halt',
-  'hold on', 'hold up', 'nevermind', 'never mind', 'nvm',
+  'stop', 'cancel', 'abort', 'halt',
+  // Russian
+  'стоп', 'остановись', 'остановить',
+  'отмена', 'прекрати', 'прекращай', 'хватит', 'отставить',
+]);
+
+// SOFT phrases: conversational filler that COULD mean abort but commonly
+// doesn't. Whole-message match only.
+const SOFT_ABORT_PHRASES = new Set([
+  // English
+  'wait', 'hold on', 'hold up', 'nevermind', 'never mind', 'nvm',
   'forget it', 'forget that',
   // Russian
-  'стоп', 'подожди', 'подожди-ка', 'остановись', 'остановить',
-  'отмена', 'отставить', 'прекрати', 'прекращай', 'хватит',
-  'забей', 'не надо', 'отмени',
+  'подожди', 'подожди-ка', 'забей', 'не надо', 'отмени',
 ]);
 
+// Combined set for whole-message matching. Kept exported as ABORT_PHRASES
+// for backward compatibility with any callers / tests that import it
+// directly.
+const ABORT_PHRASES = new Set([...HARD_ABORT_PHRASES, ...SOFT_ABORT_PHRASES]);
+
 const ABORT_SLASH_RE = /^\/(stop|abort|cancel)(\s|$|@)/i;
 
 // Strip leading @botname mentions ("@shumobot stop" → "stop"). Matches any
@@ -58,20 +95,28 @@ function isAbortRequest(text) {
   const n = normalize(text);
   if (!n) return false;
   // Whole-message exact match (capped — a long message that happens to
-  // start with "stop" is real content, not an abort).
+  // start with "stop" is real content, not an abort). HARD or SOFT
+  // phrases both qualify here — the user typed JUST that word, which is
+  // unambiguous regardless of category.
   if (n.length <= 40 && ABORT_PHRASES.has(n)) return true;
 
   // First-sentence exact match. Splits on . ! ? (NOT comma — "Stop, look
-  // here" is ambiguous and stays non-abort). The leading @-mention has
-  // already been stripped by normalize but only on the whole string, so
-  // we strip it again on the raw text before splitting.
+  // here" is ambiguous and stays non-abort). HARD phrases ONLY — soft
+  // phrases like "wait" or "hold on" are conversational openers ("Wait?
+  // There is something wrong...") and shouldn't hijack a message where
+  // the rest contains real content.
   const head = text.trim().replace(LEADING_MENTION_RE, '');
   const firstSentence = head.split(/[.!?]/, 1)[0]?.trim().toLowerCase();
-  if (firstSentence && firstSentence.length <= 40 && ABORT_PHRASES.has(firstSentence)) {
+  if (firstSentence && firstSentence.length <= 40 && HARD_ABORT_PHRASES.has(firstSentence)) {
     return true;
   }
 
   return false;
 }
 
-module.exports = { isAbortRequest, ABORT_PHRASES };
+module.exports = {
+  isAbortRequest,
+  ABORT_PHRASES,
+  HARD_ABORT_PHRASES,
+  SOFT_ABORT_PHRASES,
+};

package/lib/abort-grace.js

@@ -0,0 +1,62 @@
+/**
+ * Abort-grace tracker — per-session timestamps marking "user just
+ * /stop'd this session, suppress the next batch of generic error
+ * replies".
+ *
+ * Why this exists: when the user types /stop (or natural-language
+ * "стоп"), polygram calls pm.kill(sessionKey). The kill SIGTERM's
+ * the in-flight process — every pending in the queue rejects with
+ * "Process killed" or INTERRUPTED. WITHOUT abort-grace, polygram
+ * would post "💥 Hit a snag" for each rejected pending, even though
+ * the user already saw the /stop ack and these errors are caused
+ * by their own action.
+ *
+ * Timestamp model (vs the earlier "delete after first read" Set):
+ * a single /stop can drain many pendings, so we mark a TS and let
+ * every error within ABORT_GRACE_MS see "yes, aborted, stay quiet".
+ *
+ * Closes v6 plan §7.1 G11 unit gate.
+ */
+
+'use strict';
+
+const DEFAULT_ABORT_GRACE_MS = 15_000;
+
+/**
+ * @param {object} [opts]
+ * @param {number} [opts.windowMs]   — grace window (default 15s)
+ * @param {() => number} [opts.now]  — clock injection for tests
+ */
+function createAbortGrace({ windowMs = DEFAULT_ABORT_GRACE_MS, now = () => Date.now() } = {}) {
+  const aborted = new Map();        // sessionKey → ts of abort
+
+  function mark(sessionKey) {
+    if (!sessionKey) return;
+    const ts = now();
+    aborted.set(sessionKey, ts);
+    // Sweep old entries opportunistically. Use 2× window so a
+    // session that's marked-and-checked at the boundary doesn't
+    // disappear before the check completes.
+    for (const [k, t] of aborted) {
+      if (ts - t > windowMs * 2) aborted.delete(k);
+    }
+  }
+
+  function isRecent(sessionKey) {
+    const ts = aborted.get(sessionKey);
+    return ts != null && (now() - ts) < windowMs;
+  }
+
+  function clear(sessionKey) {
+    aborted.delete(sessionKey);
+  }
+
+  return {
+    mark,
+    isRecent,
+    clear,
+    get size() { return aborted.size; },
+  };
+}
+
+module.exports = { createAbortGrace, DEFAULT_ABORT_GRACE_MS };