commit

# Commit with auto version bump This project follows semver. **Every commit must include a version bump** in: - `plugins/corezoid/.claude-plugin/plugin.json` - `.claude-plugin/marketplace.json` ## Step 1 — Inspect changes Run in parallel: - `git diff HEAD` — see what changed - `git status` — see untracked files - `git log -5 --oneline` — see recent commit style ## Step 2 — Determine bump type | Change type | Bump | |---|---| | New feature, new tool, new skill, new node type | **minor** (2.3.x → 2.4.0) | | Bug fix, doc update, text fix, refactor | **patch** (2.3.x → 2.3.x+1) | | Breaking change, major redesign | **major** (2.x.x → 3.0.0) | Read current version from `plugins/corezoid/.claude-plugin/plugin.json`. ## Step 3 — Update versions Update the `"version"` field in **both** files to the new version: - `plugins/corezoid/.claude-plugin/plugin.json` - `.claude-plugin/marketplace.json` ## Step 3.5 — Update CHANGELOG.md Prepend a new entry at the top of `CHANGELOG.md` (right after the `# Changelog` heading) following the existing format: ``` ## [<new_version>] - <bullet summarising what changed — one line per logical change> ``` Derive the bullets from the staged diff: group related changes into a single readable line each. Keep it concise — one sentence per item. ## Step 3.6 — Update README.md Review the diff for changes that affect README content and update the relevant sections in `README.md`: | What changed | What to update in README.md | |---|---| | New or...