@sjawhar/pi-legion-envoy 7.6.5 → 7.7.1

package/dist/envoy.js

@@ -32756,6 +32756,32 @@ function renderAdvice(tool, key, advice, opts) {
   }
   return lines;
 }
+function renderSuggestions(suggestions, configUrl) {
+  if (suggestions === undefined)
+    return [];
+  if (suggestions.missing !== undefined) {
+    return [`Related-item search was skipped: ${suggestions.missing}.`];
+  }
+  const lines = [];
+  if (suggestions.related.length > 0) {
+    lines.push("Possibly related, found by search:");
+    for (const item of suggestions.related) {
+      lines.push(`- ${suggestionLabel(item)} \u2192 ${new URL(item.href, configUrl).toString()}`);
+    }
+  }
+  if (suggestions.decision !== undefined) {
+    const item = suggestions.decision;
+    const when = item.answered_at === undefined ? "" : ` on ${item.answered_at}`;
+    lines.push(`A past decision may already answer this: ${suggestionLabel(item)}, answered by ${item.answered_by}${when} \u2192 ${new URL(item.href, configUrl).toString()}`);
+  }
+  return lines;
+}
+function suggestionLabel(item) {
+  if (item.owner.kind === "issue") {
+    return `${item.owner.key} [${item.owner.status}] ${item.owner.title}`;
+  }
+  return `${item.owner.name} (${item.owner.project}/${item.owner.slug})`;
+}
 function documentResultDetails(artifact) {
   return {
     project: artifact.project,
@@ -33936,7 +33962,8 @@ async function executeDispatchTool(input) {
           ...renderAdvice(input.tool, created.key, created.advice, {
             isPrimarySpec: spec !== undefined
           }),
-          ...componentGuidance === undefined ? [] : [componentGuidance]
+          ...componentGuidance === undefined ? [] : [componentGuidance],
+          ...renderSuggestions(created.advice?.suggestions, configUrl)
         ];
         return {
           text: [
@@ -34216,7 +34243,10 @@ async function executeDispatchTool(input) {
       };
       const ask = resolved?.owner.kind === "project" ? await client.artifactAsk(resolved.artifact.id, askInput) : await client.ask(issue2(), askInput);
       const askOwner = ask.issue_key !== null ? issueTopic(ask.issue_key) : resolved === undefined ? issueTopic(issue2()) : documentTopic(resolved.artifact);
-      const adviceLines = renderAdvice(input.tool, askOwner.label, ask.advice, {});
+      const adviceLines = [
+        ...renderAdvice(input.tool, askOwner.label, ask.advice, {}),
+        ...renderSuggestions(ask.advice?.suggestions, configUrl)
+      ];
       return {
         text: [
           `Asked ${ask.id} on ${askOwner.label} (urgency ${ask.urgency}): ${ask.question}

package/dist/legion.js

@@ -15541,6 +15541,32 @@ function renderAdvice(tool, key, advice, opts) {
   }
   return lines;
 }
+function renderSuggestions(suggestions, configUrl) {
+  if (suggestions === undefined)
+    return [];
+  if (suggestions.missing !== undefined) {
+    return [`Related-item search was skipped: ${suggestions.missing}.`];
+  }
+  const lines = [];
+  if (suggestions.related.length > 0) {
+    lines.push("Possibly related, found by search:");
+    for (const item of suggestions.related) {
+      lines.push(`- ${suggestionLabel(item)} \u2192 ${new URL(item.href, configUrl).toString()}`);
+    }
+  }
+  if (suggestions.decision !== undefined) {
+    const item = suggestions.decision;
+    const when = item.answered_at === undefined ? "" : ` on ${item.answered_at}`;
+    lines.push(`A past decision may already answer this: ${suggestionLabel(item)}, answered by ${item.answered_by}${when} \u2192 ${new URL(item.href, configUrl).toString()}`);
+  }
+  return lines;
+}
+function suggestionLabel(item) {
+  if (item.owner.kind === "issue") {
+    return `${item.owner.key} [${item.owner.status}] ${item.owner.title}`;
+  }
+  return `${item.owner.name} (${item.owner.project}/${item.owner.slug})`;
+}
 function documentResultDetails(artifact) {
   return {
     project: artifact.project,
@@ -16721,7 +16747,8 @@ async function executeDispatchTool(input) {
           ...renderAdvice(input.tool, created.key, created.advice, {
             isPrimarySpec: spec !== undefined
           }),
-          ...componentGuidance === undefined ? [] : [componentGuidance]
+          ...componentGuidance === undefined ? [] : [componentGuidance],
+          ...renderSuggestions(created.advice?.suggestions, configUrl)
         ];
         return {
           text: [
@@ -17001,7 +17028,10 @@ async function executeDispatchTool(input) {
       };
       const ask = resolved?.owner.kind === "project" ? await client.artifactAsk(resolved.artifact.id, askInput) : await client.ask(issue2(), askInput);
       const askOwner = ask.issue_key !== null ? issueTopic(ask.issue_key) : resolved === undefined ? issueTopic(issue2()) : documentTopic(resolved.artifact);
-      const adviceLines = renderAdvice(input.tool, askOwner.label, ask.advice, {});
+      const adviceLines = [
+        ...renderAdvice(input.tool, askOwner.label, ask.advice, {}),
+        ...renderSuggestions(ask.advice?.suggestions, configUrl)
+      ];
       return {
         text: [
           `Asked ${ask.id} on ${askOwner.label} (urgency ${ask.urgency}): ${ask.question}
@@ -17524,7 +17554,7 @@ function endInjectedUserTurns(sessionID) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion-envoy",
-  version: "7.6.5",
+  version: "7.7.1",
   license: "Apache-2.0",
   type: "module",
   omp: {
@@ -18460,7 +18490,7 @@ function handoffSchemaFields(z2) {
     ready: z2.boolean().optional()
   };
 }
-var HANDOFF_DESCRIPTION = "Handoff actions (phase workers; the daemon accepts a completion only from the role working " + "the issue's current phase, never from an architect): handoff_write writes this phase's handoff " + "(`phase`, and `data`: the phase-specific fields as a JSON object, never the schemaVersion, " + "phase and completed the command writes itself) to `.legion/<phase>.json` in " + "the issue workspace; handoff_read returns the handoffs (every phase, or `phase`); " + "handoff_complete reports this phase complete to the daemon (`summary`: two sentences for the " + "architect, or the merger's READY packet; `verdict` pass|fail when your role's instructions " + "require one; `ready: true` for the merger's READY; no `phase` is needed, and one other than " + "your own is refused). Each " + "returns the command's output; a failed action changed nothing. What a later phase needs goes " + "in your handoff; a question for another live role goes to its role topic with envoy_publish.";
+var HANDOFF_DESCRIPTION = "Handoff actions (phase workers; the daemon accepts a completion only from the role working " + "the issue's current phase, never from an architect): handoff_write writes this phase's handoff " + "(`phase`, and `data`: the phase-specific fields as a JSON object, never the schemaVersion, " + "phase, completed and issue the command writes itself) to `.legion/<phase>.json` in " + "the issue workspace; handoff_read returns the handoffs (every phase, or `phase`); " + "handoff_complete reports this phase complete to the daemon (`summary`: two sentences for the " + "architect, or the merger's READY packet; `verdict` pass|fail when your role's instructions " + "require one; `ready: true` for the merger's READY; no `phase` is needed, and one other than " + "your own is refused). Each " + "returns the command's output; a failed action changed nothing. What a later phase needs goes " + "in your handoff; a question for another live role goes to its role topic with envoy_publish.";
 function rootArchitectHandoffRefusal(operation) {
   return `${operation} is not available to a root architect session; a root architect reads handoffs with \`legion handoff read [--phase <phase>]\` from bash`;
 }

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

@@ -27,6 +27,10 @@ parent's children and the issue's `Components:` line show where the rest of that
 
 ## What to do with what you find
 
+Filing an issue or opening an ask also searches for you: the result's `advice.suggestions` names
+likely duplicates or a decision that may already settle it. Treat a hit there the same as one you
+found yourself.
+
 - **The work is already tracked: extend that issue.** Put the finding on it (a comment, a message,
   or an edit to its spec) instead of filing another. File a new issue only when no hit covers the
   work, and cite the nearest one you ruled out (`dispatch://KEY`).

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

@@ -250,8 +250,10 @@ The daemon keeps this order from its fixed table; you start none of its steps:
 
 1. tester green and review cycles complete;
 2. on a clean review, the reviewer approves the head by SHA, and the daemon moves the issue to
-   `retro`. No role pushes a `.legion/` deletion: the approved head still carries `.legion/`, and
-   the operator removes it from the default branch in a follow-up pull request after the merge;
+   `retro`. No role pushes a `.legion/` deletion: the approved head still carries `.legion/`. The
+   daemon strips whatever `.legion/` main still carries from the next issue's branch before any of
+   its roles start, so that tree's own merge carries the removal onto the default branch; no
+   operator sweep follows;
 3. retro commits its learnings under `docs/solutions/` on top of the approved head; that
    commit does not void the approval and never returns the tree to the tester or reviewer;
 4. the merger verifies the current head is the reviewer-approved head plus only commits that

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

@@ -19,7 +19,9 @@ retrospective's durable output.
 
 1. Tester green and all code-review cycles finish.
 2. The reviewer approves the head. It still carries `.legion/`: no role removes it before the
-   merge, and the operator removes it from the default branch after the merge.
+   merge. The daemon strips whatever `.legion/` main still carries from the next issue's branch
+   before any of its roles start, so that tree's own merge carries the removal onto the default
+   branch; no operator sweep follows.
 3. Run this retro: commit durable learnings to `docs/solutions/` and post the retro message on
    the Dispatch issue.
    Retro writes **no `.legion` file**, so it never changes the approved head's handoffs.

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

@@ -397,9 +397,11 @@ pushes nothing.
 
 Do not report phase completion until the write, existence check, handoff commit, and push
 succeed. This is the committed copy the next phase reads after revival. No phase removes
-`.legion/`: the reviewer approves a head that carries it, and the operator removes it from the
-default branch after the merge. Retro and the post-merge production check write no
-`.legion/<phase>.json`, commit no handoff, and report with `handoff_complete` alone (below).
+`.legion/`: the reviewer approves a head that carries it. The daemon strips any `.legion/` still on
+main from the next issue's branch before any of its roles start (dispatch://LEGION-565), so that
+tree's own merge carries the removal onto the default branch; no operator sweep follows. Retro and
+the post-merge production check write no `.legion/<phase>.json`, commit no handoff, and report with
+`handoff_complete` alone (below).
 
 ## Completion: report to the architect, then stay
 

package/dist/skills/legion-worker/references/merge-gate.md

@@ -6,11 +6,13 @@ path it cites is in sjawhar/legion.
 
 The order, in full: the tester's evidence green → the reviewer's approval of the head →
 retro → the merger's READY → the human merge → the implementer's production check. No role
-removes `.legion/` before the merge: the approved head carries it, and the operator removes it
-from the default branch after the merge. After the approval, only retro's `docs/solutions/`
-commit leaves it standing on its own (*Retro*, below). A conflict-forced merge goes back to the
-reviewer for a confirmation or a new round, as the fingerprint decides (*The reviewer*, below,
-and `skill://legion-worker/references/conflicts-and-rewrites.md`), and any other change voids it.
+removes `.legion/` before the merge: the approved head carries it. The daemon strips whatever
+`.legion/` main still carries from the next issue's branch before any of its roles start
+(dispatch://LEGION-565), so that tree's own merge carries the removal onto the default branch; no
+operator sweep follows. After the approval, only retro's `docs/solutions/` commit leaves it
+standing on its own (*Retro*, below). A conflict-forced merge goes back to the reviewer for a
+confirmation or a new round, as the fingerprint decides (*The reviewer*, below, and
+`skill://legion-worker/references/conflicts-and-rewrites.md`), and any other change voids it.
 
 ## The reviewer
 

package/package.json

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