@sjawhar/pi-legion 8.5.0 → 8.6.0

package/dist/legion.js

@@ -15309,7 +15309,7 @@ function onEnvoyRoleRegained(listener) {
 // package.json
 var package_default = {
   name: "@sjawhar/pi-legion",
-  version: "8.5.0",
+  version: "8.6.0",
   license: "Apache-2.0",
   type: "module",
   omp: {

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

@@ -59,7 +59,11 @@ only on this phase's artifact.
 
 You never start another Legion role: the daemon starts every phase worker itself, from its fixed
 workflow table. You may still use ordinary `task` subagents for your own phase work; none of them
-is a Legion role.
+is a Legion role. A subagent runs in your pane as you, with every host tool but the `legion` tool
+(it is never offered one), so a `legion` command from its bash, a completion included, is yours at
+the daemon: give a subagent no completion step. Today such a command runs on the per-call grant
+your own last credentialed call wrote, within its 60 seconds (*Four facts about `gh`*, below);
+LEGION-631 (dispatch://LEGION-631) replaces that grant with the role's mounted token file.
 Escalate a product, scope, design, cross-phase, or lifecycle decision to the owning architect with
 `envoy_publish` to its role topic (`notifications.role.` followed by its encoded token, see
 above), carrying the verified facts and the decision needed. A `write` to `agent://` only reaches
@@ -422,17 +426,18 @@ check write no `.legion/<issue>/<phase>.json`, commit no handoff, and report wit
 
 ## Completion: report to the architect, then stay
 
-Report completion to the architect: call the `legion` tool with `op: "handoff_complete"` and
-`summary`: two sentences for the architect. Report it through that tool call, never the shell
-command `legion handoff complete`: the tool call is what the extension's phase stall records, and
-a turn that ends with the phase still open gets one reminder. A completion run from the shell is
-recorded by the daemon all the same, but the stall does not see it and sends its one reminder; do
-not complete again on that reminder — the first completion stands, and a second is refused
-because the issue has already left your phase.
-
-This publishes your phase's completion to the architect's role and clears the daemon's
-record of this issue's active phase. Do not add pipeline labels, run a controller loop, or
-invent a different completion protocol — this is the whole contract.
+Report completion to the architect with the `legion` tool's `handoff_complete` and a two-sentence
+`summary`. This publishes your phase's completion to the architect's role and clears the daemon's
+record of this issue's active phase. A shell `legion handoff complete`, should one run, completes
+the phase at the daemon just as well and is not refused, but only the tool call tells the
+extension's phase stall: after a shell completion the reminder arrives when the turn settles and
+again after each later Envoy delivery's turn, until a tool `handoff_complete` next succeeds (in
+practice the next phase's). A completion made on that reminder is refused and closes nothing —
+`HANDOFF_NOT_CURRENT_PHASE` once the phase has moved, `HANDOFF_ALREADY_RECORDED` where a
+completion moves nothing (the implementer before its pull request exists; the production check) —
+so answer the reminder with a WAITING line saying the phase was completed from the shell. Do not
+add pipeline labels, run a controller loop, or invent a different completion protocol — this is the
+whole contract.
 
 A reviewer's phase ends with its completion, not with its review; the order of a review round
 (the handoff push; for an approval, CI settled green at that head; the review of that head; then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/pi-legion",
-  "version": "8.5.0",
+  "version": "8.6.0",
   "license": "Apache-2.0",
   "type": "module",
   "omp": {