v0.30.0 — one vocabulary
Breaking, in the plugins. Three commands were renamed, and both plugins gained a /help.
If you have either plugin installed
claude plugin update stocks@moshcode
claude plugin update crypto@moshcodeThen restart the engine. Until you do, your install keeps the old names — a moshcode upgrade does not carry plugin changes.
| was | now |
|---|---|
/stocks:stocks NVDA |
/stocks:report NVDA |
/crypto:crypto BTC |
/crypto:report BTC |
/crypto:coin bitcoin |
/crypto:lookup bitcoin |
One vocabulary across both
The two plugins had grown separate words for the same question — stocks and crypto for "the full report", coin and lookup for "name → symbol". Knowing one taught you nothing about the other. And the headline command in each was named after its own plugin, which is what produced the /crypto:crypto stutter.
They can't ship the same set — a crypto pair has no earnings transcript, an equity has no order book — but they can share vocabulary, and now do:
stocks@moshcode |
crypto@moshcode |
|
|---|---|---|
| shared | help report quote lookup |
help report quote lookup |
| its own | signals research reports discover |
book bars spark pairs |
Eight each, four spelled identically. /stocks:report NVDA and /crypto:report BTC are the same question asked of different markets.
New
/stocks:help, /crypto:help — each lists its own plugin's commands, no tool call needed. "Command not found" now has a signpost.
/stocks:quote NVDA — the four-line read: price, score, and how stale the snapshot is. It exists because moshcode stocks quote already worked in the CLI, so the plugin was the one surface where the word didn't — which is how it got found.
Guards
Two tests now hold the shape: every plugin must ship each shared name, and no command may repeat its own plugin's name — the rule /crypto:crypto would have failed.
Nothing in the moshcode CLI changed. moshcode stocks and moshcode crypto keep every verb and alias they had.