@sjawhar/opencode-legion-envoy 6.3.0 → 6.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/opencode-legion-envoy",
3
- "version": "6.3.0",
3
+ "version": "6.3.1",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "main": "dist/src/server.js",
@@ -424,9 +424,12 @@ report with `handoff_complete` alone (below).
424
424
  ## Completion: report to the architect, then stay
425
425
 
426
426
  Report completion to the architect: call the `legion` tool with `op: "handoff_complete"` and
427
- `summary`: two sentences for the architect. A worker never runs `legion handoff complete` from
428
- bash, where the extension refuses it: the tool call is what the extension records, and a turn that
429
- ends with the phase still open gets one reminder.
427
+ `summary`: two sentences for the architect. Report it through that tool call, never the shell
428
+ command `legion handoff complete`: the tool call is what the extension's phase stall records, and
429
+ a turn that ends with the phase still open gets one reminder. A completion run from the shell is
430
+ recorded by the daemon all the same, but the stall does not see it and sends its one reminder; do
431
+ not complete again on that reminder — the first completion stands, and a second is refused
432
+ because the issue has already left your phase.
430
433
 
431
434
  This publishes your phase's completion to the architect's role and clears the daemon's
432
435
  record of this issue's active phase. Do not add pipeline labels, run a controller loop, or