@sjawhar/pi-legion-envoy 0.4.0 → 0.5.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 (8) hide show
  1. package/README.md +9 -7
  2. package/dist/bin/dispatch-mcp-shim.js +496 -10187
  3. package/dist/envoy.js +1572 -10743
  4. package/dist/skills/AGENTS.md +1 -0
  5. package/dist/skills/dispatch/SKILL.md +94 -0
  6. package/dist/skills/envoy/SKILL.md +24 -16
  7. package/dist/skills/legion-architect/SKILL.md +2 -1
  8. package/package.json +1 -1
package/README.md CHANGED
@@ -69,13 +69,15 @@ OpenCode sessions do: the shared `@legion/envoy-client` shim mounts as a stdio M
69
69
  and it serves when `dispatch.enabled` is true in the shared envoy.json
70
70
  (`~/.config/opencode/envoy.json`, shallow-merged with `<cwd>/.opencode/envoy.json`) or
71
71
  `DISPATCH_MCP_URL` is set explicitly. The server URL comes from `dispatch.serverUrl`
72
- (default `http://localhost:8766`). Dispatch exists so headless unattended agents —
73
- Legion architects, planners, phase workers — can raise durable questions to the human.
74
- Replies route back to the asking session, which is auto-subscribed to the thread's
75
- GitHub topic; a Legion role's session survives kill/resume because Legion resurrection
76
- resumes the same OMP session file, so the reply still lands. Lifecycle and scope
77
- decisions still go through `hub` to the owning architect — Dispatch is for durable
78
- questions to the human, not for coordination between roles.
72
+ (default `http://localhost:8766`). Dispatch is how any agent — an interactive session or
73
+ a headless Legion role — raises a durable question to the human: the thread lands as a
74
+ GitHub issue in the session cwd's repo (or an explicit `repo`), carries the session's
75
+ provenance, and shows up on the Dispatch dashboard. The `dispatch` skill (shipped in
76
+ `skills/`) says when to use it. Replies route back to the asking session, which is
77
+ auto-subscribed to the thread's GitHub topic; a Legion role's session survives kill/resume
78
+ because Legion resurrection resumes the same OMP session file, so the reply still lands.
79
+ Lifecycle and scope decisions still go through `hub` to the owning architect — Dispatch is
80
+ for durable questions to the human, not for coordination between roles.
79
81
 
80
82
  No manual mount is needed: the package-root `.mcp.json` ships the server with the
81
83
  package, so any session that loads it (installed plugin, `--extension`, the Legion