cyberfleet 0.6.0 → 0.8.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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cyberfleet",
3
- "version": "0.6.0",
3
+ "version": "0.8.0",
4
4
  "description": "Fleet & crew personas over cyberlegion — Pod (ship's bridge), Operator (command center), Crimp (crew recruitment), and Mechanic (automaton building).",
5
5
  "author": {
6
6
  "name": "unional"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cyberfleet",
3
- "version": "0.6.0",
3
+ "version": "0.8.0",
4
4
  "description": "Fleet & crew personas over cyberlegion — Pod (ship's bridge), Operator (command center), Crimp (crew recruitment), and Mechanic (automaton building).",
5
5
  "author": {
6
6
  "name": "unional"
package/.plugin/pins.json CHANGED
@@ -1,3 +1,3 @@
1
1
  {
2
- "cyberlegion": "1.1.0"
2
+ "cyberlegion": "1.7.0"
3
3
  }
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # cyberfleet
2
2
 
3
+ ## 0.8.0
4
+
5
+ ### Minor Changes
6
+
7
+ - d5e7c75: Rewrite the `close-sessions` skill: it acts only on units in the caller's multiplexer, fetches pull requests once per repository instead of once per unit, and asks each live unit that passes the mechanical close whether it has unfinished work (by mail) instead of inspecting transcripts. A reply can only keep a unit.
8
+ - 70e6817: `cyberfleet jump` now does `/jump`'s deterministic work, and the `/jump` skill needs only `cyberfleet`. **Breaking:** its arguments and output changed. `cyberfleet jump <target> [--repo <name>] [--branch <name>]... [--mentions <n>]` focuses the one live unit an id, handle, branch, or repo name equals, follows the jump history on `back`, and otherwise prints `candidates`, a `task` (repo, `<owner>/<repo>` from `origin`, number), or `prose` (the live units, for the skill to match) without focusing anything. It never focuses the calling session and never picks among several matches. It no longer prints a worktree path when a unit has no pane; it fails instead. cyber-mux is now bundled into the CLI, so `/jump back` works when the `cyber-mux` on `PATH` is old or missing.
9
+
10
+ ### Patch Changes
11
+
12
+ - f4490e6: `/jump` no longer fails as ambiguous when the calling session is one of the units a repo or branch matches: it jumps to the one other unit by id. The skill also says the task form needs GitHub and an authenticated `gh`, reads this session's id as JSON, and checks its result against the fleet list before reporting.
13
+
14
+ ## 0.7.0
15
+
16
+ ### Minor Changes
17
+
18
+ - ddaf2a0: Add the `close-sessions` skill: a mechanical sweep that closes every agent session whose branch's pull requests have all landed, and keeps every session that might still have work.
19
+ - 9f663f9: Add the `jump` skill: `/jump [repo|branch|pod|task|back|<prose>]` moves the view to the one pane working on what the argument names, through `cyberlegion unit focus`, and `/jump back` returns through cyber-mux's jump history. More than one match lists the candidates and stops.
20
+
3
21
  ## 0.6.0
4
22
 
5
23
  ### Minor Changes
@@ -113,7 +113,7 @@ the Operator's; the per-unit spawn mechanism is cyberlegion's.
113
113
  Every `cyberlegion …` command in this loop runs whichever CLI resolves below, resolved afresh in each
114
114
  session and again after any plugin reload. Never hardcode a versioned
115
115
  `~/.claude/plugins/cache/…/<version>/` path: a reload installs a new version beside the old one, and a
116
- remembered path keeps running the old CLI. The pin is `1.1.0`. Take the first rung that
116
+ remembered path keeps running the old CLI. The pin is `1.7.0`. Take the first rung that
117
117
  resolves and whose `cyberlegion --version` is at or above it; skip a rung that reports an older
118
118
  version:
119
119
 
@@ -121,11 +121,11 @@ version:
121
121
  2. The installed cyberlegion plugin: read `~/.claude/plugins/installed_plugins.json` now, take the
122
122
  `installPath` of its `cyberlegion@<marketplace>` entry, and run `node
123
123
  <installPath>/bin/cyberlegion.mjs`.
124
- 3. `npx -y cyberlegion@1.1.0`.
124
+ 3. `npx -y cyberlegion@1.7.0`.
125
125
 
126
126
  When no rung resolves, stop the tick and report it up the relay with the
127
127
  install hint: install the `cyberlegion` plugin beside this one, or `npm install -g
128
- cyberlegion@1.1.0`.
128
+ cyberlegion@1.7.0`.
129
129
 
130
130
  ## Stateless per tick
131
131