cyberfleet 0.5.0 → 0.5.1

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
 	"name": "cyberfleet",
-	"version": "0.5.0",
+	"version": "0.5.1",
 	"description": "Fleet & crew personas over cyberlegion — Pod (ship's bridge), Operator (command center), Crimp (crew recruitment), and Mechanic (automaton building).",
 	"author": {
 		"name": "unional"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
 	"name": "cyberfleet",
-	"version": "0.5.0",
+	"version": "0.5.1",
 	"description": "Fleet & crew personas over cyberlegion — Pod (ship's bridge), Operator (command center), Crimp (crew recruitment), and Mechanic (automaton building).",
 	"author": {
 		"name": "unional"
@@ -13,8 +13,5 @@
 		"inter-agent",
 		"fleet"
 	],
-	"skills": "./skills",
-	"agents": [
-		"./agents/headless-operator.md"
-	]
+	"skills": "./skills"
 }

package/agents/headless-operator.md

@@ -83,7 +83,11 @@ all spawning is Operator's, and **Pod never spawns**, so there is no intra-missi
 contrast against. Never invoke a rule of the in-ship Pod persona; never type into a dispatched ship's
 pane. Dispatch is `cyberlegion unit spawn` with a brief
 that stands on its own (the new Pod starts cold and reads it through its own SessionStart hook) and
-`--at workspace` so each ship opens in its own workspace.
+`--at workspace` so each ship opens in its own workspace. The brief names its thread id and spells out
+the exact reply command, as the in-session Operator's does: `cyberlegion mail send --to <return handle>
+--thread <thread id> --subject "<done|blocked>: <work item>" --body "<pull request URL, CI state, anything held>"`,
+the same send with `--to operator` when the return handle resolves to no live unit, and never the
+harness's own messaging tool, which cannot reach cyberlegion handles.
 
 ## Report and ask via the relay
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cyberfleet",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "Harness-agnostic, MCP-free inter-agent sessions 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": "cyberfleet",
-	"version": "0.5.0",
+	"version": "0.5.1",
 	"description": "Fleet & crew personas over cyberlegion — Pod (ship's bridge), Operator (command center), Crimp (crew recruitment), and Mechanic (automaton building).",
 	"author": {
 		"name": "unional"

package/skills/operator/SKILL.md

@@ -65,6 +65,13 @@ connected wherever the Council invokes it, including inside a project an agent i
   this brief's thread to the return address when the work is done or blocked; **never merge** the pull request;
   and when told trunk moved, rebase onto it, adapt the work to what landed, re-verify, push, and report
   again.
+- Every brief spells out the **exact reply command** — the return address is a cyberlegion handle, and
+  a pod that is not told how to reach it reaches for its harness's own messaging tool, which cannot see
+  cyberlegion handles, so the report is lost. Name the thread id in the brief and write the command
+  out with it: `cyberlegion mail send --to <return handle> --thread <thread id> --subject "<done|blocked>: <work item>"
+  --body "<pull request URL, CI state, anything held>"`. Say not to use the harness's own messaging
+  tool (Claude Code's SendMessage and the like) for fleet handles. The fallback goes through the same
+  command: if the return handle resolves to no live unit, the same send with `--to operator`.
 - With the dispatch, **announce the merges** to the Council: say that you will merge each pull request of
   this order's pods once it is clean, name the four-part bar below, and ask the Council to reply before
   the first one lands. The Council's reply, in its own words, is what authorizes those merges — the order

package/skills/pod/SKILL.md

@@ -102,7 +102,10 @@ times out, stop and report the state as it stands. Never loop past the timeout.
 4. **Sweep once more on green.** Bots often post just after CI finishes. Read the comments again
    before reporting. If that sweep pushes a commit, the new head needs its own green.
 5. **Report** to whoever dispatched you, on the brief's thread (`cyberlegion mail send --to
-   <return address> --thread <id>`). Include the pull request URL; the CI result (green, red with the
+   <return address> --thread <thread id> --subject ... --body ...`). The return address is a cyberlegion
+   handle: never use the harness's own messaging tool (Claude Code's SendMessage and the like), whose
+   recipients are the harness's agents and cannot reach it. If the handle resolves to no live unit, send
+   the same command with `--to operator`. Include the pull request URL; the CI result (green, red with the
    failing check, or timed out); each finding and how it was handled (fixed with its commit, discarded
    with its reason, escalated); and anything that needs a human decision.
 6. **Tell your spawner when you are ready to discharge.** You are ready when all of these hold: the