agentbundle 0.33.1__tar.gz → 0.34.0__tar.gz

{agentbundle-0.33.1/agentbundle.egg-info → agentbundle-0.34.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentbundle
-Version: 0.33.1
+Version: 0.34.0
 Summary: npm for your coding agent. Install packs of skills, subagents, and hooks into any repo, for every major agent.
 Author-email: eugenelim <eugenelim@users.noreply.github.com>
 License-Expression: Apache-2.0 OR MIT
@@ -34,12 +34,25 @@ python -m pip install agentbundle
 
 Requires Python 3.11+. Runs on macOS, Linux, and Windows.
 
-## What's new in 0.33.1
+## What's new in 0.34.0
 
-If you maintain a catalogue with repository-level tests, `agentbundle catalogue
-verify --root .` now recognizes the top-level `tests/` tree as
-repository-owned. Those paths no longer produce `[info] unclassified` notices;
-genuinely unknown paths still do, and the notices remain informational.
+Inspect the exact public contracts bundled with the installed AgentBundle
+version without network access:
+
+```bash
+agentbundle catalogue contracts list
+agentbundle catalogue contracts show pack.schema.json
+agentbundle catalogue contracts export --output ./reference-contracts
+```
+
+`list` and `show` are read-only. `export` writes reference copies through a
+no-follow, preflighted batch writer; those copies do not override the contracts
+AgentBundle uses for validation.
+
+Successful `agentbundle catalogue init` output now points to the scaffolded
+`guides/_shared/reference/catalogue-authoring-standards.md`, contract discovery,
+and catalogue verification. The guide's bundled-contract section documents all
+three commands. JSON init output remains unchanged.
 
 **Install into a repo** — so everyone who clones it gets the pack. `core` is the flagship pack, the loop itself:
 
@@ -258,6 +271,10 @@ agentbundle catalogue init --target /path/to/new-catalogue
 
 Scaffolds `catalogue.toml`, the required directory tree (`packs/`, `profiles/`, `contracts/`, `.claude-plugin/`), and a starter `marketplace.json`. Skips files that already exist; reports conflicts without overwriting. Pass `--dry-run` to preview.
 
+After initialization, use `agentbundle catalogue contracts list` to find the
+contract names bundled with your installed version. `show` prints one contract;
+`export --output <dir>` copies the full public set for offline reference.
+
 **Bootstrap a self-hosted enterprise catalogue** from an existing source:
 
 ```bash
@@ -461,6 +478,9 @@ python3 -m agentbundle.workspace_mcp
 > spawn mode (`python3 -I -m agentbundle.workspace_mcp`) is planned for
 > Stage 2 and will require a stable non-editable install.
 
+In trusted mode, workspace status prefers an installed core-pack projection and
+falls back to the byte-identical engine projection bundled with `agentbundle`.
+
 **Inject the session instruction** so the agent knows to use the tools:
 
 ```python

{agentbundle-0.33.1 → agentbundle-0.34.0}/README-pypi.md

@@ -14,12 +14,25 @@ python -m pip install agentbundle
 
 Requires Python 3.11+. Runs on macOS, Linux, and Windows.
 
-## What's new in 0.33.1
+## What's new in 0.34.0
 
-If you maintain a catalogue with repository-level tests, `agentbundle catalogue
-verify --root .` now recognizes the top-level `tests/` tree as
-repository-owned. Those paths no longer produce `[info] unclassified` notices;
-genuinely unknown paths still do, and the notices remain informational.
+Inspect the exact public contracts bundled with the installed AgentBundle
+version without network access:
+
+```bash
+agentbundle catalogue contracts list
+agentbundle catalogue contracts show pack.schema.json
+agentbundle catalogue contracts export --output ./reference-contracts
+```
+
+`list` and `show` are read-only. `export` writes reference copies through a
+no-follow, preflighted batch writer; those copies do not override the contracts
+AgentBundle uses for validation.
+
+Successful `agentbundle catalogue init` output now points to the scaffolded
+`guides/_shared/reference/catalogue-authoring-standards.md`, contract discovery,
+and catalogue verification. The guide's bundled-contract section documents all
+three commands. JSON init output remains unchanged.
 
 **Install into a repo** — so everyone who clones it gets the pack. `core` is the flagship pack, the loop itself:
 
@@ -238,6 +251,10 @@ agentbundle catalogue init --target /path/to/new-catalogue
 
 Scaffolds `catalogue.toml`, the required directory tree (`packs/`, `profiles/`, `contracts/`, `.claude-plugin/`), and a starter `marketplace.json`. Skips files that already exist; reports conflicts without overwriting. Pass `--dry-run` to preview.
 
+After initialization, use `agentbundle catalogue contracts list` to find the
+contract names bundled with your installed version. `show` prints one contract;
+`export --output <dir>` copies the full public set for offline reference.
+
 **Bootstrap a self-hosted enterprise catalogue** from an existing source:
 
 ```bash
@@ -441,6 +458,9 @@ python3 -m agentbundle.workspace_mcp
 > spawn mode (`python3 -I -m agentbundle.workspace_mcp`) is planned for
 > Stage 2 and will require a stable non-editable install.
 
+In trusted mode, workspace status prefers an installed core-pack projection and
+falls back to the byte-identical engine projection bundled with `agentbundle`.
+
 **Inject the session instruction** so the agent knows to use the tools:
 
 ```python

{agentbundle-0.33.1 → agentbundle-0.34.0}/agentbundle/_data/catalogue-scaffold/guides/_shared/reference/catalogue-authoring-standards.md

@@ -407,6 +407,23 @@ every optional pack.
 
 ---
 
+## 12. Bundled contract inspection
+
+List, inspect, or export the contracts bundled with the running AgentBundle version
+without network access:
+
+```bash
+agentbundle catalogue contracts list
+agentbundle catalogue contracts show <name>
+agentbundle catalogue contracts export --output <dir>
+```
+
+`list` and `show` are read-only. `export` writes one regular file per listed contract
+to the selected directory. These are reference copies only. They do not override the
+contracts used for validation by this agentbundle version.
+
+---
+
 ## Journey format
 
 > **Not yet available.** Wave 4 of the catalogue-contracts initiative will define the

{agentbundle-0.33.1 → agentbundle-0.34.0}/agentbundle/_data/catalogue-scaffold/manifest.json

@@ -1,6 +1,6 @@
 {
   "files": {
-    "guides/_shared/reference/catalogue-authoring-standards.md": "ff4bdc203affda0a2f41641c1155b3f4e90aade022e122999a82e7093e94d2ee",
+    "guides/_shared/reference/catalogue-authoring-standards.md": "3217e6bfcc15dc116d40e1b327b6bf19b66212c7e13553e42966f9982b3c3487",
     "guides/_shared/reference/catalogue-ci-contract.md": "fae793ab47989b6dd3c731afcb0b4cda21c7d08bbe7fa40fca6d3abb3d158141",
     "packs/AGENTS.md": "9bfeda4069826e518a4f4fdae45bd40f4393c1c5aaf146149d3eb4aece30be83",
     "packs/README.md": "d2de5f9556f4c8e521103474bde74636e02cc805f9bf5312a3a61a1f3eb45d8f",

agentbundle-0.34.0/agentbundle/_data/public-contracts.txt

@@ -0,0 +1,12 @@
+adapter.schema.json
+adapter.toml
+catalogue.schema.json
+guide.schema.json
+marketplace-entry.schema.json
+pack.schema.json
+plugin-manifest.derived.schema.json
+plugin-manifest.schema.json
+profile.schema.json
+skill-manifest.schema.json
+skill.schema.json
+target-vocab.toml