@sjawhar/pi-legion-envoy 0.8.4 → 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.",
@@ -31329,6 +31329,34 @@ function toolFailure(error) {
   return { content: [{ type: "text", text: messageFor(error) }], details: {}, isError: true };
 }
 
+// extensions/envoy-message-renderer.ts
+import { Box, Spacer, Text } from "@oh-my-pi/pi-tui";
+var ENVOY_MESSAGE_COLLAPSED_LINES = 12;
+function renderEnvoyMessage(message, options, theme) {
+  const box = new Box(1, 1, undefined, {
+    chars: theme.boxRound,
+    color: (text) => theme.fg("borderMuted", text)
+  });
+  box.setIgnoreTight(true);
+  box.addChild(new Text(theme.fg("customMessageLabel", theme.bold(message.customType)), 0, 0));
+  box.addChild(new Spacer(1));
+  let text = message.content;
+  if (!options.expanded) {
+    const lines = text.split(`
+`);
+    if (lines.length > ENVOY_MESSAGE_COLLAPSED_LINES) {
+      text = `${lines.slice(0, ENVOY_MESSAGE_COLLAPSED_LINES).join(`
+`)}
+\u2026`;
+    }
+  }
+  box.addChild(new Text(theme.fg("customMessageText", text), 0, 0));
+  return box;
+}
+function registerEnvoyMessageRenderer(pi) {
+  pi.registerMessageRenderer("envoy-message", renderEnvoyMessage);
+}
+
 // extensions/envoy-whoami-command.ts
 import { copyToClipboard } from "@oh-my-pi/pi-coding-agent";
 function registerEnvoyWhoamiCommand(api, cachedSessionID) {
@@ -31410,6 +31438,7 @@ function envoyExtension(pi) {
   let activeSessionContext;
   const inbox = [];
   pi.on("resources_discover", async () => ({ skillPaths: [SKILLS_DIRECTORY] }));
+  registerEnvoyMessageRenderer(pi);
   const ensureConnection = async () => {
     if (connection?.isClosed() === false)
       return connection;

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.4",
+  "version": "0.9.0",
   "type": "module",
   "omp": {
     "extensions": [
@@ -15,7 +15,7 @@
     "dist"
   ],
   "scripts": {
-    "build": "bun build extensions/envoy.ts extensions/legion.ts --outdir dist --target bun --format esm --external @oh-my-pi/pi-coding-agent",
+    "build": "bun build extensions/envoy.ts extensions/legion.ts --outdir dist --target bun --format esm --external @oh-my-pi/pi-coding-agent --external @oh-my-pi/pi-tui",
     "prepack": "./scripts/prepack.sh",
     "postpack": "rm -rf dist/skills",
     "typecheck": "bunx tsc --noEmit",
@@ -27,6 +27,7 @@
     "@legion/contracts": "0.10.0",
     "@legion/envoy-client": "0.1.0",
     "@legion/workspace": "0.1.0",
+    "@oh-my-pi/pi-tui": "^18.1.15",
     "@toon-format/toon": "^4.1.1",
     "@types/bun": "latest",
     "nats": "^2.29.2",