@sjawhar/opencode-legion-envoy 0.8.0 → 0.10.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.
package/README.md CHANGED
@@ -8,14 +8,27 @@ This package exposes:
8
8
  - `envoy_unsubscribe`
9
9
  - `envoy_list`
10
10
  - `envoy_send`
11
+ - `envoy_publish`
12
+ - `envoy_role_set`
13
+ - `envoy_whoami`
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.
11
24
 
12
25
  It also maintains the live session registry metadata needed for Envoy to discover OpenCode sessions and their API ports.
13
26
 
14
27
  Slack topic examples must use the real Slack `team_id`, for example:
15
28
 
16
- - `notifications.slack.T09FRELLTS8.C0A0DHVU8HE.mention`
29
+ - `notifications.slack.T01234567.C0A0DHVU8HE.mention`
17
30
 
18
- Do not use workspace slugs like `trajectorylabs` in the topic path.
31
+ Do not use workspace slugs like `acme` in the topic path.
19
32
 
20
33
  ## Sync to another machine
21
34