@sjawhar/pi-legion-envoy 5.11.1 → 5.13.0

package/dist/envoy.js

@@ -35188,6 +35188,27 @@ function onEnvoyRoleRegained(listener) {
   legionRoleClaimBridge().regained = listener;
 }
 
+// src/side-turn.ts
+function btwPrompt(question) {
+  return [
+    "<btw>",
+    "Ephemeral side question for current interactive session.",
+    "Answer briefly, directly; use conversation context already provided.",
+    "NEVER use tools.",
+    "NEVER ask follow-up questions.",
+    "Question:",
+    question,
+    "</btw>"
+  ].join(`
+`);
+}
+function sideTurn(pi, context) {
+  const runEphemeralTurn = context?.runEphemeralTurn;
+  if (runEphemeralTurn === undefined)
+    return pi.askEphemeral;
+  return ({ prompt, signal }) => runEphemeralTurn({ promptText: btwPrompt(prompt), signal });
+}
+
 // src/subagent-session.ts
 import fs from "fs";
 import path3 from "path";
@@ -35433,7 +35454,6 @@ function envoyExtension(pi) {
     availabilityWarningSessionIDs.add(sessionID2);
     context.ui.notify(`envoy: Dispatch open-ask check unavailable (${messageFor(error48)}); the stop-time ask reminder is off until it recovers`, "warning");
   };
-  const askEphemeral = pi.askEphemeral;
   const overriddenTimeout = Number(process.env.ENVOY_SELF_CHECK_TIMEOUT_MS);
   const selfCheckTimeoutMs = Number.isFinite(overriddenTimeout) && overriddenTimeout > 0 ? overriddenTimeout : ASK_SELF_CHECK_TIMEOUT_MS;
   const selfCheckWarningSessionIDs = new Set;
@@ -35542,13 +35562,18 @@ function envoyExtension(pi) {
         } else if (rendered.malformedDelivery === true) {
           console.warn("[envoy] dropping malformed Dispatch targeted delivery without a reply address");
         } else if (rendered.delivery?.mode === "btw") {
-          if (pi.askEphemeral === undefined) {
+          const answer = sideTurn(pi, activeSessionContext);
+          if (shuttingDown) {
+            await postDispatchReply(rendered.delivery, {
+              error: "This OMP session is shutting down"
+            });
+          } else if (answer === undefined) {
             await postDispatchReply(rendered.delivery, {
               error: "This OMP host does not support BTW delivery"
             });
           } else {
             try {
-              const reply2 = await pi.askEphemeral({ prompt: rendered.delivery.body });
+              const reply2 = await answer({ prompt: rendered.delivery.body });
               await postDispatchReply(rendered.delivery, { body: reply2.replyText });
             } catch (error48) {
               await postDispatchReply(rendered.delivery, { error: messageFor(error48) });
@@ -35733,7 +35758,7 @@ function envoyExtension(pi) {
     ],
     port: 0,
     title: activeSessionContext?.sessionManager.getSessionName?.() ?? "",
-    capabilities: typeof pi.askEphemeral === "function" ? DELIVERY_CAPABILITIES : CAPABILITIES_WITHOUT_BTW,
+    capabilities: sideTurn(pi, activeSessionContext) === undefined ? CAPABILITIES_WITHOUT_BTW : DELIVERY_CAPABILITIES,
     driving: false,
     selfSubscribed: true
   });
@@ -36127,7 +36152,7 @@ function envoyExtension(pi) {
   registerEnvoyWhoamiCommand(pi, replyAddress);
   pi.on("before_agent_start", async (event, context) => {
     const id = context.sessionManager.getSessionId();
-    if (id === "" || event.prompt.trim() === "" || !context.hasUI || askEphemeral === undefined || legionManaged(id)) {
+    if (id === "" || event.prompt.trim() === "" || !context.hasUI || sideTurn(pi, context) === undefined || legionManaged(id)) {
       return;
     }
     if (await isSubagent(context))
@@ -36158,39 +36183,40 @@ function envoyExtension(pi) {
   pi.on("agent_end", async (event, context) => {
     const id = context.sessionManager.getSessionId();
     const lastReply = event.messages?.findLast((message) => message.role === "assistant");
-    if (event.willContinue === true || lastReply?.stopReason !== "stop" || !context.hasUI || id === "" || !checkOwed(id)) {
+    const ask = sideTurn(pi, context);
+    if (event.willContinue === true || lastReply?.stopReason !== "stop" || !context.hasUI || id === "" || ask === undefined || !checkOwed(id)) {
       return;
     }
+    const settle = { context, ask, seenRun: runSeq, generation: awarenessGeneration };
     if (askCheckInFlight) {
-      settledDuringCheck = { context, seenRun: runSeq };
+      settledDuringCheck = settle;
       return;
     }
     askCheckInFlight = true;
+    context.setTimeout(() => checkFromSettle(id, settle), 0);
+  });
+  async function checkFromSettle(id, first) {
     try {
-      let settle = { context, seenRun: runSeq };
+      let settle = first;
       while (settle !== undefined) {
         await checkAtSettle(id, settle);
         settle = takeSettledDuringCheck();
-        if (settle?.context.sessionManager.getSessionId() !== id || settle.seenRun !== runSeq || !checkOwed(id)) {
-          settle = undefined;
-        }
       }
     } finally {
       askCheckInFlight = false;
       settledDuringCheck = undefined;
     }
-  });
+  }
   function checkOwed(id) {
-    return !(shuttingDown || legionManaged(id) || askAwareness.session_id !== id || askAwareness.period === 0 || !askAwareness.check_due || askAwareness.checks >= ASK_CHECKS_PER_PERIOD || askAwareness.baseline_as_of === null || askEphemeral === undefined);
+    return !(shuttingDown || legionManaged(id) || askAwareness.session_id !== id || askAwareness.period === 0 || !askAwareness.check_due || askAwareness.checks >= ASK_CHECKS_PER_PERIOD || askAwareness.baseline_as_of === null);
   }
   async function checkAtSettle(id, settle) {
-    const { context, seenRun } = settle;
+    const { context, ask, seenRun, generation } = settle;
     const period = askAwareness.period;
-    const generation = awarenessGeneration;
     const baseline = askAwareness.baseline_as_of;
-    if (baseline === null || askEphemeral === undefined)
-      return;
     const stale = () => shuttingDown || generation !== awarenessGeneration || context.sessionManager.getSessionId() !== id || legionManaged(id) || askAwareness.session_id !== id || askAwareness.period !== period || !askAwareness.check_due;
+    if (baseline === null || !checkOwed(id) || stale() || runSeq !== seenRun)
+      return;
     let open;
     try {
       open = await queryOpenAsks(id, baseline);
@@ -36207,7 +36233,7 @@ function envoyExtension(pi) {
     askCheckAbort = abort;
     let answered;
     try {
-      answered = askEphemeral({
+      answered = ask({
         prompt: ASK_SELF_CHECK_PROMPT(open.snapshot.asks),
         signal: abort.signal
       }).then((reply) => reply.replyText, (error48) => {

package/dist/legion.js

@@ -16192,7 +16192,7 @@ import { logger } from "@oh-my-pi/pi-utils";
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion-envoy",
-  version: "5.11.1",
+  version: "5.13.0",
   type: "module",
   omp: {
     extensions: [

package/dist/skills/dispatch/SKILL.md

@@ -106,7 +106,10 @@ A spec has two readers: the human who decides reads the **Summary** and **New si
   between two lanes or a halt condition, a question for the platform PO (see
   [Before you ask](#before-you-ask) under Asking).
 - Keep each section to one screen; work that exceeds one screen per section is two specs.
-- Update the spec as decisions land: the spec is the record, comments are the discussion.
+- Update the spec as decisions land: the spec is the record, comments are the discussion. It
+  records decisions and requirements, never progress: no status, timestamps, "Update HH:MMZ"
+  section, PR list, or handoff notes. Progress is not a Dispatch object at all; it lives in your
+  transcript and your pull request (see [Messages](#messages)).
 - Before sending it: no sections conflict, every requirement has exactly one reading, and the
   Summary and every ask block pass the phone test above.
 
@@ -274,6 +277,10 @@ start with the issue key; standalone project-document hit lines start with
 
 `dispatch_issue` refuses a title that near-duplicates an issue in the same project and returns the candidates (`POSSIBLE_DUPLICATE`).
 Read them; reference the existing issue, or repeat the call with `force: true` when it is genuinely new work.
+The check compares title words only (shared stemmed terms), never meaning: "four tests that fail a
+merge" pairs with "four CI gates that cannot fail a merge". So when you force past a candidate, give
+the new issue a title that names what differs where you can, and open its spec's Summary with the
+distinction from the named issue, citing it (`dispatch://KEY`), for whoever reads the next pairing.
 
 ## Reading a project's backlog
 
@@ -548,9 +555,8 @@ the document's approval state; `stale` means it was approved and then edited - r
 ## The Spec
 
 The spec holds requirements, design, acceptance, decisions, and rejected alternatives, structured per [Writing a spec](#writing-a-spec).
-It changes only when a decision or requirement changes, and every version that records one is named with `summary`. Never write
-progress, status, timestamps, an "Update HH:MMZ" section, a PR list, or handoff notes into the spec. Progress is not a
-Dispatch object at all: it lives in your transcript and your pull request (see [Messages](#messages)).
+It changes only when a decision or requirement changes, and every version that records one is named with `summary`. What it
+never carries is in [Rules](#rules) under Writing a spec.
 
 Read the current document before changing it:
 

package/dist/skills/envoy/SKILL.md

@@ -140,7 +140,7 @@ Each session row from `envoy_sessions` carries `capabilities`, the targeted-deli
 session's host honours: `aside` (a message queued beside the model's work), `btw` (an ephemeral
 question the host answers without disturbing the current turn), and `steer` (an interjection at
 the next tool boundary). An OMP session advertises `aside`, `btw`, and `steer` (`aside` and
-`steer` on a host without `askEphemeral`); a Claude Code session advertises `aside` only, because
+`steer` on a host that cannot run a side turn); a Claude Code session advertises `aside` only, because
 its channel notifications queue for the next turn. Target a session only with a mode it
 advertises.
 

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

@@ -97,7 +97,8 @@ arrives as a wake. At every start, before anything else:
    `issues.<KEY>.architect.state` is `failed` and whose `issues.<KEY>.phase` is not `done`, exactly
    as the matching wake below. A parked tree (root phase `done`: it lingers or is closed) needs
    nothing from you: a failed architect ignores the park and reads `failed` until the tree closes.
-2. List the project's triage issues with `dispatch_issues({project, status: "triage", limit: 250})`.
+2. List the project's triage issues handed to Legion with
+   `dispatch_issues({project, status: "triage", label: "legion", limit: 250})`.
    When its first line ends `(showing N of M)`, it is one page: say in your summary how many rows
    it left unread. The rows show no parent, so open each row with `dispatch_read`: one whose
    `Links:` name a `child_of` issue is a child, which its parent's architect owns, so leave it,
@@ -105,12 +106,24 @@ arrives as a wake. At every start, before anything else:
    of this issue, not its parent). Of the rest, triage each that `legion state --json` does not
    record under `issues` as a new issue. A root recorded there and now in `triage` is work the
    daemon holds that a human pulled back: never re-admit it yourself; name it in your summary to
-   the human ("<KEY> was pulled back to triage; what do you want?"). This listing is also the only
-   way you learn of an unrecorded root moved back into triage, or of a child detached to a root
-   while it is in triage, since the daemon wakes you only on a root's creation.
+   the human ("<KEY> was pulled back to triage; what do you want?").
 
 The issue record and Dispatch are the truth; the topic is the wake.
 
+### Issues handed to Legion (Go daemon)
+
+The Go daemon works only the issues handed to it with the Dispatch label `legion` (in any case),
+since its project may be shared with humans and other agents. It never admits a root in `todo`
+without the label, and wakes you for a root in `triage` only while the root carries it and is
+unrecorded: on its creation with the label, and on each change to it after that while it stays
+in triage, the change that adds the label included (the dashboard creates an issue without
+labels, so a human adds it from the issue header). Leave an issue without the label alone:
+handing work to Legion is its owner's decision, so never triage, park, label, or comment on it.
+A child needs no label: it runs under its tree's architect once its root is admitted.
+`legion status <KEY> todo` admits a root only while it carries the label, so a root you file for
+Legion to run carries it (`labels: ["legion"]` in `dispatch_issue`). Taking the label off a
+waiting root drops it from the waiting line; taking it off an admitted tree does not stop it.
+
 ## Deployment instructions
 
 Deployment instructions, when present, are the operator's standing rules for this repository —
@@ -137,7 +150,7 @@ quoted here.
 
 | Wake | Content | Controller action |
 |---|---|---|
-| New issue created in the Dispatch project (`issue.created`, status `triage`; under the TypeScript daemon resync heals misses, under the Go daemon the boot step above does). From the Go daemon: `triage on <KEY>` (payload `{kind: "triage"}`) on the controller topic, for a root only | issue key + triage context (incl. pre-existing children) | Triage: `legion status <KEY> todo` to admit, or set `backlog`/`icebox` to park |
+| New issue created in the Dispatch project (`issue.created`, status `triage`; under the TypeScript daemon resync heals misses, under the Go daemon the boot step above does). From the Go daemon: `triage on <KEY>` (payload `{kind: "triage"}`) on the controller topic, for an unrecorded root carrying the `legion` label only ("Issues handed to Legion" above) | issue key + triage context (incl. pre-existing children) | Triage: `legion status <KEY> todo` to admit, or set `backlog`/`icebox` to park |
 | Backlog eligibility | slot freed / priority change | Reconsider parked items and move the eligible root to `todo` |
 | Architect escalation (controller-actionable only: re-file a child as a root issue, capacity, cross-tree conflicts) | request + context | Judge and act; issue-scoped human Q&A goes through `dispatch_ask` from the owning architect, not here |
 | Resync report | artifact-driven anomaly list (zero-owner trees, untriaged-open, launch-failed, admission-drift) | Verify against fresh state, then heal |
@@ -172,9 +185,9 @@ quoted here.
    legion status <issue> backlog
    ```
 
-   (or `icebox` for longer-term deferral). Dispatch status is the durable record;
-   there is no separate marker to maintain. Do not triage a system-created child as a root
-   issue.
+   (or `icebox` for longer-term deferral). Dispatch status is the durable record; there is no
+   other marker to maintain, beyond the Go daemon's `legion` label, which parking leaves in
+   place. Do not triage a system-created child as a root issue.
 4. When you post a triage note (a `dispatch_comment` on the issue saying what you decided and
    why), name who will be asked: `Assigned to <login>, who will get this tree's questions`,
    or, when the `Assignee:` line says `unassigned`, `Unassigned — nobody's Inbox shows this
@@ -197,7 +210,8 @@ architect, not the controller.
 For an independence judgment, verify the child and its parent against current daemon state
 and the Dispatch issue. If the work belongs in an independent root:
 
-1. File a **fresh root issue** with `dispatch_issue({ project, title, spec })` (no `parent`).
+1. File a **fresh root issue** with `dispatch_issue({ project, title, spec })` (no `parent`;
+   under the Go daemon add `labels: ["legion"]`, without which it is never admitted).
    `project` is the issue key's prefix before `-<n>` (e.g. `LEGSMOKE-3` → `LEGSMOKE`) — not
    the role-token `<project>` (the daemon's own project, e.g. `acme`), a different string.
 2. Park the child (`legion status <child> icebox`) and leave

package/package.json

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