@sjawhar/opencode-legion-envoy 1.50.0 → 1.52.0

package/dist/src/server.js

@@ -13931,12 +13931,13 @@ var dispatchToolSpecs = [
   {
     name: "dispatch_issue_update",
     example: { issue: "DSP-1", status: "in_progress" },
-    description: "Update an existing issue: move its lifecycle status, retitle it, replace its labels, link a URL " + "(the pull request that delivers it, a run, a document), set its route, set or clear its parent, " + "or attach it to architecture components. Status is one of " + `${ISSUE_STATUSES.join(", ")}; outside Legion, move it yourself as the work advances; inside ` + "Legion the daemon moves it. external_links are " + "merged into the issue's existing links by URL, so linking the pull request you just opened " + "keeps every earlier link. components replaces the issue's own attachment and is allowed on a " + "closed issue. Priority is the human's and is not settable here. At least one " + `field besides issue is required. ${ISSUE_REFERENCE}`,
+    description: "Update an existing issue: move its lifecycle status, retitle it, replace its labels, set " + "its priority, link a URL (the pull request that delivers it, a run, a document), set its " + "route, set or clear its parent, or attach it to architecture components. Status is one of " + `${ISSUE_STATUSES.join(", ")}; outside Legion, move it yourself as the work advances; inside ` + "Legion the daemon moves it. external_links are " + "merged into the issue's existing links by URL, so linking the pull request you just opened " + "keeps every earlier link. components replaces the issue's own attachment. A closed issue " + "takes only rank, components, and a reopening status (any status but done); everything " + "else, priority included, waits for the reopen. " + "priority is yours to set and a human overrides it; rank, the board's own order, is not " + "settable here. At least one " + `field besides issue is required. ${ISSUE_REFERENCE}`,
     arguments: (z) => ({
       issue: z.string().describe(ISSUE_REFERENCE),
       status: z.enum(ISSUE_STATUSES).describe("New lifecycle status.").optional(),
       title: z.string({ min: 1 }).describe("Replacement title.").optional(),
       labels: z.array(z.string({ min: 1, max: 40 }), { max: 20 }).describe("Replacement label set, at most 20 labels of up to 40 characters; replaces every existing label.").optional(),
+      priority: z.number({ int: true, min: 0, max: 3 }).nullable().optional().describe("Coarse priority: 0 is P0 (highest) through 3 is P3 (lowest); null clears it."),
       external_links: z.array(z.string({ min: 1 })).describe("URLs to link; merged into the issue's existing external links by URL.").optional(),
       route: z.string().describe("Route the issue to role:<name> or session:<id>; an empty string clears it.").optional(),
       parent: z.string().describe("Parent issue key in the same project; an empty string clears the parent.").optional(),
@@ -13945,9 +13946,9 @@ var dispatchToolSpecs = [
     validation: {
       check: (value) => {
         const input = value;
-        return typeof input.status === "string" || typeof input.title === "string" || Array.isArray(input.labels) || Array.isArray(input.external_links) || typeof input.route === "string" || typeof input.parent === "string" || typeof input.components === "object" && input.components !== null;
+        return typeof input.status === "string" || typeof input.title === "string" || Array.isArray(input.labels) || typeof input.priority === "number" || input.priority === null || Array.isArray(input.external_links) || typeof input.route === "string" || typeof input.parent === "string" || typeof input.components === "object" && input.components !== null;
       },
-      message: "Issue update requires at least one field besides issue: status, title, labels, external_links, route, parent, or components."
+      message: "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, or components."
     },
     strict: true
   },
@@ -15577,6 +15578,12 @@ function optionalNumber(args, name) {
   const value = args[name];
   return typeof value === "number" ? value : undefined;
 }
+function optionalPriority(args, name) {
+  const value = args[name];
+  if (value === null)
+    return null;
+  return typeof value === "number" ? value : undefined;
+}
 function optionalComponents(args, name) {
   const value = args[name];
   if (typeof value !== "object" || value === null)
@@ -16421,7 +16428,7 @@ async function executeDispatchTool(input) {
       const external = optionalString(args, "external");
       const force = optionalBoolean(args, "force");
       const spec = optionalString(args, "spec");
-      const priority = optionalNumber(args, "priority");
+      const priority = optionalPriority(args, "priority");
       const assignee = optionalString(args, "assignee");
       const components = optionalComponents(args, "components");
       const labels = args.labels;
@@ -16483,6 +16490,7 @@ async function executeDispatchTool(input) {
       const route = optionalString(args, "route");
       const parent = optionalString(args, "parent");
       const components = optionalComponents(args, "components");
+      const priority = optionalPriority(args, "priority");
       const labels = Array.isArray(args.labels) ? args.labels : undefined;
       const requestedLinks = Array.isArray(args.external_links) ? [...new Set(args.external_links)] : undefined;
       let newLinks = [];
@@ -16494,6 +16502,7 @@ async function executeDispatchTool(input) {
           ...status === undefined ? {} : { status },
           ...title === undefined ? {} : { title },
           ...labels === undefined ? {} : { labels },
+          ...priority === undefined ? {} : { priority },
           ...route === undefined ? {} : { route },
           ...parent === undefined ? {} : { parent: parent === "" ? null : parent },
           ...components === undefined ? {} : { components },
@@ -16505,6 +16514,7 @@ async function executeDispatchTool(input) {
           ...status === undefined ? [] : [`status ${before.status} -> ${after.status}`],
           ...title === undefined ? [] : [`title "${after.title}"`],
           ...labels === undefined ? [] : [after.labels.length === 0 ? "labels cleared" : `labels ${after.labels.join(", ")}`],
+          ...priority === undefined ? [] : [after.priority === null ? "priority cleared" : `priority -> P${after.priority}`],
           ...requestedLinks === undefined ? [] : [
             newLinks.length === 0 ? `already linked ${requestedLinks.join(", ")} ${linkCount}` : `linked ${newLinks.join(", ")} ${linkCount}`
           ],

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -154,7 +154,7 @@ Architects create newly tracked child work with:
 ```ts
 dispatch_issue({ project, title, parent?, external?, spec?, force?, labels?: string[], priority?: 0 | 1 | 2 | 3, assignee?: string })
 ```
-`labels` are optional initial labels: Dispatch trims them, preserves their case, and removes case-insensitive duplicates. Set `priority` on creation only when the human's intent makes the bucket clear; otherwise priority remains the human's decision. Set `assignee` (a GitHub login on the sign-in allowlist) only when the human said who owns the work; otherwise the default above applies, so a child inherits its parent's assignee. It returns
+`labels` are optional initial labels: Dispatch trims them, preserves their case, and removes case-insensitive duplicates. `priority` is yours on creation too — see [Priority is yours to set](#priority-is-yours-to-set). Set `assignee` (a GitHub login on the sign-in allowlist) only when the human said who owns the work; otherwise the default above applies, so a child inherits its parent's assignee. It returns
 `details` `{ issue }`; creating an issue does not subscribe you to it (see [Following](#following)). Use `dispatch_issue` only to create an issue; never use it to park a question. When `spec` is supplied,
 follow [Writing a spec](#writing-a-spec).
 
@@ -167,16 +167,19 @@ production-like surface, `needs_review` when its pull request is open and waitin
 queue, `done` when the change has been driven in production (a merge is not `done`). Move child
 issues you own as well as the root. An issue left at `triage` while work is underway is a defect:
 Sami, 2026-09-15, on the roadmap he could not read — "I'm not even sure what their development
-status is." Waiting for the deploy lane is not a status and is never announced. Priority stays the
-human's: set it on creation only when their intent is clear, and change it only on their word.
+status is." Waiting for the deploy lane is not a status and is never announced.
 
 ```ts
-// PATCH /api/v1/issues/{key} — status, title, labels, external_links (merged by URL), route, parent
+// PATCH /api/v1/issues/{key} — status, title, labels, priority, external_links (merged by URL), route, parent
 dispatch_issue_update({ issue: "AGENTC-175", status: "testing" })
+dispatch_issue_update({ issue: "AGENTC-175", priority: 1 }) // 0–3; see Priority is yours to set
 dispatch_issue_update({ issue: "AGENTC-175", external_links: ["https://github.com/owner/repo/pull/7"] })
 dispatch_issue_update({ issue: "AGENTC-175", parent: "AGENTC-170" }) // same-project key; "" clears the parent
 ```
 
+The two clears differ: `priority` clears with `null`, while `parent` and `route` clear with `""`.
+Guessing the other one is a refusal either way.
+
 Link the pull request that delivers the issue in `external_links` when you open it; the issue page
 renders its state and checks from that link. The call is authenticated with the same bearer as every
 other `dispatch_*` tool: a Legion pane reads it from the `DISPATCH_TOKEN_FILE` path the daemon sets on
@@ -185,6 +188,18 @@ the pane; an OMP session outside Legion reads `dispatch.token` from `~/.config/o
 A write to an issue still in `triage` answers once with `… is still in triage …`; move the status
 when work has started.
 
+## Priority is yours to set
+
+Priority is the coarse bucket a backlog is read by: `0` is P0, the highest, through `3`, P3, the
+lowest, and `null` clears it. Sami ruled on 2026-09-24, answering "may agents set issue priority
+(P0–P3), or only propose it for you?" on `dispatch://LEGION/artifact/issue-status-conventions-md`:
+**"Agents may set"**. So set it — on creation, and on a grooming pass over issues that have none —
+and say what you set and why; he overrides anything he disagrees with from the dashboard. A closed
+issue takes only `rank`, `components`, and a reopening `status` (any status but `done`);
+everything else, `priority` included, waits for the reopen (`409 ISSUE_CLOSED`). So reopen it
+first, then set the priority — the two cannot go in one call. `rank` itself is not a tool field:
+reorder it the way [Issue reads](#your-owner) describes, through `PATCH /api/v1/issues/{key}`.
+
 ## Search first
 
 Before you create an issue or start a design document, search: