allye-pi 2.15.1 → 2.16.0

package/README.md

@@ -75,7 +75,7 @@ Pair this install with your Allye account and every new, cleared or compacted se
 
 #### Live session reporting (Claude Code only, optional)
 
-When paired, hooks send Allye the state of your sessions (started, working, waiting, idle, ended), the tool names in use (within about 2 seconds of the call), subagent ids and types with their outcome, the spec and task keys the session is bound to and, on by default, short texts the agent wrote, each at most 140 characters: the description of a subagent dispatch, an activity phrase for each tool call (the `description` of a Bash or Agent call, else a fixed phrase such as "Read tree.ts", "Run vitest" or "Search the code" that holds at most one file name or Allye key and nothing else of the call), the `summary:` line of a crew report, and a session label (at most 60 characters: the `ALLYE_SESSION_LABEL` variable or the title Claude Code gives the session) with the name of the working folder. A crew report is also read from the subagent transcript when the final message has none (only its whole-line fields leave, never the transcript). Small numbers and keywords from the report (attempt, next step, gate, checks, finding counts, phase, ready/approved) and the pull request number from the `- PR: #N` line of the mission log go with them. Paths, URLs, emails, IP addresses, secrets and backticked code are stripped on your machine on a best-effort basis, with no guarantee, and Allye scrubs them again (the Allye scrub is the authoritative one); `/allye:hooks live activity off` turns the texts off (so does Detailed Live in the Allye app). Only you can see these texts in Allye (a teammate's token receives none). Allye keeps them for 30 days with the run: the three texts, the session labels, up to 50 activity phrases per step and the working folder name; turning Detailed Live off deletes them. A small background watcher (one per session, no network use while Claude Code runs) ends the run on Allye when Claude Code is closed without a normal exit. Through the Allye MCP, `task_start`, `task_submit`, `spec_context` and `spec_get` (and a `/bridge` launch with a key) tie a session to a spec or task. The subagent type, tool names, the texts and `allye:<action>` / spec / task keys DO leave your machine; prompts, commands, tool inputs and outputs, file paths, notification messages, assistant messages other than the report's whole-line fields, transcripts, branch names and credentials never do. The name of the working folder (one path component, never the path) leaves only with a session label, and not when its name looks secret. Update the plugin only after the Allye API that accepts the new fields is live. Control it with `/allye:hooks live off|on|status`; events, fields, the watcher and local files are in [docs/live-reporting.md](docs/live-reporting.md).
+When paired, hooks send Allye the state of your sessions (started, working, waiting, idle, ended), the tool names in use (within about 2 seconds of the call), subagent ids and types with their outcome, the spec and task keys the session is bound to and, on by default, short texts the agent wrote, each at most 140 characters: the description of a subagent dispatch, an activity phrase for each tool call (the `description` of a Bash or Agent call, else a fixed phrase such as "Read tree.ts" or "Run vitest" that holds at most one file name or Allye key and nothing else of the call. Without an agent-written description, Live sends only a fixed phrase from a short list: git actions (Commit to git, Push to git, Merge in git, Fetch from git, Read the history), pull request actions (Open the PR, Merge the PR, Check the PR), Check the heavy lock, Update the mission log, Search the code, Find .<ext> files (or Find files), Send a message, Save a memory, Update task <KEY> (or Update a task), the test, lint, build and diff phrases such as Run tests or Check git status, and Run a command for anything else (any pipe, redirect, chain with an unknown part or long command); no argument, branch, remote, message, path or flag value of a command is ever sent. The task key a subagent passes to its own task_start can label its step (a display hint).), the `summary:` line of a crew report, and a session label (at most 60 characters: the `ALLYE_SESSION_LABEL` variable or the title Claude Code gives the session) with the name of the working folder. A crew report is also read from the subagent transcript when the final message has none (only its whole-line fields leave, never the transcript). Small numbers and keywords from the report (attempt, next step, gate, checks, finding counts, phase, ready/approved) and the pull request number from the `- PR: #N` line of the mission log go with them. Paths, URLs, emails, IP addresses, secrets and backticked code are stripped on your machine on a best-effort basis, with no guarantee, and Allye scrubs them again (the Allye scrub is the authoritative one); `/allye:hooks live activity off` turns the texts off (so does Detailed Live in the Allye app). Only you can see these texts in Allye (a teammate's token receives none). Allye keeps them for 30 days with the run: the three texts, the session labels, up to 50 activity phrases per step and the working folder name; turning Detailed Live off deletes them. A small background watcher (one per session, no network use while Claude Code runs) ends the run on Allye when Claude Code is closed without a normal exit. Through the Allye MCP, `task_start`, `task_submit`, `spec_context` and `spec_get` (and a `/bridge` launch with a key) tie a session to a spec or task. The subagent type, tool names, the texts and `allye:<action>` / spec / task keys DO leave your machine; prompts, commands, tool inputs and outputs, file paths, notification messages, assistant messages other than the report's whole-line fields, transcripts, branch names and credentials never do. The name of the working folder (one path component, never the path) leaves only with a session label, and not when its name looks secret. Update the plugin only after the Allye API that accepts the new fields is live. Control it with `/allye:hooks live off|on|status`; events, fields, the watcher and local files are in [docs/live-reporting.md](docs/live-reporting.md).
 
 #### Answering from Allye (Claude Code only, optional)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "allye-pi",
-  "version": "2.15.1",
+  "version": "2.16.0",
   "description": "Allye extension for Pi and OMP: the Allye bootstrap, the Bridge skill and the repository-to-project link",
   "type": "module",
   "keywords": [

package/skills/bridge/SKILL.md

@@ -124,3 +124,5 @@ next: <action|none>
 ## Limits
 
 Do not deploy, request reviewers, widen scope, touch another repo, or publish unapproved risk. A material change stops the slice (`workflow.md` §10). Keep the log factual and free of secrets.
+
+**Bash descriptions** apply unconditionally to the Mothership and every crew role: give each Bash call a verb-first `description` saying what and why, at most 60 characters, no paths; state the purpose, never data: no values, tokens, customer or person names. Dispatch descriptions keep the task key first (`references/delegation.md`).

package/skills/bridge/references/delegation.md

@@ -124,7 +124,7 @@ next: <recommended action>
 - `checks: ok=<n> run=<n>` — Copilot: ok = reruns whose `match` is true, run = reruns executed; Watcher: ok = satisfied ACs, run = total ACs.
 - `severity_counts: critical=<n> high=<n> medium=<n> low=<n> info=<n>` — Medic, Shield, Copilot and Watcher; all five keys once, in that order.
 
-**Bash descriptions.** Every crew role gives each Bash call a verb-first `description` of at most 60 characters with no paths (such as `Run the skills tests`). This is advisory: the hard cap stays 140 and the cleaner and API scrub of BR-04 still apply; the rule only makes the Live phrase come from the agent instead of the classifier.
+**Bash descriptions.** Every crew role gives each Bash call a verb-first `description` of at most 60 characters with no paths (such as `Run the skills tests`). This is advisory: the hard cap stays 140 and the cleaner and API scrub of BR-04 still apply; the rule only makes the Live phrase come from the agent instead of the classifier. The same rule binds the Mothership and every crew role, unconditionally (BR-08): say what and why (such as `Run the full hooks suite before the PR`), and state the purpose, never data: no values, tokens, customer or person names. A heredoc or pipe call without a description falls back to a generic `Run a command` phrase, so the description is what makes the Live view useful. Dispatch descriptions keep the task key first (such as `Pilot PROJ-12.2 · wire the panel`).
 
 Each `<n>` is an integer 0-99 without sign, decimal point or leading zero.