@sjawhar/opencode-legion-envoy 3.1.0 → 3.1.2

package/dist/src/server.js

@@ -14032,7 +14032,7 @@ var dispatchToolSpecs = [
       ask: "01234567-0000-4000-8000-000000000001",
       question: "Ship the revised plan?"
     },
-    description: "Edit an open question in place. Use it to correct or refine the same decision; retract the " + "old ask and open a new one when the decision itself changes. Previous text remains in the " + "event log. Only the asking session can edit it; answered or resolved asks cannot be edited. " + "An ask that lives as an `ask` block in a document is written in the document too, changing " + "only the fields you name - pass urgency alone and the question's wording, formatting, links " + "and comment anchors are untouched - so the edit writes a document version and closes a " + "spec's design gate until that version is " + 'approved; an option label containing ": " and a question with a line beginning ":::" are ' + "refused, naming the field, because the block cannot carry them unchanged.",
+    description: "Edit an open question in place. Use it to correct or refine the same decision; retract the " + "old ask and open a new one when the decision itself changes. Previous text remains in the " + "event log. Only the asking session can edit it; answered or resolved asks cannot be edited. " + "An ask that lives as an `ask` block in a document is written in the document too, changing " + "only the fields you name - pass urgency alone and the question's wording, formatting, links " + "and comment anchors are untouched - so the edit writes a document version and closes a " + "spec's design gate until that version is " + "approved; text the block cannot carry back unchanged is refused, naming the field - an " + 'option label containing ": ", the separator between a label and its description, is one ' + "example.",
     arguments: (z2) => ({
       ask: z2.string().describe("Ask id (uuid); an 8+ hex prefix unique among this session's own open asks works too."),
       question: z2.string({ max: ASK_QUESTION_MAX }).describe(`Replacement decision question, at most ${ASK_QUESTION_MAX} characters.`).optional(),

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -452,8 +452,8 @@ is rewritten, so anchors inside the text you replaced move as they would for any
 writes a new version, which on a spec awaiting approval closes the design gate until the new version is approved. Editing the block
 with `dispatch_doc_edit` works too and is the way to change anything else about it, including adding formatting to a question.
 Re-sending a field unchanged rewrites nothing, so retrying the whole ask is safe.
-Two shapes the block cannot carry are refused outright, naming the field and writing nothing: an option label containing `": "`,
-which is what separates a label from its description, and a question with a line beginning `:::`. Blank lines separate paragraphs;
+Text the block cannot carry back unchanged is refused outright, naming the field and writing nothing - an option label containing
+`": "`, the separator between a label and its description, is one example of text that cannot survive the round trip. Blank lines separate paragraphs;
 a single newline is kept as a line break.
 
 An ask stays open until a human answers, unless its question no longer needs that answer. Retract a moot or superseded question, or

package/skills/legion-worker/SKILL.md

@@ -603,6 +603,28 @@ This publishes your phase's completion to the architect's role and clears the da
 record of this issue's active phase. Do not add pipeline labels, run a controller loop, or
 invent a different completion protocol — this is the whole contract.
 
+**A refused completion is information, not a retry loop.** The daemon attributes your report to
+the run whose task you took, and answers with what it found. What each answer carries, and what to
+do:
+
+- `HANDOFF_STALE_GENERATION` — names the issue, the run it is on, and the run your completion
+  reported. The issue has moved to a newer run since your task was given, so the work you just
+  reported belongs to a run that is over. Nothing you can repeat changes that: stop, push nothing
+  further, and tell the architect what you completed and that its run has been superseded. A task
+  for the current run arrives in this same session if the phase still needs you.
+- `HANDOFF_NOT_CURRENT_PHASE` — names your role, the issue, and the phase it is in now. The issue
+  has left your phase; report to the architect rather than completing again.
+- `HANDOFF_NO_RUN` — names neither: it says this claim has taken no task, so the daemon cannot
+  tell which run you are reporting. Your pane is completing outside any assignment. Say so to the
+  architect; do not re-run the phase.
+- `HANDOFF_ALREADY_RECORDED` — names your role, the phase, the review round and the commit. This
+  exact call was received before, and its first answer stands — accepted, or one of the refusals
+  above. Sending it again changes nothing; if you did not see that first answer, tell the
+  architect so and quote this one.
+
+Quote the answer verbatim in what you tell the architect: with the run and phase it names, the
+difference between "my work is lost" and "my work belongs to the previous run" is visible.
+
 **Stay in this session afterward.** Your process does not exit when your phase completes;
 it goes idle in its pane, and after `worker_idle_retire_seconds` (default 600 s) idle with no
 active phase the daemon retires it — your next assignment resumes this same session from its