@sjawhar/opencode-legion-envoy 1.55.3 → 2.0.0

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": "1.55.3",
3
+ "version": "2.0.0",
4
4
  "type": "module",
5
5
  "main": "dist/src/server.js",
6
6
  "exports": {
@@ -189,14 +189,17 @@ comments live on that path too, so edit them with `gh pr comment`) — printing
189
189
  `Legion issues live on Dispatch; use dispatch_message or dispatch_comment on <your LEGION_ISSUE>`:
190
190
  Legion never reads or writes a GitHub issue (LEGION-78). `pr comment`, `pr review`,
191
191
  `api …/pulls/…`, `api graphql`, and issue reads are unaffected. The credential reaches `legion`
192
- through the file `$LEGION_GRANT_FILE` names, written before each of your bash commands by the
193
- extension (and by the `legion` tool before its `handoff_complete`); never `cat`, `echo`, copy, or
192
+ through the file `$LEGION_GRANT_FILE` names, written by the extension before each of your bash
193
+ commands, each `github` tool call, and each `read`/`grep` of a `pr://` or `issue://` URL (and by
194
+ the `legion` tool before its `handoff_complete`); never `cat`, `echo`, copy, or
194
195
  `export` it — `legion credential`, `legion gh`, `jj git push`, and `handoff_complete` read it
195
- themselves. The file is the pane's, not the
196
- command's: a `task` subagent, an `eval` subprocess, or a background job in your pane reads the
197
- grant your last bash command minted, so its `legion gh` or `jj git push` succeeds only within 60
198
- seconds of that call and 403s afterwards — a timing artifact, not a broken credential; run
199
- credentialed commands from your own bash calls.
196
+ themselves. The file is the pane's, not the command's, and a grant lives 60 seconds: a `task`
197
+ subagent, an `eval` subprocess, or a background job in your pane reads the grant your last such
198
+ call wrote, and a `github` tool `run_watch` keeps polling `gh` on the one written when the call
199
+ began, so each succeeds only within 60 seconds of that call and 403s afterwards — a timing
200
+ artifact, not a broken credential. Run credentialed commands from your own bash calls, and watch a
201
+ run that may outlast a minute with `gh run watch` in bash, which redeems once and then runs on the
202
+ token it got.
200
203
 
201
204
  ## GitHub PR comment attribution
202
205
 
@@ -265,6 +268,7 @@ later phase keeps it current rather than replacing it:
265
268
  `legion threads resolve --pr <n> --repo <owner>/<repo>` at <head-sha>:
266
269
  resolved <thread URL>
267
270
  left open <thread URL> — newest reply by <login> is not an acceptance
271
+ left open <thread URL> — newest reply by <login> is an unsubmitted draft in a pending review
268
272
 
269
273
  **Thermo:** `ce-simplify-code` once at <head-sha>: <0 applied | applied → new head <sha>>; thermonuclear pair at the final head <sha>:
270
274
  <verdict>. (omitted entirely on a docs-only PR — there is no code for either pass, so neither runs)