agentbundle 0.22.1__tar.gz → 0.27.1__tar.gz

{agentbundle-0.22.1 → agentbundle-0.27.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentbundle
-Version: 0.22.1
+Version: 0.27.1
 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: Apache-2.0 OR MIT
@@ -144,7 +144,7 @@ rollback. Never silently downgrades an `ahead` row.
 **Package your catalogue for Artifactory:**
 
 ```bash
-agentbundle package-catalogue \
+agentbundle catalogue package \
   --root /path/to/catalogue \
   --bundle my-packs \
   --release 1.0.0 \
@@ -156,6 +156,19 @@ Produces a deterministic, reproducible gzip archive (versioned) and a mutable ch
 descriptor JSON (`stable.json`), ready to upload to Artifactory. Identical inputs
 produce byte-identical archives (honors `SOURCE_DATE_EPOCH`).
 
+**Source distribution for air-gapped or self-hosted catalogues:**
+
+```bash
+agentbundle catalogue package \
+  --root /path/to/catalogue \
+  --bundle my-packs \
+  --release 1.0.0 \
+  --flavor source \
+  --output dist/
+```
+
+Produces a `catalogue-source-<release>.tar.gz` from a positive allowlist (packs, profiles, guides, marketplace manifest, legal files). Includes a `self-hosted-source-manifest.json` with per-file SHA-256 digests and provenance fields. `agentbundle install` refuses to install a source archive, preventing accidental misuse.
+
 **Org bootstrap — ship the default channel in your fork:**
 
 Add an `[organization.artifactory]` block to
@@ -187,7 +200,31 @@ disconnected hosts, and security controls).
 
 ## Build your own catalogue
 
-`agentbundle` isn't tied to the agent-ready-repo catalogue. Any repo that lays its packs out the same way can use it. A pack is a directory:
+`agentbundle` isn't tied to the agent-ready-repo catalogue. Any repo that lays its packs out the same way can use it.
+
+**Bootstrap a new catalogue** in an empty directory:
+
+```bash
+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.
+
+**Bootstrap a self-hosted enterprise catalogue** from an existing source:
+
+```bash
+agentbundle catalogue init \
+  --preset self-hosted \
+  --source /path/to/source-catalogue.tar.gz \
+  --tooling vendored \
+  --attribution white-label \
+  --repository-url https://github.com/your-org/your-catalogue \
+  --owner-email admin@example.com
+```
+
+Copies selected packs and profiles from the source archive, generates `catalogue.toml` with your identity, runs a fail-closed leak check, and writes `.agentbundle/self-host-state.json` to track managed files. `--tooling vendored` also copies the `agentbundle` source and `catalogue-curation` pack into `.agentbundle/tooling/` for air-gapped deployments. Re-run to apply updates; stale owned files are removed (sha256-guarded, user-modified files are skipped).
+
+A pack is a directory:
 
 ```text
 my-pack/
@@ -226,6 +263,11 @@ preferred_adapter = "cursor"
 
 The org hint fires after the user-config but before the on-disk IDE probe — so `--adapter`, user-config, and upgrade state-hints all take priority. An invalid value exits 1 before writing anything. See the [`agentbundle` reference](https://github.com/eugenelim/agent-ready-repo/blob/main/docs/guides/_shared/reference/agentbundle.md#org-adapter-default) for the full cascade.
 
+**Bundled contracts** — the wheel ships the machine contracts used for offline validation:
+`pack.schema.json`, `skill.schema.json`, `guide.schema.json`, `skill-manifest.schema.json`,
+`profile.schema.json`, `catalogue.schema.json`, `target-vocab.toml`, and the adapter
+contract files. All are available without network access via `importlib.resources`.
+
 **Lint your catalogue** — shallow structural checks run without extra dependencies:
 
 ```bash
@@ -239,6 +281,14 @@ pip install 'agentbundle[lint]'
 agentbundle catalogue lint --root . --deep
 ```
 
+**Check self-host projection drift** — verifies that adapter-projected files (skills, agents, hooks) match their `.apm/` sources without writing anything:
+
+```bash
+agentbundle catalogue self-host --check --root .
+```
+
+Exits non-zero if any projected file is out of date. Safe to run in CI as a required check; use `--write` locally to regenerate.
+
 **Run Tier-A activation evals** to measure whether each covered skill fires on the prompts it should:
 
 ```bash

{agentbundle-0.22.1 → agentbundle-0.27.1}/README-pypi.md

@@ -122,7 +122,7 @@ rollback. Never silently downgrades an `ahead` row.
 **Package your catalogue for Artifactory:**
 
 ```bash
-agentbundle package-catalogue \
+agentbundle catalogue package \
   --root /path/to/catalogue \
   --bundle my-packs \
   --release 1.0.0 \
@@ -134,6 +134,19 @@ Produces a deterministic, reproducible gzip archive (versioned) and a mutable ch
 descriptor JSON (`stable.json`), ready to upload to Artifactory. Identical inputs
 produce byte-identical archives (honors `SOURCE_DATE_EPOCH`).
 
+**Source distribution for air-gapped or self-hosted catalogues:**
+
+```bash
+agentbundle catalogue package \
+  --root /path/to/catalogue \
+  --bundle my-packs \
+  --release 1.0.0 \
+  --flavor source \
+  --output dist/
+```
+
+Produces a `catalogue-source-<release>.tar.gz` from a positive allowlist (packs, profiles, guides, marketplace manifest, legal files). Includes a `self-hosted-source-manifest.json` with per-file SHA-256 digests and provenance fields. `agentbundle install` refuses to install a source archive, preventing accidental misuse.
+
 **Org bootstrap — ship the default channel in your fork:**
 
 Add an `[organization.artifactory]` block to
@@ -165,7 +178,31 @@ disconnected hosts, and security controls).
 
 ## Build your own catalogue
 
-`agentbundle` isn't tied to the agent-ready-repo catalogue. Any repo that lays its packs out the same way can use it. A pack is a directory:
+`agentbundle` isn't tied to the agent-ready-repo catalogue. Any repo that lays its packs out the same way can use it.
+
+**Bootstrap a new catalogue** in an empty directory:
+
+```bash
+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.
+
+**Bootstrap a self-hosted enterprise catalogue** from an existing source:
+
+```bash
+agentbundle catalogue init \
+  --preset self-hosted \
+  --source /path/to/source-catalogue.tar.gz \
+  --tooling vendored \
+  --attribution white-label \
+  --repository-url https://github.com/your-org/your-catalogue \
+  --owner-email admin@example.com
+```
+
+Copies selected packs and profiles from the source archive, generates `catalogue.toml` with your identity, runs a fail-closed leak check, and writes `.agentbundle/self-host-state.json` to track managed files. `--tooling vendored` also copies the `agentbundle` source and `catalogue-curation` pack into `.agentbundle/tooling/` for air-gapped deployments. Re-run to apply updates; stale owned files are removed (sha256-guarded, user-modified files are skipped).
+
+A pack is a directory:
 
 ```text
 my-pack/
@@ -204,6 +241,11 @@ preferred_adapter = "cursor"
 
 The org hint fires after the user-config but before the on-disk IDE probe — so `--adapter`, user-config, and upgrade state-hints all take priority. An invalid value exits 1 before writing anything. See the [`agentbundle` reference](https://github.com/eugenelim/agent-ready-repo/blob/main/docs/guides/_shared/reference/agentbundle.md#org-adapter-default) for the full cascade.
 
+**Bundled contracts** — the wheel ships the machine contracts used for offline validation:
+`pack.schema.json`, `skill.schema.json`, `guide.schema.json`, `skill-manifest.schema.json`,
+`profile.schema.json`, `catalogue.schema.json`, `target-vocab.toml`, and the adapter
+contract files. All are available without network access via `importlib.resources`.
+
 **Lint your catalogue** — shallow structural checks run without extra dependencies:
 
 ```bash
@@ -217,6 +259,14 @@ pip install 'agentbundle[lint]'
 agentbundle catalogue lint --root . --deep
 ```
 
+**Check self-host projection drift** — verifies that adapter-projected files (skills, agents, hooks) match their `.apm/` sources without writing anything:
+
+```bash
+agentbundle catalogue self-host --check --root .
+```
+
+Exits non-zero if any projected file is out of date. Safe to run in CI as a required check; use `--write` locally to regenerate.
+
 **Run Tier-A activation evals** to measure whether each covered skill fires on the prompts it should:
 
 ```bash

{agentbundle-0.22.1 → agentbundle-0.27.1}/README.md

@@ -118,7 +118,7 @@ rollback. Never silently downgrades an `ahead` row.
 **Package your catalogue for Artifactory:**
 
 ```bash
-agentbundle package-catalogue \
+agentbundle catalogue package \
   --root /path/to/catalogue \
   --bundle my-packs \
   --release 1.0.0 \
@@ -130,6 +130,10 @@ Produces a deterministic, reproducible gzip archive (versioned) and a mutable ch
 descriptor JSON (`stable.json`), ready to upload to Artifactory. Identical inputs
 produce byte-identical archives (honors `SOURCE_DATE_EPOCH`).
 
+For the full CI pipeline contract — publication ordering, exit codes, and the responsibility
+boundary between the CLI and your CI system — see the
+[Catalogue CI contract](https://github.com/eugenelim/agent-ready-repo/blob/main/guides/_shared/reference/catalogue-ci-contract.md).
+
 **Org bootstrap — ship the default channel in your fork:**
 
 Add an `[organization.artifactory]` block to

agentbundle-0.27.1/agentbundle/_data/catalogue-scaffold/guides/_shared/reference/catalogue-authoring-standards.md

@@ -0,0 +1,192 @@
+---
+title: "Catalogue authoring standards"
+summary: "Routing table for every catalogue authoring standard: pack manifests, skill frontmatter, profile format, lint and verify commands, CI contract, and packaging."
+pack: _shared
+kind: reference
+status: stable
+---
+
+# Catalogue authoring standards
+
+Machine contracts in `contracts/` are normative. These guides explain how to use them.
+
+Each section below names the authoritative contract and points to the guide that
+explains it. When a guide and its contract disagree, the contract is right.
+
+---
+
+## 1. Catalogue manifest
+
+**Contract:** `contracts/catalogue.schema.json`
+
+- `guides/_shared/how-to/create-a-catalogue.md` — scaffold a new catalogue with
+  `agentbundle catalogue init`.
+- `guides/_shared/how-to/create-external-catalogue.md` — self-hosted or enterprise-deployed
+  variant. (Available in the full guide library; not bundled in this scaffold.)
+
+---
+
+## 2. Pack manifest
+
+**Contract:** `contracts/pack.schema.json`
+
+The `pack.toml` file at the root of every pack. Required fields: `[pack]` with `name`
+and `version`; `[pack.adapter-contract]` with `version`.
+
+- [packs/README.md](../../../packs/README.md) — pack layout, versioning rules, lint commands.
+- [packs/AGENTS.md](../../../packs/AGENTS.md) — agent-facing schema map and primary workflow.
+
+---
+
+## 3. Pack README standard
+
+A pack README serves adopters, not contributors. It states the pack's intent and the
+user journey it serves — not a skill inventory. See the `_example` pack for a template.
+
+- [packs/_example/README.md](../../../packs/_example/README.md) — canonical example.
+
+---
+
+## 4. Pack layout
+
+Primitive sources live under `.apm/` and are projected per adapter by `catalogue self-host`.
+
+| Source directory | Primitive type |
+|------------------|----------------|
+| `.apm/skills/` | Skills |
+| `.apm/agents/` | Subagents |
+| `.apm/hooks/` | Hook bodies |
+| `.apm/hook-wiring/` | Hook wiring |
+| `.apm/commands/` | Commands |
+
+---
+
+## 5. Skill frontmatter and body
+
+**Contract:** `contracts/skill.schema.json`
+
+Every skill is a Markdown file with YAML frontmatter. Required frontmatter keys:
+`title`, `description` (≤ 1024 characters), `kind`.
+
+- `guides/_shared/how-to/author-a-skill.md` — frontmatter key list, body structure,
+  naming rules, progressive-disclosure pattern, three-tier dependency policy, and eval
+  coverage. (Available in the full guide library; not bundled in this scaffold.)
+
+---
+
+## 6. Skill body and progressive disclosure
+
+Long skills use progressive disclosure: a brief required-reading summary at the top,
+with detail sections the agent loads on demand. This keeps context usage bounded.
+
+See `guides/_shared/how-to/author-a-skill.md` for the full pattern.
+
+---
+
+## 7. Profile format
+
+**Contract:** `contracts/profile.schema.json`
+
+A profile is a blessed combination of packs installed in a single command.
+
+- [profiles/README.md](../../../profiles/README.md) — profile layout and authoring rules.
+- [profiles/AGENTS.md](../../../profiles/AGENTS.md) — agent-facing schema map.
+- `guides/_shared/how-to/design-a-profile.md` — step-by-step authoring guide. (Available
+  in the full guide library; not bundled in this scaffold.)
+
+---
+
+## 8. Lint and verify commands
+
+```bash
+agentbundle catalogue lint --root .           # style and basic correctness
+agentbundle catalogue verify --root .         # full validation (lint + schema + self-host drift)
+agentbundle catalogue self-host --root . --check  # scaffold projection drift check
+```
+
+Run all three before opening a PR. The CI contract (section 9) details the exit codes.
+
+---
+
+## 9. CI contract
+
+**Contract:** `contracts/catalogue-ci-contract.md` (in this scaffold)
+
+Provider-neutral validation, packaging, publication, and evidence requirements for a
+catalogue CI pipeline.
+
+- [catalogue-ci-contract.md](catalogue-ci-contract.md) — exit codes, required steps,
+  evidence manifest.
+
+---
+
+## 10. Package and publication
+
+```bash
+agentbundle catalogue package --root . --output dist/
+```
+
+Produces a distributable archive with a content manifest. See the CI contract (section 9)
+for the full pipeline sequence.
+
+---
+
+## 11. Optional pack integrations
+
+**Contract:** `contracts/pack.schema.json` (`[[pack.integrations]]` array)
+
+A pack can declare optional behavior seams with other packs using the
+`[[pack.integrations]]` array table in `pack.toml`. The entire array is
+optional — packs without integrations remain fully valid and installable.
+
+**The ten fields** (all fields in each entry are required except `version`):
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `id` | string | yes | Unique kebab-case identifier within this pack |
+| `pack` | string | yes | Name of the target pack |
+| `kind` | string | yes | One of: `input`, `augment`, `review`, `handoff` |
+| `role` | string | yes | Short user-facing label for this integration |
+| `consumers` | string[] | yes | Type-qualified primitive refs in the declaring pack |
+| `providers` | string[] | yes | Type-qualified primitive refs in the target pack |
+| `when` | string | yes | Human-readable conditions under which this seam activates |
+| `purpose` | string | yes | What the integration achieves when active |
+| `fallback` | string | yes | What the consuming skill does when the target pack is absent |
+| `version` | string | no | Semver range of the target pack version |
+
+**The four `kind` values:**
+
+- `input` — the target provides an artifact the declaring pack's skill reads
+- `augment` — the target pack's skill is inlined into the consuming skill's workflow
+- `review` — the target pack's agent or skill is invoked as a reviewer pass
+- `handoff` — the consuming skill passes control to the target at a defined boundary
+
+**What integrations are not:**
+
+No auto-install (declaring an integration does not install the target pack), no
+dependency closure (`[pack.dependencies]` owns hard requirements), no executable
+`when` expressions (the `when` field is explanatory text only).
+
+**The `fallback` requirement:**
+
+Every integration must declare what the consuming skill does when the target is
+absent. An agent reading the integration without the target installed needs to
+know how to proceed.
+
+**Lint and verify:**
+
+```bash
+agentbundle catalogue verify --root .
+```
+
+Primitive refs (e.g., `"skill:work-loop"`) are validated against the declaring
+and target packs' `.apm/` directories. An absent target pack does not fail
+verification — the check is portable across catalogues that may not include
+every optional pack.
+
+---
+
+## Journey format
+
+> **Not yet available.** Wave 4 of the catalogue-contracts initiative will define the
+> journey format and its contract. This section will be filled in when that wave ships.

agentbundle-0.27.1/agentbundle/_data/catalogue-scaffold/guides/_shared/reference/catalogue-ci-contract.md

@@ -0,0 +1,253 @@
+---
+title: "Catalogue CI contract"
+summary: "The provider-neutral validation, packaging, publication, and evidence contract for an AgentBundle catalogue CI pipeline."
+pack: _shared
+kind: reference
+status: stable
+---
+
+# Catalogue CI contract
+
+This page defines the portable contract any CI system can implement to validate,
+package, and publish an AgentBundle catalogue. It names the commands, outputs,
+exit codes, publication ordering, and responsibility boundaries — without
+prescribing a CI provider or a specific workflow shape.
+
+## Responsibility boundary
+
+Three parties share responsibility for a catalogue CI pipeline. No party may
+silently assume another's obligations.
+
+| Party | Owns | Never does |
+|---|---|---|
+| **AgentBundle CLI** | Correct catalogue validation; deterministic archive + SHA256 sidecar; stable JSON output shapes; stable exit-code contract | Read secrets; issue network calls; control upload order; manage retention |
+| **Organization CI** | Secrets and credential injection; HTTPS upload; publication serialization (ensuring one release lands at a time); rollback policy; artifact retention | Implement validation logic; bypass exit-code signals; skip the admission command |
+| **Host Repository** | CI workflow files and trigger config; internal governance gates; tests proving the portable commands work in this repository | Alter the portable command signatures; branch AgentBundle's output format |
+
+## CI lifecycle phases
+
+### Phase 1 — Tool acquisition
+
+The CI environment must have `agentbundle` available before any catalogue
+command runs. Two patterns are equally valid:
+
+**Externally managed.** The CI step installs agentbundle from a package registry:
+
+```bash
+pip install agentbundle
+```
+
+Pin the version for reproducibility:
+
+```bash
+pip install 'agentbundle==<version>'
+```
+
+**Vendored.** The organization pre-installs agentbundle into a shared CI image or
+tool layer. The CI step runs catalogue commands without an explicit install.
+
+Either way, confirm the tool is present:
+
+```bash
+agentbundle --version
+```
+
+### Phase 2 — Change validation
+
+Every pipeline run that touches catalogue content must pass the admission
+command before proceeding to packaging:
+
+```bash
+agentbundle catalogue verify --root . --format json
+```
+
+`--format json` writes a machine-readable result to stdout and exits 0 (clean)
+or 1 (failures). The CI step fails on any non-zero exit, blocking packaging.
+
+`catalogue lint` runs as an earlier, faster check against pack sources only. It
+is optional but recommended as a pre-commit or fast-path gate:
+
+```bash
+agentbundle catalogue lint --root . --format json
+```
+
+### Phase 3 — Release packaging
+
+After verify exits 0, package the release:
+
+```bash
+agentbundle catalogue package \
+  --root . \
+  --bundle  "$BUNDLE" \
+  --release "$RELEASE" \
+  --channel "$CHANNEL" \
+  --output  "$OUTPUT"
+```
+
+The command writes three artifacts under `$OUTPUT`:
+
+```
+$OUTPUT/
+  catalogues/
+    $BUNDLE/
+      releases/
+        $RELEASE/
+          catalogue-$RELEASE.tar.gz       ← immutable archive
+          catalogue-$RELEASE.tar.gz.sha256 ← SHA256 sidecar
+      channels/
+        $CHANNEL.json                      ← mutable channel descriptor
+```
+
+The archive is deterministic given the same source content. The SHA256 sidecar
+is computed over the archive and stored alongside it. The channel descriptor is a
+small JSON file that records which release the channel currently points to; it is
+the live pointer consumers use to resolve the latest version.
+
+Re-run `agentbundle catalogue verify --archive <path>.tar.gz` after packaging to
+confirm the archive is valid before uploading it.
+
+### Phase 4 — Publication
+
+Upload artifacts in this exact order:
+
+1. The archive (`.tar.gz`)
+2. The SHA256 sidecar (`.sha256`)
+3. The channel descriptor (`channels/<channel>.json`) — **upload last**
+
+The channel descriptor is the live pointer. Writing it last minimises the window
+during which the descriptor references an archive that has not yet landed in the
+target store. A consumer that resolves the channel between steps 2 and 3 finds no
+channel pointer and fails cleanly; a consumer that resolves after step 3 finds the
+archive already present.
+
+Publication serialization — preventing two concurrent releases from interleaving
+their uploads — is the CI system's responsibility.
+
+### Phase 5 — Post-publication verification
+
+After the channel descriptor is published, download the archive and sidecar from
+the publication store and verify them locally:
+
+```bash
+# Download from the store first (provider-specific step)
+# Then verify the local copies:
+agentbundle catalogue verify \
+  --archive "/path/to/downloaded/catalogue-$RELEASE.tar.gz" \
+  --sha256-file "/path/to/downloaded/catalogue-$RELEASE.tar.gz.sha256"
+```
+
+`--archive` accepts a local filesystem path only; pass the path to the downloaded
+archive. This confirms the archive round-trips through the publication store
+without corruption.
+
+Optionally, smoke-test pack installation from the published catalogue to confirm
+consumer-side resolution.
+
+### Phase 6 — Evidence retention
+
+The CI system is responsible for retaining the evidence needed for rollback,
+audit, and incident response. Minimum retention artifacts:
+
+- The archive and SHA256 sidecar for every published release
+- The JSON output of `catalogue verify --format json` from Phase 2
+- The JSON output of `catalogue verify --archive ...` from Phase 5
+
+Retention period and storage location are Organization CI policy, not
+AgentBundle's.
+
+## Exit codes
+
+All `agentbundle catalogue` commands follow the same convention:
+
+| Code | Meaning |
+|------|---------|
+| `0` | Success |
+| `1` | Validation or operational failure (errors in the catalogue, archive mismatch, internal error) |
+| `2` | CLI usage error (missing required flag, unknown option) |
+
+These codes are stable. A CI step that treats any non-zero exit as a failure
+gets the correct behaviour.
+
+## Secrets and network calls
+
+`agentbundle catalogue lint`, `agentbundle catalogue verify`, and
+`agentbundle catalogue package` do not read secrets and do not issue network
+calls. They operate entirely on the local filesystem.
+
+TLS certificate verification, bearer-token injection, proxy configuration, and
+upload credentials are exclusively Organization CI responsibilities. The
+`AGENTBUNDLE_HTTP_BEARER_TOKEN`, `AGENTBUNDLE_CA_BUNDLE`, and `HTTPS_PROXY`
+environment variables control AgentBundle's behaviour when resolving a remote
+catalogue source (used by install and upgrade verbs, not by the catalogue
+pipeline commands above).
+
+## Command reference
+
+### `agentbundle catalogue lint`
+
+```
+agentbundle catalogue lint [--root ROOT] [--pack PACK] [--format {table,json}] [--deep]
+```
+
+Validates pack sources against contracts without building. Exits 0 when all
+checks pass, 1 on any error.
+
+`--format json` writes to stdout:
+
+```json
+{
+  "schema_version": "1",
+  "command": "catalogue lint",
+  "operation": "lint",
+  "agentbundle_version": "<version>",
+  "catalogue_schema_version": "<version>",
+  "ok": true,
+  "diagnostics": []
+}
+```
+
+Human-readable output (table format) goes to stderr and is absent when
+`--format json` is used.
+
+### `agentbundle catalogue verify`
+
+```
+agentbundle catalogue verify [--root ROOT] [--pack PACK]
+                             [--archive ARCHIVE] [--sha256-file SHA256_FILE]
+                             [--format {table,json}]
+```
+
+Runs the full source pipeline (source mode) or validates an archive against its
+SHA256 sidecar and checks the extracted layout (archive mode).
+Exits 0 on clean, 1 on any failure.
+
+`--format json` writes the same JSON shape as `catalogue lint` to stdout.
+
+### `agentbundle catalogue package`
+
+```
+agentbundle catalogue package --bundle BUNDLE --release RELEASE
+                               --channel CHANNEL --output OUTPUT
+                               [--root ROOT]
+                               [--source-revision SOURCE_REVISION]
+                               [--minimum-agentbundle-version VERSION]
+                               [--published-at DATETIME]
+```
+
+Required flags: `--bundle`, `--release`, `--channel`, `--output`.
+Optional: `--root` (defaults to `.`), `--source-revision`, `--minimum-agentbundle-version`,
+`--published-at`.
+
+`catalogue package` does not support `--format json`; its result is the output
+directory layout described in [Phase 3](#phase-3--release-packaging). Exits 0
+on success, 1 on failure, 2 on missing required flags.
+
+## See also
+
+- **`agentbundle` reference** — install the CLI, install a pack, configure the
+  default adapter, source-resolution chain, environment variables. See the
+  `agentbundle.md` reference guide in your local guides tree, or the project
+  docs site.
+- **Catalogue format** — what makes a directory a valid catalogue, schema
+  contracts, and validation. See the `catalogue-format.md` reference guide in
+  your local guides tree, or the project docs site.

agentbundle-0.27.1/agentbundle/_data/catalogue-scaffold/manifest.json

@@ -0,0 +1,18 @@
+{
+  "files": {
+    "guides/_shared/reference/catalogue-authoring-standards.md": "4fe9ce077af089ab52840d1b3de600c09ca23eace114c1e28c4685a3b7289520",
+    "guides/_shared/reference/catalogue-ci-contract.md": "fae793ab47989b6dd3c731afcb0b4cda21c7d08bbe7fa40fca6d3abb3d158141",
+    "packs/AGENTS.md": "5962bfa1342ee145847eab48764535c6ea50f665b43c92ff93d1538f0110535a",
+    "packs/README.md": "68a141500fed78988dbfe7400ea9b8fa0b7d97186d420a93dfe40763272b69ee",
+    "packs/_example/.apm/skills/example-skill/SKILL.md": "33be8cbf4b2c014a5a63e788b7d0b350ad8061c6c4b2579369a3e984135bf9f1",
+    "packs/_example/.claude-plugin/plugin.json": "d38c8456640d5e2f9296361f7e3e675e368ddd3eb22a6245267560f460155f41",
+    "packs/_example/README.md": "ef130c9c1f97a75a07cc59fc55fc5b3bf71846dd2f06c3cddf5a1154023b6ef6",
+    "packs/_example/evals/eval_queries.json": "f41ecda0834a22f3b4823c81ab02e58b0e4beba610e3b40c185579abff9cfeee",
+    "packs/_example/pack.toml": "94e2c7fd25d4d115858728c7ecb8f739adfd0f594b29596c106daba0791a4b94",
+    "profiles/AGENTS.md": "8950438d9e0f57c13613104c88c90b598b53196c91bfdced6d63e4e01b5e9254",
+    "profiles/README.md": "a0b0268edc57fc575f7fea08f3363ba7da9f6e67dc4a0a6f8bd38c9668c97922",
+    "profiles/_example/README.md": "164494df049ddce3e57cb44ed604cb3d39be0a6ec2072e609ea3fa4bbfc74c72",
+    "profiles/_example/profile.toml": "68af18cf50fa0327a9776b029c92bb1cf82710c649691b3ac889eb8537b8eac7"
+  },
+  "version": 1
+}