@sjawhar/pi-legion-envoy 5.26.0 → 5.27.1

package/dist/envoy.js

@@ -31769,6 +31769,16 @@ function dispatchPayload(event) {
   const parsed = schema.safeParse(event.payload);
   return parsed.success ? parsed.data : event.payload;
 }
+function hasTarget(value) {
+  return isObject2(value) && "target" in value;
+}
+function dispatchPayloadForReader(event, sessionID) {
+  const payload = dispatchPayload(event);
+  if (!hasTarget(payload))
+    return payload;
+  const target = payload.target;
+  return target === `session:${sessionID}` ? { ...payload, target: `you (${target})` } : payload;
+}
 function dispatchAskQuestion(comment) {
   return comment?.ask_question !== undefined && comment.ask_question !== "" ? textHead(comment.ask_question) : undefined;
 }
@@ -31994,7 +32004,7 @@ function renderInbound(raw, sessionID, subject2) {
           owner: dispatchOwner(frame.event, topic),
           type: frame.event.type,
           actor: frame.event.actor,
-          ...compactRecord ?? { payload: dispatchPayload(frame.event) }
+          ...compactRecord ?? { payload: dispatchPayloadForReader(frame.event, sessionID) }
         };
         dispatchActor = frame.event.actor;
       } else {
@@ -32035,7 +32045,7 @@ function renderInbound(raw, sessionID, subject2) {
     ...dispatchIssue === undefined ? [] : [dispatchIssue]
   ].join(", ") || undefined;
   const rendered = {
-    ...envelope2.topic === agentSubject(sessionID) ? { to: `you (${sessionID.slice(0, 4)}\u2026)` } : {},
+    ...envelope2.topic === agentSubject(sessionID) ? { to: `you (${sessionID})` } : {},
     from: senderLabel(envelope2),
     at: inboundTimestamp(envelope2.issued_at),
     id: envelope2.event_id ?? "unknown",

package/dist/legion.js

@@ -33611,7 +33611,7 @@ import { logger } from "@oh-my-pi/pi-utils";
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion-envoy",
-  version: "5.26.0",
+  version: "5.27.1",
   type: "module",
   omp: {
     extensions: [

package/dist/skills/envoy/SKILL.md

@@ -45,7 +45,7 @@ Envoy renders an annotated delivery before its source summary and complete paylo
 
 ```text
 envoy:
-  to: you (01a0…)
+  to: you (ses_example_recipient)
   from: 01a0bbbb-cccc-7ddd-eeee-0123456789ab (Reviewer)
   at: "2026-09-07T04:41:12Z"
   id: agent-message-2

package/dist/skills/legion-worker/SKILL.md

@@ -287,7 +287,7 @@ rather than creating a replacement bookmark or PR.
 
 ## PR body, review, and the merge gate
 
-The implementer writes the pull request body in the READY format when it opens the pull request,
+The implementer writes the pull request body from the template when it opens the pull request,
 and every later phase edits its own lines of the live body rather than replacing it. Each proof
 (the implementer's `E2E (implementer)` line and `proof` array, the tester's `E2E (tester)` line
 and `proof` array) is the changed behaviour exercised on a production-like surface, recorded as

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

@@ -71,14 +71,17 @@ completion leaves the issue in reviewing until you finish.
   First `cd -- "$LEGION_WORKSPACE" && jj -R "$LEGION_WORKSPACE" git fetch && jj -R
   "$LEGION_WORKSPACE" diff --from <approved-sha> --to <tip-sha> --summary`, whose output is quoted
   in READY (an empty output is quoted as `no file changes above the approved head`); then the same
-  with `'~docs/solutions'` appended, which must print nothing. The merger always posts
-  `READY #<n> at <current sha> (approved at <approved sha>) for <KEY> (<pr url>)` (the shape
-  `packages/pi-envoy/roles/merger.md` defines), its summary, and the PR body's gate facts as a
-  `dispatch_message` on the issue. When the `Legion addressing` line names a merge queue, it also
-  publishes the same packet there with `envoy_publish`; a 404 means the Dispatch message remains
-  the durable notice and the merger stays idle. The READY packet names both the implementer's and
-  tester's `E2E` lines; a missing one is reported to the architect instead of published. Legion
-  never merges.
+  with `'~docs/solutions'` appended, which must print nothing. *The READY packet*: the merger
+  always posts `READY #<n> at <current sha> (approved at <approved sha>) for <KEY> (<pr url>)`
+  (the shape `packages/pi-envoy/roles/merger.md` defines), then the PR body's `Outcome:` line and
+  its `Not proven / risk:` value — every bullet under that label joined with `; ` on the one
+  READY line, or `none` — quoted from the `## For the reviewer` block at that same head (or one
+  line saying the body carries no brief — the packet still publishes), then the `--summary`
+  output and the PR body's gate facts, as a `dispatch_message` on the issue. When the `Legion
+  addressing` line names a merge queue, it also publishes the same packet there with
+  `envoy_publish`; a 404 means the Dispatch message remains the durable notice and the merger
+  stays idle. The READY packet names both the implementer's and tester's `E2E` lines; a missing
+  one is reported to the architect instead of published. Legion never merges.
 
 ## After the human merge
 

package/dist/skills/legion-worker/references/pr-body.md

@@ -4,12 +4,24 @@ Part of `skill://legion-worker`. Read it before you write or edit any line of th
 body, put a `proof` array in a handoff, verify another phase's proof, or run the simplify pass.
 Every path it cites is in sjawhar/legion.
 
-## The READY format
+## The pull request body template
 
-The implementer writes the PR body in the READY format from the moment the PR opens, and every
+The implementer writes the PR body from this template from the moment the PR opens, and every
 later phase keeps it current rather than replacing it:
 
 ```
+## For the reviewer
+
+**Outcome:** <one sentence a user of this repository would recognise: what someone can now do, or what stops going wrong>
+**Why:** <the problem, one or two sentences, ending with the Dispatch key in parentheses — the key only, never a URL>
+**Change:**
+- <two to five bullets, each one behaviour a user or operator meets, never a file name>
+**Look at first:** <one to three `path:line` places where a wrong decision would hurt> (the reviewer writes this line)
+**Proven by:** <the `E2E (implementer)` line's surface and run, one line>
+**Not proven / risk:**
+- <one line per claim recorded as unproven before READY>, or the single word `none` (the reviewer writes this line; `none` is invalid while such a claim stands)
+**Size:** <files changed, +added/−removed>
+
 ## Verification
 
 **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>.
@@ -42,6 +54,22 @@ Verified the implementer's proof by <re-running its command | driving the same s
 **Chain:** stacked on <base bookmark> frozen at <sha> / not stacked.
 ```
 
+## The brief for the human
+
+`## For the reviewer` is written for the person who merges; `## Verification` below it stays the
+ledger the reviewer and merger check against GitHub. The implementer writes `Outcome`, `Why`,
+`Change`, `Proven by`, and `Size` when the pull request opens, and keeps them true after every
+push; `Outcome` is a sentence a user of the repository would recognise, never "fix bug" or a file
+name, and `Why` ends with the Dispatch key, never a URL. The reviewer writes `Look at first` and
+`Not proven / risk` at each round, into the live body (`legion gh -- api
+repos/{owner}/{repo}/pulls/{number} --jq .body`, edit, then `--method PATCH ... -F body=@body.md`);
+`Not proven / risk` copies every claim recorded as unproven before READY — the tester's
+`failures`, the reviewer's own review, any proof-check comment already on the pull request —
+word for word, and `none` is a finding while one stands. The merger quotes `Outcome` and
+`Not proven / risk` from the body at the published head in the READY packet
+(*The READY packet* in `skill://legion-worker/references/merge-gate.md`); a stale `Outcome` that no
+longer describes the diff is a finding against the implementer, not a line the merger rewrites.
+
 ## What a proof is
 
 **A proof** is the changed behaviour exercised on the surface a user reaches it through, recorded

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion-envoy",
-  "version": "5.26.0",
+  "version": "5.27.1",
   "type": "module",
   "omp": {
     "extensions": [