@sjawhar/pi-legion-envoy 1.63.0 → 1.65.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 +2 -2
- package/dist/envoy.js +4603 -4496
- package/dist/legion.js +3890 -3851
- package/dist/skills/dispatch/SKILL.md +60 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -86,7 +86,7 @@ extension files it does not contain.
|
|
|
86
86
|
|
|
87
87
|
## Native Dispatch tools
|
|
88
88
|
|
|
89
|
-
The extension registers twenty native Dispatch tools: `dispatch_issue`, `dispatch_issue_update`, `dispatch_ask`, `dispatch_edit_ask`,
|
|
89
|
+
The extension registers twenty-one native Dispatch tools: `dispatch_issue`, `dispatch_issue_update`, `dispatch_claim`, `dispatch_ask`, `dispatch_edit_ask`,
|
|
90
90
|
`dispatch_resolve_ask`, `dispatch_resolve_comment`, `dispatch_follow`, `dispatch_comment`, `dispatch_suggest`,
|
|
91
91
|
`dispatch_message`, `dispatch_doc_edit`, `dispatch_doc_read`, `dispatch_request_approval`, `dispatch_artifact`,
|
|
92
92
|
`dispatch_read`, `dispatch_search`, `dispatch_issues`, `dispatch_architecture_sync`, `dispatch_open_asks`, and `dispatch_whoami`, when Dispatch configuration resolves both a base URL and bearer token.
|
|
@@ -113,7 +113,7 @@ whose trimmed contents are the token — how the Legion daemon delivers it to a
|
|
|
113
113
|
pane) wins over every other token source and never falls back when unreadable.
|
|
114
114
|
Omitting `dispatch.serverUrl` while `dispatch.enabled` is true targets
|
|
115
115
|
`http://localhost:8766`, the Go server's listen address. Invalid configuration,
|
|
116
|
-
an invalid URL, or an empty token leaves the twenty tools unavailable and
|
|
116
|
+
an invalid URL, or an empty token leaves the twenty-one tools unavailable and
|
|
117
117
|
reports the source of the error.
|
|
118
118
|
|
|
119
119
|
Owner-scoped calls use either an issue (a native `KEY` or external `owner/repo#n` reference) or
|