publish-plugins

# Publish Plugins Prepare the repo's plugins for release: work out which ones changed, bump their versions, and check the manifests still describe what is on disk. Each plugin owns its version in its own `.claude-plugin/plugin.json`, and the repo-root `.claude-plugin/marketplace.json` carries no `version` fields: | Plugin | Manifest | | ------------------------- | ------------------------------------------------------------ | | `hal-skills` | `skills/.claude-plugin/plugin.json` | | `hal-voice` | `plugins/hal-voice/.claude-plugin/plugin.json` | | `hal-session-auto-rename` | `plugins/hal-session-auto-rename/.claude-plugin/plugin.json` | ## 1. Find the changed plugins ```bash git diff --name-only origin/main... ``` `skills/**` belongs to `hal-skills`, `plugins/<name>/**` to that plugin. Only the plugins with changes are candidates for a bump. ## 2. Check what is already bumped For each candidate, compare the working-tree version against `origin/main`: ```bash git show origin/main:skills/.claude-plugin/plugin.json ``` If a plugin's version already differs from `origin/main`, it was bumped for unreleased work. **Do not bump it again.** Only bump a plugin whose version still matches `origin/main`. Check each candidate independently — a change under `skills/` says nothing about whether `hal-voice` needs a bump. ## 3. Bump - **Patch** (0...