@sjawhar/opencode-legion-envoy 1.13.0 → 1.14.0

package/dist/src/server.js

@@ -13594,6 +13594,11 @@ var askEventPayloadFields = {
   question: string2().optional(),
   options: array(object({ label: string2().optional() })).nullish(),
   answer: object({ selected: array(string2()).nullish(), text: string2().nullish() }).nullish(),
+  anchor: object({
+    quote: string2().optional(),
+    mark_id: string2().optional(),
+    block_id: string2().nullable().optional()
+  }).passthrough().nullish(),
   resolution: object({
     kind: _enum2(["retracted", "resolved"]).optional(),
     reason: string2().optional(),
@@ -13621,12 +13626,14 @@ var AskEditedEventPayloadSchema = object({
 var CommentEventPayloadSchema = object({
   id: string2().optional(),
   artifact_name: string2().optional(),
+  project_key: string2().optional(),
+  artifact_slug: string2().optional(),
   body: string2().optional(),
   reply_to: string2().nullish(),
   ask_id: string2().nullish(),
   ask_question: string2().optional(),
   ask_state: _enum2(["open", "answered", "resolved"]).optional(),
-  anchor: object({ quote: string2().optional() }).nullish(),
+  anchor: object({ block_id: string2().nullable().optional(), quote: string2().optional() }).nullish(),
   suggestion: object({ replace_with: string2().optional() }).nullish(),
   author: object({ kind: string2(), id: string2() }).optional(),
   created_at: string2().optional()
@@ -13758,7 +13765,7 @@ var dispatchToolSpecs = [
   },
   {
     name: "dispatch_ask",
-    description: "Open a durable, answerable decision or human to-do on an issue or project document. Do not use it for a status update or discussion; " + "use dispatch_message instead. Use kind: action for a to-do a human must complete; it has fixed Done / Can't answers. " + "Anchor a document question, thread reply_to/reply_to_ask, or cite a dispatch:// " + `reference \u2014 it must be answerable from its own text and anchor alone, never "see above". Question is at most 800 ` + `characters and has at most 8 options. ${OWNER_REFERENCE}`,
+    description: "Open a durable, answerable decision or human to-do on an issue or project document. Do not use it for a status update or discussion; " + "use dispatch_message instead. Use kind: action for a to-do a human must complete; it has fixed Done / Can't answers. " + "Anchor a document question, thread reply_to/reply_to_ask, or cite a dispatch:// " + 'reference \u2014 it must be answerable from its own text and anchor alone, never "see above". A quote anchor is pinned to its block. Question is at most 800 ' + `characters and has at most 8 options. ${OWNER_REFERENCE}`,
     arguments: (z) => ({
       issue: z.string().describe(ISSUE_REFERENCE).optional(),
       project: z.string().describe("Project key owning the document.").optional(),
@@ -13812,7 +13819,7 @@ var dispatchToolSpecs = [
   },
   {
     name: "dispatch_comment",
-    description: "Add review feedback to an issue or project document quote, or reply to a question asked with dispatch_ask. " + "Do not use it for an exact replacement; use " + `dispatch_suggest instead. Body is at most 2,000 characters. ${OWNER_REFERENCE}`,
+    description: "Add review feedback to an issue or project document quote, or reply to a question asked with dispatch_ask. " + "Do not use it for an exact replacement; use " + `dispatch_suggest instead. A quote anchor is pinned to its block. Body is at most 2,000 characters. ${OWNER_REFERENCE}`,
     arguments: (z) => ({
       issue: z.string().describe(ISSUE_REFERENCE).optional(),
       project: z.string().describe("Project key owning the document.").optional(),
@@ -13821,7 +13828,7 @@ var dispatchToolSpecs = [
       quote: z.string().describe("Optional exact quoted document text.").optional(),
       occurrence: z.number({ int: true, min: 0 }).describe("Optional zero-based occurrence of quote.").optional(),
       body: z.string({ max: 2000 }).describe("Review comment, at most 2,000 characters."),
-      reply_to: z.string().describe("Optional comment id to reply to.").optional(),
+      reply_to: z.string().describe("Full id of a comment to reply to; replying to any comment in a thread continues that " + "thread (an ask's clarification thread included).").optional(),
       reply_to_ask: z.string().describe("Optional ask id to reply to, threading this comment under that question. Mutually " + "exclusive with reply_to.").optional()
     }),
     validation: documentOwnerValidation(true)

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -127,8 +127,10 @@ recommendation and its reason last, in `question`. Never put file paths, line nu
 numbers, document versions, or role tokens in the question; if the human needs that detail, anchor
 the ask to the document passage instead. Apply the phone test from "Writing for the human" before
 posting. Anchor a document question with `anchor: { artifact, quote, occurrence? }`; `occurrence`
-is zero-based and selects a repeated quote, and an anchor whose quote later disappears becomes
-orphaned but stays readable against its original document version.
+is zero-based and selects a repeated quote. A quote anchor is pinned to its lowest complete
+containing block while retaining its quote as display text, so rewording the passage keeps it
+attached; a quote spanning top-level blocks, and existing anchors without a block, stay readable
+against their original document version if their quote disappears.
 
 An ask must be answerable from its own text and its anchor alone. Anchor a question about a document passage with `anchor`; thread one
 about a comment with `reply_to`; thread a follow-up on your own ask with `reply_to_ask`; cite anything else with a `dispatch://`
@@ -179,10 +181,11 @@ in its Conversation card and reply thread. Resolution is not an answer: it never
 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 human reply while your ask is still open (the delivered `comment.created` carries `ask_state: open`) is a request for
-clarification, not an answer: the human did not understand the question or needs more before choosing. The ask now waits on you
-in their Inbox. Answer in the same thread with `dispatch_comment({ reply_to_ask })`, or reword the question itself with
-`dispatch_edit_ask` when the wording was the problem; either puts the ask back in front of them. Do not open a second ask.
+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
+an answer: the human did not understand the question or needs more before choosing. The ask now waits on you in their Inbox. Answer
+in the same thread with `dispatch_comment({ reply_to_ask })`, or reword the question itself with `dispatch_edit_ask` when the wording
+was the problem; either puts the ask back in front of them. Do not open a second ask.
 
 ## Approval of a spec
 
@@ -289,9 +292,10 @@ dispatch_comment({ issue?, project?, artifact?, ref?, quote?, occurrence?, body,
 
 It returns issue or project-document owner details plus `comment` and, for writes, `topic`.
 `ref` names the owner (an issue or project-document reference) in place of `issue`/`project`.
-`quote` requires `artifact`; omit both for a floating issue comment. A reply (`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
+`quote` requires `artifact`; its anchor is pinned to the containing block while retaining the quote
+for display. Omit both for a floating issue comment. A reply (`reply_to`/`reply_to_ask`) takes no
+`quote`; it belongs to its parent's anchor. Reply to any comment in a thread; the server keeps
+threads flat. A reply to a resolved thread reopens it. Use `reply_to_ask` to reply directly under a
 question asked with `dispatch_ask`. 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> })`.