polygram 0.8.0-rc.27 → 0.8.0-rc.28

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.27",
+  "version": "0.8.0-rc.28",
   "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/package.json

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

@@ -3730,6 +3730,18 @@ async function main() {
   };
   process.on('SIGINT', shutdown);
   process.on('SIGTERM', shutdown);
+  // rc.28: also catch SIGHUP. The shumabit deploy path runs polygram
+  // inside `tmux new-session`; on `launchctl kickstart -k` the
+  // shumabit-start launcher does `tmux kill-session -t polygram`
+  // FIRST, then `pkill polygram --bot` 1s later. tmux kill-session
+  // closes polygram's controlling pty → SIGHUP, not SIGTERM. Without
+  // this listener, the shutdown drain never fires; in-flight rows
+  // never flip to 'replay-pending'; boot-replay still picks them up
+  // via the 'dispatched' status (3-min window), but anything that's
+  // been mid-tool-use longer than the replayWindowMs gets silently
+  // dropped. Surface symptom: bot stops responding after deploy on
+  // long agent runs (the §7.4 incident).
+  process.on('SIGHUP', shutdown);
 
   try {
     // Fresh per-boot secret, persisted 0600 for same-UID readers (cron