Skip to content

chore(apm): upgrade zava-agent-config v1.0.0 → v3.0.0 (selective marketplace pins)#1

Merged
danielmeppiel merged 2 commits into
mainfrom
chore/upgrade-cfg-v2
May 6, 2026
Merged

chore(apm): upgrade zava-agent-config v1.0.0 → v3.0.0 (selective marketplace pins)#1
danielmeppiel merged 2 commits into
mainfrom
chore/upgrade-cfg-v2

Conversation

@danielmeppiel

@danielmeppiel danielmeppiel commented May 6, 2026

Copy link
Copy Markdown
Contributor

Lloyds Block 2.B reference: selective marketplace consumption

Upgrades shared agent config from v1.0.0 (monolithic .apm/...) to v3.0.0 (5-plugin marketplace), pinning only the 4 plugins relevant to a service repo.

What changes

 dependencies:
   apm:
-    - DevExpGbb/zava-agent-config#v1.0.0
+    - DevExpGbb/zava-agent-config/plugins/secure-baseline#v3.0.0
+    - DevExpGbb/zava-agent-config/plugins/code-kit#v3.0.0
+    - DevExpGbb/zava-agent-config/plugins/release-kit#v3.0.0
+    - DevExpGbb/zava-agent-config/plugins/operate-kit#v3.0.0

Skipped: ideate-kitmeeting-to-issue belongs upstream of a service repo (PM/architect surface), not the storefront team. Demonstrating selective consumption is the entire point.

What deploys (verified locally)

apm install →
  [+] code-kit         — 1 agent (architect), 1 skill (panel-review)
  [+] operate-kit      — 1 skill (incident-to-pr)
  [+] secure-baseline  — 1 agent (security), 2 instructions (secure-coding-base, docs-style-guide)
  [+] ship-kit         — 1 instruction (ci-cd-golden-paths)

  Total: 2 agents + 3 instructions + 2 skills

Lockfile shows package_type: marketplace_plugin, is_virtual: true, virtual_path: plugins/<kit> for each dep — clean.

Lloyds Block 2.B narrative this PR enables

  1. Marketplace authoring (zava-agent-config v3.0.0) — apm.yml marketplace: block + apm pack.claude-plugin/marketplace.json (5 packages); self-audit CI green.
  2. Selective consumption (this PR) — engineers pin only their stage kits via subdir-pin syntax.
  3. Governance unchangedapm-audit workflow on this repo still enforces SBOM + signature + policy gates against the new pin set.

Background — why v3.0.0 and not v2.0.0

v2.0.0 had a discovery bug: instructions at plugin root weren't picked up by APM (Anthropic-shape plugin model only knows agents/, skills/, commands/, hooks/ at root; instructions are an APM extension discovered via .apm/instructions/). v3.0.0 moves instructions into <plugin>/.apm/instructions/. Same marketplace structure.

Reviewers

  • @Jfhelin (GitHub) — sanity-check marketplace consumption shape ahead of Block 2.B walkthrough
  • self-merge after green checks — Wave 2 dependency

cc Lloyds Wave 1.5 in delivery/lloyds-ph1-delivery-plan.md

@danielmeppiel danielmeppiel force-pushed the chore/upgrade-cfg-v2 branch from 89e545f to 23352a7 Compare May 6, 2026 11:05
@danielmeppiel danielmeppiel changed the title chore(apm): upgrade zava-agent-config v1.0.0 → v2.0.1 (selective marketplace pins) chore(apm): upgrade zava-agent-config v1.0.0 → v3.0.0 (selective marketplace pins) May 6, 2026
…etplace pins)

zava-agent-config v3.0 restructured into a 5-plugin marketplace per
PLATFORM.md SDLC ribbon (IDEATE · CODE · RELEASE · OPERATE +
cross-cutting secure-baseline). Storefront consumes 4 of the 5 plugins
selectively via subdir-pin syntax:

  - secure-baseline   (security agent + secure-coding + docs-style instructions)
  - code-kit          (architect agent + panel-review skill)
  - release-kit       (ci-cd-golden-paths instructions)
  - operate-kit       (incident-to-pr skill)

Skipped: ideate-kit (meeting-to-issue belongs upstream of a service
repo). Storefront engineers don't need the meeting-to-code primitive.

This is the Lloyds Block 2.B reference upgrade: demonstrates that a
consumer can pin only the kits relevant to their SDLC stage rather than
inheriting the whole bag — the entire point of the marketplace
restructure.

Verified locally:
  apm install → 4 plugins resolved, 2 agents + 3 instructions + 2 skills
  deployed. Lockfile shows package_type: marketplace_plugin per dep.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@danielmeppiel danielmeppiel force-pushed the chore/upgrade-cfg-v2 branch from 23352a7 to a41131f Compare May 6, 2026 11:37
zava-agent-config v4.0.0 standardizes all primitive types under .apm/<type>/
inside each plugin (resolves install-time integrator asymmetry — see
microsoft/apm#1161).

No behavior change for storefront — same 7 primitives deploy correctly.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant