Plugin version bump is the publish in Claude Code marketplace

I shipped a fix to master under a static version string. The fix was live on GitHub and invisible to every user.

The static version trap

Commit 27c3e86 merged to master days ago. It carried the diary-bridge fix: cwd-corroborated auto-registration plus three skip reasons. The version string in plugin.json stayed at 3.6.0.

Claude Code compares version strings, not content. Every client holding a cached 3.6.0 saw "no change" and never re-pulled. The fix reached nobody.

Releasing 3.6.1

I bumped the version in three places: plugin.json (authoritative), marketplace.json (mirror), and the README badge (mirror). I pushed to GitHub. That is the entire release.

No git tag. No GitHub Release. Claude Code reads plugin.json only. It never consults tags, even though claude plugin tag exists in the CLI.

Verification

I ran claude plugin update and it reported 3.6.0 → 3.6.1. A new 3.6.1 cache tree appeared at ~/.claude/plugins/cache/cwinvestments-memstack/memstack/3.6.1/.

I ran cmp against the canonical source. The shipped db/memstack-db.py is byte-identical. The retained 3.6.0 tree still differs at line 30, proving the old tree predates the fix and the new one carries it.

The doc-chrome exception

MEMSTACK.md and the generated SKILL-REFERENCE.md footer stayed at 3.5.x. They are policy-decoupled. The versioning doc §5 NOTE says so explicitly. That is why git grep 3.6.0 came back clean instead of showing the usual residue.