@sjawhar/opencode-legion-envoy 5.9.3 → 5.10.1

package/dist/src/server.js

@@ -13564,6 +13564,7 @@ var DEFAULT_ISSUE_PAGE_LIMIT = 50;
 var ASK_TURNS = ["human", "agent"];
 var DELIVERY_CAPABILITIES = ["aside", "btw", "steer"];
 var DELIVERY_DUPLICATE_WINDOW_MS = 72 * 60 * 60 * 1000;
+var SEARCH_DEGRADED_EMBEDDER_UNAVAILABLE = "embedder_unavailable";
 var DispatchEventSchema = exports_external.object({
   issue_key: exports_external.string().nullable(),
   artifact_id: exports_external.string().nullish(),
@@ -15736,14 +15737,20 @@ function searchAnswer(search, query, offset, configUrl) {
   const lines = results.map((result) => searchResultLine(result, configUrl));
   const noun = count === 1 ? "result" : "results";
   const noResults = `No results for "${query}".`;
+  const degraded = search.degraded === SEARCH_DEGRADED_EMBEDDER_UNAVAILABLE ? "Searched by keyword only: meaning search was unavailable for this request." : undefined;
   if (typeof search.total !== "number") {
     if (offset !== undefined && offset > 0) {
       throw new Error(`Dispatch answered without a total: it predates search paging and ignored offset ${offset}, so this would be its first page again.`);
     }
     return {
-      text: count === 0 ? noResults : [`${count} ${noun} for "${query}" (${search.took_ms} ms)`, ...lines].join(`
+      text: count === 0 ? [noResults, ...degraded === undefined ? [] : [degraded]].join(`
+`) : [
+        `${count} ${noun} for "${query}" (${search.took_ms} ms)`,
+        ...degraded === undefined ? [] : [degraded],
+        ...lines
+      ].join(`
 `),
-      details: { query, results }
+      details: { query, results, ...degraded === undefined ? {} : { degraded: search.degraded } }
     };
   }
   const { total, reachable, offset: pageOffset } = search;
@@ -15755,12 +15762,15 @@ function searchAnswer(search, query, offset, configUrl) {
     total,
     reachable,
     offset: pageOffset,
-    limit: search.limit
+    limit: search.limit,
+    ...degraded === undefined ? {} : { degraded: search.degraded }
   };
   if (count === 0) {
     return {
-      text: total === 0 ? noResults : [
+      text: total === 0 ? [noResults, ...degraded === undefined ? [] : [degraded]].join(`
+`) : [
         `No results for "${query}" at offset ${pageOffset}: it matches ${total}, and the pages reach the first ${reachable}.`,
+        ...degraded === undefined ? [] : [degraded],
         ...cut === undefined ? [] : [cut]
       ].join(`
 `),
@@ -15771,6 +15781,7 @@ function searchAnswer(search, query, offset, configUrl) {
   return {
     text: [
       `${count} ${noun} for "${query}" (${showing}${search.took_ms} ms)`,
+      ...degraded === undefined ? [] : [degraded],
       ...cut === undefined ? [] : [cut],
       ...lines,
       ...end < reachable ? [`Next page: offset ${end}.`] : []

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "5.9.3",
+  "version": "5.10.1",
   "license": "Apache-2.0",
   "type": "module",
   "main": "dist/src/server.js",

package/skills/dispatch/SKILL.md

@@ -164,14 +164,14 @@ do with each hit. What it leaves out:
 dispatch_search({ query, project?, limit?, offset? })
 ```
 Websearch syntax applies: `"merge queue"`, `-daemon`, `OR`. Issues, documents, asks, comments, and messages rank separately; the
-merged page orders each kind's best in turn — issue, document, ask, comment, message — and a bare issue key ranks first. A page
-holds `limit` hits (20 default, 50 max); the first line gives the total (`showing 1-20 of 312`); see
-[Search paging](skill://dispatch/references/issues.md#search-paging) for more. Queries over 1,000 characters are refused: use the
-few words `skill://dispatch-first` names, never a pasted passage. Issue hits start with the issue key; document hits start with
-`dispatch://PROJECT/artifact/<slug>`, then the link. Cite the hit (`dispatch://KEY` or the doc ref) or say "no prior issue".
-
-`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.
+merged page orders each kind's best in turn — issue, document, ask, comment, message — and a bare issue key ranks first. Each
+kind's list also merges a query embedding's meaning match with keyword hits (LEGION-549): a paraphrase with no shared word can
+still match; without an embedder, it says so and ranks by keyword alone. A page holds `limit` hits (20 default, 50 max); the first
+line gives the total (`showing 1-20 of 312`); see [Search paging](skill://dispatch/references/issues.md#search-paging) for more.
+Queries over 1,000 characters are refused: use the few words `skill://dispatch-first` names, never a pasted passage. Issue hits
+start with the issue key; document hits start with `dispatch://PROJECT/artifact/<slug>`, then the link. Cite the hit (`dispatch://KEY` or the doc ref) or say "no prior issue".
+
+`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 with the

package/skills/legion-oracle/SKILL.md

@@ -50,6 +50,11 @@ judgment across many files). Do not name any other agent.
 | 3. Framework docs | `read` the library's documentation URL | [library] [topic] |
 | 4. External practices | `web_search`, then `read` the primary source | Current best practices for [topic] |
 
+Before relying on a step 1 hit, also search for `supersedes: docs/solutions/<its-path>` and
+`Extends docs/solutions/<its-path>` naming it: a newer file may extend or supersede what you
+found, and Legion runs no pass that reconciles these links, so following them is the only way to
+know the hit is still current.
+
 ## Output
 
 **Found:** Answer with source (file:line or URL)

package/skills/legion-retro/SKILL.md

@@ -67,13 +67,26 @@ Do not start retro before step 2 or skip it because the change seems mechanical;
 ## Durable outputs
 
 Write the integrated learning as one or more discoverable documents under `docs/solutions/`.
-Organize by reusable topic rather than by pull request. Search `docs/solutions/` for the topic
-first: when a document already states the rule, update it in place (sharpen the rule, add this
-issue and pull request to `related_issues`) rather than writing a sibling; when the new learning
-replaces an old document, set the old one's `status: superseded` and add
-`superseded_by: docs/solutions/<path>.md`. Open each document with the rule in a few imperative
-lines; the incident that taught it goes in an Evidence section below, never in the rule. Each
-document uses this front matter:
+Organize by reusable topic rather than by pull request, but never edit a document you did not
+write this retro — not its frontmatter, not its body. Two trees' retros can land within the same
+hour, and an in-place edit (another `related_issues` entry, a sharpened sentence, a `status`
+flip) conflicts with any other tree's edit to the same lines of the same file. Search
+`docs/solutions/` for the topic first; before relying on a hit, also search for
+`supersedes: docs/solutions/<its-path>` and `Extends docs/solutions/<its-path>` naming it —
+Legion runs no pass that reconciles these links, so a newer file that extends or supersedes the
+one you found is discoverable only by following them. Then write a new file of your own, named
+`docs/solutions/<category>/<slug>-<LEGION_ISSUE>.md` so two trees never choose the same path:
+
+- **A fresh topic:** state the rule in a few imperative lines; the incident goes in an Evidence
+  section below, never in the rule.
+- **A topic an existing document already covers:** underneath its own H1 heading, the first line
+  reads `Extends docs/solutions/<existing-path>.md.`; the rule states only the delta.
+- **A topic an existing document states wrongly:** frontmatter adds
+  `supersedes: docs/solutions/<existing-path>.md`; the first line under the H1 says why. Leave
+  the old file's frontmatter and body untouched: Legion runs no pass that reconciles it, so the
+  `supersedes:` link is the only thing that makes the correction discoverable from the old file.
+
+Each document uses this front matter:
 
 ```yaml
 ---