@sjawhar/pi-envoy 10.17.6 → 10.17.8

package/dist/dispatch.js

@@ -15027,13 +15027,34 @@ function machineID() {
 
 // ../envoy-client/src/dispatch-cwd.ts
 var execFileAsync = promisify(execFile);
-var defaultExec = (file2, args, options) => execFileAsync(file2, args, { cwd: options.cwd, timeout: 5000 });
-async function tryExec(exec, file2, args, cwd) {
+var defaultExec = (file2, args, { cwd, signal }) => {
+  const call = execFileAsync(file2, args, { cwd, signal });
+  const kill = () => call.child.kill("SIGKILL");
+  if (signal.aborted)
+    kill();
+  else
+    signal.addEventListener("abort", kill, { once: true });
+  return call;
+};
+var REMOTE_LOOKUP_MS = 5000;
+var TMUX_PANE_LOOKUP_MS = 1000;
+async function tryExec(exec, file2, args, cwd, limitMs) {
+  const controller = new AbortController;
+  const expired = Promise.withResolvers();
+  const timer = setTimeout(() => {
+    controller.abort();
+    expired.resolve(null);
+  }, limitMs);
   try {
-    const { stdout } = await exec(file2, args, { cwd });
-    return stdout;
+    const answer = await Promise.race([
+      exec(file2, args, { cwd, signal: controller.signal }),
+      expired.promise
+    ]);
+    return answer?.stdout ?? null;
   } catch {
     return null;
+  } finally {
+    clearTimeout(timer);
   }
 }
 function parseRemoteList(stdout) {
@@ -15072,12 +15093,12 @@ function parseGitHubRemoteUrl(url2) {
   return null;
 }
 async function resolveCwdRepo(cwd, exec) {
-  const jjOutput = await tryExec(exec, "jj", ["git", "remote", "list"], cwd);
+  const jjOutput = await tryExec(exec, "jj", ["git", "remote", "list"], cwd, REMOTE_LOOKUP_MS);
   if (jjOutput !== null) {
     const url2 = selectRemoteUrl(parseRemoteList(jjOutput));
     return url2 ? parseGitHubRemoteUrl(url2) : null;
   }
-  const originUrl = await tryExec(exec, "git", ["remote", "get-url", "origin"], cwd);
+  const originUrl = await tryExec(exec, "git", ["remote", "get-url", "origin"], cwd, REMOTE_LOOKUP_MS);
   return originUrl ? parseGitHubRemoteUrl(originUrl) : null;
 }
 async function resolveOrigin(env, exec, cwd) {
@@ -15087,7 +15108,7 @@ async function resolveOrigin(env, exec, cwd) {
   };
   const pane = env.TMUX_PANE;
   if (pane) {
-    const output = await tryExec(exec, "tmux", ["display-message", "-p", "-t", pane, "#S:#I.#P #{pane_id}"], cwd);
+    const output = await tryExec(exec, "tmux", ["display-message", "-p", "-t", pane, "#S:#I.#P #{pane_id}"], cwd, TMUX_PANE_LOOKUP_MS);
     const [target, paneId] = output?.trim().split(" ") ?? [];
     if (target)
       origin.tmux = target;

package/dist/skills/dispatch/SKILL.md

@@ -98,6 +98,8 @@ Outside Legion, the session doing the work moves its issue and the children it o
 
 A design decision a document records is a decision block in it, at every phase, approved or not. A block in an approved document makes the approval stale until its answer. A Legion phase worker sends the decision to its architect (`skill://legion-worker`). A to-do or permission only a human can give, or a decision with no document, is a `dispatch ask`. The gates apply to both.
 
+In a Legion session, a role or any of its subagents that finds a problem outside its own issue never files an issue for it (the issue creation in [Your owner](#your-owner) included). It opens a `dispatch ask` as `skill://legion-worker/references/findings.md` says, on the issue that reference names. That overrides "Ask on your own issue" in gate 1, and gate 4's rule to ask nothing beside what the human asked for.
+
 ### Before you ask
 
 1. **Does it need the human's authority, taste or risk appetite?** Your lane decides schema shapes, field names and migration internals. Decide them in the plan or code, not in the spec. Settle a two-lane contract over Envoy, with no ask. A halt condition passes the gate. That is an IAM change, deleting or exposing production data, or anything that reaches a customer. Ask on your own issue.

package/dist/skills/dispatch-first/SKILL.md

@@ -28,6 +28,7 @@ dispatch search --query 'reviewer threads OR review comments'
 - **Question already decided:** the answered ask is the record. Cite it (`dispatch://KEY/ask/<id>`) where you rely on it. Do not ask again.
 - **Duplicate found:** keep the issue with the spec and the discussion, and copy over what only the duplicate has. Then close it: `dispatch issue-update --issue <KEY> --status done --reason 'Duplicate of dispatch://KEY.'`. If it has the `legion` label, or another session or a human holds its claim, comment on it with the survivor's name. Do not close it.
 - **Every ask and message stands alone:** the reader sees only that text. Put the facts, the options and your recommendation in it. Link what you cite (`dispatch://…`). Never write "see above" or "my earlier message".
+- **In a Legion session, a finding outside your own issue is never an issue you file.** A Legion role, and each of its subagents, opens a `dispatch ask` as `skill://legion-worker/references/findings.md` says, in place of filing above.
 
 ## Design in the spec
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-envoy",
-  "version": "10.17.6",
+  "version": "10.17.8",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {