@sjawhar/opencode-legion-envoy 1.4.2 → 1.6.0

package/dist/src/server.js

@@ -13566,6 +13566,7 @@ var DispatchEventSchema = object({
 var IssueEventPayloadSchema = object({
   title: string2().optional(),
   status: string2().optional(),
+  rank: string2().optional(),
   route: string2().nullish()
 });
 var ArtifactCreatedEventPayloadSchema = object({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sjawhar/opencode-legion-envoy",
-  "version": "1.4.2",
+  "version": "1.6.0",
   "type": "module",
   "main": "dist/src/server.js",
   "exports": {

package/skills/dispatch/SKILL.md

@@ -29,6 +29,13 @@ vocabulary, and is often on a phone. Write for that person.
 - Before posting, test it: could Sami, reading only this text on his phone, know what he is being
   told or asked? If not, rewrite it. Length is not the problem; density is.
 
+## Agent authentication
+
+Use a personal Dispatch token: a human mints it in Dispatch **Settings → Agent tokens** and supplies
+it to the agent through `dispatch.token` in `~/.config/opencode/envoy.json` or `DISPATCH_TOKEN`.
+The server records the minting human as the owner of that session's writes. `DISPATCH_AGENT_TOKEN`
+is the shared devbox fallback; do not configure it for an individual agent.
+
 ## Writing a spec
 
 A spec has two readers: the human who decides reads the top; the implementer who builds reads the
@@ -65,6 +72,8 @@ exactly one owner to every owner-scoped tool: `issue` for an issue, or `project`
 [References](#references) for the resulting ref shape). On first use, an external issue reference creates its native issue in the
 project configured for that repository in Dispatch Settings, then falls back to `DISPATCH_DEFAULT_PROJECT`.
 
+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.
+
 Architects create newly tracked child work with:
 ```ts
 dispatch_issue({ project, title, parent?, external?, spec?, force? })