@sjawhar/opencode-legion-envoy 7.1.2 → 7.3.0

package/dist/dispatch.js

@@ -13557,6 +13557,7 @@ function serviceSubjectLabel(subject) {
   }
   return subject;
 }
+var MAX_ISSUE_BLOCKERS = 20;
 var ISSUE_TITLE_MAX = 1000;
 var MAX_ISSUE_PAGE_LIMIT = 250;
 var DEFAULT_ISSUE_PAGE_LIMIT = 50;
@@ -14023,6 +14024,7 @@ var dispatchToolSpecs = [
       project: z2.string().describe("Project key for the new issue."),
       title: z2.string({ max: ISSUE_TITLE_MAX }).describe("Concise issue title, at most 1,000 characters."),
       parent: z2.string().describe("Optional parent issue.").optional(),
+      blocked_by: z2.array(z2.string({ min: 1 }), { max: MAX_ISSUE_BLOCKERS }).describe("Issue keys in the same project this issue waits on. Dispatch refuses a dependency cycle.").optional(),
       external: z2.string().describe("Optional external issue reference.").optional(),
       force: z2.boolean().describe("Create even though POSSIBLE_DUPLICATE listed similar issues; pass it only after reading them.").optional(),
       spec: z2.string().describe(`Optional initial primary-document markdown. ${SPEC_WRITING_POINTER}`).optional(),
@@ -14039,7 +14041,7 @@ var dispatchToolSpecs = [
       status: "done",
       reason: "Shipped in owner/repo#7; verified on the production dashboard."
     },
-    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. Closing an issue " + "(status done) requires reason, the note that says why: it is posted on the issue as a " + "message, then the issue closes, because a closed issue refuses messages, comments, and " + "artifacts; reason goes only with status done. 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}`,
+    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, replace the issues it is blocked by, 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. Closing an issue " + "(status done) requires reason, the note that says why: it is posted on the issue as a " + "message, then the issue closes, because a closed issue refuses messages, comments, and " + "artifacts; reason goes only with status done. 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: (z2) => ({
       issue: z2.string().describe(ISSUE_REFERENCE),
       status: z2.enum(ISSUE_STATUSES).describe("New lifecycle status.").optional(),
@@ -14050,15 +14052,16 @@ var dispatchToolSpecs = [
       external_links: z2.array(z2.string({ min: 1 })).describe("URLs to link; merged into the issue's existing external links by URL.").optional(),
       route: z2.string().describe("Route the issue to role:<name> or session:<id>; an empty string clears it.").optional(),
       parent: z2.string().describe("Parent issue key in the same project; an empty string clears the parent.").optional(),
+      blocked_by: z2.array(z2.string({ min: 1 }), { max: MAX_ISSUE_BLOCKERS }).describe("Replacement list of issue keys in the same project this issue waits on; [] clears it. Dispatch refuses a dependency cycle.").optional(),
       components: componentsArgument(z2).optional()
     }),
     validation: {
       check: (value) => {
         const input = value;
         const reasonFits = input.status === "done" ? typeof input.reason === "string" && input.reason.trim() !== "" : input.reason === undefined;
-        return reasonFits && (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);
+        return reasonFits && (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" || Array.isArray(input.blocked_by) || typeof input.components === "object" && input.components !== null);
       },
-      message: "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, or components. " + "status done requires reason, a non-empty note saying why the issue is closing, posted on the issue before it closes because a closed issue refuses messages, comments, and artifacts; reason goes only with status done."
+      message: "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, blocked_by, or components. " + "status done requires reason, a non-empty note saying why the issue is closing, posted on the issue before it closes because a closed issue refuses messages, comments, and artifacts; reason goes only with status done."
     },
     strict: true
   },
@@ -17496,11 +17499,13 @@ async function executeDispatchTool(input) {
       const assignee = optionalString(args, "assignee");
       const components = optionalComponents(args, "components");
       const labels = args.labels;
+      const blockedBy = args.blocked_by;
       try {
         const created = await client.issue({
           project,
           title,
           ...parent === undefined ? {} : { parent },
+          ...Array.isArray(blockedBy) ? { blocked_by: blockedBy } : {},
           ...external2 === undefined ? {} : { external: external2 },
           ...force === undefined ? {} : { force },
           ...spec === undefined ? {} : { spec },
@@ -17558,6 +17563,7 @@ async function executeDispatchTool(input) {
       const components = optionalComponents(args, "components");
       const priority = optionalPriority(args, "priority");
       const labels = Array.isArray(args.labels) ? args.labels : undefined;
+      const blockedBy = Array.isArray(args.blocked_by) ? args.blocked_by : undefined;
       const requestedLinks = Array.isArray(args.external_links) ? [...new Set(args.external_links)] : undefined;
       let before;
       try {
@@ -17591,6 +17597,7 @@ async function executeDispatchTool(input) {
           ...priority === undefined ? {} : { priority },
           ...route === undefined ? {} : { route },
           ...parent === undefined ? {} : { parent: parent === "" ? null : parent },
+          ...blockedBy === undefined ? {} : { blocked_by: blockedBy },
           ...components === undefined ? {} : { components },
           ...requestedLinks === undefined ? {} : { external_links: [...before.external_links, ...newLinks.map((url2) => ({ url: url2 }))] },
           actor
@@ -17618,6 +17625,9 @@ async function executeDispatchTool(input) {
         ],
         ...route === undefined ? [] : [after.route === null ? "route cleared" : `route ${after.route}`],
         ...parent === undefined ? [] : [after.parent === null ? "parent cleared" : `parent -> ${after.parent}`],
+        ...blockedBy === undefined ? [] : [
+          after.blocked_by.length === 0 ? "blocked_by cleared" : `blocked by ${after.blocked_by.join(", ")}`
+        ],
         ...components === undefined ? [] : [componentsChange(components, after.components)]
       ];
       const adviceLines = renderAdvice(input.tool, after.key, after.advice, {

package/dist/src/server.js

@@ -13552,6 +13552,7 @@ function date4(params) {
 // ../../node_modules/.bun/zod@4.3.6/node_modules/zod/v4/classic/external.js
 config(en_default());
 // ../contracts/src/dispatch-api.ts
+var MAX_ISSUE_BLOCKERS = 20;
 var ISSUE_TITLE_MAX = 1000;
 var MAX_ISSUE_PAGE_LIMIT = 250;
 var DEFAULT_ISSUE_PAGE_LIMIT = 50;
@@ -13880,6 +13881,7 @@ var dispatchToolSpecs = [
       project: z2.string().describe("Project key for the new issue."),
       title: z2.string({ max: ISSUE_TITLE_MAX }).describe("Concise issue title, at most 1,000 characters."),
       parent: z2.string().describe("Optional parent issue.").optional(),
+      blocked_by: z2.array(z2.string({ min: 1 }), { max: MAX_ISSUE_BLOCKERS }).describe("Issue keys in the same project this issue waits on. Dispatch refuses a dependency cycle.").optional(),
       external: z2.string().describe("Optional external issue reference.").optional(),
       force: z2.boolean().describe("Create even though POSSIBLE_DUPLICATE listed similar issues; pass it only after reading them.").optional(),
       spec: z2.string().describe(`Optional initial primary-document markdown. ${SPEC_WRITING_POINTER}`).optional(),
@@ -13896,7 +13898,7 @@ var dispatchToolSpecs = [
       status: "done",
       reason: "Shipped in owner/repo#7; verified on the production dashboard."
     },
-    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. Closing an issue " + "(status done) requires reason, the note that says why: it is posted on the issue as a " + "message, then the issue closes, because a closed issue refuses messages, comments, and " + "artifacts; reason goes only with status done. 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}`,
+    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, replace the issues it is blocked by, 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. Closing an issue " + "(status done) requires reason, the note that says why: it is posted on the issue as a " + "message, then the issue closes, because a closed issue refuses messages, comments, and " + "artifacts; reason goes only with status done. 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: (z2) => ({
       issue: z2.string().describe(ISSUE_REFERENCE),
       status: z2.enum(ISSUE_STATUSES).describe("New lifecycle status.").optional(),
@@ -13907,15 +13909,16 @@ var dispatchToolSpecs = [
       external_links: z2.array(z2.string({ min: 1 })).describe("URLs to link; merged into the issue's existing external links by URL.").optional(),
       route: z2.string().describe("Route the issue to role:<name> or session:<id>; an empty string clears it.").optional(),
       parent: z2.string().describe("Parent issue key in the same project; an empty string clears the parent.").optional(),
+      blocked_by: z2.array(z2.string({ min: 1 }), { max: MAX_ISSUE_BLOCKERS }).describe("Replacement list of issue keys in the same project this issue waits on; [] clears it. Dispatch refuses a dependency cycle.").optional(),
       components: componentsArgument(z2).optional()
     }),
     validation: {
       check: (value) => {
         const input = value;
         const reasonFits = input.status === "done" ? typeof input.reason === "string" && input.reason.trim() !== "" : input.reason === undefined;
-        return reasonFits && (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);
+        return reasonFits && (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" || Array.isArray(input.blocked_by) || typeof input.components === "object" && input.components !== null);
       },
-      message: "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, or components. " + "status done requires reason, a non-empty note saying why the issue is closing, posted on the issue before it closes because a closed issue refuses messages, comments, and artifacts; reason goes only with status done."
+      message: "Issue update requires at least one field besides issue: status, title, labels, priority, external_links, route, parent, blocked_by, or components. " + "status done requires reason, a non-empty note saying why the issue is closing, posted on the issue before it closes because a closed issue refuses messages, comments, and artifacts; reason goes only with status done."
     },
     strict: true
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "7.1.2",
+  "version": "7.3.0",
   "license": "Apache-2.0",
   "type": "module",
   "main": "dist/src/server.js",

package/skills/dispatch/references/issues.md

@@ -85,7 +85,7 @@ issues you own as well as the root. An issue left at `triage` while work is unde
 Waiting for the deploy lane is not a status and is never announced.
 
 ```bash
-# PATCH /api/v1/issues/{key} — status, title, labels, priority, external links (merged by URL), route, parent
+# PATCH /api/v1/issues/{key} — status, title, labels, priority, external links (merged by URL), route, parent, blocked_by
 dispatch issue-update --issue PROJ-175 --status testing
 dispatch issue-update --issue PROJ-175 --status done --reason 'Shipped in owner/repo#7; verified on the production dashboard.'
 dispatch issue-update --issue PROJ-175 --priority 1   # 0–3; see Priority is yours to set

package/skills/legion-worker/SKILL.md

@@ -305,11 +305,11 @@ line), the full definition of a proof, what the tester verifies, and the simplif
 - **The merge gate**, in order: the tester's evidence green → the reviewer's approval of the head
   → retro → the merger's READY → the merge → the implementer's production check. On READY's
   acceptance the merger submits the pull request with
-  `gh pr merge <n> -R <owner>/<repo> --auto --squash --match-head-commit <head>`, and the
-  repository's required reviews and checks decide when it lands
+  `gh pr merge <n> -R <owner>/<repo> --auto --squash --match-head-commit <head>`, unless the
+  answer's note begins `MANUAL_MERGE_REQUIRED:`, where a person merges it; the repository's
+  required reviews and checks decide when it lands
   (`skill://legion-worker/references/merge-gate.md`). The reviewer's submissions, retro's commit,
-  the merger's READY and its submission, the implementer's disarming of a withdrawn READY, and the
-  production check follow the same reference.
+  the merger's READY and its submission, and the production check follow the same reference.
 - **No surface reaches the changed path** is a report to the architect, never a reason to
   complete the phase: `skill://legion-worker/references/pr-body.md`.
 
@@ -360,13 +360,13 @@ The daemon reads no handoff file and no branch head; it refuses, before recordin
 
 - `HANDOFF_NOT_NEW` — the commit is the one you reported for your previous phase: write and
   commit this phase's handoff before completing.
-- `READY_HEAD_CARRIES_HANDOFFS`, `READY_HEAD_CONFLICTS` and `READY_CHECKS_NOT_GREEN` — the
-  merger's READY, in `skill://legion-worker/references/merge-gate.md`.
+- each `READY_…` refusal of the merger's READY — named, with its remedy, in the merger's role
+  prompt (`skill://legion-worker/references/merge-gate.md` says how READY is checked).
 - `GITHUB_READ_FAILED` — GitHub's failure, not the head's, reading READY's checks: complete again.
 
 Such a refusal records nothing, so the corrected call at the same commit is applied. The answer
 may carry a `note` (READY published on an already-merged pull request, or a base requiring no
-check).
+check, or the `MANUAL_MERGE_REQUIRED:` note of a pull request a person merges).
 
 Retro's last commit removes `.legion/<issue>/` from the head that merges (`skill://legion-retro`);
 a round after it, such as one a withdrawn READY sends back, writes and commits its own handoff

package/skills/legion-worker/references/merge-gate.md

@@ -1,8 +1,8 @@
 # The merge gate: review, retro, READY, and the production check
 
 Part of `skill://legion-worker`. Read it when you are the reviewer submitting a review or an
-approval, the implementer disarming a withdrawn READY or recording the production check, or the
-merger building READY and submitting the merge. Every path it cites is in sjawhar/legion.
+approval, the implementer recording the production check, or the merger building READY and
+submitting the merge. Every path it cites is in sjawhar/legion.
 
 The order, in full: the tester's evidence green → the reviewer's approval of the head →
 retro → the merger's READY → the merge → the implementer's production check. The approved
@@ -97,45 +97,46 @@ review posted without a completion leaves the issue in reviewing until you finis
 - READY is `handoff_complete` with `ready: true` and the packet as its `summary`; the merger runs
   no pre-flight of its own, and its completion reports the commit the workspace stands on. READY's
   checks run in the daemon, which reads the pull request's head on GitHub and refuses, before
-  recording anything: `READY_HEAD_CARRIES_HANDOFFS` while the head still carries `.legion/<issue>/`
-  (tell the architect, which has you move the issue back to `retro` with `request_backward_move`,
-  so the implementer's retro removes it; a refusal saying GitHub's read of the directory failed is
-  GitHub's failure, not the head's: complete again); `READY_HEAD_CONFLICTS` while the pull
-  request conflicts with its base, named — GitHub can neither merge it nor start pull_request CI
-  for it, so the implementer brings the base into the branch with a forward merge; and
-  `READY_CHECKS_NOT_GREEN` unless every check the base branch requires has succeeded at that head
-  and every workflow its rulesets require has a passing run there — no result for a check, or no
-  run of a workflow, means that head's push skipped CI when it should not have; a check still
-  running means wait; a failed one is a finding. Report the refusal to the architect; never
-  push a commit to make CI run. On success the daemon posts the packet as a `dispatch message` on
-  the issue, publishes it to the project's merge queue role when one is set, and says on the issue
-  when that role has no live holder; the answer's `note` says when READY was published on a pull
-  request a person already merged, whose head can no longer change, or on a base that requires no
-  check, which the packet itself also says.
-- **The merger submits the merge the moment READY is accepted.** In the same turn, before anything
-  else, it runs `gh pr merge <n> -R <owner>/<repo> --auto --squash --match-head-commit <head>` with
-  its pane's plain `gh`: `<n>` the pull request number, `<head>` the full sha of the current head
-  READY named. A repository with a merge queue enqueues the pull request; one without arms
-  auto-merge; one whose rules are already satisfied merges at once. `--match-head-commit` has
-  GitHub refuse the request when the head has moved since READY read it. The repository's required
-  reviews and checks decide when it lands: the merger makes no merge by hand and bypasses no
-  rule. It then tells the architect with `envoy_publish` to its encoded role token what the
-  command answered — enqueued, auto-merge enabled, or merged — and the head. On any READY refusal
-  it submits nothing, since an armed request would merge through the gate the refusal names; a
-  READY the design gate refused is submitted later, on the architect's word, once the gate opens,
-  and that turn runs only `gh`. A `gh pr merge` GitHub refuses is reported to the architect with
-  its message; a person can still merge after READY. The packet's second line records the step,
-  `Merge: submitted on acceptance with gh pr merge <n> -R <owner>/<repo> --auto --squash --match-head-commit <head>`.
-- **A withdrawn READY is disarmed by the implementer.** When READY is withdrawn (the head's CI
-  turned red, or it conflicts with its base, after READY, which sends the issue back to
-  `implementing`), a merge queue drops the pull request on the red check, but auto-merge stays
-  enabled across pushes, and `--match-head-commit` was checked only when it was enabled. So the
-  implementer, at the start of that implementing round, runs
-  `gh pr merge <n> -R <owner>/<repo> --disable-auto` before any push. A pull request still in a
-  merge queue is removed with `gh api graphql -f query='mutation($id:ID!){dequeuePullRequest(input:{id:$id}){mergeQueueEntry{id}}}' -F id=<pull request node id>`
-  (`--disable-auto` dequeues nothing). When nothing is armed — the merger's submission was refused,
-  or a queue already dropped it — the command exits 1 with "Can't disable auto-merge for this pull
-  request.": run it anyway and take that answer as nothing to disarm.
+  recording anything, on each ground the merger's role prompt names in its `Go daemon workflow`
+  part, by its code and with its remedy. That part is the one complete list of READY's refusals.
+  A refusal records nothing; the merger reports it to the architect unless it says to complete
+  again, and never pushes a commit to make CI run. On success the daemon posts the packet as a
+  `dispatch message` on the issue, publishes it to the project's merge queue role when one is set,
+  and says on the issue when that role has no live holder; the answer's `note` says when READY was
+  published on a pull request a person already merged, whose head can no longer change, or on a
+  base that requires no check, which the packet itself also says, or carries the by-hand note of a
+  pull request a person merges.
+- **The merger submits the merge the moment READY is accepted, unless the answer says a person
+  merges it.** In the same turn, before anything else, it runs
+  `gh pr merge <n> -R <owner>/<repo> --auto --squash --match-head-commit <head>` with its pane's
+  plain `gh`: `<n>` the pull request number, `<head>` the full sha of the current head READY named.
+  A repository with a merge queue enqueues the pull request; one without arms auto-merge; one whose
+  rules are already satisfied merges at once. `--match-head-commit` has GitHub refuse the request
+  when the head has moved since READY read it. The repository's required reviews and checks decide
+  when it lands: the merger makes no merge by hand and bypasses no rule. It then tells the
+  architect with `envoy_publish` to its encoded role token what the command answered — enqueued,
+  auto-merge enabled, or merged — and the head. When the answer's `note` begins
+  `MANUAL_MERGE_REQUIRED:` (the pull request touches a path the project's `merge.by_hand` names),
+  READY stands but the merger submits nothing: it tells the architect the note and the head, and a
+  person merges under the repository's rules. The daemon tells that READY with the note at its head
+  and the packet's `Merge:` line replaced, so the issue and the merge queue role are never asked to
+  arm it. On any READY refusal it submits nothing, since an armed request would merge through the
+  gate the refusal names; a READY the design gate refused is submitted later, on the architect's
+  word, once the gate opens, and that turn runs only `gh` and a read of the READY the daemon posted
+  then: a refusal or a posted READY carrying the by-hand note is submitted by nobody. A push that
+  moves the head past a READY the gate holds voids it before then: the architect is told
+  `READY_HEAD_MOVED` and has the merger build a new READY at the new head. A
+  `gh pr merge` GitHub refuses is reported to the architect with its message; a person can still
+  merge after READY. The packet's second line records the step,
+  `Merge: submit on normal acceptance with gh pr merge <n> -R <owner>/<repo> --auto --squash --match-head-commit <head>`.
+- **The daemon disarms a merge no READY covers.** Auto-merge stays enabled across pushes, and
+  `--match-head-commit` is checked only when it is enabled, so the daemon itself disables the pull
+  request's auto-merge and takes it out of a merge queue, as the implement App, on any push or
+  reopen but one landing on an awaiting READY's head, when READY is withdrawn (a push or reopen
+  moved the head past it, its CI turned red, or it conflicts with its base, each of which sends the
+  issue back to `implementing`), when a child is set back to `todo`, and when the issue leaves the
+  workflow. A by-hand READY covers no arm, so whoever arms it is undone. READY waits
+  (`READY_DISARM_PENDING`) until that disarm has finished. No role runs a disarm.
 
 ## After the merge