@sjawhar/opencode-legion-envoy 1.20.2 → 1.21.0

package/dist/src/server.js

@@ -13649,7 +13649,7 @@ var MessageEventPayloadSchema = object({
 });
 var DispatchTargetedMessagePayloadSchema = MessageEventPayloadSchema.extend({
   id: string2(),
-  issue_key: string2(),
+  issue_key: string2().nullable(),
   author: object({ kind: string2(), id: string2() }),
   body: string2(),
   target: string2(),
@@ -13662,6 +13662,7 @@ var MessageDeliveryEventPayloadSchema = object({
   attempt: number2().int().positive().optional(),
   delivery: _enum2(["btw", "aside", "steer"]).optional(),
   session_id: string2().optional(),
+  target: string2().optional(),
   title: string2().optional(),
   state: _enum2(["sent", "failed"]).optional(),
   error: string2().optional()
@@ -15634,17 +15635,18 @@ async function executeDispatchTool(input) {
     }
     case "dispatch_message": {
       const inReplyTo = messageInReplyTo(args);
-      const message = await client.message(issue(), {
+      const issueKey = issue();
+      const message = await client.message(issueKey, {
         body: stringArg(args, "body"),
         ...inReplyTo === undefined ? {} : { in_reply_to: inReplyTo },
         actor
       });
-      const messageRef = `dispatch://${message.issue_key}/message/${message.id}`;
+      const messageRef = `dispatch://${issueKey}/message/${message.id}`;
       return {
         text: `Posted message ${message.id} (${messageRef})`,
         details: {
-          issue: message.issue_key,
-          topic: dispatchIssueSubject(message.issue_key, ">"),
+          issue: issueKey,
+          topic: dispatchIssueSubject(issueKey, ">"),
           message: message.id
         }
       };

package/package.json

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

package/skills/legion-retro/SKILL.md

@@ -45,7 +45,7 @@ before step 3. The design gate is not a substitute for review and retro.
 
 1. Re-read the issue, its acceptance criteria, the PR, test evidence, and review evidence.
    Confirm the PR carries both proofs: the implementer's own `E2E (implementer)` line and the tester's `E2E (tester)` line,
-   each naming a production-like surface (a scratch daemon, a smoke rig, a sandbox repository, a devN
+   each naming a production-like surface (the daemon's test harness (`packages/daemon/src/daemon/__tests__/`) and real-process fixtures; a live check at the operator's next daemon restart, recorded on the PR; a sandbox repository, a devN
    stack, staging, or a local stack with real migrations), a command or run id, an observation, a head
    SHA, and a negative control. If either is missing, or links only a unit suite, the retro's first
    durable learning is that gap and the issue goes back — to the implementer for its own proof, to the

package/skills/legion-worker/SKILL.md

@@ -251,7 +251,7 @@ PR opens, and every later phase keeps it current rather than replacing it:
 ```
 ## Verification
 
-**CI:** `Tests` run <run-id> — jobs lint, pr-title, typecheck, test all success at <head-sha>.
+**CI:** `Tests` run <run-id> — jobs lint, typecheck, test all success at <head-sha>; `PR Title` run <run-id> — job pr-title success at <head-sha>.
 
 **Threads:** <n> resolved, 0 unresolved. Each disposed individually, never in bulk:
 - Thread <id>: fixed in <commit-sha> — <one line>.
@@ -276,6 +276,7 @@ Verified the implementer's proof by <re-running its command | driving the same s
 **Fast-follow:** <one named cleanup item and where it will land>, or "none".
 
 **Chain:** stacked on <base bookmark> frozen at <sha> / not stacked.
+**Retarget:** Retargeting a pull request to a new base does not re-run Tests; after a retarget, rebase onto the new base and push — the new head runs Tests against the new merge result — and cite that run in the PR body.
 ```
 
 - **Threads are dispositioned individually, never resolved in bulk.** Every open review
@@ -301,11 +302,11 @@ Verified the implementer's proof by <re-running its command | driving the same s
   changes behavior, hides an error, or breaks a gate is fixed here — never deferred.
   Findings about naming, duplication, or wording are batched into the single `Fast-follow`
   line instead of iterating per push.
-- **Rebase only on a real conflict.** Sami, 2026-09-11, verbatim:
+- **Rebase only on a real conflict, except after a base retarget.** Sami, 2026-09-11, verbatim:
   "Please don't do unnecessary rebases (i.e. unless there are merge conflicts). The CI queue is too long and slow."
-  The implementer rebases the issue branch only when GitHub reports it `CONFLICTING` or the
-  controller asks because of a conflict — never to pick up `main` or to refresh CI. A single
-  failed CI job is re-run on its own with `legion gh -- run rerun <run-id> --failed`, never by
+  The implementer rebases the issue branch only when GitHub reports it `CONFLICTING`, the controller asks
+  because of a conflict, or after the pull request is retargeted to a new base. Otherwise, never rebase to
+  pick up `main` or refresh CI. A single failed CI job is re-run on its own with `legion gh -- run rerun <run-id> --failed`, never by
   pushing a new commit. A conflict-forced rebase that leaves the branch's diff unchanged is a
   confirmation, not a new round (see *The unchanged-diff check* below). Before rebasing, record
   the fingerprint at the current tip; after pushing the rebased branch, record it at the new
@@ -317,9 +318,10 @@ Verified the implementer's proof by <re-running its command | driving the same s
   field names naming, duplication, or wording cleanup only; anything that changes behaviour,
   hides an error, or breaks a gate lands in this PR.
 - **The implementer proves the change before its phase completes, and writes the `E2E (implementer)` line when the pull request opens.**
-  The proof is the changed behaviour exercised on the surface a user reaches it through — a
-  scratch daemon, a smoke rig, a sandbox repository, a real browser, a devN stack, a local stack
-  with real migrations — with the exact command or run id, what was observed, the head SHA, and
+  The proof is the changed behaviour exercised on the surface a user reaches it through — the daemon's
+  test harness (`packages/daemon/src/daemon/__tests__/`) and real-process fixtures; a live check at the
+  operator's next daemon restart, recorded on the PR; a sandbox repository, a real browser, a devN stack,
+  or a local stack with real migrations — with the exact command or run id, what was observed, the head SHA,
   one negative control. The same proof goes into `.legion/implement.json` as its required `proof`
   array (`legion handoff write --phase implement` refuses a payload without one and names the
   field), and into the PR body, because the reviewer and the merger verify facts on GitHub and