agentbundle 0.29.3__tar.gz → 0.29.5__tar.gz

{agentbundle-0.29.3 → agentbundle-0.29.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentbundle
-Version: 0.29.3
+Version: 0.29.5
 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
@@ -156,6 +156,13 @@ 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`).
 
+Build residue is excluded, so it does not matter whether you packaged a working
+tree you had just tested or npm-installed in. Pruned at every level of a pack:
+`__pycache__`, `.pytest_cache`, `.mypy_cache`, `.ruff_cache`, `.tox`,
+`.hypothesis`, `htmlcov`, `node_modules`, `.venv`, `venv` — plus `*.pyc`,
+`*.pyo`, `.DS_Store`, `coverage.xml` and `.coverage*` shards. The drop is
+silent, so do not name a directory you mean to ship after one of those.
+
 **Source distribution for air-gapped or self-hosted catalogues:**
 
 ```bash
@@ -167,7 +174,7 @@ agentbundle catalogue package \
   --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.
+Produces a `catalogue-source-<release>.tar.gz` from a positive allowlist (packs, profiles, guides, marketplace manifest, legal files), with the same build-residue exclusions as the default flavour. 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:**
 
@@ -234,16 +241,29 @@ my-pack/
   .claude-plugin/
     plugin.json              # Claude Code plugin manifest (hand-authored)
   README.md                  # the pack's portable doc — projected with the pack
-  .apm/                      # primitives — projected by the build pipeline
+  .apm/                      # runtime — projected by the build pipeline
     skills/<name>/
       SKILL.md               # the skill body; one folder per skill
+      scripts/               # helper code the skill invokes
       references/            # progressive-disclosure docs, loaded on demand
       assets/                # templates the skill copies into the repo
+      evals/                 # activation + output-quality evals, skill-local
     agents/<name>.md         # subagents
     hooks/<name>.py          # lifecycle hooks
+  tests/                     # implementation tests — NEVER projected
+    skills/<name>/
+    hooks/
+    pack/
   seeds/                     # files scaffolded into the adopter repo
 ```
 
+Three boundaries: the **pack** owns and executes its tests, **`.apm/`** is the
+runtime export boundary, and a **skill** owns its eval fixtures. Only `.apm/`
+and `seeds/` are projected into an installed environment — `tests/` is visible
+in a catalogue archive, so an extracted pack can verify itself, but `install`
+never places it. Keep tests out of `.apm/` even though the installer would
+ignore them there; the separation is structural, not incidental.
+
 `pack.toml` is the **single source of truth** for a pack's metadata. Declare
 `license`, `[[pack.maintainers]]`, `[pack.links]`, `categories`, and
 `keywords` once; the build projects the cleanly-mappable subset — plus the

{agentbundle-0.29.3 → agentbundle-0.29.5}/README-pypi.md

@@ -134,6 +134,13 @@ 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`).
 
+Build residue is excluded, so it does not matter whether you packaged a working
+tree you had just tested or npm-installed in. Pruned at every level of a pack:
+`__pycache__`, `.pytest_cache`, `.mypy_cache`, `.ruff_cache`, `.tox`,
+`.hypothesis`, `htmlcov`, `node_modules`, `.venv`, `venv` — plus `*.pyc`,
+`*.pyo`, `.DS_Store`, `coverage.xml` and `.coverage*` shards. The drop is
+silent, so do not name a directory you mean to ship after one of those.
+
 **Source distribution for air-gapped or self-hosted catalogues:**
 
 ```bash
@@ -145,7 +152,7 @@ agentbundle catalogue package \
   --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.
+Produces a `catalogue-source-<release>.tar.gz` from a positive allowlist (packs, profiles, guides, marketplace manifest, legal files), with the same build-residue exclusions as the default flavour. 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:**
 
@@ -212,16 +219,29 @@ my-pack/
   .claude-plugin/
     plugin.json              # Claude Code plugin manifest (hand-authored)
   README.md                  # the pack's portable doc — projected with the pack
-  .apm/                      # primitives — projected by the build pipeline
+  .apm/                      # runtime — projected by the build pipeline
     skills/<name>/
       SKILL.md               # the skill body; one folder per skill
+      scripts/               # helper code the skill invokes
       references/            # progressive-disclosure docs, loaded on demand
       assets/                # templates the skill copies into the repo
+      evals/                 # activation + output-quality evals, skill-local
     agents/<name>.md         # subagents
     hooks/<name>.py          # lifecycle hooks
+  tests/                     # implementation tests — NEVER projected
+    skills/<name>/
+    hooks/
+    pack/
   seeds/                     # files scaffolded into the adopter repo
 ```
 
+Three boundaries: the **pack** owns and executes its tests, **`.apm/`** is the
+runtime export boundary, and a **skill** owns its eval fixtures. Only `.apm/`
+and `seeds/` are projected into an installed environment — `tests/` is visible
+in a catalogue archive, so an extracted pack can verify itself, but `install`
+never places it. Keep tests out of `.apm/` even though the installer would
+ignore them there; the separation is structural, not incidental.
+
 `pack.toml` is the **single source of truth** for a pack's metadata. Declare
 `license`, `[[pack.maintainers]]`, `[pack.links]`, `categories`, and
 `keywords` once; the build projects the cleanly-mappable subset — plus the

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

@@ -0,0 +1,357 @@
+---
+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
+
+Three boundaries, each owned by a different thing:
+
+- The **pack** is the ownership and test-execution boundary.
+- `.apm/` is the **runtime export** boundary.
+- A **skill** is the evaluation-fixture boundary.
+
+```
+packs/<pack>/
+├── pack.toml
+├── README.md
+├── .apm/                          # runtime — projected into installed environments
+│   └── skills/<skill>/
+│       ├── SKILL.md
+│       ├── scripts/
+│       ├── references/
+│       ├── assets/
+│       └── evals/                 # skill-local, projected with the skill
+├── tests/                         # implementation verification — never projected
+│   └── skills/<skill>/
+└── seeds/                         # governance files projected to the repo root
+```
+
+Deterministic implementation tests live under `packs/<pack>/tests/`. Runtime
+skill evals live under `.apm/skills/<skill>/evals/`. `[pack.evals].skills`
+selects which skill-local activation evals the pack evaluator runs.
+
+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 |
+| `.apm/shared-libs/` | Shared libraries |
+| `.apm/skills/<skill>/evals/` | Activation and output-quality evals (projected with the skill) |
+
+### Tests live with the pack, outside the payload they validate
+
+Keep tests beside the pack they validate, but out of the runtime payload.
+`.apm/` holds only files meant to participate in installation, projection, or
+execution — so a test never belongs there, **even where the installer happens
+to ignore its path**. Runtime separation is expressed by directory structure,
+not by relying on an implicit exclusion that a future adapter may not honour.
+
+```
+packs/<pack>/tests/
+├── skills/
+│   └── <skill>/          # unit/, integration/, fixtures/ as the skill warrants
+├── hooks/
+├── pack/                 # manifest, metadata, projection
+└── fixtures/
+```
+
+Tests should execute or import the real implementation under `.apm/`. Never
+duplicate production code into the test tree.
+
+### Tests versus evaluations
+
+Two different questions, two homes.
+
+| | `tests/` | `evals/` |
+|---|---|---|
+| Verifies | Deterministic software behaviour | Agent-level behaviour |
+| Covers | Function output, parsing, exit status, CLI behaviour, error handling, projected install contents | Whether a skill activates, whether a near-miss avoids activation, whether output satisfies a rubric |
+| Run by | pytest, Vitest, Go test, shell tooling | The eval runner |
+| Lives at | `packs/<pack>/tests/` | `.apm/skills/<skill>/evals/` |
+
+Evaluations do not replace unit or integration tests for scripts.
+
+Evals are skill-local by design, not by accident. A fixture only means anything
+next to the skill it exercises, so it belongs to the skill and is projected with
+it — the adapters copy `.apm/skills/<skill>/` wholesale. That is why the `tests/`
+rule is scoped to the `.apm/` boundary rather than "anything that isn't runtime":
+`evals/` is runtime-adjacent content, a test suite is not. The linter enforces
+this — it looks for `eval_queries.json` and `evals.json` under
+`<skill>/evals/`, and requires one for every skill named in `[pack.evals].skills`.
+
+A **diagnostic** may live under `.apm/` when it is an intentional runtime
+feature users or agents invoke — `scripts/doctor.py`,
+`scripts/check_environment.py`. Those are runtime commands, not test suites.
+
+### Catalogue archives may carry tests; installers must not install them
+
+A catalogue or source archive walks `packs/**`, so it carries a pack's
+`pack.toml`, `README.md`, `.apm/**`, `seeds/**`, `tests/**`, `docs/**`,
+`.claude-plugin/`, and pack-root markdown. Shipping tests in a source-oriented
+archive supports downstream verification, auditing, security review, and
+testing an extracted release.
+
+Catalogue inclusion does not imply runtime installation. Installers and
+projection adapters treat `.apm/` and `seeds/` as the projected surfaces, so
+nothing outside those two — `tests/` included — reaches an installed
+environment.
+
+### Test dependencies are not runtime dependencies
+
+A skill's runtime dependency declaration lists only what the installed skill
+needs at run time. `pytest`, `hypothesis`, `vitest`, `eslint`,
+`mypy`, `ruff` and friends belong in development configuration.
+
+Fixtures under a pack's test tree ship in the archive, so they must carry no
+credentials or private data, prefer synthetic data, stay modest in size, and
+name their licence when sourced externally. Fuzzing corpora, generated output,
+coverage reports, and caches are neither committed nor packaged.
+
+The packager enforces the second half. It prunes these directory names at every
+level of a pack, and never descends into them:
+
+```
+__pycache__  .pytest_cache  .mypy_cache  .ruff_cache  .tox
+.hypothesis  htmlcov  node_modules  .venv  venv
+```
+
+plus `*.pyc`, `*.pyo`, `.DS_Store`, `coverage.xml`, and any `.coverage*` shard.
+A directory you mean to ship must not be named one of those — the drop is
+silent. Note this is matched by name at any depth, so it is deliberately *not*
+the same list as the repository-root exclusions.
+
+### Repository-root tests
+
+A test concerning one pack stays inside that pack. Behaviour no single pack
+owns — the catalogue system, packaging, shared projection machinery, profiles,
+cross-pack interaction — belongs to the repository, not to a pack.
+
+Where that lives is the repository's call. This catalogue splits it: behaviour
+that exercises the engine keeps to the engine's own suite
+(`packages/agentbundle/tests/`), while cross-pack *lints* — the ones that read
+every pack's tree and belong to no pack — live with the repository's other
+tooling. Neither is a root `tests/` tree; a catalogue that wants the separate
+tree can add one. Don't create a top-level directory for a single test — the
+ownership rule is what matters, not the path.
+
+### One test process per skill
+
+Run each skill's suite in its own process. This is a correctness requirement,
+not a performance preference.
+
+Skills are independent, so two of them may reasonably ship a `render.py`, and
+their suites may both be called `test_render.py`. Collect them into one pytest
+run and two things break: pytest refuses the duplicate test basenames outright
+(`import file mismatch`), and if it did not, the first `render` module imported
+would serve every suite that expects its own.
+
+```
+pytest packs/<pack>/tests/skills/<skill>/     # one invocation per skill
+```
+
+An invocation that spans two skill test directories is safe only while their
+basenames happen not to collide — which is a property of today's contents, not
+of the layout. Keep the invocations separate and the question never arises.
+
+### Normative summary
+
+- A pack **MUST** be the ownership boundary for its tests.
+- Pack-specific tests **MUST** live under `packs/<pack>/tests/`.
+- Ordinary tests **MUST NOT** live under `.apm/`.
+- `.apm/` **MUST** contain only runtime or projectable content.
+- Agent evaluations **MUST** live under `.apm/skills/<skill>/evals/` and stay
+  distinct from implementation tests.
+- Test dependencies **MUST NOT** be declared as runtime dependencies.
+- Tests **MAY** be included in catalogue or source archives.
+- Tests **MUST NOT** be projected into installed agent environments. Evals
+  **are** projected, as a skill subdirectory — they are runtime-adjacent.
+- Tests that no single pack owns **SHOULD** be kept out of pack test trees,
+  wherever the repository chooses to put them.
+- CI **SHOULD** exercise both the source implementation and the projected
+  runtime artifact.
+
+Release validation should therefore project the pack into a temporary agent
+environment, smoke-test it there, and confirm the projection contains no
+`tests/`, `__pycache__/`, `.pytest_cache/`, coverage output, or
+`test-results/`.
+
+---
+
+## 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.29.3 → agentbundle-0.29.5}/agentbundle/_data/catalogue-scaffold/manifest.json

@@ -1,13 +1,13 @@
 {
   "files": {
-    "guides/_shared/reference/catalogue-authoring-standards.md": "4fe9ce077af089ab52840d1b3de600c09ca23eace114c1e28c4685a3b7289520",
+    "guides/_shared/reference/catalogue-authoring-standards.md": "cec0f7afd7a0bf61d7bedd9facd096b083cb7413679a6fbcd0af28d40bece58c",
     "guides/_shared/reference/catalogue-ci-contract.md": "fae793ab47989b6dd3c731afcb0b4cda21c7d08bbe7fa40fca6d3abb3d158141",
-    "packs/AGENTS.md": "4d9e94478d3c941d4a08c8827ed9d30edaa07207854eac020b9fc3014f5b3237",
-    "packs/README.md": "68a141500fed78988dbfe7400ea9b8fa0b7d97186d420a93dfe40763272b69ee",
+    "packs/AGENTS.md": "861a029007741cd7645cdfcc018e5ac85cf218d332f6688115156c9c676381b8",
+    "packs/README.md": "d2de5f9556f4c8e521103474bde74636e02cc805f9bf5312a3a61a1f3eb45d8f",
     "packs/_example/.apm/skills/example-skill/SKILL.md": "33be8cbf4b2c014a5a63e788b7d0b350ad8061c6c4b2579369a3e984135bf9f1",
+    "packs/_example/.apm/skills/example-skill/evals/eval_queries.json": "f41ecda0834a22f3b4823c81ab02e58b0e4beba610e3b40c185579abff9cfeee",
     "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",

{agentbundle-0.29.3 → agentbundle-0.29.5}/agentbundle/_data/catalogue-scaffold/packs/AGENTS.md

@@ -5,12 +5,17 @@ Read `packs/AGENTS.local.md` when present — it carries host-specific overrides
 
 ## Pack layout
 
+The pack is the ownership and test-execution boundary; `.apm/` is the runtime export boundary; a skill is the
+evaluation-fixture boundary. Tests go in `packs/<pack>/tests/`, never under `.apm/`; evals stay skill-local at
+`.apm/skills/<skill>/evals/` and project with the skill. `tools/lint-pack-test-boundary.py` enforces both across
+every pack, plus one pytest process per skill test dir. Shape: `docs/architecture/pack-layout.md`.
+
 | Path | Purpose |
 |------|---------|
 | `pack.toml` | Pack metadata — version, description, adapter-contract, categories |
 | `.claude-plugin/plugin.json` | Claude plugin manifest source (must match `pack.toml` version, stay schema-valid) |
 | `seeds/` | Adopter scaffold templates (brownfield install) |
-| `docs/` | Concept anchor and pack guides — never projected or installed |
+| `tests/` · `docs/` | Never projected — implementation tests (`skills/<skill>/`, `hooks/`, `pack/`) · concept anchor and pack guides |
 | `.apm/skills/` | Skill sources → projected per adapter |
 | `.apm/agents/` | Agent sources → projected per adapter |
 | `.apm/hooks/` | Hook-body sources → projected per adapter |
@@ -40,10 +45,7 @@ installed, and are not included in packaged archives. See `packs/README.md`.
 | `[pack.evals]` | — | `skills` (array of covered skill names) |
 | `[pack.recipes.*]` | `description` | `steps`, `adapter` |
 | `[pack.dependencies]` | — | `required`, `recommended`, `conflicts` (arrays) |
-| `[pack.seeds]` | — | Seed path configuration |
-| `[pack.layout]` | — | Per-scope layout overrides |
-| `[pack.first-value]` | — | First-value install metadata |
-| `[pack.adaptation]` | — | Adaptation inference rules |
+| `[pack.seeds]` · `[pack.layout]` · `[pack.first-value]` · `[pack.adaptation]` | — | Seed paths · per-scope layout overrides · first-value install metadata · adaptation inference rules |
 
 `[pack.install]` is required when `adapter-contract.version` ≥ 0.2.
 

{agentbundle-0.29.3 → agentbundle-0.29.5}/agentbundle/_data/catalogue-scaffold/packs/README.md

@@ -20,7 +20,7 @@ Copy `packs/_example` to `packs/<your-pack>`, then:
 1. Update `pack.toml` — set `[pack].name`, `version`, `description`, and `[pack.install]` fields.
 2. Update `.claude-plugin/plugin.json` — set `name`, `version`, and `description` to match.
 3. Rename `.apm/skills/example-skill` to your skill name and rewrite `SKILL.md`.
-4. Update `evals/eval_queries.json` with activation fixtures for your skill.
+4. Update `.apm/skills/<skill>/evals/eval_queries.json` with activation fixtures for your skill.
 5. Rewrite `README.md` with your pack's outcome, audience, and install instructions.
 6. Run `agentbundle catalogue verify --root .` from the catalogue root.
 
@@ -50,7 +50,7 @@ full primitive directory list and adapter-contract map.
 
 `seeds/` holds adopter scaffold templates delivered on brownfield install.
 
-`evals/eval_queries.json` holds Tier-A activation eval fixtures — should-trigger and near-miss
+`.apm/skills/<skill>/evals/eval_queries.json` holds Tier-A activation eval fixtures — should-trigger and near-miss
 queries for each user-triggered skill. List every covered skill in `[pack.evals].skills`.
 
 ## Versioning expectations