squadrant 0.9.2 → 0.11.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "squadrant",
   "packageManager": "pnpm@10.30.3",
-  "version": "0.9.2",
+  "version": "0.11.0",
   "description": "Multi-project orchestration for your coding agents (Claude, Codex, opencode, Gemini)",
   "type": "module",
   "bin": {
@@ -41,12 +41,13 @@
     "jsonc-parser": "^3.3.1"
   },
   "devDependencies": {
+    "@grammyjs/types": "3.28.0",
+    "@squadrant/agents": "workspace:*",
     "@squadrant/cli": "workspace:*",
     "@squadrant/core": "workspace:*",
-    "@squadrant/agents": "workspace:*",
     "@squadrant/shared": "workspace:*",
-    "@squadrant/workspaces": "workspace:*",
     "@squadrant/web": "workspace:*",
+    "@squadrant/workspaces": "workspace:*",
     "@types/node": "^22.0.0",
     "tsup": "^8.5.1",
     "typescript": "^5.7.0",

package/plugin/skills/captain-ops/SKILL.md

@@ -241,6 +241,75 @@ After a crew task completes:
 
 Status writes (`write-status.sh`) are opt-in; you don't need to write status after every event.
 
+## Status Board (show after substantive turns)
+
+After a **substantive turn** — shipped a release, opened or merged a PR, filed an issue, spawned or closed crews, or moved multiple threads at once — end your reply with a tight scannable board. Skip it after trivial answers; the board is signal, not noise.
+
+### When to show
+
+| Show | Skip |
+|------|------|
+| Opened / merged / closed a PR | Answered a quick question |
+| Tagged a release or published to npm | Read a file or ran a status check |
+| Filed a GitHub issue | Forwarded a one-line follow-up to an existing crew |
+| Spawned or closed crew(s) | Repeated state the user just asked for |
+| Multiple threads moved in one turn | |
+
+### Pull state fresh before writing
+
+No memory, no approximation — run these first:
+
+```bash
+gh pr list --state open --json number,title,headRefName,isDraft   # open PRs
+squadrant crew list <project>                                      # live crews
+gh release list --limit 3                                         # recent tags
+npm view squadrant version 2>/dev/null                            # published version
+```
+
+### Board format
+
+```
+Right now → <one sentence: what just happened and what it unblocks>
+
+✅ Done         <completed item — note what it unblocks>
+✅ Done         <another if multiple>
+
+⏳ In progress  <crew-name> — <task + current state: idle|working|blocked>
+⏳ In progress  <another crew if running>
+
+▶️ Next         <immediate next action — specific, actionable>
+▶️ Next         <secondary if clear>
+
+👀 Watch        PR #N — <title> (draft | ready | needs review)
+👀 Watch        <release or deploy or issue to monitor>
+```
+
+### Rules
+
+- **Live data only.** Run the commands above; do not recall from memory. A stale board is worse than no board.
+- **~20–35 lines total.** Omit rows with nothing to say — an empty ⏳ section is just noise.
+- **One punchline.** The `Right now →` line is one sentence capturing the net state change.
+- **Portable.** Uses `gh` and `squadrant` CLI — works for claude, codex, opencode, and gemini crews alike.
+
+### Replying to Telegram-originated tasks
+
+When a task arrived from Telegram (captain pane received a message prefixed `[from Telegram]` / a `captain.message` inbound), push your answer back to that project's topic after acting:
+
+```bash
+squadrant telegram send <project> "<answer + brief board>"
+```
+
+**When to push:** At meaningful moments — your answer, a key decision, done/blocked. Not every line; keep it concise to avoid flooding the phone.
+
+**What to include:** One sentence of answer or status, then a condensed board (3–5 lines: what happened, what's next, any blocker). Example:
+
+```
+Shipped fix for #42 — merged to develop.
+✅ crew/fix-42 done  ▶️ next: bump version
+```
+
+**Portable:** uses the CLI only — works from any agent session (claude, codex, opencode, gemini).
+
 ## Session Shutdown (Opt-In Writes)
 
 End-of-session writes are **opt-in**, not on a schedule. Only write what is meaningful:

package/plugin/skills/telegram/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: telegram
+description: Set up and manage the squadrant↔Telegram integration — bot setup, remote control, command-menu registration, and per-project notification tuning (mute, crew tiers, cap). Use when the user asks about Telegram setup, "why don't commands work", registering the /command menu, or muting/tuning notifications.
+---
+
+# squadrant:telegram — Telegram Integration
+
+Squadrant pushes crew lifecycle events to Telegram forum topics and accepts commands back from your phone.
+
+## Setup
+
+Run the wizard once (re-run at any time to reconfigure):
+
+```bash
+squadrant telegram setup
+```
+
+The wizard will:
+1. Detect an existing bot token and reuse it (or prompt for a new one).
+2. Wait for a message in your forum supergroup to detect the group id and your user-id.
+3. Ask whether to enable **remote control** — say **yes** to capture your user-id and enable Gate 2 (command execution).
+
+After setup, the bot's `/command` menu is registered automatically.
+
+**Re-run setup if** `remoteControl` ended up OFF (you said no, or it was skipped). Use `--reset-token` to rotate the bot token.
+
+## Two Gates
+
+| Gate | What it checks | Controls |
+|------|----------------|----------|
+| Gate 1 — chats allowlist | `telegram.chats` contains the chat id | Inbound messages are processed |
+| Gate 2 — remoteControl + user-id | `remoteControl: true` AND sender is in `telegram.users` | Commands execute |
+
+"⛔ not authorized" means Gate 2 is closed — re-run setup and say yes to remote control.
+
+Reference: [`docs/diagrams/2026-06-23-telegram-daemon-architecture.html`](../docs/diagrams/2026-06-23-telegram-daemon-architecture.html)
+
+## Register the `/` Command Menu
+
+Setup registers the menu automatically. To re-register on demand:
+
+```bash
+squadrant telegram register-commands
+```
+
+If the `/` autocomplete shows no commands in Telegram, run this command.
+
+## Notifications
+
+**Live toggle (ephemeral — resets on restart):**
+
+```bash
+squadrant telegram notify <project> on
+squadrant telegram notify <project> off
+```
+
+**Persistent preferences (written to per-project config):**
+
+```bash
+squadrant telegram notify <project> crew <all|alert_only|done_only|none>
+squadrant telegram notify <project> cap <on|off>
+squadrant telegram notify --status
+```
+
+Crew notification tiers (cumulative — each includes all below):
+
+| Tier | What fires |
+|------|-----------|
+| `all` | Every crew event (started, blocked, done, failed) |
+| `alert_only` | Blocked + done + failed (default) |
+| `done_only` | Done + failed only |
+| `none` | No crew notifications |
+
+`cap=off` silences captain push messages (`squadrant telegram send`) for the project.
+
+**From Telegram** (Gate 2 required):
+
+```
+/notify crew done_only
+/mute
+/unmute
+```
+
+A mute confirmation is posted to the topic when you quiet a project.
+
+## Troubleshooting
+
+| Symptom | Fix |
+|---------|-----|
+| "⛔ not authorized" | `remoteControl` is OFF or wrong user-id — re-run `squadrant telegram setup` and say yes |
+| No `/` autocomplete menu | Run `squadrant telegram register-commands` |
+| Topic went silent | `squadrant telegram notify --status`; check crew tier |
+| Mute not reflected | Re-run `squadrant telegram notify <project> on` |
+| `createForumTopic` 400 errors | Topic already exists in state — `squadrant telegram status` to inspect links |