plugin-versioninglisted

# Plugin Versioning ## Overview rnd-framework uses strict semver (`X.Y.Z`) in its plugin manifest. Version bumping, changelog management, and structural validation are automated via `lib/bump.sh` and `lib/validate.sh`. Always run validation after changes to skills, commands, hooks, or agents. ## Version Bumping ### Usage ```bash "${CLAUDE_PLUGIN_ROOT}/lib/bump.sh" "Short headline" "Optional longer description" ``` ### What It Does 1. Reads current version from `.claude-plugin/plugin.json` 2. Increments patch number (e.g., `1.0.1` -> `1.0.2`) 3. Writes new version to `plugin.json` 4. Prepends a CHANGELOG entry with today's date 5. Stages `plugin.json` and `CHANGELOG.md` via `git add` ### CHANGELOG Format ```markdown ## 1.0.2 — 2026-03-28 ### Short headline Optional longer description ``` ### When NOT to Bump - Pure documentation changes (README, CLAUDE.md edits) - Test-only changes (no user-facing behavior change) - Work-in-progress commits during a pipeline run (bump once at the end) ## Versioning Policy ### 0.x by Design rnd-framework stays on `0.x` while it is an experimental R&D system. This is a deliberate stance following ZeroVer (0ver.org): a `0.` major signals that the interfaces, protocols, and quality gates are actively evolving and that no stability guarantee has been made. The major version will not advance to `1` until the design has stabilised and a compatibility commitment is warranted. Attempting `bump.sh --major` while the version is `0.x` is r