v0.29.3 — updates that reach you

A patch release. The moshcode half changes nothing you can see; the part that matters is in the plugins.

Both plugins are now 0.2.0

Claude Code only pulls a new copy of a plugin when the plugin's own version moves:

"If set, users only receive updates when you bump this field."

Both plugins had declared 0.1.0 since the day they were created — through every change since, including v0.29.2, which rewrote every command file to carry the namespaced /stocks:… and /crypto:… names. Existing installs kept serving the old copy, so the surface people were told to use was not the surface they had.

Both now declare 0.2.0, which makes those edits reachable:

claude plugin update stocks@moshcode
claude plugin update crypto@moshcode

Restart the engine afterwards. If you installed either plugin for the first time today, you already have the current content and this changes nothing for you.

moshcode upgrade does not do this. It updates the CLI and leaves installed plugins exactly where they were — which was not obvious anywhere, and is now in the README.

Stopping it happening again

The plugin version joins the catalog in src/plugins.mjs, right beside the command list an editor is already touching when they change a plugin, with the update mechanism spelled out above it. A test pins the catalog to the manifest that ships, and it was checked to fail when the two disagree rather than merely passing today.