dexterm-cli 0.1.3 → 0.1.4

package/dist/packages/mcp/assets/kb/docs/docs-scan-the-read.md

@@ -0,0 +1,25 @@
+---
+id: docs-scan-the-read
+title: AI scan mode › The read
+kind: docs
+page: scan
+page_title: AI scan mode
+heading: The read
+anchor: the-read
+url: https://dexterm.xyz/docs/scan#the-read
+tags:
+  - docs
+  - scan
+  - read
+  - mode
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scan.md
+date: 2026-10-16
+---
+
+A lock opens the coin exactly as `⏎` would (the same loader, the same fetches that token costs anyway) and starts a chat turn asking for the short read, with the WHY reasons passed as **numbers only, never token text**. Refreshes ask the same warm session what changed. Answers follow the short style (https://dexterm.xyz/docs/analyst#answer-style): call, why, levels, size, one risk.

package/dist/packages/mcp/assets/kb/docs/docs-scan-triggers-and-score.md

@@ -0,0 +1,37 @@
+---
+id: docs-scan-triggers-and-score
+title: AI scan mode › Triggers and score
+kind: docs
+page: scan
+page_title: AI scan mode
+heading: Triggers and score
+anchor: triggers-and-score
+url: https://dexterm.xyz/docs/scan#triggers-and-score
+tags:
+  - docs
+  - scan
+  - triggers
+  - score
+  - mode
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scan.md
+date: 2026-10-16
+---
+
+Inputs come from memory and the local SQLite cache only: the screener rows, the DexScreener pair already cached for the flow panel, the open token's loaded view, and LARP verdicts that already exist. A unit test wraps the HTTP client and asserts zero calls over fifty scan ticks; measured live, requests per minute with the scan on and off were the same.
+
+| trigger | fires when (defaults) | weight |
+|---|---|---|
+| `vol` | 5m volume ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands)× the coin's own average 5-minute pace (6h, falling back to 1h/24h), at least $(generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands); full strength at (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands)× | 30 |
+| `flow` | buy/sell flip: 5m buy share ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) while the 1h share ≤ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands), at least (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) 5m transactions | 25 |
+| `fresh` | age ≤ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) min, ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) 5m transactions, 5m buy share ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands), 5m volume ≥ $(generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) | 20 |
+| `breakout` | last close above the prior (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) cached candles' high by ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands)% (only coins whose candles are already loaded, in practice the open one) | 20 |
+| `liq` | liquidity ≥ +(generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands)% vs the coin's own 10-minute minimum | 15 |
+| `holders` | holders ≥ +(generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands)% and ≥ +(generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) vs the oldest 10-minute sample | 15 |
+
+Points per fired trigger = weight × (0.5 + 0.5 × strength); the score is the sum, capped at 100. A coin is **exciting** at score ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) with ≥ (generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands) triggers. Gate: liquidity ≥ $(generated from the app: see https://dexterm.xyz/docs/scan#triggers-and-score; app-help has the exact keys and commands). Vetoes set the score to zero and say why: an existing `LARP` verdict (the detector is never invoked by the scan), or a mint or freeze authority that is still enabled.

package/dist/packages/mcp/assets/kb/docs/docs-scan.md

@@ -0,0 +1,24 @@
+---
+id: docs-scan
+title: AI scan mode
+kind: docs
+page: scan
+page_title: AI scan mode
+url: https://dexterm.xyz/docs/scan
+tags:
+  - docs
+  - scan
+  - mode
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scan.md
+date: 2026-10-16
+---
+
+An observe-only watcher that scores every coin on screen, pulls up the one that lights up, and keeps analysing it.
+
+AI scan mode watches the screener for you: it scores every coin from data the app already holds, and when one crosses the line it opens that coin's token screen and starts a short analyst read. It is **off by default**, it adds **no network requests**, and it is **observe-only**: a scan session can never open a ticket, sign, confirm or trade. Four structural layers enforce that, not a prompt.

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-frozen-canary.md

@@ -0,0 +1,30 @@
+---
+id: docs-scorecard-frozen-canary
+title: Public measurement scorecard › Latest skill-care run › Frozen canary
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Frozen canary
+anchor: frozen-canary
+url: https://dexterm.xyz/docs/scorecard#frozen-canary
+tags:
+  - docs
+  - scorecard
+  - frozen
+  - canary
+  - latest
+  - skill-care
+  - run
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+The fixed task-1401 test split is the canary. Shipped LARP MCC is **0.054** against a frozen baseline of **0.054**; the candidate scored **0.053**. Shipped rug-rule MCC is **0.159**, the same as its frozen baseline and candidate. The gate reported that the canary held, but it still rejected the candidate because the held-out improvement test failed.

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-frozen-task-1401-evaluation.md

@@ -0,0 +1,35 @@
+---
+id: docs-scorecard-frozen-task-1401-evaluation
+title: Public measurement scorecard › Frozen task-1401 evaluation
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Frozen task-1401 evaluation
+anchor: frozen-task-1401-evaluation
+url: https://dexterm.xyz/docs/scorecard#frozen-task-1401-evaluation
+tags:
+  - docs
+  - scorecard
+  - frozen
+  - task-1401
+  - evaluation
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+**Dataset:** 1054 coins observed from 2026-10-10 through 2026-10-13, with a 3-day outcome horizon. The earlier 726 rows were the train split; the later **328 rows were held out**, including 61 bad outcomes. Tuning used train rows only and the code refuses test rows. Rates use 95% Wilson intervals; fewer than 20 rows gets counts only.
+
+Evidence was restricted to a point-in-time token record fetched no more than one hour after t0. Later records were excluded. Labels are keyless recorder proxies, not chain-adjudicated facts.
+
+| Held-out result | Before | Shipped | Reading |
+|---|---:|---:|---|
+| Links-only LARP MCC | 0.039 | **0.054** | **Weak.** Link shape alone barely separated bad coins from the rest. |
+| Rug-rule MCC | 0.043 | **0.159** | Better, but still modest and dataset-specific. |

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-latest-skill-care-run.md

@@ -0,0 +1,33 @@
+---
+id: docs-scorecard-latest-skill-care-run
+title: Public measurement scorecard › Latest skill-care run
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Latest skill-care run
+anchor: latest-skill-care-run
+url: https://dexterm.xyz/docs/scorecard#latest-skill-care-run
+tags:
+  - docs
+  - scorecard
+  - latest
+  - skill-care
+  - run
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+This rolling check was generated **2026-10-16** from 1000 labelled coins: 670 train and **330 held out**. It proposed **no change**. There were 0 new labelled coins since the last accepted tuning; the gate requires 150. The recorded reason also says no subject cleared noise on the held-out window.
+
+| Held-out check | Current | Candidate | What happened |
+|---|---:|---:|---|
+| Links-only LARP MCC | 0.084 | 0.058 | Candidate was worse. Candidate precision was 27.3% (95% CI 13.2%–48.2%); recall was 9.7% (95% CI 4.5%–19.5%). |
+| Rug-rule MCC | 0.142 | 0.142 | No change. Precision was 28.2% (95% CI 19.8%–38.6%); recall was 38.7% (95% CI 27.6%–51.2%). |

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-links-only-larp-baseline-where-it-is-weak.md

@@ -0,0 +1,35 @@
+---
+id: docs-scorecard-links-only-larp-baseline-where-it-is-weak
+title: Public measurement scorecard › Frozen task-1401 evaluation › Links-only LARP baseline: where it is weak
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Links-only LARP baseline: where it is weak
+anchor: links-only-larp-baseline-where-it-is-weak
+url: https://dexterm.xyz/docs/scorecard#links-only-larp-baseline-where-it-is-weak
+tags:
+  - docs
+  - scorecard
+  - links-only
+  - larp
+  - baseline
+  - where
+  - weak
+  - frozen
+  - task-1401
+  - evaluation
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+The shipped held-out MCC is **0.054**. The `LARP` grade appeared only 14 times and 4 later had a bad outcome. Because that is fewer than 20 rows, the harness withholds precision and the grade-level confidence interval; it is **too small to rate**. The raw confusion matrix is 4 true positives, 10 false positives, 57 false negatives and 257 true negatives.
+
+The `EARLY_BUT_REAL` grade had 19/184 bad outcomes: 10.3% (95% CI 6.7%–15.6%). The whole held-out set had 61/328 bad outcomes: 18.6% (95% CI 14.8%–23.2%). This is a links-only prior. It cannot score the fetched-page, domain, GitHub or model-judgement stage.

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-not-measured.md

@@ -0,0 +1,29 @@
+---
+id: docs-scorecard-not-measured
+title: Public measurement scorecard › Not measured
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Not measured
+anchor: not-measured
+url: https://dexterm.xyz/docs/scorecard#not-measured
+tags:
+  - docs
+  - scorecard
+  - measured
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+- **Full LARP judgement:** fetched pages, domain history, GitHub evidence and the model stage cannot be reconstructed as they appeared in the past. Forward scoring waits for at least 50 recorded verdicts matched to later outcomes.
+- **Rug model output:** probability and bias are measured forward from recorded pack verdicts, not by this replay.
+- **Trench scan:** there is no per-token labelled outcome.
+- **Dev-history backtest:** No checked-in dev-history backtest result exists yet. This section deliberately shows no metric.

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-rug-verdict-rules.md

@@ -0,0 +1,33 @@
+---
+id: docs-scorecard-rug-verdict-rules
+title: Public measurement scorecard › Frozen task-1401 evaluation › Rug verdict rules
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Rug verdict rules
+anchor: rug-verdict-rules
+url: https://dexterm.xyz/docs/scorecard#rug-verdict-rules
+tags:
+  - docs
+  - scorecard
+  - rug
+  - verdict
+  - rules
+  - frozen
+  - task-1401
+  - evaluation
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+For the shipped rules, warning grades had precision **28.6% (95% CI 20.3%–38.6%)** and recall **42.6% (95% CI 31.0%–55.1%)** on the held-out split. The confusion matrix is 26 true positives, 65 false positives, 35 false negatives and 202 true negatives.
+
+The strongest measured split was low liquidity: `SPECULATIVE` had 23/42 bad outcomes, **54.8% (95% CI 39.9%–68.8%)**. `WATCH` had 34/236, **14.4% (95% CI 10.5%–19.5%)**. Dev percentage, organic score and top-10 concentration did not predict a worse 72-hour outcome in this dataset; they now lower confidence instead of setting the verdict.

package/dist/packages/mcp/assets/kb/docs/docs-scorecard-source-and-rebuild.md

@@ -0,0 +1,31 @@
+---
+id: docs-scorecard-source-and-rebuild
+title: Public measurement scorecard › Source and rebuild
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+heading: Source and rebuild
+anchor: source-and-rebuild
+url: https://dexterm.xyz/docs/scorecard#source-and-rebuild
+tags:
+  - docs
+  - scorecard
+  - source
+  - rebuild
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+- Frozen data and report: `packages/packs/eval/skills-eval.json` and `packages/packs/eval/skills-backtest.json`.
+- Rolling skill care: `packages/packs/eval/skill-care-latest.json`.
+- Method details: LARP and skill evaluation (https://dexterm.xyz/docs/larp#measured-accuracy).
+
+`dexterm/scripts/docs-sync.sh` regenerates this page before rebuilding the analyst docs knowledge base. `npm run docs:check` compares this file byte-for-byte with the generator output, so edited claims or favorable rounding fail the check.

package/dist/packages/mcp/assets/kb/docs/docs-scorecard.md

@@ -0,0 +1,27 @@
+---
+id: docs-scorecard
+title: Public measurement scorecard
+kind: docs
+page: scorecard
+page_title: Public measurement scorecard
+url: https://dexterm.xyz/docs/scorecard
+tags:
+  - docs
+  - scorecard
+  - public
+  - measurement
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/scorecard.md
+date: 2026-10-16
+---
+
+Held-out results, confidence intervals, frozen canaries, and the weak spots—generated from checked-in research outputs.
+
+This page is generated from the checked-in backtest JSON. It reports the weak results with the same prominence as the stronger ones and does not turn a small or missing sample into a claim. These metrics measure agreement with a later **bad price outcome** (rug or dead under the recorder label), not whether a product is real, safe, or worth trading.
+
+> warn: this is model evaluation, not trading performance. A grade is a risk flag, not a certificate. Nothing here predicts returns.

package/dist/packages/mcp/assets/kb/docs/docs-screens-1-screener.md

@@ -0,0 +1,35 @@
+---
+id: docs-screens-1-screener
+title: Screens tour › 1 · Screener
+kind: docs
+page: screens
+page_title: Screens tour
+heading: 1 · Screener
+anchor: 1-screener
+url: https://dexterm.xyz/docs/screens#1-screener
+tags:
+  - docs
+  - screens
+  - screener
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+the screener on sample data
+
+A live table of DexScreener + Jupiter rows refreshed every (generated from the app: see https://dexterm.xyz/docs/screens#1-screener; app-help has the exact keys and commands) s through a rate limiter. Columns: price, 5m/1h/6h/24h change, volume, liquidity, market cap, age, holders, organic score, `P(RUG)`, flags, a sparkline. Cells whose source is down show `—` and the panel caption names the column and the reason; safety checks the keyless sources cannot answer render `○ … needs key`, never a pass or a fail.
+
+`P(RUG)` is a **model output, not a fact**: the pre-registered `H1-v0.1` heuristic (an additive points rule, not a learned model) scored from the row's own liquidity, cap, age, holders, organic score, top-10 and dev share and mint/freeze authorities. The panel caption names the model (`p(rug) = H1-v0.1 heuristic`), the spotlight card repeats the value with the model and, on the line under it, how old the scored data is (`p(rug) 0.45 · H1-v0.1 heuristic` / `model output · data 12s old`), and a row with nothing to score shows `—`. Red at or above the model's own flag line (0.50), amber from 0.35. `rug` is a sort key (safest first). Like `FLAGS`, the column is shed first when the table is narrow: with the spotlight open it needs about 184 columns; below that the caption and the spotlight still carry the value and the model id. How well H1 does is measured, not assumed: see backtests (https://dexterm.xyz/docs/analyst#mcp-tools) and the changelog (https://dexterm.xyz/changelog/) for the latest numbers and their sample size.
+
+- `/` opens the filter line. The grammar: space-separated clauses, ANDed. `vol24 > 250K liq > 50K age < 30d org >= 60 launchpad:pump !flag:mint`. Fields and aliases are in the CLI reference (https://dexterm.xyz/docs/cli#filter-grammar). Errors show inline with the column that failed. `\` clears the filter.
+- `s` opens the sort menu; `⏎` on the current key flips the direction.
+- `\[` and `\`] step through the presets: (generated from the app: see https://dexterm.xyz/docs/screens#1-screener; app-help has the exact keys and commands). Gated presets say why they are unavailable (Graduating waits on the bonding feed; Smart money needs a Tier-1 key).
+- `w` watches the highlighted row, `b` proposes a liquidity alert, `⏎` opens the token.
+- The cursor resting on a row for a third of a second prefetches that token's candles when the chart source is idle (capped at 3 a minute), so `⏎` paints the chart instantly.

package/dist/packages/mcp/assets/kb/docs/docs-screens-2-new-pairs.md

@@ -0,0 +1,28 @@
+---
+id: docs-screens-2-new-pairs
+title: Screens tour › 2 · New pairs
+kind: docs
+page: screens
+page_title: Screens tour
+heading: 2 · New pairs
+anchor: 2-new-pairs
+url: https://dexterm.xyz/docs/screens#2-new-pairs
+tags:
+  - docs
+  - screens
+  - new
+  - pairs
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+new pairs on sample data
+
+A push stream of pump.fun creates and migrations from PumpPortal on one WebSocket, plus Jupiter `recent` and RugCheck `new_tokens` polls. Bonding progress is estimated from the curve's virtual reserves at create time and says so. The SNIPE and BUNDLE columns and the spotlight's Snipers and Bundled rows come from the wallet-intel scan (https://dexterm.xyz/docs/screens#bubble-map) of the row your cursor rests on, after about 2 s. The scan only runs with a free Helius key, because only Helius history can read the launch window. An unscanned row shows a dash, a scan in flight shows `…`, and without the key the spotlight says `needs Helius key`. No number is guessed. The highlight follows the coin you picked by mint, so a new arrival never shifts your cursor onto another row.

package/dist/packages/mcp/assets/kb/docs/docs-screens-3-watchlist.md

@@ -0,0 +1,27 @@
+---
+id: docs-screens-3-watchlist
+title: Screens tour › 3 · Watchlist
+kind: docs
+page: screens
+page_title: Screens tour
+heading: 3 · Watchlist
+anchor: 3-watchlist
+url: https://dexterm.xyz/docs/screens#3-watchlist
+tags:
+  - docs
+  - screens
+  - watchlist
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+the watchlist on sample data
+
+A local SQLite watchlist priced every (generated from the app: see https://dexterm.xyz/docs/screens#3-watchlist; app-help has the exact keys and commands) s, with the LIVE/POLL badge per row. Alerts are proposals until you arm them with `y`; armed rules fire once into the ALERTS log. `d` removes a row. Nothing here trades.

package/dist/packages/mcp/assets/kb/docs/docs-screens-4-analyst-tab.md

@@ -0,0 +1,28 @@
+---
+id: docs-screens-4-analyst-tab
+title: Screens tour › 4 · Analyst tab
+kind: docs
+page: screens
+page_title: Screens tour
+heading: 4 · Analyst tab
+anchor: 4-analyst-tab
+url: https://dexterm.xyz/docs/screens#4-analyst-tab
+tags:
+  - docs
+  - screens
+  - analyst
+  - tab
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+the analyst tab on sample data (the transcript is demo text; a real run spawns your own claude)
+
+A chat beside a navigable coin list. `↑`/`↓` change the selected coin (which updates the context the analyst sees next turn); `PgUp`/`PgDn` scroll the transcript; `i` or `⏎` focuses the input. When an answer lists coins it renders as a table you can navigate: `⏎` opens the coin, `o` opens its PAPER ticket. Details in the analyst (https://dexterm.xyz/docs/analyst).

package/dist/packages/mcp/assets/kb/docs/docs-screens-bubble-map.md

@@ -0,0 +1,32 @@
+---
+id: docs-screens-bubble-map
+title: Screens tour › Bubble map
+kind: docs
+page: screens
+page_title: Screens tour
+heading: Bubble map
+anchor: bubble-map
+url: https://dexterm.xyz/docs/screens#bubble-map
+tags:
+  - docs
+  - screens
+  - bubble
+  - map
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+`M` on a token opens the holder graph. Each of the top token accounts (merged by owner) is a disc whose **area is its share of supply**, drawn on a half-row pixel grid so it is round in the terminal without any image protocol. **Colour is the rule that labelled the wallet, never a judgement:** yellow dev / dev-linked, magenta bundle, green linked by a shared funder (orange for a direct transfer), red sniper, cyan pool / LP / program-owned vault, grey exchange or multi-token whale, dim unlinked. Linked wallets sit inside a dotted ring with a tag like `B·C1 6w 12.0%`; `j`/`k` select a holder (phosphor, with dotted edges to its cluster mates), `m` flips to a treemap (share, not linkage), `z` zooms the selected cluster, `D` forces a deep scan, `r` rescans, `M` opens the popup window (https://dexterm.xyz/docs/popup-chart#bubble-map-popup).
+
+The rules (from the task-1286 spike, replay-tested against its recordings): **P1 pool** (the selling counterparty in ≥ 25 % of launch transactions), **D1 creator** (fee payer of the first transaction referencing the mint), **R1 funder** (two holders share a funding source; a shared exchange funder is a veto, not a link), **R1b** (a holder funded another holder), **R2 bundle** (same-slot buys **and** a shared funder; same-slot alone is a cohort), **R3 transfer** (a direct token move between two holders, pools excluded), **R4 dev-linked** (funded by the creator), **R5 same-slot-created** (weak, shown, never links), **S1 sniper** (bought in the first 3 slots after the first pool trade), **F1 fresh-at-buy** (the wallet's first transactions already move this token), **X1 multi-token-top20**, and **L0** static lists. The **WHY THIS LABEL** panel leads with the holder's class (POOL, CURVE, VAULT, LOCK, CEX, BURN, DEV, LINKED or UNLABELLED) and the on-chain reason, then prints each rule with its confidence (`on-chain`, `program-authority`, `derived`, `seed`, `weak`) and up to three evidence lines; exchange labels come from a typed seed list and always read **unverified**. Cabal-class labels (cabal-candidate, smart, bot, follower, call-group) are hidden until their precision is measured.
+
+**HOLDER INSIGHTS** print their sample every time (`sample top 20 accts of 142.5K holders · 55% supply · funders 7/20 · launch 300 txs`): top-10 raw (by token account, the explorer number), **ex-pool** (POOL / CURVE / VAULT / LOCK / BURN owners dropped; the cluster-adjusted figure, with linked owners merged and exchanges dropped too, rides underneath), a red **main risk** line when a counted owner holds more than 30 %, snipers, bundled supply, dev share (an upper bound when the creator is outside the sample) and fresh wallets. The token screen's Snipers and Bundled supply rows, the new-pairs SNIPE / BUNDLE columns and the `I` token popup read the same scan.
+
+Two scan tiers, both through the limiter, the health registry and the Helius credit meter: **light** when a token opens (top-20 accounts, owner kinds, funders for the 7 largest wallets, the first 100 launch transactions; about 80 credits, less once funders are cached, since a wallet's first inflow never changes) and **deep** for watchlist coins or on `D` (every top wallet, 300 launch transactions). Funders and the launch window are Helius-only (`getTransactionsForAddress`): **keyless, the map still draws** from the public RPC holder list with static labels and says plainly that a free Helius key adds funders and the launch window; when no endpoint serves the ranked holder list at all, the screen says `unavailable` with the reason and the fix, never a fake map.

package/dist/packages/mcp/assets/kb/docs/docs-screens-coin-images.md

@@ -0,0 +1,32 @@
+---
+id: docs-screens-coin-images
+title: Screens tour › Coin images
+kind: docs
+page: screens
+page_title: Screens tour
+heading: Coin images
+anchor: coin-images
+url: https://dexterm.xyz/docs/screens#coin-images
+tags:
+  - docs
+  - screens
+  - coin
+  - images
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+Every row in the screener, new pairs and watchlist carries the coin's picture as a 2-cell icon (dropped silently when the frame is too narrow); the token screen shows an 8×4 picture at the left of its header, the screener's spotlight card a 6×3 one, and the chart popup a 16 px one in its title strip.
+
+- **Real pixels** in terminals with an inline-image protocol: kitty graphics (kitty, Ghostty, WezTerm, Konsole), iTerm2 inline images (iTerm2), sixel where the terminal advertises it. At startup dexterm sends one short capability query to the terminal (≤ 150 ms) and picks the richest protocol it actually answers.
+- **Everywhere else, Apple Terminal.app included: block art.** The picture is sampled into half-block and quadrant cells and, on a 256-colour terminal, dithered into the xterm palette so round logos keep their disc. Not a photo, but recognisable at a glance. `dexterm doctor` has a **Coin images** line that says which path you get; Ghostty or iTerm2 (both free) give the real pictures.
+- **A placeholder, never an error:** while a picture loads, when a coin has none, or when its host is down, the box shows the ticker's initial on a colour hashed from the symbol.
+- **Off switch:** `--no-images`, `DEXTERM_IMAGES=0`, or `~/.dexterm/images.json` (`{"enabled": false}`). Replays and offline runs have no network, so pictures there could only come from the cache: they stay off unless asked.
+- **Privacy:** fetching a picture contacts the host that serves it (DexScreener's image CDN for most coins, otherwise the token's own metadata host). dexterm fetches once through its own local cache and the chart popup is served the cached copy, so an image host never sees a popup load and a coin seen before is never fetched again. `--no-images` keeps every image host from ever seeing your IP. Bytes are treated as hostile: sniffed by magic bytes, capped, and decoded by dexterm's own pure-TypeScript decoders (PNG, JPEG, GIF) — nothing executes. The trust page (https://dexterm.xyz/trust/#privacy) has the statement.

package/dist/packages/mcp/assets/kb/docs/docs-screens-live-holder-and-rug-signals.md

@@ -0,0 +1,51 @@
+---
+id: docs-screens-live-holder-and-rug-signals
+title: Screens tour › Live holder and rug signals
+kind: docs
+page: screens
+page_title: Screens tour
+heading: Live holder and rug signals
+anchor: live-holder-and-rug-signals
+url: https://dexterm.xyz/docs/screens#live-holder-and-rug-signals
+tags:
+  - docs
+  - screens
+  - live
+  - holder
+  - rug
+  - signals
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+While a token is open, its holder and rug-risk reads update as the data moves, not only when you open the screen. When a reading crosses a threshold, a **LIVE SIGNALS** strip in the ON-CHAIN panel shows a line like `⚑ top-10 concentration 31% → 38% (pools excluded)` with its **source** and the **age** of the data, and a short notice flashes. Each signal is a risk flag to check, not a verdict.
+
+| signal | fires when |
+| --- | --- |
+| dev sell | the creator's share drops by 1 point or more |
+| concentration | the top-10 share (pools excluded) moves by 3 points or more |
+| LP unlock | the locked share of the liquidity drops by 1 point or more |
+| liquidity | liquidity falls by 25 % or more |
+| authority | the mint or freeze authority appears or is revoked |
+| bundle / sniper | bundled supply rises by 1 point, or another sniper appears |
+| fresh wallets | the share of fresh-at-buy wallets rises by 5 points |
+| bonding / migrated | bonding-curve progress rises by 5 points, or the coin migrates |
+
+- **Three cadences, each honest about its source.** Authorities, LP, liquidity and the top-10 share refresh with the token poll (every (generated from the app: see https://dexterm.xyz/docs/screens#live-holder-and-rug-signals; app-help has the exact keys and commands) s). Bonding progress streams sub-second from the same on-chain push as the LIVE price badge. Holder, bundle, sniper and fresh-wallet reads re-scan every 45 s while the token is open, and only with a free Helius key. Keyless, they show a dash and spend no requests.
+- **Stale never fires.** The first reading of each field is a baseline and fires nothing. A reading older than 60 s, or one its source marks stale, never fires a signal and is shown as **stale**, never hidden or filled in. A migration is caught on the next token refresh, not sub-second.
+- **Every signal is an alert trigger.** The rules engine (https://dexterm.xyz/docs/configuration#rules-engine) reads the open token's live fields `top10`, `dev`, `bundled`, `snipers`, `fresh`, `cluster`, `lplocked`, `bonding`, `mintable` and `freezable` (1 when that authority is present), with `.delta` and `.velocity`. A rule can then reach your push channels (https://dexterm.xyz/docs/configuration#push-alerts-and-dexterm-watch):
+
+```text
+when dev.delta < -2 then alert(down, "dev selling")
+when mintable > 0 then alert(warn, "mint authority present")
+when top10.delta > 5 then alert(warn, "concentration up")
+```
+
+The signals read the same keyless and free-tier sources as the rest of the token screen, through the same rate limiter. They raise flags; they cannot trade, arm or sign anything.

package/dist/packages/mcp/assets/kb/docs/docs-screens-order-plans.md

@@ -0,0 +1,26 @@
+---
+id: docs-screens-order-plans
+title: Screens tour › Order plans
+kind: docs
+page: screens
+page_title: Screens tour
+heading: Order plans
+anchor: order-plans
+url: https://dexterm.xyz/docs/screens#order-plans
+tags:
+  - docs
+  - screens
+  - order
+  - plans
+  - tour
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/screens.md
+date: 2026-10-16
+---
+
+`O` from anywhere opens the order-plans screen: a PLANS / MANDATES tab strip (`tab` flips), each plan on one line with its status tone (proposed, armed, filled, done, cancelled, expired) and the signer's read-back of what it will do. `a` on a row opens a hold-to-arm prompt; only a key held at the terminal arms, and the prompt is unreachable from the popup, voice, an agent or piped input. `c` cancels a plan, `r` revokes a mandate, `!` is panic (revoke everything), `M` opens the read-only plans popup, `G` shows the hands-free gate setting (GATE ON by default), and `L` raises the fire-path prompt: a held keypress switches plan fills between PAPER and LIVE · DEVNET · fast wallet (refused while plans are armed, without the signer process, off devnet or without a fast wallet). The header says PAPER unless a fill path is provably live. Plans, mandates, caps and the journal are in order plans and standing mandates (https://dexterm.xyz/docs/paper-trading#order-plans-and-standing-mandates).