@sjawhar/pi-legion-envoy 0.3.0 → 0.4.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.
- package/.mcp.json +7 -0
- package/README.md +7 -12
- package/dist/bin/dispatch-mcp-shim.js +13899 -0
- package/dist/envoy.js +22 -5
- package/dist/skills/envoy/SKILL.md +8 -0
- package/package.json +3 -2
package/.mcp.json
ADDED
package/README.md
CHANGED
|
@@ -77,18 +77,13 @@ resumes the same OMP session file, so the reply still lands. Lifecycle and scope
|
|
|
77
77
|
decisions still go through `hub` to the owning architect — Dispatch is for durable
|
|
78
78
|
questions to the human, not for coordination between roles.
|
|
79
79
|
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
"args": ["<checkout>/packages/envoy-client/bin/dispatch-mcp-shim.ts"]
|
|
88
|
-
}
|
|
89
|
-
}
|
|
90
|
-
}
|
|
91
|
-
```
|
|
80
|
+
No manual mount is needed: the package-root `.mcp.json` ships the server with the
|
|
81
|
+
package, so any session that loads it (installed plugin, `--extension`, the Legion
|
|
82
|
+
daemon's repo checkout) discovers `dispatch` automatically. The committed manifest
|
|
83
|
+
runs `./bin/dispatch-mcp-shim.ts` from source; the release workflow points the
|
|
84
|
+
published tarball at the self-contained `./dist/bin/dispatch-mcp-shim.js`. A
|
|
85
|
+
same-named `dispatch` entry in `~/.omp/agent/mcp.json` would override the package
|
|
86
|
+
mount — remove machine-local entries rather than maintaining both.
|
|
92
87
|
|
|
93
88
|
The shim forwards newline-delimited JSON-RPC from stdin to the dispatch server's Streamable
|
|
94
89
|
HTTP `/mcp` endpoint with a cached GitHub bearer from the user's `gh` shim. The
|