cyberlegion 0.4.0 → 0.5.0

package/skills/relay-governance/SKILL.md

@@ -12,6 +12,11 @@ lifecycle, the same way `dispatch-governance` forces `run-inline` from "do I hav
 contract is loaded by `dispatch-governance` (to relay a callee's `needsInput`) and by every headless
 agent (`headless-legate`, `sdd-automaton`, the cold judges) to know how *it* reports.
 
+> **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@0.5.0`.
+
 ## The one probe: who, if anyone, collects my return?
 
 A model is not running between turns. Whatever a headless agent emits must reach a collector, or be
@@ -50,7 +55,7 @@ exiting. Resolve the owner recipient in this order:
 Then:
 
 ```bash
-npx cyberlegion@0.3.1 mail send --to <owner> --subject "<what>" --body-file <report> [--thread <t>]
+node scripts/cyberlegion.mjs mail send --to <owner> --subject "<what>" --body-file <report> [--thread <t>]
 ```
 
 and **exit**. Do not park waiting for a live answer — a cron session has no one to answer live. The
@@ -135,7 +140,7 @@ the receiver's **own owner** — the unit that dispatched it — **and** the dec
 session by whoever is already in position to do so). Either one alone leaves it a peer steer. It is
 then adoptable **within its named scope and nothing adjacent**, provided it carries **four parts**:
 
-1. the **Council's verbatim words** — what the position holding the user channel actually said,
+1. the **user-channel holder's verbatim words** — what the position holding the user channel actually said,
    quoted, not summarized;
 2. **where they were said** — the session, thread, or artifact the words came from;
 3. the **relaying unit** — who is passing it down;

package/skills/relay-governance/scripts/cyberlegion.mjs

@@ -0,0 +1,31 @@
+#!/usr/bin/env node
+// Runs the cyberlegion CLI this plugin ships, so the skill beside it never fetches a copy through npx.
+// The package root is three levels up from this file (skills/<skill>/scripts/), resolved from the
+// file's own location: the working directory is the repository the agent is working on, not the plugin.
+// Arguments, output, and the exit code pass straight through the package's bin.
+//
+// A skill folder installed on its own has no package around it. Then this runs the published CLI of
+// the version that shipped the skill instead, so the skill still works, only slower. The version sync
+// run at release keeps FALLBACK at the package version.
+import { spawnSync } from 'node:child_process'
+import { existsSync } from 'node:fs'
+import { fileURLToPath } from 'node:url'
+
+const FALLBACK = 'npx -y cyberlegion@0.5.0'
+const bin = new URL('../../../bin/cyberlegion.mjs', import.meta.url)
+
+if (existsSync(fileURLToPath(bin))) {
+	await import(bin.href)
+} else {
+	process.stderr.write(`cyberlegion: no plugin package around this skill; running ${FALLBACK}\n`)
+	const [command, ...args] = FALLBACK.split(' ')
+	const res = spawnSync(command, [...args, ...process.argv.slice(2)], {
+		stdio: 'inherit',
+		shell: process.platform === 'win32',
+	})
+	if (res.error) {
+		process.stderr.write(`cyberlegion: could not run ${FALLBACK}: ${res.error.message}\n`)
+		process.exit(1)
+	}
+	process.exit(res.status ?? 1)
+}

package/skills/subagent-backend-governance/SKILL.md

@@ -11,10 +11,15 @@ one-shot unit with no live user channel, spawned through the caller's own Task t
 always in this order. What may reach that unit **mid-flight** is not decided by this backend but by
 the unit's **role** — see *Mid-turn messaging is scoped by role*, below.
 
+> **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@0.5.0`.
+
 ## 1. Resolve the agent def
 
 ```bash
-npx cyberlegion@0.3.1 agent resolve <R> --format json
+node scripts/cyberlegion.mjs agent resolve <R> --format json
 ```
 
 Returns `model`, `effort`, `harness`, and `instructions` for role `R`. `cyberlegion` allocates no

package/skills/subagent-backend-governance/scripts/cyberlegion.mjs

@@ -0,0 +1,31 @@
+#!/usr/bin/env node
+// Runs the cyberlegion CLI this plugin ships, so the skill beside it never fetches a copy through npx.
+// The package root is three levels up from this file (skills/<skill>/scripts/), resolved from the
+// file's own location: the working directory is the repository the agent is working on, not the plugin.
+// Arguments, output, and the exit code pass straight through the package's bin.
+//
+// A skill folder installed on its own has no package around it. Then this runs the published CLI of
+// the version that shipped the skill instead, so the skill still works, only slower. The version sync
+// run at release keeps FALLBACK at the package version.
+import { spawnSync } from 'node:child_process'
+import { existsSync } from 'node:fs'
+import { fileURLToPath } from 'node:url'
+
+const FALLBACK = 'npx -y cyberlegion@0.5.0'
+const bin = new URL('../../../bin/cyberlegion.mjs', import.meta.url)
+
+if (existsSync(fileURLToPath(bin))) {
+	await import(bin.href)
+} else {
+	process.stderr.write(`cyberlegion: no plugin package around this skill; running ${FALLBACK}\n`)
+	const [command, ...args] = FALLBACK.split(' ')
+	const res = spawnSync(command, [...args, ...process.argv.slice(2)], {
+		stdio: 'inherit',
+		shell: process.platform === 'win32',
+	})
+	if (res.error) {
+		process.stderr.write(`cyberlegion: could not run ${FALLBACK}: ${res.error.message}\n`)
+		process.exit(1)
+	}
+	process.exit(res.status ?? 1)
+}