@sjawhar/opencode-legion-envoy 1.5.0 → 1.6.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/dist/src/server.js +1 -0
- package/package.json +1 -1
- package/skills/dispatch/SKILL.md +2 -0
package/dist/src/server.js
CHANGED
|
@@ -13566,6 +13566,7 @@ var DispatchEventSchema = object({
|
|
|
13566
13566
|
var IssueEventPayloadSchema = object({
|
|
13567
13567
|
title: string2().optional(),
|
|
13568
13568
|
status: string2().optional(),
|
|
13569
|
+
rank: string2().optional(),
|
|
13569
13570
|
route: string2().nullish()
|
|
13570
13571
|
});
|
|
13571
13572
|
var ArtifactCreatedEventPayloadSchema = object({
|
package/package.json
CHANGED
package/skills/dispatch/SKILL.md
CHANGED
|
@@ -72,6 +72,8 @@ exactly one owner to every owner-scoped tool: `issue` for an issue, or `project`
|
|
|
72
72
|
[References](#references) for the resulting ref shape). On first use, an external issue reference creates its native issue in the
|
|
73
73
|
project configured for that repository in Dispatch Settings, then falls back to `DISPATCH_DEFAULT_PROJECT`.
|
|
74
74
|
|
|
75
|
+
Issue reads include `rank`, the server-owned ordering key used by project boards; reorder through `PATCH /api/v1/issues/{key}` with neighboring issue keys rather than writing a priority value.
|
|
76
|
+
|
|
75
77
|
Architects create newly tracked child work with:
|
|
76
78
|
```ts
|
|
77
79
|
dispatch_issue({ project, title, parent?, external?, spec?, force? })
|