@sjawhar/opencode-legion-envoy 8.3.0 → 8.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.
Files changed (3) hide show
  1. package/package.json +1 -1
  2. package/skills/legion-controller/SKILL.md +1 -1
  3. package/skills/legion-worker/SKILL.md +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/opencode-legion-envoy",
3
- "version": "8.3.0",
3
+ "version": "8.3.1",
4
4
  "license": "Apache-2.0",
5
5
  "type": "module",
6
6
  "main": "dist/src/server.js",
package/skills/legion-controller/SKILL.md CHANGED
@@ -16,7 +16,7 @@ The Legion extension registers this session with the daemon as the controller an
16
16
  `legion-<project>-controller` during session startup. Do not handle a wake unless that startup
17
17
  succeeded.
18
18
 
19
- The session's `gh` acts as the review App (`legion-reviewer[bot]` in Legion's own deployment) from
19
+ The session's `gh` acts as the review App's bot account (`gh api graphql -f query='{viewer{login}}'` names it) from
20
20
  `GH_CONFIG_DIR`, a directory Legion keeps current: in the pod the daemon launches, through the
21
21
  controller's role Secret the daemon refreshes every minute; in `legion controller start`'s session,
22
22
  through that command's own refresh loop. `gh pr view`, `gh api` and the rest read and write GitHub
package/skills/legion-worker/SKILL.md CHANGED
@@ -174,8 +174,8 @@ in any jj or Git scope — not `jj config set`, not `--config`, not `git config`
174
174
  the pane environment and would put the wrong App back on your commits, and the repository-scoped jj
175
175
  config is one file shared by every issue workspace of the clone. Legion has two GitHub Apps, not
176
176
  one per role: your role's App is the **implement** App if you are the implementer or the merger,
177
- and the **review** App if you are the planner, tester, reviewer, or an architect (in Legion's own
178
- deployment, `legion-implementer[bot]` and `legion-reviewer[bot]`). A planner's commits authored
177
+ and the **review** App if you are the planner, tester, reviewer, or an architect; your pane's
178
+ `JJ_USER` and `JJ_EMAIL` name your role's App's bot account. A planner's commits authored
179
179
  by the review App are right. Before a push, check
180
180
  `jj -R "$LEGION_WORKSPACE" log -r 'main@origin..@' -T 'author.email() ++ " | " ++ committer.email() ++ " " ++ description.first_line() ++ "\n"'`
181
181
  shows your role's App in both columns **on every commit you made** — not on the whole list: