polygram 0.3.0 → 0.3.2

package/.claude-plugin/marketplace.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
+  "name": "shumkov",
+  "description": "Ivan Shumkov's Claude Code plugins.",
+  "owner": {
+    "name": "Ivan Shumkov",
+    "email": "ivanshumkov@gmail.com"
+  },
+  "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.",
+      "category": "integration",
+      "source": "./",
+      "homepage": "https://github.com/shumkov/polygram"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "polygram",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "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/README.md

@@ -120,23 +120,40 @@ For production, LaunchAgent plists are in `ops/`. See `ops/README.md`.
 polygram also ships as a Claude Code plugin — adds admin slash commands
 and bundles the transcript-query skill for use inside your Claude sessions.
 
+The repo doubles as a single-plugin marketplace. Two commands at your
+Claude Code `/` prompt:
+
+```
+/plugin marketplace add https://github.com/shumkov/polygram.git
+/plugin install polygram@shumkov
 ```
-/plugin install https://github.com/shumkov/polygram.git
+
+The first registers the marketplace (`shumkov`). The second installs the
+`polygram` plugin from it.
+
+To enable in a specific Claude project, add to `.claude/settings.json`:
+
+```json
+{
+  "enabledPlugins": {
+    "polygram@shumkov": true
+  }
+}
 ```
 
-Once installed:
+Once enabled:
 
-- `/polygram:status` — running bots, IPC health, recent events, one-line verdict
+- `/polygram:status` — running bots, IPC health, recent events
 - `/polygram:logs <bot>` — tail `~/polygram/logs/<bot>.log`
 - `/polygram:pair-code` — walks you through issuing a pairing code (in-band via Telegram)
 - `/polygram:approvals [bot]` — pending and recent tool-approval rows
 
-The bundled **`telegram-history` skill** lets Claude query the transcript
-directly:
+The bundled **`history` skill** lets Claude query the transcript directly
+when you ask about past chat activity:
 
 ```
 "Summarise the Orders topic today" →
-  uses skills/history to run `recent <chat> --since 24h`
+  Claude invokes the history skill → runs `recent <chat> --since 24h`
 ```
 
 Scope is derived from `process.cwd()`: the skill refuses to run from an

package/commands/status.md

@@ -2,39 +2,66 @@
 description: Show polygram daemon health — running bots, IPC sockets, recent events.
 ---
 
-You are asked to report the current health of the polygram Telegram daemon.
-
-Do these checks, in order, using the Bash tool, and summarise the results in
-a short Markdown table (one row per bot):
-
-1. **Which bots are supervised by launchd.** Run:
-   ```
-   launchctl list | grep -i polygram || echo "no LaunchAgents loaded"
-   ```
-   Parse the output. Each line `<PID>\t<exit>\t<label>` is one bot
-   (e.g. `com.polygram.my-bot`). The PID column tells you whether it is
-   running; `-` means loaded but not currently running.
-
-2. **Is each bot's Unix socket alive?** For every bot you identified, run:
-   ```
-   node ~/polygram/scripts/ipc-smoke.js <bot-name>
-   ```
-   Interpret the result:
-   - `ping: {"id":null,"ok":true,"pong":true,"bot":"<bot>"}` → socket alive
-   - `ERR: connect ECONNREFUSED` → socket stale (polygram not actually
-     serving despite plist being loaded)
-   - `ERR: ENOENT` → socket missing (polygram never got that far at boot)
-
-3. **Recent events in each bot's DB.** For every bot, run:
-   ```
-   sqlite3 ~/polygram/<bot>.db "SELECT ts, kind, detail_json FROM events ORDER BY ts DESC LIMIT 5;"
-   ```
-   Call out anything that looks like an error (`-fail`, `-error`,
-   `crashed-mid-send`, `poll-stalled`, `approval-sweep-failed`).
-
-4. **Summarise.** A two-line per-bot summary, plus an overall verdict at
-   the bottom (✅ healthy / ⚠️ degraded / ❌ broken).
-
-If the user's polygram install is not at `~/polygram`, they may have set
-`POLYGRAM_HOME` or a custom path. Ask them to point you at it rather than
-guessing.
+Report the health of the polygram Telegram daemon.
+
+Do these checks with the Bash tool and summarise per-bot in a short
+Markdown table. Cover launchd **and** tmux supervision — users run either.
+
+### 1. Discover configured bots
+
+Read bot names from `~/polygram/config.json` (or `$POLYGRAM_CONFIG`):
+
+```
+jq -r '.bots | keys[]' ~/polygram/config.json
+```
+
+### 2. Per bot, check supervisor + process
+
+**a) LaunchAgent** — `launchctl list | grep com.polygram.<bot>`. If
+present the bot is under launchd. PID `-` means loaded but not running.
+
+**b) tmux** — `tmux list-windows -a 2>/dev/null | grep <bot>`. If
+present the bot is running in a tmux pane (most common during testing).
+
+**c) Process** — `pgrep -f "polygram --bot <bot>"`. Confirms the Node
+process is actually alive regardless of supervisor.
+
+Label supervision as:
+- `launchd` — plist loaded
+- `tmux` — window present
+- `foreground` — alive but unsupervised (will die on logout/crash)
+- `absent` — no process
+
+### 3. IPC socket liveness
+
+```
+polygram-ipc <bot-name>
+```
+
+That's the `polygram-ipc` bin installed alongside the daemon. Interpret:
+- `ping: {"ok":true,...}` — socket alive ✅
+- `ERR: ECONNREFUSED` — socket stale (supervisor claims running, isn't serving)
+- `ERR: ENOENT` — socket missing
+- `command not found: polygram-ipc` — user has polygram < 0.3.2; tell
+  them to `npm install -g polygram@latest`
+
+### 4. Recent events
+
+```
+sqlite3 ~/polygram/<bot>.db "SELECT ts, kind FROM events ORDER BY ts DESC LIMIT 5;"
+```
+
+Flag anything ending in `-failed`, `-error`, `crashed-mid-send`,
+`poll-stalled`, `approval-sweep-failed`.
+
+### 5. Summarise
+
+Compact Markdown table + overall verdict:
+
+- ✅ **healthy** — every bot supervised, live socket, no recent errors
+- ⚠️ **degraded** — running but not supervised (foreground) OR sweeper
+  events present OR stale socket
+- ❌ **broken** — any bot has no live process or no live socket
+
+If the install isn't at `~/polygram/`, ask for the data-dir path rather
+than guessing.

package/package.json

@@ -1,11 +1,12 @@
 {
   "name": "polygram",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "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": {
     "polygram": "polygram.js",
-    "polygram-split-db": "scripts/split-db.js"
+    "polygram-split-db": "scripts/split-db.js",
+    "polygram-ipc": "scripts/ipc-smoke.js"
   },
   "files": [
     "polygram.js",