versionlisted

# /forge:version Cut a release: determine the current version, bump it, update the version files, and create and push an annotated tag. Works for code projects, writing projects, and plugin repos. Requested bump: $ARGUMENTS. Accepts `major`, `minor`, `patch`, or an explicit version like `1.2.3`. If empty, ask. ## Orientation - In a plugin marketplace monorepo (a `marketplace.json` listing more than one plugin), ask which plugin this release covers. Each plugin versions independently from its own `plugin.json`. Tag as `{plugin}--v{version}`, the double-hyphen form `claude plugin tag` produces and dependency resolution filters on. Update the changelog beside that plugin's manifest when one exists, else the root changelog. - Otherwise, find the current version in this order: `VERSION.md`, semver git tags, a manifest version field. Nothing found means `0.0.0` and a first tagged release. Say so. ## Workflow 1. Report the current and new version. Tag only after the user confirms. 2. Update the version where it lives: the plugin's `plugin.json` in a marketplace monorepo, otherwise `VERSION.md` when present plus known manifest files. Never search-and-replace across the repo. 3. Update the changelog: a new top section with commit subjects since the last matching tag (`{plugin}--v*` in a monorepo, limited to commits touching that plugin's directory), grouped by type per the `conventional-commits` skill. 4. Commit everything together as `chore(rel