buddy-agent-harness 0.10.0 → 0.12.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
 	"name": "buddy-agent-harness",
-	"version": "0.10.0",
+	"version": "0.12.0",
 	"description": "Initialize standards-based agent configuration across agent harnesses",
 	"author": {
 		"name": "repobuddy"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
 	"name": "buddy-agent-harness",
-	"version": "0.10.0",
+	"version": "0.12.0",
 	"description": "Initialize standards-based agent configuration across agent harnesses",
 	"author": {
 		"name": "repobuddy"

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
 	"name": "buddy-agent-harness",
-	"version": "0.10.0",
+	"version": "0.12.0",
 	"description": "Initialize standards-based agent configuration across agent harnesses",
 	"author": {
 		"name": "repobuddy"

package/README.md

@@ -9,7 +9,7 @@ An agent plugin and CLI for initializing or updating a consumer repository's sta
 
 ## Install the plugin
 
-In Claude Code, add the [cyberplace](https://github.com/cyberuni/cyberplace) marketplace and install the plugin and its `init` skill:
+In Claude Code, add the [cyberplace](https://github.com/cyberuni/cyberplace) marketplace and install the plugin and its `init-buddy-agent-harness` skill:
 
 ```text
 /plugin marketplace add cyberuni/cyberplace
@@ -18,7 +18,7 @@ In Claude Code, add the [cyberplace](https://github.com/cyberuni/cyberplace) mar
 
 ## CLI
 
-`init` runs behind the `init` skill, which sorts the configuration you already wrote before the command links anything. Install the package alongside `repobuddy` to mount every command on `buddy`, as `buddy agent-harness doctor`, `buddy agent-harness init`, and `buddy agent-harness dep-plugins`.
+`init` runs behind the `init-buddy-agent-harness` skill, which sorts the configuration you already wrote before the command links anything. Install the package alongside `repobuddy` to mount every command on `buddy`, as `buddy agent-harness doctor`, `buddy agent-harness init`, and `buddy agent-harness dep-plugins`.
 
 The repository root's `AGENTS.md` and `.agents/` tree are canonical: `.agents/AGENTS.md` holds shared behavior, `.agents/skills/**/SKILL.md` holds capabilities, and separately named files hold tool settings. The active harness is enabled by default; explicit user preferences add others. The command preserves user-authored configuration and projects only supported mappings; it records nothing on disk.
 

package/bin/buddy-agent-harness.mjs

@@ -3,10 +3,11 @@ import { dirname, join } from 'node:path'
 import { fileURLToPath, pathToFileURL } from 'node:url'
 
 const dir = dirname(fileURLToPath(import.meta.url))
+// `dist/cli.mjs`, and each shipped skill's own bundle, are built by `pnpm build` (see
+// `tsdown.config.ts`) and are not committed.
 const { run } = await import(pathToFileURL(join(dir, '..', 'dist', 'cli.mjs')).href)
 
-// The process boundary: the only place that reads `process.argv` or writes `process.exitCode`.
-// Applied only when non-zero, so a usage code `clibuilder` recorded itself is not overwritten by
-// the zero `run` returns on that path.
+// The process boundary — the only place that reads `process.argv` or writes `process.exitCode`.
+// Applied only when non-zero: clibuilder already sets it itself on an unknown option/command.
 const code = await run(process.argv)
 if (code !== 0) process.exitCode = code