moshcode 0.29.2 → 0.30.0

package/README.md

@@ -376,18 +376,32 @@ moshcode plugin install crypto    # add the marketplace + install `crypto`
 moshcode plugin remove stocks     # take it back off
 ```
 
-`stocks@moshcode` adds `/stocks:stocks`, `/stocks:signals`, `/stocks:research`,
-`/stocks:lookup`, `/stocks:reports`, and `/stocks:discover` — the same advis0r research surface described above,
-driven from inside a coding session.
+The two plugins share the four names for the questions both markets answer, and
+differ only where the markets do. Either one's `/…:help` prints its own list.
 
-`crypto@moshcode` adds `/crypto:crypto`, `/crypto:quote`, `/crypto:book`,
-`/crypto:bars`, `/crypto:spark`, `/crypto:pairs`, and `/crypto:coin`. It ships separately because it is a different surface,
-not a mode of the first: live venue reads instead of stored snapshots, and a
-score that must not be ranked against an equity's.
+| | `stocks@moshcode` | `crypto@moshcode` |
+|---|---|---|
+| shared | `help` `report` `quote` `lookup` | `help` `report` `quote` `lookup` |
+| its own | `signals` `research` `reports` `discover` | `book` `bars` `spark` `pairs` |
+
+So `/stocks:report NVDA` and `/crypto:report BTC` are the same question asked of
+different markets, while `/stocks:signals` (what an executive said on a call)
+and `/crypto:book` (live order book depth) have no counterpart on the other
+side. They ship separately because they are different surfaces, not modes of one
+another: stored snapshots versus live venue reads, and a crypto score that must
+not be ranked against an equity's.
 
 Restart the engine after installing either; a newly installed plugin is not live
 in a session that is already running.
 
+Updating an installed plugin is its own step, and upgrading moshcode does not do
+it: an engine only pulls a new copy when the *plugin's* own version moves.
+
+```sh
+claude plugin update stocks@moshcode
+claude plugin update crypto@moshcode
+```
+
 Plugin commands are namespaced `/<plugin>:<command>` — always, not only when two
 plugins collide — so it is `/stocks:signals AAPL`, and a bare `/signals` answers
 `Unknown command`. Typing `/` and picking from the menu inserts the right form.
@@ -412,7 +426,7 @@ any marketplace". `moshcode plugin install` runs both steps for you.
 ### Upgrading from `ticker@moshcode`
 
 `stocks` was called `ticker` before v0.29.0. Installing the new id does **not**
-replace the old one — engines install plugins side by side, so `/stocks:stocks` would
+replace the old one — engines install plugins side by side, so `/stocks:report` would
 come from two plugins at once. Remove the old id first:
 
 ```sh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "moshcode",
-  "version": "0.29.2",
+  "version": "0.30.0",
   "type": "module",
   "description": "moshcode — a metal wrapper for coding engines and native UGig/CoinPay workflow CLIs, with OpenPRD and moshscript",
   "repository": {

package/plugins/crypto/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "crypto",
   "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.",
-  "version": "0.1.0",
+  "version": "0.3.0",
   "author": {
     "name": "moshcoder",
     "url": "https://moshcode.sh"

package/plugins/crypto/README.md

@@ -6,13 +6,19 @@ across Alpaca's US crypto venue.
 
 | command | what it does |
 | --- | --- |
-| `/crypto:crypto BTC` | price, technicals, score, supply, order book |
+| `/crypto:help` | this list, in the engine |
+| `/crypto:report BTC` | price, technicals, score, supply, order book |
 | `/crypto:quote ETH-USD` | latest trade and quote, with the spread in bps |
+| `/crypto:lookup bitcoin` | asset name → `BTC/USD` |
 | `/crypto:book BTC-USD` | top of the order book, both sides |
 | `/crypto:bars ETH-USD` | historical OHLCV at any supported timeframe |
 | `/crypto:spark BTC ETH SOL` | recent moves across pairs, ranked |
 | `/crypto:pairs` | every supported pair, grouped by quote asset |
-| `/crypto:coin bitcoin` | asset name → `BTC/USD` |
+
+The first four names mean the same thing in `stocks@moshcode` — `help`,
+`report`, `quote`, `lookup` — so knowing one plugin gets you half the other.
+The rest are the parts a 24/7 venue has and equities do not: a live order book,
+arbitrary timeframes, and cross-pair comparison.
 
 Pairs are accepted as `BTC`, `BTC-USD`, `BTC/USD` or `BTCUSD`. A bare asset
 resolves to that asset's USD pair.
@@ -50,9 +56,9 @@ Point the commands at another instance with `MOSHCODE_ADVISOR_URL`.
 ## Why this is separate from `stocks`
 
 They answer different questions from different data, and share only a hostname.
-A `/stocks:stocks` report is a **stored snapshot** built from transcripts, SEC
+A `/stocks:report` report is a **stored snapshot** built from transcripts, SEC
 fundamentals and extracted signals — its risk is a stale price read as a live
-one. A `/crypto:crypto` report is a **live venue read** with no transcripts, no
+one. A `/crypto:report` report is a **live venue read** with no transcripts, no
 filings and no signals — its risk is the opposite: a price that is accurate to
 the second and stale by the time you act on it.
 

package/plugins/crypto/commands/help.md

@@ -0,0 +1,39 @@
+---
+description: What the crypto plugin can do, and the exact command names to type.
+---
+
+## Task
+
+List what this plugin provides. Do not call any tool — everything needed is
+below. Render it as a compact table, then the notes.
+
+| command | what it does |
+| --- | --- |
+| `/crypto:report <PAIR>` | the full report — price, technicals, score, supply, order book |
+| `/crypto:quote <PAIR>` | the short answer — latest trade, bid/ask, spread |
+| `/crypto:lookup <name>` | asset name → pair (`bitcoin` → `BTC/USD`) |
+| `/crypto:book <PAIR>` | top of the order book, both sides |
+| `/crypto:bars <PAIR>` | historical OHLCV at any supported timeframe |
+| `/crypto:spark <PAIR…>` | recent moves across several pairs, ranked |
+| `/crypto:pairs` | every supported pair, grouped by quote asset |
+
+## Notes to pass on
+
+- Pairs are accepted as `BTC`, `BTC-USD`, `BTC/USD` or `BTCUSD`. A bare asset
+  resolves to that asset's USD pair.
+- Every command name is namespaced `/crypto:…`. A bare `/report` is not a
+  command — Claude Code always prefixes plugin commands with the plugin name.
+- `stocks@moshcode` is the sibling plugin, and the four shared names mean the
+  same thing there: `/stocks:report`, `/stocks:quote`, `/stocks:lookup`,
+  `/stocks:help`. It adds `/stocks:signals`, `/stocks:research`,
+  `/stocks:reports` and `/stocks:discover` — transcript and filing work that
+  has no crypto equivalent.
+- **These are live venue reads, not stored snapshots** — the opposite of the
+  stocks plugin. Prices are Alpaca's US crypto venue alone and can differ
+  materially from other exchanges. Crypto trades 24/7: no close, no halt.
+- The crypto technical score counts venue-local liquidity, so it is **not
+  comparable** to a `/stocks:report` score. Do not rank the two against
+  each other.
+
+If the user asked for something no command covers, say so rather than
+improvising one that does not exist.

package/plugins/crypto/commands/{coin.md → lookup.md}

@@ -28,4 +28,4 @@ Fallback: `curl -sS "https://advis0r.com/api/crypto/lookup?q=<url-encoded>&limit
   match is the one they meant.
 - No match: say this venue lists no such pair, and do not invent a symbol. The
   coin may exist and simply not be listed here — those are different answers.
-- Offer `/crypto:crypto <PAIR>` for the match you land on.
+- Offer `/crypto:report <PAIR>` for the match you land on.

package/plugins/crypto/commands/pairs.md

@@ -25,7 +25,7 @@ URL-safe spelling (`BTC-USD`) used in paths; `symbol` is canonical (`BTC/USD`).
   different markets with three different liquidity profiles.
 - **`idle` means listed but not currently printing trades** — it is not the same
   as unsupported. Show idle pairs, marked, rather than filtering them out.
-- If the user was looking for a specific coin, use `/crypto:coin <name>` instead of
+- If the user was looking for a specific coin, use `/crypto:lookup <name>` instead of
   scanning this list for them.
 - This is the coverage of one venue, not of crypto. A coin missing here is
   missing *from Alpaca's US venue*.

package/plugins/crypto/commands/{crypto.md → report.md}

@@ -42,9 +42,9 @@ resolves to that asset's USD pair.
 - Crypto trades 24/7 with no circuit breakers and no market close. Never
   describe a crypto price as "at the close" or "premarket".
 - State `generatedAt` / `fetchedAt`. This is a live read, so it goes stale in
-  seconds, not days — the opposite failure mode from a stored `/stocks:stocks` report.
+  seconds, not days — the opposite failure mode from a stored `/stocks:report` report.
 - The score's liquidity component counts venue-local volume only, so it is
-  **not comparable** to an equity's score from `/stocks:stocks`. Do not rank the two
+  **not comparable** to an equity's score from `/stocks:report`. Do not rank the two
   against each other.
 - End with the response's own `disclaimer`. This is research, not advice.
 - Link the shareable page: `https://advis0r.com/crypto/<PAIR>`.

package/plugins/crypto/commands/spark.md

@@ -32,5 +32,5 @@ Fallback: `curl -sS "https://advis0r.com/api/crypto/sparklines?symbols=BTC-USD,E
 - Name the window (`start` → `end`) and the period. "Up 5%" over 24h and over 7d
   are different claims.
 - Do not extrapolate a trend from 24 points, and do not call a direction
-  "momentum" without the technicals to back it — `/crypto:crypto <PAIR>` has those.
+  "momentum" without the technicals to back it — `/crypto:report <PAIR>` has those.
 - End with the response's own `disclaimer`.

package/plugins/stocks/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "stocks",
   "description": "Equity research slash commands backed by advis0r.com: scored reports, extracted signals, transcript search, company-name lookup, and ranked watchlists.",
-  "version": "0.1.0",
+  "version": "0.3.0",
   "author": {
     "name": "moshcoder",
     "url": "https://moshcode.sh"

package/plugins/stocks/README.md

@@ -6,13 +6,23 @@ and ranked watchlists.
 
 | command | what it does |
 | --- | --- |
-| `/stocks:stocks NVDA` | score, technicals, fundamentals, thesis, signals, sources |
+| `/stocks:help` | this list, in the engine |
+| `/stocks:report NVDA` | score, technicals, fundamentals, thesis, signals, sources |
+| `/stocks:quote NVDA` | the short answer — price, score, staleness |
+| `/stocks:lookup rivian` | company name → `RIVN` |
 | `/stocks:signals AAPL` | what was actually said, quoted and sourced |
 | `/stocks:research data center` | full-text search across every indexed transcript |
-| `/stocks:lookup rivian` | company name → `RIVN` |
 | `/stocks:reports` | every stored report, best score first |
 | `/stocks:discover fusion` | a ranked watchlist for a topic (slow) |
 
+The first four names mean the same thing in `crypto@moshcode` — `help`,
+`report`, `quote`, `lookup` — so knowing one plugin gets you half the other.
+The rest are the parts equities have and crypto does not: transcripts, filings,
+and a watchlist built from them.
+
+Note `report` and `reports` are different commands: singular takes a symbol and
+returns one write-up, plural takes nothing and lists the whole stored index.
+
 The `stocks:` prefix is not optional. Claude Code namespaces every plugin
 command as `/<plugin>:<command>` — always, not only when two plugins collide —
 so a bare `/stocks` answers `Unknown command`. Typing `/` and picking from the
@@ -24,11 +34,11 @@ command, not this plugin's.)
 ## Upgrading from `ticker@moshcode`
 
 This plugin used to be called `ticker`. Both it and its headline command were
-renamed so the name says which market it covers, now that `/crypto:crypto` sits beside
+renamed so the name says which market it covers, now that `/crypto:report` sits beside
 it.
 
 Installing the new one does **not** replace the old one — engines install
-plugins side by side, so `/stocks:stocks` would come from two plugins at once. Remove
+plugins side by side, so `/stocks:report` would come from two plugins at once. Remove
 the old id first:
 
 ```bash

package/plugins/stocks/commands/help.md

@@ -0,0 +1,34 @@
+---
+description: What the stocks plugin can do, and the exact command names to type.
+---
+
+## Task
+
+List what this plugin provides. Do not call any tool — everything needed is
+below. Render it as a compact table, then the notes.
+
+| command | what it does |
+| --- | --- |
+| `/stocks:report <SYMBOL>` | the full research report — score, technicals, fundamentals, thesis, signals, sources |
+| `/stocks:quote <SYMBOL>` | the short answer — price, score, staleness |
+| `/stocks:lookup <company>` | company name → ticker (`rivian` → `RIVN`) |
+| `/stocks:signals <SYMBOL>` | what was actually said, quoted and sourced |
+| `/stocks:research <words…>` | full-text search across every indexed transcript |
+| `/stocks:reports` | every stored report, best score first |
+| `/stocks:discover <topic>` | a ranked watchlist for a topic (slow — analyzes each candidate) |
+
+## Notes to pass on
+
+- **`report` and `reports` are different commands.** Singular takes a symbol and
+  returns one write-up; plural takes nothing and lists the whole stored index.
+- Every command name is namespaced `/stocks:…`. A bare `/report` is not a
+  command — Claude Code always prefixes plugin commands with the plugin name.
+- `crypto@moshcode` is the sibling plugin, and the four shared names mean the
+  same thing there: `/crypto:report`, `/crypto:quote`, `/crypto:lookup`,
+  `/crypto:help`. It adds `/crypto:book`, `/crypto:bars`, `/crypto:spark` and
+  `/crypto:pairs` for things equities do not have.
+- Everything here is a **stored snapshot** from advis0r.com, read-only and
+  public. Nothing in this plugin can place an order — that is `moshcode trade`.
+
+If the user asked for something no command covers, say so rather than
+improvising one that does not exist.

package/plugins/stocks/commands/lookup.md

@@ -22,6 +22,6 @@ Fallback: `curl -sS "https://advis0r.com/api/lookup?q=<url-encoded>&limit=10"`
 ## Rules
 
 - Show every match with its exchange — "Delta" is an airline and a faucet company.
-- Mark which ones have a report, and offer `/stocks:stocks <SYMBOL>` for those.
+- Mark which ones have a report, and offer `/stocks:report <SYMBOL>` for those.
 - One unambiguous match: say the symbol and go straight to offering the report.
 - No match: say the *directory* has no match, and do not invent a symbol.

package/plugins/stocks/commands/quote.md

@@ -0,0 +1,37 @@
+---
+description: The fast read on one ticker — price, score, and how stale the snapshot is.
+argument-hint: <SYMBOL>
+allowed-tools: Bash(moshcode stocks:*), Bash(curl -sS https://advis0r.com/api/:*)
+---
+
+## Task
+
+Give the short answer on `$ARGUMENTS` — price and score, not the full write-up.
+
+```bash
+moshcode stocks $ARGUMENTS --json
+```
+
+Fallback: `curl -sS "https://advis0r.com/api/ticker?symbol=$ARGUMENTS"`
+
+This is the same document `/stocks:report` reads. The difference is what you do
+with it: four lines, not a report. If the user wants the thesis, signals and
+sources, that is `/stocks:report`.
+
+## Reading the response
+
+Take only: `lastPrice`, `priceTimestamp`, `delayed`, `overallScore`,
+`classification`, and `companyName`.
+
+## Rules
+
+- **Four lines at most.** Price, score with classification, staleness, and one
+  pointer to `/stocks:report <SYMBOL>` for the rest. Brevity is the feature.
+- **This is a stored snapshot, not a live quote.** Print `priceTimestamp` and
+  say `delayed` when it is — a stale price presented as a live one is the one
+  failure here that costs money. Equities are not crypto: this number can be
+  days old.
+- A low score is the answer, not a failure to answer. Say it plainly.
+- Keep the response's own `disclaimer` if the user is acting on the number.
+- If the symbol 400s with `didYouMean`, they typed a company name — re-run
+  against the suggestion and say you did, or point at `/stocks:lookup`.

package/plugins/stocks/commands/reports.md

@@ -26,5 +26,5 @@ generatedAt }`, and `total` is how many exist.
 - **`generatedAt` per row, always.** These are snapshots taken at different
   times; a table that hides that reads as one consistent as-of date.
 - A row with no `aiProvider` was scored deterministically, not by a model.
-- Offer `/stocks:stocks <SYMBOL>` for anything worth a closer look.
+- Offer `/stocks:report <SYMBOL>` for anything worth a closer look.
 - This is a coverage list, not a recommendation list. Rank order is score order.

package/src/plugins.mjs

@@ -39,22 +39,51 @@ export function marketplaceSource(env = process.env) {
  * `example` exists because the invitation printed after an install has to be
  * runnable. It used to append a hardcoded "NVDA" to whatever came first in
  * `commands`, which told anyone installing the crypto plugin to try a stock.
+ *
+ * `version` mirrors each plugin's own plugin.json, and it is not decoration:
+ * "If set, users only receive updates when you bump this field."
+ * https://code.claude.com/docs/en/plugins-reference#version-management
+ *
+ * So editing a plugin's commands and shipping a moshcode release is *not*
+ * enough — an existing install keeps serving the old copy until this number
+ * moves. Both plugins sat at 0.1.0 through v0.29.2, which rewrote every command
+ * file. Change a plugin's contents, bump its version, in the same commit.
+ * A test fails when this list and the manifests disagree.
  */
 export const PLUGINS = [
   {
     name: "stocks",
+    version: "0.3.0",
     description: "equity research slash commands backed by advis0r.com",
-    commands: ["/stocks:stocks", "/stocks:signals", "/stocks:research", "/stocks:lookup", "/stocks:reports", "/stocks:discover"],
-    example: "/stocks:stocks NVDA",
+    commands: [
+      "/stocks:help", "/stocks:report", "/stocks:quote", "/stocks:lookup",
+      "/stocks:signals", "/stocks:research", "/stocks:reports", "/stocks:discover",
+    ],
+    example: "/stocks:report NVDA",
   },
   {
     name: "crypto",
+    version: "0.3.0",
     description: "crypto market data slash commands backed by advis0r.com",
-    commands: ["/crypto:crypto", "/crypto:quote", "/crypto:book", "/crypto:bars", "/crypto:spark", "/crypto:pairs", "/crypto:coin"],
-    example: "/crypto:crypto BTC",
+    commands: [
+      "/crypto:help", "/crypto:report", "/crypto:quote", "/crypto:lookup",
+      "/crypto:book", "/crypto:bars", "/crypto:spark", "/crypto:pairs",
+    ],
+    example: "/crypto:report BTC",
   },
 ];
 
+/**
+ * Command names both plugins are expected to share.
+ *
+ * The two cover different markets, so they can never ship the same *set* — a
+ * crypto pair has no earnings transcript and an equity has no order book. What
+ * they can share is vocabulary: the same question is spelled the same way on
+ * both sides, so knowing one plugin means knowing half the other. A test holds
+ * this, because the natural drift is for one side to grow a synonym.
+ */
+export const SHARED_COMMANDS = ["help", "report", "quote", "lookup"];
+
 /** How Claude Code namespaces a plugin's command. */
 export function pluginCommandName(plugin, file) {
   return `/${plugin}:${String(file).replace(/\.md$/, "")}`;