buddy-agent-harness 0.22.0 → 1.0.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.
package/llms.txt CHANGED
@@ -8,7 +8,7 @@ A repository keeps one canonical agent configuration — a root `AGENTS.md` and
8
8
 
9
9
  Of the CLI's top-level commands, `doctor` and `governance` say they are read-only; `init`, `mcp`, `dep-plugins`, and `reference` can write.
10
10
 
11
- Every runnable command takes `--format` with `toon`, `json`, or `text`; the default is `toon`, except that `reference show`, `reference create`, `reference delete`, and `governance show` default to `text`.
11
+ Every runnable command takes `--format` with `toon`, `json`, or `text`; the default is `toon`, except that `reference load`, `reference create`, `reference delete`, and `governance show` default to `text`.
12
12
 
13
13
  Documentation site: [One canonical agent configuration](https://repobuddy.github.io/buddy-agent-harness/).
14
14
 
@@ -21,16 +21,16 @@ Documentation site: [One canonical agent configuration](https://repobuddy.github
21
21
  - [`buddy-agent-harness mcp project`](https://repobuddy.github.io/buddy-agent-harness/cli/mcp/): Project the golden MCP server set into each enabled harness. A dry run unless --write; never overwrites a change made on the harness side.
22
22
  - [`buddy-agent-harness mcp reconcile`](https://repobuddy.github.io/buddy-agent-harness/cli/mcp/): Import a harness-side MCP change into the golden set, one approved field at a time. A dry run unless --accept names a field.
23
23
  - [`buddy-agent-harness dep-plugins`](https://repobuddy.github.io/buddy-agent-harness/cli/dep-plugins/): Derive the marketplace catalog for plugins shipped by this repository’s dependencies, so a harness can install them. Writes the catalog; installing is the harness’s own job.
24
- - [`buddy-agent-harness reference`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Read reference documents by name, composed from the managed, project, user, plugin, and default tiers, and write, select, or delete a contribution.
25
- - [`buddy-agent-harness reference show`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Print one or more references, each composed from its contributions as their extends and merge declare.
24
+ - [`buddy-agent-harness reference`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Read reference documents by name, composed from the managed, repo, user, plugin, and default tiers, and create, customize, or delete a contribution.
25
+ - [`buddy-agent-harness reference load`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Print one or more references, each composed from its contributions as their extends and merge declare.
26
26
  - [`buddy-agent-harness reference list`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): List every reference name, one row each, with its description, and its status when not found. A pattern keeps only the names it matches exactly.
27
27
  - [`buddy-agent-harness reference search`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Find references by name, description, tags, headings, or body, best match first.
28
- - [`buddy-agent-harness reference where`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Give the project and user files a customization or a selection of a reference is written to, who each reaches, and the heading paths of the document below each.
29
- - [`buddy-agent-harness reference create`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Start a contribution in the project or user tier, or in a plugin's or a skill's source folder, from a template or an interface. Never overwrites a file with a body.
30
- - [`buddy-agent-harness reference select`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Choose what a name builds on: write an `extends` listing the options, bottom first, in the project or user file. Its body and other keys are kept.
31
- - [`buddy-agent-harness reference delete`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Delete a project or user contribution, or one in a plugin's or a skill's source folder, and report what answers the name afterwards. Never deletes an installed or managed one.
28
+ - [`buddy-agent-harness reference where`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Give the repo and user files, and with --in a folder's project section, a customization or a selection of a reference is written to, who each reaches and what hides it, the main document's heading paths, and the read-only plugins and default the stack uses.
29
+ - [`buddy-agent-harness reference create`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Start a contribution in the repo or user tier, a folder's project section, or a plugin's or a skill's source folder, from a template or an interface. Never overwrites a file with a body; writes a file a contribution above hides, with a warning.
30
+ - [`buddy-agent-harness reference customize`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Customize a name for the repo or user tier, or a folder's project section, running no model: pick what it builds on (`extends`), write a body generated from a request with its record, or print what the generator reads (--base). Writes a file a contribution above hides, with a warning.
31
+ - [`buddy-agent-harness reference delete`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Delete a repo or user contribution, a folder's project section, or one in a plugin's or a skill's source folder, with a non-Markdown file's metadata file, and report what answers the name afterwards. Never deletes an installed or managed one.
32
32
  - [`buddy-agent-harness reference implementations`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): List the implementations of an interface a consumer can load, each with its pin, description, and unsupported sections.
33
- - [`buddy-agent-harness reference check`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Check interface documents and their implementations, each composed as `show` composes it. With no names, checks every one found. Exits 1 on any failure.
33
+ - [`buddy-agent-harness reference check`](https://repobuddy.github.io/buddy-agent-harness/cli/reference/): Check references, each composed as `load` composes it: an interface document against its shape, an implementation against its interface, and every document for the defects composing it raises. With no names, checks every name found. Every warning `load` raises is reported. A failure is an entry in `failed`, not an error; a warning never fails a check.
34
34
  - [`buddy-agent-harness governance`](https://repobuddy.github.io/buddy-agent-harness/cli/governance/): Deprecated: use `reference`. Read the governance documents the project, user, and machine-wide override layers hold. Read-only.
35
35
  - [`buddy-agent-harness governance list`](https://repobuddy.github.io/buddy-agent-harness/cli/governance/): List every governance the override layers hold, each at the layer that would win.
36
36
  - [`buddy-agent-harness governance show`](https://repobuddy.github.io/buddy-agent-harness/cli/governance/): Print one governance document, resolved through the layers in order.
@@ -80,7 +80,7 @@ Documentation site: [One canonical agent configuration](https://repobuddy.github
80
80
  ## Optional
81
81
 
82
82
  - [Library: `cyber-agentkit`](https://repobuddy.github.io/buddy-agent-harness/library/references/): exports `listReferences`, `parseReferenceName`, `resolveReference`, `searchReferences`, type `MatchKind`, type `ReferenceLayer`, type `ReferenceListing`, type `ReferenceListLayerRow`, type `ReferenceListRow`, type `ReferenceName`, type `ReferenceStatus`, type `ReferenceTier`, type `ResolvedReference`, type `ResolveOptions`, type `SearchMatch`.
83
- - [Library: `cyber-agentkit/commands`](https://repobuddy.github.io/buddy-agent-harness/library/references/): exports type `ReferenceListReport`, type `ReferenceSearchReport`, type `ReferenceShowEntry`.
83
+ - [Library: `cyber-agentkit/commands`](https://repobuddy.github.io/buddy-agent-harness/library/references/): exports type `ReferenceListReport`, type `ReferenceLoadEntry`, type `ReferenceSearchReport`.
84
84
  - [Library: `cli.ts`](https://repobuddy.github.io/buddy-agent-harness/library/init/): exports `run`.
85
85
  - [Library: `diagnose-bridges/diagnose-bridges.ts`](https://repobuddy.github.io/buddy-agent-harness/library/doctor/): exports `diagnoseBridges`, type `BridgeFinding`, type `BridgeKind`, type `BridgeReport`, type `BridgeStatus`, type `DiagnoseOptions`, type `DiagnoseResult`, type `DivergenceReport`.
86
86
  - [Library: `diagnose-bridges/diagnose-global-instructions.ts`](https://repobuddy.github.io/buddy-agent-harness/library/doctor/): exports `diagnoseGlobalInstructions`, type `GlobalInstructionKind`, type `GlobalInstructionReport`, type `GlobalInstructionStatus`.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "buddy-agent-harness",
3
- "version": "0.22.0",
3
+ "version": "1.0.0",
4
4
  "description": "Initialize standards-based agent configuration across agent harnesses",
5
5
  "keywords": [
6
6
  "repobuddy",
@@ -41,22 +41,31 @@
41
41
  "llms.txt",
42
42
  ".claude-plugin",
43
43
  ".cursor-plugin",
44
- ".codex-plugin"
44
+ ".codex-plugin",
45
+ "CHANGELOG.md"
45
46
  ],
46
47
  "engines": {
47
48
  "node": ">=22"
48
49
  },
49
50
  "dependencies": {
50
- "clibuilder": "^12.0.0",
51
- "cyber-agentkit": "^1.0.0",
51
+ "cyber-agentkit": "^2.0.0",
52
52
  "jsonc-parser": "^3.3.1",
53
53
  "smol-toml": "^1.8.0",
54
54
  "toml-eslint-parser": "^1.0.3",
55
55
  "yaml": "^2.9.0"
56
56
  },
57
+ "peerDependencies": {
58
+ "clibuilder": "^12.1.0"
59
+ },
60
+ "peerDependenciesMeta": {
61
+ "clibuilder": {
62
+ "optional": true
63
+ }
64
+ },
57
65
  "devDependencies": {
58
- "@types/node": "^24.12.4",
66
+ "@types/node": "^26.0.0",
59
67
  "@vitest/coverage-v8": "^5.0.0",
68
+ "clibuilder": "^12.1.0",
60
69
  "tsdown": "^0.23.0",
61
70
  "tsx": "^4.22.3",
62
71
  "typescript": "^7.0.0",
package/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
3
3
  "name": "buddy-agent-harness",
4
- "version": "0.22.0",
4
+ "version": "1.0.0",
5
5
  "description": "Initialize standards-based agent configuration across agent harnesses",
6
6
  "author": {
7
7
  "name": "repobuddy"
@@ -7,7 +7,7 @@ Report whether the harness skill bridges in a repository still resolve into `.ag
7
7
  `init` points every harness that cannot read `.agents/skills` at that directory, normally with a directory-level symlink. `doctor` re-checks each of those bridges after the fact and names the repair for whatever it finds. The command names an `init` invocation for a person at a shell; the skill hands the same repair to the `init-buddy-agent-harness` skill, because rebuilding a bridge can move skills a user wrote.
8
8
 
9
9
  ```sh
10
- npx -y buddy-agent-harness@0.22.0 doctor
10
+ npx -y buddy-agent-harness@1.0.0 doctor
11
11
  ```
12
12
 
13
13
  ## Why it exists
@@ -17,7 +17,7 @@ Diagnose it:
17
17
  node scripts/doctor.mjs
18
18
  ```
19
19
 
20
- That path is relative to this skill's own directory: `scripts/doctor.mjs` is a self-contained bundle built from this package's source and shipped inside the skill folder through the npm package, so it runs against the current working directory with nothing downloaded and no `node_modules` needed. Fall back to `npx -y buddy-agent-harness@0.22.0 doctor` when `scripts/doctor.mjs` is missing or cannot be run — the case for a skill installed from git rather than from the npm package, which does not carry the bundle.
20
+ That path is relative to this skill's own directory: `scripts/doctor.mjs` is a self-contained bundle built from this package's source and shipped inside the skill folder through the npm package, so it runs against the current working directory with nothing downloaded and no `node_modules` needed. Fall back to `npx -y buddy-agent-harness@1.0.0 doctor` when `scripts/doctor.mjs` is missing or cannot be run — the case for a skill installed from git rather than from the npm package, which does not carry the bundle.
21
21
 
22
22
  The command is read-only. It never repairs anything, so it is safe to run at any point, including from a session-start hook.
23
23