@sjawhar/opencode-legion-envoy 3.19.9 → 4.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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/legion-controller/SKILL.md +2 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sjawhar/opencode-legion-envoy",
3
- "version": "3.19.9",
3
+ "version": "4.0.0",
4
4
  "type": "module",
5
5
  "main": "dist/src/server.js",
6
6
  "exports": {
package/skills/legion-controller/SKILL.md CHANGED
@@ -69,9 +69,8 @@ their own machine, and you are that foreground OMP session. The command fetched
69
69
  secret from the daemon with the operator's token, wrote it to a 0600 file under `LEGION_STATE_DIR`
70
70
  (`~/.local/state/legion/<project>-controller` by default) beside the `gh` shim and the `legion`
71
71
  launcher, and started you with `LEGION_CONTROLLER=1` and the same environment a tmux controller pane
72
- carries, so nothing changes in how you handle wakes. Under the TypeScript daemon the extension
73
- claims the role and calls `/controller/ready` exactly as under tmux; under the Go daemon
74
- (`LEGION_DAEMON_API=go` in your environment) it registers on `/legion/v1/claims/register` with the
72
+ carries, so nothing changes in how you handle wakes. The extension registers on
73
+ `/legion/v1/claims/register` with the
75
74
  secret, claims the role, then subscribes to `notifications.legion.<project>.controller`, where the
76
75
  Go daemon publishes the rows marked from the Go daemon in the wake routing table. The daemon records
77
76
  you as `controllerLocator: {runtime, external: true, sessionId, registeredAt}`, `runtime` being the