@sjawhar/opencode-legion-envoy 3.1.1 → 3.1.3

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.1",
+  "version": "3.1.3",
   "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-controller/SKILL.md

@@ -61,8 +61,8 @@ into a state holder: daemon state and the Dispatch project remain authoritative.
 
 ### Started by the operator
 
-When the daemon cannot open a terminal for you — the TypeScript daemon under `runtime: kubernetes`,
-and the Go daemon under either runtime, since it launches no controller — nobody launched your
+When the daemon cannot open a terminal for you — the Go daemon, under either runtime, since it
+launches no controller — nobody launched your
 pane: the operator ran `legion controller start --config controller.yaml [--daemon-url <url>]` on
 their own machine, and you are that foreground OMP session. The command fetched a fresh controller
 secret from the daemon with the operator's token, wrote it to a 0600 file under `LEGION_STATE_DIR`