Releases: DevExpGbb/zava-agent-config
zava-agent-config v6.1.2
zava-agent-config v6.1.2
Plugins shipped as Claude Code plugin tarballs in three tiers
(baseline + phase kits + accelerators). Consumers resolve via APM
marketplace (@v6.1.2) or download tarballs below
for direct Claude Code marketplace installation.
Verify any tarball:
sha256sum -c <plugin>-<version>.tar.gz.sha256See auto-generated commit notes below for changes since the previous tag.
zava-agent-config v6.1.1
zava-agent-config v6.1.1
Plugins shipped as Claude Code plugin tarballs in three tiers
(baseline + phase kits + accelerators). Consumers resolve via APM
marketplace (@v6.1.1) or download tarballs below
for direct Claude Code marketplace installation.
Verify any tarball:
sha256sum -c <plugin>-<version>.tar.gz.sha256See auto-generated commit notes below for changes since the previous tag.
zava-agent-config v6.1.0
zava-agent-config v6.1.0
Plugins shipped as Claude Code plugin tarballs in three tiers
(baseline + phase kits + accelerators). Consumers resolve via APM
marketplace (@v6.1.0) or download tarballs below
for direct Claude Code marketplace installation.
Marketplace: marketplace-6.1.0.json
Plugins: ["code-kit","ideate-kit","modernize-kit","operate-kit","release-kit","review-kit","secure-baseline"]
Verify any tarball:
sha256sum -c <plugin>-6.1.0.tar.gz.sha256See auto-generated commit notes below for changes since the previous tag.
What's Changed
- feat(modernize-kit): add nextjs-modernizer skill (Next 14→15) — v6.1.0 by @danielmeppiel in #5
Full Changelog: v6.0.0...v6.1.0
zava-agent-config v6.0.0
zava-agent-config v6.0.0
Plugins shipped as Claude Code plugin tarballs in three tiers
(baseline + phase kits + accelerators). Consumers resolve via APM
marketplace (@v6.0.0) or download tarballs below
for direct Claude Code marketplace installation.
Marketplace: marketplace-6.0.0.json
Plugins: ["code-kit","ideate-kit","modernize-kit","operate-kit","release-kit","review-kit","secure-baseline"]
Verify any tarball:
sha256sum -c <plugin>-6.0.0.tar.gz.sha256See auto-generated commit notes below for changes since the previous tag.
What's Changed
- docs: kit pointer in README by @danielmeppiel in #2
- chore: sharper README mermaid + 3-tier taxonomy + zero-transitive intent by @danielmeppiel in #3
- feat(v6.0.0): modernize-kit accelerator — Express 4→5, the marketplace's first episodic kit by @danielmeppiel in #4
Full Changelog: v5.0.1...v6.0.0
v5.1.1 — layered policy enforcement (org + repo override)
Detects consumer's repo apm-policy.yml and uses it as policy source so extends: org layering actually applies. v5.1.0 silently bypassed repo overrides.
v5.1.0 — enforce org policy
Reusable workflow apm-audit.yml now explicitly runs apm audit --ci --policy org after install. v5.0.x only generated SARIF (drift-only); policy violations passed CI silently. Consumers bump to @v5.1.0 to actually gate on org policy.
zava-agent-config v5.0.1
zava-agent-config v5.0.1
Six SDLC-aligned plugins shipped as Claude Code plugin tarballs.
Consumers resolve via APM marketplace (@v5.0.1)
or download tarballs below for direct Claude Code marketplace
installation.
Marketplace: marketplace-5.0.1.json
Plugins: secure-baseline, ideate-kit, code-kit, review-kit, release-kit, operate-kit
Verify any tarball:
sha256sum -c <plugin>-5.0.1.tar.gz.sha256See auto-generated commit notes below for changes since the previous tag.
What's Changed
- v5.0.1: migrate workflows to microsoft/apm-action + add release workflow by @danielmeppiel in #1
New Contributors
- @danielmeppiel made their first contribution in #1
Full Changelog: v5.0.0...v5.0.1
v5.0.0 — review-kit (REVIEW phase)
What's new
New plugin: review-kit — ships the panel-review skill (multi-perspective architect+security review of staged changes), now correctly placed in the REVIEW phase per the PLATFORM.md SDLC ribbon:
IDEATE · PLAN · CODE · BUILD · TEST · REVIEW · RELEASE · OPERATE
Marketplace now publishes 6 plugins (was 5):
| Phase | Plugin |
|---|---|
| (cross-cutting) | secure-baseline |
| IDEATE | ideate-kit |
| CODE | code-kit |
| REVIEW | review-kit ← new |
| RELEASE | release-kit |
| OPERATE | operate-kit |
Breaking change
Consumers pinning code-kit#v4.0.0 for panel-review must:
- Bump
code-kitto#v5.0.0(architect persona only now) - Add
plugins/review-kit#v5.0.0pin to apm.yml
Run apm cache clean && apm install to regenerate the lockfile.
Validation
- Per-kit
apm pack --offlinesynthesizesplugin.jsonfromapm.ymland remaps.apm/<type>/ → <type>/in build output (documentation gap filed: microsoft/apm#1161 — body rewritten with evidence) - Self-audit CI green on main
- Reference consumer install (zava-storefront against v5 branch ref): 5 plugins → 7 primitives integrated (2 agents + 2 skills + 3 instructions)
Migration sub-table (v4.0.0 → v5.0.0)
See CATALOG.md for the full pinning recipe.
v4.0.0 — symmetric .apm/<type>/ source layout
What changed
All 5 plugins (secure-baseline, ideate-kit, code-kit, release-kit, operate-kit) now use .apm/<type>/ uniformly across every primitive type (agents/, skills/, instructions/, commands/, hooks/).
Why
APM has an asymmetry between its pack-export and install-integrate code paths: pack accepts both .apm/<type>/ and root-level convention dirs, but install-time integrators only guarantee .apm/<type>/ for instructions, commands, and hooks (agents and skills tolerate root convention dirs). v3.0.0's mixed layout (agents/skills at plugin root, instructions in .apm/) worked but was fragile and inconsistent across the file tree. v4.0.0 standardizes on .apm/ — the only layout that works symmetrically through both code paths for every primitive type.
Migration
Pin @v4.0.0 instead of @v3.0.0:
dependencies:
apm:
- DevExpGbb/zava-agent-config/plugins/secure-baseline#v4.0.0
- DevExpGbb/zava-agent-config/plugins/code-kit#v4.0.0
- DevExpGbb/zava-agent-config/plugins/release-kit#v4.0.0
- DevExpGbb/zava-agent-config/plugins/operate-kit#v4.0.0
# plus ideate-kit if neededNo behavior change beyond the version bump. CI reusable workflow also pinned at @v4.0.0:
uses: DevExpGbb/zava-agent-config/.github/workflows/apm-audit.yml@v4.0.0Verified
apm install from this tag deploys all 7 primitives correctly (2 agents, 2 skills, 3 instructions) into a downstream consumer.
Related
- microsoft/apm#1161 — docs gap that motivated the layout standardization
- v3.0.0 release for the prior
release-kitrename + lockstep version bump
v3.0.0 — Vocabulary alignment (ship-kit → release-kit)
v3.0.0 — Vocabulary alignment to PLATFORM ribbon (rename ship-kit → release-kit)
Breaking for v2.0.x consumers. Same marketplace structure, one kit renamed for vocabulary discipline against PLATFORM.md §6.1.
Why v3 right after v2
PLATFORM.md names the canonical SDLC ribbon as:
IDEATE · PLAN · CODE · BUILD · TEST · REVIEW · RELEASE · OPERATE
v2.0.x used ship-kit, which is non-canonical. At Lloyds we'll be teaching dev leads to navigate the platform by phase name — the marketplace plugin names must match the ribbon they're being taught from. Renaming now (while there are zero external consumers) is cheaper than carrying the alias forever.
Changes
| v2.0.1 | v3.0.0 |
|---|---|
plugins/ship-kit/ |
plugins/release-kit/ |
BUILD/RELEASE phase label |
RELEASE phase label (canonical) |
apm.yml version: 2.0.0 |
version: 3.0.0 |
Plugin pin: …/plugins/ship-kit#v2.0.1 |
…/plugins/release-kit#v3.0.0 |
All 5 plugins bump to 3.0.0 in lockstep (marketplace versioning convention — single source of truth for the bundle).
Action
dependencies:
apm:
- 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
# ideate-kit if you author work upstream of code (PMs, architects)Then apm install. Lockfile entries become package_type: marketplace_plugin with virtual_path: plugins/<kit> and is_virtual: true.
Verified
- ✅
apm pack --offline→.claude-plugin/marketplace.json(5 packages) - ✅
apm audit --ci→ 18/18 checks pass - ✅
self-auditandapm-auditworkflows green onmain(commit381c962) - ✅ Storefront upgrade verified:
apm installintegrates 2 agents + 3 instructions + 2 skills
Future kits (additive, non-breaking)
plan-kit, build-kit, test-kit, review-kit will land in 3.x as content is authored against the remaining ribbon phases. Marketplace owner spec stays fixed.