greprag 5.10.1 → 5.11.0

package/skill/{discord → commander}/SKILL.md

@@ -1,24 +1,30 @@
 ---
-name: discord
+name: commander
 description: |
-  Discord DM bridge for greprag. Pair your Discord account once, then DM the
-  bot to talk to the agent in any open Claude session. Handoff temporarily
-  pins your DMs to one specific session — say "let's continue on Discord"
-  before stepping away from the desk and your phone keeps the same thread
-  alive.
-
-  Use when: "/discord", "discord", "pair my discord", "step away", "let's
-  continue on discord", "let's continue on phone", "DM me", "handoff to
-  discord", "discord handoff", "discord status", "am I paired", "what's my
-  discord state", "I'm going for a walk", "I'll be afk".
+  Field-commander interface over greprag's Discord DM bridge. Pair your
+  Discord account once, then DM the bot to put any open Claude session
+  under your command from your phone. `/commander handoff` pins your DMs
+  to one specific session — say "step away" or "I'm going for a walk"
+  and the thread follows you off the desk. Emergency router: if you DM
+  the bot without a handoff active, the bot auto-links to the most
+  recently armed session under your tenant so you can still issue
+  orders ("find a commander in the midst of battle").
+
+  Use when: "/commander", "commander", "step away", "let's continue on
+  phone", "DM me", "handoff", "pair my discord", "commander status",
+  "am I paired", "what's my discord state", "I'm going for a walk",
+  "I'll be afk", "commander handoff", "find a session for me", "any
+  session to take this DM".
 metadata:
   author: travsteward
-  version: "1.0.0"
+  version: "2.0.0"
   repository: https://github.com/travsteward/greprag
 license: MIT
 ---
 
-# Discord DM bridge
+# Commander — Discord DM bridge
+
+The operator commands an open Claude session from Discord. The Discord side is the *channel*; "commander" is the *role* the operator inhabits when the DMs land.
 
 The agent runs `greprag discord me` to learn the current state, then branches into pair / handoff / status. Everything else is one shell command per branch.
 
@@ -96,7 +102,7 @@ Tell the user (orchestrator mode): "Orchestrator pinned for 60 min. I now see in
 
 ## Step 4 — Replying to inbound DMs
 
-Each Monitor notification carries the full event payload: `body` is the user's message text, `references.discord.snowflake` is their Discord ID.
+Each Monitor notification carries the full event payload: `body` is the user's message text, `references.discord.snowflake` is their Discord ID, and `references.discord.emergency_route` is non-null when the bot auto-routed an unassigned DM here (see Step 4b).
 
 Send your reply via the CLI:
 
@@ -106,6 +112,16 @@ greprag send --to discord:<snowflake> "your reply text"
 
 The CLI uses Node fetch (UTF-8 native) — em-dashes, curly quotes, emoji all render correctly. **Do NOT use curl from bash on Windows** for Discord sends — the local code page (Win-1252) mangles non-ASCII bytes into `?` on the user's phone.
 
+## Step 4b — Emergency-routed DMs (self-identify before answering)
+
+If `references.discord.emergency_route` is non-null, this session was auto-linked because no handoff pin was active. The user may have meant to reach a different session. **Open your first reply by self-identifying** so the operator can redirect if needed.
+
+Example first reply:
+
+> Picked this up in `<project-name>` / session `<session-8hex>` (no handoff was active, so I'm the most-recent armed watcher). Auto-pin is 10 min — slides while you keep replying. Want to redirect? `/commander handoff` from another session, or just say "redirect to <project>".
+
+The auto-pin TTL is short (10 min) and slides forward 30 min with each subsequent DM, so a real conversation keeps flowing here. If the operator goes quiet for the TTL window, the pin expires and the next DM re-runs the router (possibly landing in a different session if the topology has changed).
+
 For long agent turns where you're drafting >10s, refresh the typing indicator between work steps:
 
 ```bash

package/skill/greprag/SKILL.md

@@ -535,9 +535,11 @@ greprag corpus delete "<store>" --yes
 
 Odyssey is the agent's own past. Corpus is everything else.
 
-## Step 5g — Discord DM bridge (talk to the user via Discord)
+## Step 5g — Commander (Discord DM bridge — talk to the user from their phone)
 
-When the user wants to step away from the desk and continue the conversation on their phone, route the thread through the greprag Discord bot. There are two surfaces — one-time pairing (identity) and per-session handoff (active routing).
+For the full operator-facing flow see `/commander` (skill at `~/.claude/skills/commander/SKILL.md`). This section is the orchestrator-side summary so a greprag session can drive the same surface without loading the commander skill explicitly.
+
+When the user wants to step away from the desk and continue the conversation on their phone, route the thread through the greprag Discord bot. There are two surfaces — one-time pairing (identity) and per-session handoff (active routing). Plus an emergency-router fallback: if the user DMs the bot with no handoff active, the bot auto-links to the most-recently-attached session watcher under their tenant. Tag `references.discord.emergency_route` on the inbox row flags the auto-link; reply with self-identification on first response.
 
 ### Pairing (one-time per tenant)
 

package/skill/templates/chip-spawn.md

@@ -6,7 +6,7 @@ The `pre-spawn-check` PreToolUse hook **validates** chip prompts at the spawn bo
 
 - `title: "Chip: <verb-phrase>"` — `Chip: ` prefix enforced.
 - `prompt:` — Block 1 + task body + Block 2 (templates below).
-- `cwd:` — optional, lands the chip in a different project root.
+- `cwd:` — optional, lands the chip in a different project root. Repo paths: `~/.greprag/projects.json`.
 
 Add `mode: interactive` as the first line of the task body to pause the chip for human reply (default is autonomous).