polygram 0.10.0-rc.31 → 0.10.0-rc.32

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.31",
+  "version": "0.10.0-rc.32",
   "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/db/sessions.js

@@ -98,16 +98,33 @@ function getClaudeSessionId(db, sessionKey) {
 // ─── S2: session-config drift ────────────────────────────────────────
 //
 // A stored `sessions` row records the config the claude session was
-// SPAWNED under (agent / cwd / pm_backend). Those three are
-// spawn-identity: they are baked into the process at spawn time —
-// `--agent`, the tmux/SDK working dir, the backend class — and cannot
-// be changed on a live session. If the chat/topic config has drifted
-// from the stored row, `--resume`-ing the old session forces claude
-// to run under a config it was never built for. shumorobot
-// 2026-05-17 22:03, topic :3: the row was agent=shumabit / cwd=$HOME
-// / sdk (created before the Music topic got its per-topic override);
-// resuming it under agent=music-curation:music-curator /
-// cwd=.../Music/rekordbox / tmux left the TUI never signalling ready.
+// SPAWNED under. Two of the recorded fields are spawn-identity:
+//   - agent — `--agent <name>` is baked into the spawned process;
+//     resuming a session spawned under agent X under agent Y forces
+//     claude to use Y's system prompt + tool whitelist against
+//     conversation history built under X's. Incoherent.
+//   - cwd — `--cwd <path>` (SDK) / tmux session cwd; claude resolves
+//     project-local config (.claude/settings.json, agent files,
+//     plugins) relative to it. Mid-conversation cwd drift means
+//     half the messages are answered with one project's allowlist
+//     and the other half with another's.
+//
+// pm_backend was REMOVED from spawn-identity (rc.32, 2026-05-21).
+// Both backends spawn the same pinned claude binary and write the
+// same on-disk JSONL (~/.claude/projects/<cwd-enc>/<sid>.jsonl) —
+// claude itself doesn't know or care which Node-side wrapper invoked
+// it. Treating a backend flip as drift was destructively dropping
+// context across the SDK→tmux migration window, costing every chat
+// its conversation history on its first turn under the new backend.
+// shumorobot 2026-05-20 18:51 incident: the Music topic flipped
+// tmux→sdk→tmux during runtime and lost its agent's prior context
+// at each flip. The orphan-tmux problem that the flip ALSO triggered
+// is solved by rc.31's spawn-time reconcile (TmuxProcess.start) —
+// independently, so a backend flip is now a no-op for session-state.
+//
+// shumorobot 2026-05-17 22:03, topic :3 (the original drift incident)
+// remains correctly handled: that row had agent+cwd drift in
+// addition to backend, so the agent+cwd drift alone still drops it.
 //
 // model + effort are deliberately EXCLUDED from the invalidating set.
 // They are NOT spawn-identity: a live `/model` or `/effort` change is
@@ -118,7 +135,7 @@ function getClaudeSessionId(db, sessionKey) {
 // every model switch, double-handling what the live-apply path
 // already covers cleanly. The stored model/effort columns are
 // informational, not identity.
-const SPAWN_IDENTITY_FIELDS = ['agent', 'cwd', 'pm_backend'];
+const SPAWN_IDENTITY_FIELDS = ['agent', 'cwd'];
 
 /**
  * Decide whether a stored session can be resumed for the next spawn,

package/lib/process/tmux-process.js

@@ -499,9 +499,12 @@ class TmuxProcess extends Process {
       // Spawn-time reconcile (shumorobot 2026-05-20 18:51 incident).
       // A tmux session with our name may already exist on the host
       // BEFORE we spawn — sources:
-      //   - pm_backend drift: chat config flipped tmux → sdk → tmux;
-      //     polygram dropped its in-memory handle but the previous
-      //     daemon's tmux session is still running headless.
+      //   - pm_backend flip: chat config flipped tmux → sdk → tmux;
+      //     polygram dropped its in-memory handle on the flip away
+      //     from tmux but the previous daemon's tmux session is still
+      //     running headless. (rc.32 makes the flip context-preserving
+      //     on the session-id side; this reconcile keeps the
+      //     tmux-pane side safe.)
       //   - Boot-sweep raced a concurrent operator (already noted in
       //     lib/tmux/orphan-sweep.js header).
       //   - Crash mid-spawn: the spawn() call landed but the sessionCreated

package/package.json

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

@@ -400,18 +400,21 @@ function buildSpawnContext(sessionKey) {
   const threadId = sessionKey.includes(':') ? sessionKey.split(':')[1] : null;
 
   // S2: a stored session is valid ONLY for the config it was spawned
-  // under. agent / cwd / pm_backend are spawn-identity — baked into
-  // the process at spawn time, never mutable on a live session.
-  // Resolve them the same way the backends do (topic override merged
-  // over chat-level) and compare to the stored `sessions` row. On
-  // drift, resolveSessionForSpawn drops the stale row and returns
+  // under. agent / cwd are spawn-identity — baked into the process at
+  // spawn time, never mutable on a live session. Resolve them the
+  // same way the backends do (topic override merged over chat-level)
+  // and compare to the stored `sessions` row. On drift,
+  // resolveSessionForSpawn drops the stale row and returns
   // existingSessionId:null → the spawn starts fresh under the correct
   // config instead of `--resume`-ing a stale one. This self-heals the
   // pre-per-topic-config rows (e.g. shumorobot's Music topic :3,
-  // stored agent=shumabit / cwd=$HOME / sdk vs the current
-  // music-curation:music-curator / .../Music/rekordbox / tmux).
+  // stored agent=shumabit / cwd=$HOME vs the current
+  // music-curation:music-curator / .../Music/rekordbox).
   // model/effort are NOT compared — they apply live via setModel /
-  // applyFlagSettings with no respawn.
+  // applyFlagSettings with no respawn. pm_backend is also NOT
+  // compared (rc.32): both backends spawn the same pinned claude
+  // binary against the same on-disk JSONL, so a backend flip
+  // preserves context. See lib/db/sessions.js for full reasoning.
   //
   // The drift check runs only at COLD spawn (no warm process). A warm
   // process already runs under its spawn-time config; getOrSpawn