@sjawhar/opencode-legion-envoy 8.20.11 → 8.20.13

package/package.json

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

package/skills/dispatch/SKILL.md

@@ -87,6 +87,7 @@ A decision a human must make is an `:::ask{#slug}` block at the end of the secti
 ## Claim the issue before you work it
 
 - Before you implement, `dispatch claim --issue <KEY>` and `dispatch issue-update --issue <KEY> --status in_progress`. Release with `--release` when you finish, hand over or switch. Closing releases it.
+- Claiming does not deliver the issue's comments to you. In the same turn, route the issue to your session, `dispatch issue-update --issue <KEY> --route session:<your session id>`, or subscribe to it with `envoy_subscribe notifications.dispatch.issue.<KEY>.>`. When you release, clear the route with `--route ''`. Never route an issue with the `legion` label, or under one: Legion's roles work it, not your session.
 - Reading, commenting, asking or gating a PR claims nothing.
 - `409 ISSUE_CLAIMED`: someone else holds it. Never work it in parallel. Refusals and takeovers: [issues.md](skill://dispatch/references/issues.md).
 

package/skills/legion-controller/SKILL.md

@@ -59,7 +59,7 @@ The controller is the project's order keeper. It retains its startup role,
 `legion-<project>-controller`; `backlog-order` is retired. Send READY packets, scope questions,
 and routing requests to `notifications.role.legion-<project>-controller`, then follow
 [Backlog stewardship](skill://legion-controller/references/backlog-stewardship.md) for daily
-weekly-plan reconciliation, Sami's rulings, ownership routing, and stopped-session recovery.
+weekly-plan reconciliation, a person's rulings, ownership routing, and stopped-session recovery.
 These duties change Dispatch's priority and board-rank data and route plan work to a live session;
 they start nothing on Legion and hand it no issue ([Free slots](#free-slots-go-daemon)).
 
@@ -365,9 +365,9 @@ themselves: an issue reaches Legion only when a person hands it over
 
 - **Direct user message always first.** If this turn includes a direct user message, answer
   it before handling every other wake.
-- **Sami's rulings.** A direct Dispatch message from Sami is a ruling: after answering it, run
-  the full [Backlog stewardship](#backlog-stewardship) reconciliation and record the current rule
-  in the weekly plan.
+- **A person's rulings.** A direct Dispatch message to this controller from a person is a ruling:
+  after answering it, run the full [Backlog stewardship](#backlog-stewardship) reconciliation and
+  record the current rule in the weekly plan.
 - **One wake = one turn.** Handle exactly the wake's implication, then end the turn. Never
   poll, idle-loop, or wait for another event. Two additions, after any direct user message: every
   turn first rechecks the [trees waiting on a root

package/skills/legion-controller/references/backlog-stewardship.md

@@ -14,7 +14,7 @@ subscription: changing roles ends the controller's wake delivery.
 
 ## Reconcile the weekly plan
 
-Run this pass on the first turn of every UTC day and after every ruling from Sami:
+Run this pass on the first turn of every UTC day and after every ruling from a person:
 
 1. Read the weekly-planning issue and select its newest `plan-week-*` artifact by its latest
    `artifact.version` event. Read that artifact before changing any issue.
@@ -33,9 +33,10 @@ Run this pass on the first turn of every UTC day and after every ruling from Sam
    `dispatch doc-read`. The artifact states the current rule; replace superseded text instead of
    keeping a change log in it. A comment or message does not update the one-owner map.
 
-A ruling from Sami is a direct Dispatch message to this controller. Answer it first, carry out its
-scope or priority decision, then record the resulting current rule in the affected weekly-plan row
-(or its ruling section when it has no one line). Link the message when Dispatch gave it a reference.
+A ruling from a person is a direct Dispatch message to this controller. Answer it first, carry out
+its scope or priority decision, then record the resulting current rule in the affected weekly-plan
+row (or its ruling section when it has no one line). Link the message when Dispatch gave it a
+reference.
 A ruling triggers the full reconciliation pass even when it appears to affect only one issue.
 
 ## Answering controller deliveries