@sjawhar/opencode-legion-envoy 1.28.0 → 1.29.1

package/README.md

@@ -16,6 +16,7 @@ This package exposes:
 - `dispatch_ask`
 - `dispatch_edit_ask`
 - `dispatch_resolve_ask`
+- `dispatch_resolve_comment`
 - `dispatch_follow`
 - `dispatch_comment`
 - `dispatch_suggest`
@@ -28,7 +29,7 @@ This package exposes:
 - `dispatch_search`
 - `dispatch_open_asks`
 
-The fifteen native `dispatch_*` tools create and read Dispatch issues, asks, comments,
+The sixteen native `dispatch_*` tools create and read Dispatch issues, asks, comments,
 documents, and artifacts, or search all of them. They are present when `dispatch.enabled`
 resolves a server URL and bearer token from envoy.json (`~/.config/opencode/envoy.json`, merged
 with `<repo>/.opencode/envoy.json`) or the `DISPATCH_URL` and `DISPATCH_TOKEN` environment

package/dist/src/server.js

@@ -13849,6 +13849,14 @@ var dispatchToolSpecs = [
       reason: z.string({ min: 1 }).describe("Why the open ask no longer needs a human answer.")
     })
   },
+  {
+    name: "dispatch_resolve_comment",
+    description: "Resolve a review comment thread once it has been addressed - typically your own comment " + "after the document was fixed. Any session or human may resolve any open comment on an " + "open issue or project document; reopening a resolved comment is human-only (the dashboard). " + "Not for asks: use dispatch_resolve_ask.",
+    arguments: (z) => ({
+      comment: z.string().describe("Comment id (uuid), or a dispatch://KEY/comment/<id> or " + "dispatch://PROJECT/artifact/<slug>/comment/<id> reference; a reference accepts an " + "8+ character id prefix that is unique on its owner.")
+    }),
+    strict: true
+  },
   {
     name: "dispatch_follow",
     description: "Follow or unfollow an ask. Every session that opens or replies to an ask follows it: its answer, " + "edits, resolution, and replies reach that session directly. Unfollow to stop; follow to rejoin or " + "to hear an ask you never wrote to. Whole-issue subscription is separate: envoy_subscribe " + "notifications.dispatch.issue.<KEY>.>",
@@ -14902,6 +14910,9 @@ class DispatchClient {
   async getComment(id) {
     return this.#json("GET", ["api", "v1", "comments", id]);
   }
+  async resolveComment(id, actor) {
+    return this.#json("POST", ["api", "v1", "comments", id, "resolve"], { actor });
+  }
   async getComments(issue, artifact) {
     return this.#json("GET", ["api", "v1", "issues", await this.#resolveIssue(issue), "comments"], undefined, artifact ? { artifact } : undefined);
   }
@@ -15186,6 +15197,19 @@ async function askOwnerDetails(client, ask, resolved) {
   const artifact = resolved?.artifact ?? await client.getArtifact(ask.artifact_id);
   return { ...documentResultDetails(artifact), ask: ask.id };
 }
+async function commentOwnerResult(client, comment, artifact) {
+  if (comment.issue_key !== null) {
+    return { label: comment.issue_key, details: { issue: comment.issue_key, comment: comment.id } };
+  }
+  if (comment.artifact_id === undefined || comment.artifact_id === null) {
+    throw new Error("document comment is missing its artifact ID");
+  }
+  const owner = artifact ?? await client.getArtifact(comment.artifact_id);
+  return {
+    label: documentTopic(owner).label,
+    details: { ...documentResultDetails(owner), comment: comment.id }
+  };
+}
 async function followedAskDetails(client, ask, resolved) {
   return { ...await askOwnerDetails(client, ask, resolved), follows: { ask: ask.id } };
 }
@@ -15196,6 +15220,7 @@ var issueFreeTools = {
   dispatch_issue: true,
   dispatch_edit_ask: true,
   dispatch_resolve_ask: true,
+  dispatch_resolve_comment: true,
   dispatch_follow: true,
   dispatch_search: true,
   dispatch_open_asks: true
@@ -15318,6 +15343,7 @@ function parseDispatchRef(ref) {
 }
 var uuidPattern = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
 var askIdProblem = "ask must be a bare ask id or a dispatch://.../ask/<id> reference";
+var commentIdProblem = "comment must be a bare comment id or a dispatch://.../comment/<id> reference";
 var messageIdProblem = "in_reply_to must be a full message id (uuid) or a dispatch://KEY/message/<id> reference";
 function askId(args) {
   const ask = stringArg(args, "ask");
@@ -15373,6 +15399,13 @@ function argumentProblems(tool, args) {
       }
       break;
     }
+    case "dispatch_resolve_comment": {
+      const comment = optionalString(args, "comment");
+      if (comment?.startsWith("dispatch://") && parseDispatchRef(comment)?.kind !== "comment") {
+        problems.push(commentIdProblem);
+      }
+      break;
+    }
     case "dispatch_comment": {
       if (optionalString(args, "quote") !== undefined && optionalString(args, "artifact") === undefined) {
         problems.push("artifact is required when quote is supplied");
@@ -15952,6 +15985,23 @@ async function executeDispatchTool(input) {
         details: await askOwnerDetails(client, ask)
       };
     }
+    case "dispatch_resolve_comment": {
+      const reference = stringArg(args, "comment");
+      const ref = reference.startsWith("dispatch://") ? parseDispatchRef(reference) : null;
+      let id = reference;
+      let document;
+      if (ref?.owner.kind === "issue") {
+        const issueKey = ref.owner.issue;
+        id = await resolveIdPrefix(input.tool, "comment", ref, () => client.getComments(issueKey));
+      } else if (ref !== null) {
+        const artifact = (await resolveArtifact(client, ref.owner, ref.artifact)).artifact;
+        document = artifact;
+        id = await resolveIdPrefix(input.tool, "comment", ref, () => client.getArtifactComments(artifact.id));
+      }
+      const comment = await client.resolveComment(id, actor);
+      const { label, details } = await commentOwnerResult(client, comment, document);
+      return { text: `Resolved comment ${comment.id} on ${label}.`, details };
+    }
     case "dispatch_ask": {
       const anchorArgs = asObject(args.anchor);
       const owner = documentOwner();

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -199,6 +199,8 @@ Use `retracted` when the question is obsolete and `resolved` when you found the
 in its Conversation card and reply thread. Resolution is not an answer: it never records a human decision, and an answered ask cannot be
 resolved. A human may reply to an open or answered ask; so may you, e.g. after finding the answer — use `reply_to_ask` on
 `dispatch_comment` (mutually exclusive with `reply_to`).
+A review comment you opened has its own closer, `dispatch_resolve_comment` — see
+[Comments and suggestions](#comments-and-suggestions).
 
 A human answers or asks back from the same field; a question-shaped free-text answer is offered as a clarification first. A human
 reply while your ask is still open (the delivered `comment.created` carries `ask_state: open`) is a request for clarification, not
@@ -353,7 +355,21 @@ the human needs to act; see [Asking](#asking). Comments are edited only by their
 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:
+Resolve your own review comment once you have addressed it:
+
+```ts
+dispatch_resolve_comment({ comment })
+```
+
+`comment` is the comment id, or a `dispatch://KEY/comment/<id>` or `dispatch://PROJECT/artifact/<slug>/comment/<id>` reference (an
+8+ character id prefix is resolved against the owner's comments). It returns the owner details plus `comment`, and takes no reason —
+say what you did in a `reply_to` first if the thread needs it. The server lets any session or human resolve any open comment, so
+resolve only threads you opened or were asked to close; reopening a resolved thread is human-only (from the dashboard), though your
+reply to it reopens it. Asks are closed with `dispatch_resolve_ask` instead.
+
+An exact replacement for document text is a suggestion (`dispatch_suggest`), never a comment; a
+comment is for a question or a note the human answers in words. A human accepts a suggestion with
+one click and cannot accept a comment, so propose the replacement instead of describing it:
 
 ```ts
 dispatch_suggest({ issue?, project?, artifact, ref?, quote, replace_with, body?, occurrence? })
@@ -384,6 +400,11 @@ with your text. Never do that: the spec is edited in place with `dispatch_doc_ed
 artifact by the slug shown in the upload result or by its filename, and a project document by its artifact id, slug, or filename; the
 slug also arrives on `artifact.created` events.
 
+Documents are CommonMark. A bare `<https://example.com|text>` is a CommonMark autolink and is normalised: the angle brackets are
+dropped and the URL keeps `|text`. A backslash-escaped `\<https://example.com|text>` displays as `<https://example.com|text>` in the
+document but comes back re-escaped (`\<`) from `dispatch_doc_read`. A Slack mrkdwn draft, or any other payload that is not Markdown,
+still belongs inside a fenced code block, where it survives verbatim both ways.
+
 ## Structure over stream
 
 Dispatch is a structured workspace, never a message stream (Sami, 2026-09-13, verbatim: "strange