@sjawhar/opencode-legion-envoy 0.15.0 → 0.17.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 +16 -9
  2. package/dist/src/server.js +876 -331
  3. package/package.json +1 -1
  4. package/skills/dispatch/SKILL.md +189 -220
  5. package/skills/legion-architect/SKILL.md +61 -38
  6. package/skills/legion-retro/SKILL.md +1 -1
  7. package/skills/legion-worker/SKILL.md +9 -8
  8. package/src/server.ts +74 -93
package/README.md CHANGED
@@ -12,15 +12,22 @@ This package exposes:
12
12
  - `envoy_role_set`
13
13
  - `envoy_whoami`
14
14
  - `envoy_sessions`
15
- - `dispatch`
16
-
17
- `dispatch` raises or continues a durable question thread for the human (a GitHub
18
- issue on the Dispatch dashboard). The tool is present when `dispatch.enabled` is set in
19
- envoy.json (`~/.config/opencode/envoy.json`, merged with `<repo>/.opencode/envoy.json`) or
20
- when `DISPATCH_MCP_URL` names the service endpoint explicitly; the service URL otherwise
21
- comes from `dispatch.serverUrl`. Each call fills the target repo from the session's working
22
- directory and stamps the thread with the OpenCode session id and title, and the session is
23
- auto-subscribed to the thread so the reply arrives back through Envoy.
15
+ - `dispatch_issue`
16
+ - `dispatch_ask`
17
+ - `dispatch_comment`
18
+ - `dispatch_suggest`
19
+ - `dispatch_message`
20
+ - `dispatch_doc_edit`
21
+ - `dispatch_doc_read`
22
+ - `dispatch_artifact`
23
+ - `dispatch_read`
24
+
25
+ The native `dispatch_*` tools create and read Dispatch issues, asks, comments, documents, and
26
+ artifacts. They are present when `dispatch.enabled` resolves a server URL and bearer token from
27
+ envoy.json (`~/.config/opencode/envoy.json`, merged with `<repo>/.opencode/envoy.json`) or the
28
+ `DISPATCH_URL` and `DISPATCH_TOKEN` environment variables. Each call fills the target issue from
29
+ the session working directory, stamps it with the OpenCode session id and title, and stores
30
+ `details.topic` as tool metadata so a successful mutation subscribes to that exact Dispatch topic.
24
31
 
25
32
  It also maintains the live session registry metadata needed for Envoy to discover OpenCode sessions and their API ports.
26
33