@sjawhar/pi-legion-envoy 0.8.5 → 0.9.0

package/dist/envoy.js

@@ -29979,7 +29979,7 @@ var DISPATCH_URGENCIES = ["low", "med", "high", "blocking"];
 var DISPATCH_TOOL_DESCRIPTION = "Raise a durable question to the human as a Dispatch thread (a GitHub issue shown on the dashboard), or continue an existing thread with a follow-up question. The reader has NOT seen your transcript. Open a thread with `subject`; continue one with `thread`. The reply arrives in this session as a steer.";
 var DISPATCH_ARGUMENTS = {
   subject: "Open a new thread: one line naming the decision needed (the issue title). Omit when continuing a thread with `thread`.",
-  thread: `Continue an existing thread: "<n>" (an issue in the working directory's repo) or "owner/name#<n>". When set, omit subject, urgency, repo, and parent.`,
+  thread: 'Continue an existing thread: "<n>" (an open issue in the repo; a plain work issue is adopted as a thread) or "owner/name#<n>". When set, omit subject, urgency, repo, and parent.',
   context: `What you are doing, what you found, why you are stuck \u2014 at most ${DISPATCH_CONTEXT_MAX} characters, at most three short paragraphs or a bullet list. The reader has NOT seen your transcript: no nouns you coined this session, no internal identifiers unless the question is about them. GitHub references (#N, owner/repo#N, URLs) may be bare; the dashboard unfurls them.`,
   question: `The ask, at most ${DISPATCH_QUESTION_MAX} characters, as a list: current state \u2192 desired state \u2192 your recommendation and why; options go in \`ask\`.`,
   ask: "Structured questions rendered as buttons on the dashboard. Each: { question, header?, options: [{ label, description? }], multiple?, custom? }. Use this whenever the answer is one of N choices.",

package/dist/skills/dispatch/SKILL.md

@@ -154,7 +154,8 @@ dispatch({
 ```
 
 - `thread` replaces `subject`; `urgency`, `repo`, and `parent` are not accepted with it.
-  The thread must be open and be a dispatch thread; otherwise the tool says so
+  `thread` names an open issue in the repo; a plain work issue is adopted as a thread on
+  first use. The issue must be open and not a pull request, or the tool says so
   (`#N is not a dispatch thread`, `#N is closed; open a new thread`).
 - Same decision → same thread. A genuinely new decision → a new thread, even if it came
   up in the reply.

package/dist/skills/legion-controller/SKILL.md

@@ -50,6 +50,7 @@ into a state holder: daemon state and GitHub artifacts remain authoritative.
 | Resync report | artifact-driven anomaly list (zero-owner trees, erroring issues) | Verify against fresh state, then dispatch/heal |
 | Mention | Slack/GitHub @mention text | Answer, or route to the owning issue's architect role |
 | Approval interpretation | ambiguous human comment on a gated issue | Decide whether it's an approval; if so, apply `human-approved` via the daemon |
+| Closed-tree activity (comment, review, CI on a closed tree) | issue, root, event summary | Read the artifact; if work should resume, `legion admit <root>`; otherwise no action — the event is not held or redelivered |
 | Direct user message | — | Always first |
 
 ## New issue triage

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion-envoy",
-  "version": "0.8.5",
+  "version": "0.9.0",
   "type": "module",
   "omp": {
     "extensions": [