bump-version

# Instructions ## the scheme `vMAJOR.MINOR.PATCH`, where two of the three fields are counts rather than decisions: - MAJOR stays `0` until the marketplace is a public commitment; nothing here moves it yet - MINOR is the plugin count, so it moves only on the commit that adds a plugin tree - PATCH is `git rev-list --count <minor tag>..HEAD`, derived on every run - a reader can therefore price a version without a changelog: `v0.3.66` is three plugins, 66 commits on - the history is linear, zero merges, so an ordinal is unambiguous and `--first-parent` is moot ## the tags only MINOR tags exist as refs; PATCH is computed and never written: - a patch tag would become the newest tag and reset the count `git describe` returns - that is why the anchor lookup carries `--match 'v[0-9]*.[0-9]*.0'` rather than reading any tag - the four anchors were cut retroactively, annotated, and retro-dated through `GIT_COMMITTER_DATE` - `v0.0.0` fe9b506, the rulebook before any plugin; `v0.1.0` 63c8d3b gitgud; `v0.2.0` 2dbd3f2 retardify; `v0.3.0` 00c3dd0 operator - the three trees landed as three consecutive commits, so `v0.1.0` and `v0.2.0` each live one commit - the plugins migration at 3816224 holds no minor, since it predates all three trees; it is `v0.0.76` - ordering inside that burst is arbitrary and follows commit order, because the trees were authored together; the tags record the sequence rather than claiming a birth order ## the manifest `plugins/*/.claude-plugin/plugin.json` carr...