chore(apm): upgrade zava-agent-config v1.0.0 → v3.0.0 (selective marketplace pins)#1
Merged
Merged
Conversation
89e545f to
23352a7
Compare
…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>
23352a7 to
a41131f
Compare
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>
5e94313 to
d048227
Compare
This was referenced May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lloyds Block 2.B reference: selective marketplace consumption
Upgrades shared agent config from
v1.0.0(monolithic.apm/...) tov3.0.0(5-plugin marketplace), pinning only the 4 plugins relevant to a service repo.What changes
Skipped:
ideate-kit—meeting-to-issuebelongs upstream of a service repo (PM/architect surface), not the storefront team. Demonstrating selective consumption is the entire point.What deploys (verified locally)
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
apm.ymlmarketplace:block +apm pack→.claude-plugin/marketplace.json(5 packages); self-audit CI green.apm-auditworkflow 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
cc Lloyds Wave 1.5 in delivery/lloyds-ph1-delivery-plan.md