@sjawhar/opencode-legion-envoy 1.4.1 → 1.5.0

package/dist/src/server.js

@@ -13552,6 +13552,9 @@ function date4(params) {
 // ../../node_modules/.bun/zod@4.3.6/node_modules/zod/v4/classic/external.js
 config(en_default());
 // ../contracts/src/dispatch-api.ts
+function searchOwnerOf(result) {
+  return result.owner ?? { kind: "issue", key: result.issue.key };
+}
 var DispatchEventSchema = object({
   issue_key: string2().nullable(),
   artifact_id: string2().nullish(),
@@ -14898,9 +14901,14 @@ function duplicateCandidates(error) {
   return error.candidates;
 }
 function searchResultLine(result, baseUrl) {
+  const href = new URL(result.href, baseUrl).toString();
+  const owner = searchOwnerOf(result);
+  if (owner.kind === "document") {
+    const reference = `dispatch://${owner.project}/artifact/${owner.slug}`;
+    return `${reference} [document] ${owner.name} - ${result.kind}: ${snippetText(result.snippet)} -> ${href}`;
+  }
   const artifactName = result.artifact ? ` ${result.artifact.name}` : "";
   const label = `${result.issue.key} [${result.issue.status}] ${result.issue.title} - ${result.kind}${artifactName}`;
-  const href = new URL(result.href, baseUrl).toString();
   return `${label}: ${snippetText(result.snippet)} -> ${href}`;
 }
 function askUrgency(args) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "1.4.1",
+  "version": "1.5.0",
   "type": "module",
   "main": "dist/src/server.js",
   "exports": {

package/skills/dispatch/SKILL.md

@@ -29,6 +29,13 @@ vocabulary, and is often on a phone. Write for that person.
 - Before posting, test it: could Sami, reading only this text on his phone, know what he is being
   told or asked? If not, rewrite it. Length is not the problem; density is.
 
+## Agent authentication
+
+Use a personal Dispatch token: a human mints it in Dispatch **Settings → Agent tokens** and supplies
+it to the agent through `dispatch.token` in `~/.config/opencode/envoy.json` or `DISPATCH_TOKEN`.
+The server records the minting human as the owner of that session's writes. `DISPATCH_AGENT_TOKEN`
+is the shared devbox fallback; do not configure it for an individual agent.
+
 ## Writing a spec
 
 A spec has two readers: the human who decides reads the top; the implementer who builds reads the
@@ -78,9 +85,11 @@ Before you create an issue or start a design document, search:
 ```ts
 dispatch_search({ query, project?, limit? })
 ```
-It returns every issue, document, comment, ask, and message that contains the words, with the issue key and a link. Cite the hit you
-build on (`dispatch://KEY` or the document reference), or state "no prior issue" in the spec. Websearch syntax applies: `"merge queue"`,
-`-daemon`, `OR`.
+It returns every issue, document, comment, ask, and message that contains the words. Issue-owned hit lines
+start with the issue key; standalone project-document hit lines start with
+`dispatch://PROJECT/artifact/<slug>`, followed by the absolute link. Cite the hit you build on
+(`dispatch://KEY` or the document reference), or state "no prior issue" in the spec. Websearch syntax applies:
+`"merge queue"`, `-daemon`, `OR`.
 
 `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.