fix(release): align cli versioning with repo tags

docs/solutions/adding-converter-target-providers.md

@@ -653,7 +653,8 @@ Use this checklist when adding a new target provider:
 - [ ] Update `CHANGELOG.md` with new target
 
 ### Version Bumping
-- [ ] Bump version in `package.json` (minor for new target)
+- [ ] Use a `feat(...)` conventional commit so semantic-release cuts the next minor root CLI release on `main`
+- [ ] Do not hand-start a separate root CLI version line in `package.json`; the root package follows the repo `v*` tags and semantic-release writes that version back after release
 - [ ] Update plugin.json description if component counts changed
 - [ ] Verify CHANGELOG entry is clear
 

docs/solutions/plugin-versioning-requirements.md

@@ -13,6 +13,8 @@ component: plugin-development
 
 When making changes to the compound-engineering plugin, documentation can get out of sync with the actual components (agents, commands, skills). This leads to confusion about what's included in each version and makes it difficult to track changes over time.
 
+This document applies to the embedded marketplace plugin metadata, not the root CLI package release version. The root CLI package (`package.json`, root `CHANGELOG.md`, repo `v*` tags) is managed by semantic-release and follows the repository tag line.
+
 ## Solution
 
 **Every change to the plugin MUST include:**
@@ -75,3 +77,5 @@ This documentation serves as a reminder. When Claude Code works on this plugin,
 - `/Users/kieranklaassen/compound-engineering-plugin/plugins/compound-engineering/.claude-plugin/plugin.json`
 - `/Users/kieranklaassen/compound-engineering-plugin/plugins/compound-engineering/CHANGELOG.md`
 - `/Users/kieranklaassen/compound-engineering-plugin/plugins/compound-engineering/README.md`
+- `/Users/kieranklaassen/compound-engineering-plugin/package.json`
+- `/Users/kieranklaassen/compound-engineering-plugin/CHANGELOG.md`