@sjawhar/opencode-legion-envoy 8.18.1 → 8.19.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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/legion-controller/SKILL.md +7 -7
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/opencode-legion-envoy",
3
- "version": "8.18.1",
3
+ "version": "8.19.0",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "main": "dist/src/server.js",
package/skills/legion-controller/SKILL.md CHANGED
@@ -24,12 +24,13 @@ the owner a command names (`-R owner/repo`, `repos/owner/repo` in `gh api`, a Gi
24
24
  the first owner's (`GH_CONFIG_DIR`) otherwise, so name the repository. Against a daemon with no
25
25
  GitHub App, `legion controller start` says so when it starts (`[legion] the daemon has no GitHub
26
26
  App to act as; the controller's gh acts as nobody`), and `gh` acts as nobody. The controller reads
27
- Dispatch and the daemon's state, and applies its controller
28
- capability, through the `legion` tool alone: `op: "read_state"` returns the daemon's whole state
29
- (`issues.<KEY>.phase`, `issues.<KEY>.holdReason`, `issues.<KEY>.architect`, `admission.cap`,
30
- `admission.active`, `admission.waiting`, `capabilities[]`, `daemon.project`), and `op: "set_status"`
31
- with `issue` and `status` (`todo`, `backlog` or `icebox`) moves an issue. It runs no `legion` from
32
- bash. Any pull-request comment or review the controller posts ends with
27
+ Dispatch and the daemon's state, and applies its controller capability, through the `legion` tool
28
+ alone: `op: "read_state"` returns the daemon's whole state (`issues.<KEY>.phase`,
29
+ `issues.<KEY>.holdReason`, `issues.<KEY>.architect`, `admission.cap`, `admission.active`,
30
+ `admission.waiting`, `capabilities[]`, `daemon.project`, and `settings`, how the daemon is tuned:
31
+ its resolved `legion.yaml`, `max_fix_attempts` and the rest, with no credential in it, LEGION-791),
32
+ and `op: "set_status"` with `issue` and `status` (`todo`, `backlog` or `icebox`) moves an issue. It
33
+ runs no `legion` from bash. Any pull-request comment or review the controller posts ends with
33
34
  `<!-- legion: {"session":"<session-id>","phase":"controller"} -->`, the footer every Legion role
34
35
  appends: the daemon reads the session to tell a controller's review from the reviewer's verdict. A
35
36
  review the controller submits without that footer still decides nothing for Legion's own workflow
@@ -495,4 +496,3 @@ controller never opens a gate and there is no operator command for it; a project
495
496
  want the gate at all runs `gates.design: off` in its `legion.yaml`. Otherwise resolve the
496
497
  authoritative owning architect role and route the verified context with `envoy_publish`. Do not
497
498
  route raw event traffic or invent a role token from a partial issue reference.
498
-