@sjawhar/opencode-legion-envoy 0.41.0 → 0.41.1

package/dist/src/server.js

@@ -13603,15 +13603,22 @@ var AskEditedEventPayloadSchema = object({
   edited_by: object({ kind: string2(), id: string2() }).passthrough()
 });
 var CommentEventPayloadSchema = object({
+  id: string2().optional(),
   artifact_name: string2().optional(),
   body: string2().optional(),
   reply_to: string2().nullish(),
   ask_id: string2().nullish(),
   ask_question: string2().optional(),
   anchor: object({ quote: string2().optional() }).nullish(),
-  suggestion: object({ replace_with: string2().optional() }).nullish()
+  suggestion: object({ replace_with: string2().optional() }).nullish(),
+  author: object({ kind: string2(), id: string2().optional() }).passthrough().optional(),
+  created_at: string2().optional()
+});
+var MessageEventPayloadSchema = object({
+  id: string2().optional(),
+  body: string2().optional(),
+  author: object({ kind: string2(), id: string2().optional() }).passthrough().optional()
 });
-var MessageEventPayloadSchema = object({ body: string2().optional() });
 var ChildStatusEventPayloadSchema = object({
   child_key: string2().optional(),
   from: string2().optional(),
@@ -14901,7 +14908,7 @@ async function resolveOwnerArguments(tool, args, cwd, env, exec) {
     return { args, ref: null, owner: null };
   const refArgument = args.ref;
   const ref = typeof refArgument === "string" ? parseDispatchRef(refArgument) ?? (() => {
-    throw new Error("ref must be a valid dispatch:// reference");
+    throw new Error("ref must be a valid dispatch:// reference such as dispatch://KEY-1, " + "dispatch://KEY-1/ask/<uuid>, dispatch://KEY-1/comment/<uuid>, " + "dispatch://KEY-1/artifact/<slug>, or dispatch://PROJECT/artifact/<slug>");
   })() : null;
   const issueArgument = args.issue;
   const projectArgument = args.project;
@@ -14973,13 +14980,23 @@ async function resolveArtifact(client, owner, artifactReference) {
     if (artifactReference === undefined) {
       throw new Error("artifact is required for a project document");
     }
-    return {
-      owner,
-      artifact: await client.getProjectArtifact(owner.project, artifactReference)
-    };
+    try {
+      return {
+        owner,
+        artifact: await client.getProjectArtifact(owner.project, artifactReference)
+      };
+    } catch (error) {
+      if (!(error instanceof DispatchServiceError) || error.status !== 404)
+        throw error;
+      const artifacts = await client.listProjectArtifacts(owner.project);
+      const artifact = artifacts.find((candidate) => candidate.name === artifactReference);
+      if (!artifact)
+        throw error;
+      return { owner, artifact };
+    }
   }
   const issue = await client.getIssue(owner.issue);
-  const artifact = artifactReference === undefined || artifactReference === "spec" ? issue.artifacts.find((candidate) => candidate.primary || candidate.id === issue.primary_artifact_id) : issue.artifacts.find((candidate) => candidate.id === artifactReference || candidate.slug === artifactReference);
+  const artifact = artifactReference === undefined || artifactReference === "spec" ? issue.artifacts.find((candidate) => candidate.primary || candidate.id === issue.primary_artifact_id) : issue.artifacts.find((candidate) => candidate.id === artifactReference || candidate.slug === artifactReference || candidate.name === artifactReference);
   if (!artifact) {
     throw new Error(`artifact ${artifactReference ?? "spec"} was not found on issue ${issue.key}`);
   }
@@ -15345,8 +15362,9 @@ Open anchored asks/comments: ${marks.join(", ")}`,
       };
       const artifactOwner = documentOwner();
       const result = artifactOwner.kind === "project" ? await client.projectArtifact(artifactOwner.project, artifactInput) : await client.artifact(issue(), artifactInput);
+      const artifactRef = artifactOwner.kind === "project" ? `dispatch://${artifactOwner.project}/artifact/${result.artifact.slug}` : `dispatch://${issue()}/artifact/${result.artifact.slug}`;
       return {
-        text: `Uploaded ${result.artifact.name} as version ${result.version.number}`,
+        text: `Uploaded ${result.artifact.name} as version ${result.version.number} (artifact slug ${result.artifact.slug}; ${artifactRef})`,
         details: artifactOwner.kind === "project" ? {
           ...documentResultDetails(result.artifact),
           version: result.version.number

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -5,8 +5,8 @@ description: "Use when asking Sami a question, updating the spec, commenting on
 
 # Dispatch
 
-Dispatch is your issue's living spec, asks, comments, and artifacts. The transcript is your
-scratch pad. Anything meant for a human goes through a `dispatch_*` tool.
+Dispatch is your issue's or project document's living spec, asks, comments, and artifacts. The
+transcript is your scratch pad. Anything meant for a human goes through a `dispatch_*` tool.
 
 The server enforces high signal: an ask question is at most 800 characters with at most eight
 options; comment and message bodies are at most 2,000 characters; an artifact is at most 25 MiB.
@@ -143,6 +143,7 @@ dispatch_doc_read({ issue?, project?, artifact?, version?, ref? })
 It returns live or versioned markdown with open marks. `issue` with an omitted `artifact`
 reads the issue specification; a project needs `artifact`; and a
 `dispatch://PROJECT/artifact/<slug>` ref supplies both. Then write narrative with:
+
 ```ts
 dispatch_doc_edit({ issue?, project?, artifact, ops, summary? })
 ```
@@ -162,15 +163,22 @@ type EditOp = {
 ```
 
 Target `replace` and `delete` by the document's plain text: inline-code and link text match
-without Markdown syntax, and a table-cell anchor is its cell text. `replace` requires `find` and
-`with`; `delete` requires `find`; `insert` requires `markdown` and exactly one of `after` or
-`before`. An insert anchor is a quote, `"start"`, `"end"`, or `"heading:Title"`. Every insert
-creates a sibling block before or after the quote or heading's enclosing document block; `"start"`
-and `"end"` select the document edges. At a table-cell quote, pipe-table body-row fragments extend
-that table before or after the matched row; omit table header and delimiter rows, and do not exceed
-the table width. Use `replace` for inline continuation. Use zero-based `occurrence` for a repeated
-target. When a decision lands, pass `summary` to name the resulting version. Never paste progress
-into a message.
+without Markdown syntax, and a table-cell anchor is its cell text. Quote code-block contents
+without their Markdown fences. A quote must stay within one textblock; split changes that
+span separate blocks into separate operations.
+
+`replace` requires `find` and `with`; `delete` requires `find`; `insert` requires `markdown`
+and exactly one of `after` or `before`. An insert anchor is a quote, `"start"`, `"end"`, or
+`"heading:Title"`. Ordinary inserts create a sibling block before or after the quote or
+heading's enclosing document block; `"start"` and `"end"` select the document edges.
+
+At a table-cell quote, pipe-table body-row fragments extend that table before or after the
+matched row; omit table header and delimiter rows. Short rows are padded to the table width;
+rows wider than the table are rejected.
+Deleting a cell's quoted text removes that text, not the surrounding row or table.
+Use `replace` for inline continuation. Use zero-based `occurrence` for a repeated target;
+re-read a missing or ambiguous target before retrying. Pass `summary` to name the version
+when recording a decision. Never paste progress into a message.
 
 ## Comments and suggestions
 
@@ -185,7 +193,9 @@ It returns issue or project-document owner details plus `comment` and, for write
 (`reply_to`/`reply_to_ask`) takes no `quote`; it belongs to its parent's anchor. Use `reply_to`
 to continue a comment thread at its root; a reply to a resolved thread reopens it. Use
 `reply_to_ask` to reply directly under a question asked with `dispatch_ask`. The two are
-mutually exclusive. Comments are edited only by their author from the dashboard.
+mutually exclusive. Comments are edited only by their author from the dashboard. A delivered
+`comment.created` event carries the comment `id`; reply to it with
+`dispatch_comment({ reply_to: <id> })`.
 
 Propose an exact replacement instead of describing it:
 
@@ -222,6 +232,7 @@ document; it must not include `artifact`. Exactly one of `path` and `content` is
 inline form sends JSON with `Content-Type: application/json`. It returns issue or
 project-document owner details plus `artifact`, `version`, and its write `topic`. Uploading the
 same `name` creates its next version. Use `content` when the text is already in the call.
+Address an existing artifact by the slug shown in the upload result or by its filename.
 
 ## Messages
 
@@ -321,8 +332,8 @@ dispatch_doc_edit({
   ops: [
     {
       op: "replace",
-      find: "## Delivery\n\nRelease pending.",
-      with: "## Delivery\n\nRelease merged and ready for deployment.",
+      find: "Release pending.",
+      with: "Release merged and ready for deployment.",
     },
   ],
   summary: "Recorded merged release",