@sjawhar/opencode-legion-envoy 0.24.0 → 0.26.0

package/README.md

@@ -25,7 +25,8 @@ This package exposes:
 The native `dispatch_*` tools create and read Dispatch issues, asks, comments, documents, and
 artifacts. 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 variables. Each call fills the target issue from
+`DISPATCH_URL` and `DISPATCH_TOKEN` environment variables; `dispatch.enabled: true` without
+`dispatch.serverUrl` targets `http://localhost:8766`. Each call fills the target issue from
 the session working directory, stamps it with the OpenCode session id and title, and stores
 `details.topic` as tool metadata so a successful mutation subscribes to that exact Dispatch topic.
 

package/dist/src/server.js

@@ -13580,6 +13580,8 @@ var CommentEventPayloadSchema = object({
   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()
 });
@@ -13630,14 +13632,15 @@ var dispatchToolSpecs = [
   },
   {
     name: "dispatch_comment",
-    description: "Add review feedback to an issue or document quote. Do not use it for an exact replacement; use " + `dispatch_suggest instead. Body is at most 2,000 characters. ${ISSUE_REFERENCE}`,
+    description: "Add review feedback to an issue or 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. ${ISSUE_REFERENCE}`,
     arguments: (z) => ({
       issue: z.string().describe(ISSUE_REFERENCE),
       artifact: z.string().describe("Artifact slug or id required when quote is given.").optional(),
       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("Optional comment id to reply to.").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()
     })
   },
   {
@@ -13948,25 +13951,10 @@ var LegionDaemonApi = {
     request: architectCapability.extend({ issue: nonEmptyString, comment: string2().optional() }),
     response: object({})
   },
-  SpawnToken: {
-    request: architectCapability.extend({ issue: nonEmptyString, role: legionRole }),
-    response: object({ spawnToken: nonEmptyString })
-  },
   ProvisioningCredential: {
     request: architectCapability.extend({ issue: nonEmptyString }),
     response: object({ token: nonEmptyString })
   },
-  RoleBacking: {
-    request: strictObject({
-      tree: nonEmptyString,
-      issue: nonEmptyString,
-      role: legionRole,
-      sessionId: nonEmptyString,
-      agentId: nonEmptyString,
-      spawnToken: nonEmptyString
-    }),
-    response: object({})
-  },
   WorkerStarted: {
     request: strictObject({
       tree: nonEmptyString,
@@ -14013,20 +14001,6 @@ var LegionDaemonApi = {
       roleToken: nonEmptyString
     })
   },
-  Phase: {
-    request: strictObject({
-      tree: nonEmptyString,
-      issue: nonEmptyString,
-      phase: nonEmptyString,
-      sessionId: nonEmptyString,
-      spawnToken: nonEmptyString
-    }),
-    response: object({
-      secret: nonEmptyString,
-      gitName: nonEmptyString,
-      gitEmail: nonEmptyString
-    })
-  },
   WorkerSession: {
     request: strictObject({
       sessionId: nonEmptyString,
@@ -14668,8 +14642,12 @@ function childrenSummary(issue) {
   ].join(`
 `);
 }
-function askSummary(ask) {
+function askSummary({ ask, replies }) {
   const answer = ask.answer;
+  const chain = replies.flatMap((reply) => [
+    `${reply.id} \xB7 ${reply.author.kind} ${reply.author.id}`,
+    `Body: ${reply.body}`
+  ]);
   return [
     `Question: ${ask.question}`,
     "Options:",
@@ -14680,7 +14658,9 @@ function askSummary(ask) {
       `- By: ${answer.user}`,
       `- Selected: ${answer.selected.length === 0 ? "none" : answer.selected.join(", ")}`,
       ...answer.text === null ? [] : [`- Text: ${answer.text}`]
-    ]
+    ],
+    "Replies:",
+    ...chain.length === 0 ? ["- none"] : chain
   ].join(`
 `);
 }
@@ -14779,10 +14759,15 @@ async function executeDispatchTool(input) {
       const resolved = artifactReference ? await resolveArtifact(client, issue(), artifactReference) : undefined;
       const anchored = resolved ? anchor(resolved.artifact, args) : undefined;
       const replyTo = optionalString(args, "reply_to");
+      const replyToAsk = optionalString(args, "reply_to_ask");
+      if (replyTo !== undefined && replyToAsk !== undefined) {
+        throw new Error("reply_to and reply_to_ask cannot both be set");
+      }
       const comment = await client.comment(issue(), {
         body: stringArg(args, "body"),
         ...anchored === undefined ? {} : { anchor: anchored },
         ...replyTo === undefined ? {} : { reply_to: replyTo },
+        ...replyToAsk === undefined ? {} : { ask_id: replyToAsk },
         actor
       });
       return {
@@ -14891,10 +14876,13 @@ Open anchored asks/comments: ${marks.join(", ")}`,
     }
     case "dispatch_read": {
       if (issueArguments.ref?.kind === "ask") {
-        const ask = await client.getAsk(issueArguments.ref.id);
+        const askRead = await client.getAsk(issueArguments.ref.id);
         return {
-          text: askSummary(ask),
-          details: { issue: ask.issue_key, topic: dispatchIssueSubject(ask.issue_key, ">") }
+          text: askSummary(askRead),
+          details: {
+            issue: askRead.ask.issue_key,
+            topic: dispatchIssueSubject(askRead.ask.issue_key, ">")
+          }
         };
       }
       if (issueArguments.ref?.kind === "comment") {

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -46,6 +46,12 @@ Anchor a document question with `anchor: { artifact, quote, occurrence? }`; `occ
 zero-based and selects a repeated quote. An anchor whose quote disappears becomes orphaned but
 remains readable against its original document version. An ask stays open until a human answers;
 you cannot withdraw it. Ask once and well. The host steers you when a human answers.
+
+An ask is a thread, not a dead end: a human can reply to it before or after answering, and you
+(the asker) can reply too — e.g. acknowledging a clarifying question, or following up after the
+answer. Use `reply_to_ask` on `dispatch_comment` to reply under your own ask; it is mutually
+exclusive with `reply_to`.
+
 ## The spec is where narrative goes
 
 Read the current document before changing it:
@@ -85,11 +91,12 @@ message.
 Add feedback with:
 
 ```ts
-dispatch_comment({ issue, artifact?, quote?, occurrence?, body, reply_to? })
+dispatch_comment({ issue, artifact?, quote?, occurrence?, body, reply_to?, reply_to_ask? })
 ```
 
 It returns `details` `{ issue, topic, comment }`. `quote` requires `artifact`; omit both for a
-floating issue comment. Use `reply_to` to continue a comment.
+floating issue comment. Use `reply_to` to continue a comment thread; use `reply_to_ask` to reply
+directly under a question asked with `dispatch_ask`. The two are mutually exclusive.
 
 Propose an exact replacement instead of describing it:
 
@@ -149,9 +156,9 @@ dispatch_read({ issue?, ref? })
 ```
 
 With an issue ref, it returns the issue summary, open asks, and recent events with `details`
-`{ issue }`. With an ask ref, it returns that ask's question, options, state, and answer. With a
-comment ref, it returns that comment and its quoted reply chain. Use `dispatch_doc_read` for
-document contents.
+`{ issue }`. With an ask ref, it returns that ask's question, options, state, answer, and its
+reply thread. With a comment ref, it returns that comment and its quoted reply chain. Use
+`dispatch_doc_read` for document contents.
 
 ## References
 

package/skills/legion-architect/SKILL.md

@@ -213,7 +213,7 @@ corresponding lifecycle procedure.
 | `pr-closed-unmerged` | Decide from current scope whether to reopen the work, send a fresh implementer, or cancel it with a reason. Delegate the repository action to the responsible phase worker and keep ownership. |
 | `issue-comment` | Interpret the comment in the issue's design context. Answer it, adjust the plan, or relay it via `envoy_publish` to the responsible worker's role token; scope and product decisions remain with you. |
 | `catchup-overseer` | Verify its gates, child counts, and PR verdicts against current artifacts, then resume the applicable numbered lifecycle step. It is a current-state snapshot, not a raw-event replay. For each entry in its `phaseCompletions` (`{issue, role, summary, at}`, phases that completed while you were not live), handle it exactly as a `phase-complete` wake. |
-| `revive-worker` | The extension has revived the backed worker. Do not create a duplicate; message the restored worker via `envoy_publish` to its role token if action is needed and rely on its committed handoff over recollection. |
+| `worker-died` | Payload `{type:"worker-died", issue, role}`. The daemon probed and retried this role's worker through `MAX_LAUNCH_FAILURES` attempts and could not confirm a boot — never a raw-event replay or a silent revive. Reassess the work and `spawn_worker` again for the role (it resumes the same agent via `--resume` if a session file survived) or reassign it if the failure looks environmental, not agent-specific. |
 | `reopened` | Reopen the root lifecycle: inspect the reason and current artifacts, reassess scope and children, and resume at the first applicable numbered step. |
 
 ## Escalation judgment