moshcode 0.29.2 → 0.29.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -388,6 +388,14 @@ score that must not be ranked against an equity's.
388
388
  Restart the engine after installing either; a newly installed plugin is not live
389
389
  in a session that is already running.
390
390
 
391
+ Updating an installed plugin is its own step, and upgrading moshcode does not do
392
+ it: an engine only pulls a new copy when the *plugin's* own version moves.
393
+
394
+ ```sh
395
+ claude plugin update stocks@moshcode
396
+ claude plugin update crypto@moshcode
397
+ ```
398
+
391
399
  Plugin commands are namespaced `/<plugin>:<command>` — always, not only when two
392
400
  plugins collide — so it is `/stocks:signals AAPL`, and a bare `/signals` answers
393
401
  `Unknown command`. Typing `/` and picking from the menu inserts the right form.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "moshcode",
3
- "version": "0.29.2",
3
+ "version": "0.29.3",
4
4
  "type": "module",
5
5
  "description": "moshcode — a metal wrapper for coding engines and native UGig/CoinPay workflow CLIs, with OpenPRD and moshscript",
6
6
  "repository": {
@@ -2,7 +2,7 @@
2
2
  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
3
3
  "name": "crypto",
4
4
  "description": "Crypto market data slash commands backed by advis0r.com: live prices, technical scores, order books, OHLCV history and sparklines across Alpaca's US crypto venue.",
5
- "version": "0.1.0",
5
+ "version": "0.2.0",
6
6
  "author": {
7
7
  "name": "moshcoder",
8
8
  "url": "https://moshcode.sh"
@@ -2,7 +2,7 @@
2
2
  "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
3
3
  "name": "stocks",
4
4
  "description": "Equity research slash commands backed by advis0r.com: scored reports, extracted signals, transcript search, company-name lookup, and ranked watchlists.",
5
- "version": "0.1.0",
5
+ "version": "0.2.0",
6
6
  "author": {
7
7
  "name": "moshcoder",
8
8
  "url": "https://moshcode.sh"
package/src/plugins.mjs CHANGED
@@ -39,16 +39,28 @@ export function marketplaceSource(env = process.env) {
39
39
  * `example` exists because the invitation printed after an install has to be
40
40
  * runnable. It used to append a hardcoded "NVDA" to whatever came first in
41
41
  * `commands`, which told anyone installing the crypto plugin to try a stock.
42
+ *
43
+ * `version` mirrors each plugin's own plugin.json, and it is not decoration:
44
+ * "If set, users only receive updates when you bump this field."
45
+ * https://code.claude.com/docs/en/plugins-reference#version-management
46
+ *
47
+ * So editing a plugin's commands and shipping a moshcode release is *not*
48
+ * enough — an existing install keeps serving the old copy until this number
49
+ * moves. Both plugins sat at 0.1.0 through v0.29.2, which rewrote every command
50
+ * file. Change a plugin's contents, bump its version, in the same commit.
51
+ * A test fails when this list and the manifests disagree.
42
52
  */
43
53
  export const PLUGINS = [
44
54
  {
45
55
  name: "stocks",
56
+ version: "0.2.0",
46
57
  description: "equity research slash commands backed by advis0r.com",
47
58
  commands: ["/stocks:stocks", "/stocks:signals", "/stocks:research", "/stocks:lookup", "/stocks:reports", "/stocks:discover"],
48
59
  example: "/stocks:stocks NVDA",
49
60
  },
50
61
  {
51
62
  name: "crypto",
63
+ version: "0.2.0",
52
64
  description: "crypto market data slash commands backed by advis0r.com",
53
65
  commands: ["/crypto:crypto", "/crypto:quote", "/crypto:book", "/crypto:bars", "/crypto:spark", "/crypto:pairs", "/crypto:coin"],
54
66
  example: "/crypto:crypto BTC",