cyberlegion 1.9.0 → 2.0.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cyberlegion",
-  "version": "1.9.0",
+  "version": "2.0.0",
   "description": "Harness-agnostic agent session spawning and messaging over the filesystem",
   "keywords": [
     "agent",

package/plugin.json

@@ -1,7 +1,7 @@
 {
 	"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
 	"name": "cyberlegion",
-	"version": "1.9.0",
+	"version": "2.0.0",
 	"description": "Agent session spawning, messaging, and dispatch — the Legion and its Legate.",
 	"author": {
 		"name": "unional"

package/readme.md

@@ -30,7 +30,7 @@ npx cyberlegion unit register --handle scout        # register/refresh this sess
 npx cyberlegion unit register --standing --handle homa  # mint a standing, session-independent owner inbox
 npx cyberlegion unit whoami                          # print your own identity
 npx cyberlegion unit who                             # list addressable peers / live peer sessions
-npx cyberlegion unit prune                           # mark dead agents exited and sweep
+npx cyberlegion unit prune                           # mark dead agents exited; delete exited ones with no worktree
 npx cyberlegion unit spawn --agent reviewer          # launch a peer in its own git worktree (tmux/herdr)
 npx cyberlegion unit focus <ref>                     # move input focus to a peer's session
 npx cyberlegion unit nudge <ref>                     # ring a peer's session (doorbell)

package/skills/dispatch-governance/SKILL.md

@@ -12,12 +12,13 @@ place that judgment lives, loaded in-session by the `legate` gateway on a dispat
 realized headless by the `headless-legate` agent. Both loads run the exact same procedure below.
 
 **Input:** an intent to fulfill role `R` with brief `B`, optionally expecting a result that
-satisfies verdict schema `V`.
+satisfies verdict schema `V`, and optionally the path `P` of an agent definition file. When the
+caller supplies `P`, it is the definition to use; the by-name lookup is skipped.
 
 > **Running the CLI.** Every `node scripts/cyberlegion.mjs …` command below runs the `cyberlegion` CLI
 > this plugin ships. The path is relative to this skill's own directory, not the working directory.
 > If you cannot resolve it, run the published CLI of the version that shipped this skill instead,
-> with the same arguments: `npx -y cyberlegion@1.9.0`.
+> with the same arguments: `npx -y cyberlegion@2.0.0`.
 
 ## 1. Resolve the agent definition
 
@@ -25,6 +26,18 @@ satisfies verdict schema `V`.
 node scripts/cyberlegion.mjs agent resolve <R> --format json
 ```
 
+When the intent carries a definition path `P`, resolve that file instead and do not look `<R>` up by
+name (a definition a plugin ships is not under the project's `.agents/agents/`, so by name it is not
+found):
+
+```bash
+node scripts/cyberlegion.mjs agent resolve --file <P> --format json
+```
+
+Everything below reads the same resolved def either way. Wherever a step passes `--agent <R>` to
+`unit spawn`, pass `--agent-file <P>` instead when `P` was given, and the subagent path builds its
+instruction from the def resolved from `P`.
+
 Read `model`, `effort`, `harness`, `warm`, `interactive` off the resolved def. `warm` marks a role
 that should run as a live peer session (not a fire-and-forget unit); `interactive` marks a role that
 may need to grill the caller or converse over multiple rounds, not just return one result.
@@ -53,7 +66,7 @@ to open a pane in; its absence rules that strategy out regardless of what the ag
   mint a thread id, weave it (and an instruction to reply on it) into brief `B`, then:
 
   ```bash
-  node scripts/cyberlegion.mjs unit spawn --agent <R> --brief-file <B> --at <placement>
+  node scripts/cyberlegion.mjs unit spawn --agent <R> --brief-file <B> --at <placement>   # or --agent-file <P> when given
   node scripts/cyberlegion.mjs mail await --thread <the-minted-thread-id> [--timeout <ms>] [--max-wait <s>]
   ```