dexterm-cli 0.1.3 → 0.1.4

package/dist/packages/mcp/assets/kb/docs/docs-copy-trading-stage-2-the-one-key-mirror-ticket-a-proposal.md

@@ -0,0 +1,56 @@
+---
+id: docs-copy-trading-stage-2-the-one-key-mirror-ticket-a-proposal
+title: Copy trading (staged, personal, paper by default) › Stage 2: the one-key mirror ticket (a proposal)
+kind: docs
+page: copy-trading
+page_title: Copy trading (staged, personal, paper by default)
+heading: Stage 2: the one-key mirror ticket (a proposal)
+anchor: stage-2-the-one-key-mirror-ticket-a-proposal
+url: https://dexterm.xyz/docs/copy-trading#stage-2-the-one-key-mirror-ticket-a-proposal
+tags:
+  - docs
+  - copy-trading
+  - stage
+  - one-key
+  - mirror
+  - ticket
+  - proposal
+  - copy
+  - trading
+  - staged
+  - personal
+  - paper
+  - default
+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/copy-trading.md
+date: 2026-10-16
+---
+
+On a followed wallet, `m` previews a **MIRROR TICKET** for that wallet's latest buy. The preview shows every check and its number:
+
+| check | refuses when | why |
+|---|---|---|
+| lag | more than 30 s since the leader's block | you are late |
+| drift | the price is more than 5 % above the leader's fill | you are chasing |
+| liquidity | under $25k | you cannot get out |
+| age | the pair is under 60 s old | launch noise |
+| leader sold | the leader has already sold this mint since the buy | they left |
+| leader dev / leader holds | the leader is linked to the dev cluster, or holds more than 5 % of supply (from a bubble-map scan) | they may be distributing to you |
+
+Unknown facts are shown as unknown (`?`), never guessed, except decimals: without them the drift cannot be computed and the mirror is refused until the token is open. The size is `min(your cap, k × the leader's size, 1 % of liquidity)`; the cap is $20 per mirror today (the mandate's per-trade cap applies again at arming). `m` again **proposes**: an order plan, buy now, no ladder, 3 % slippage, expiring in 10 minutes, labelled `copy`, that lands on the `O` screen exactly like a typed or spoken plan. It is inert until you hold `a` to arm it into an armed mandate, or approve it in Phantom; nothing on the follows screen can arm.
+
+The same mirror ticket works from a shell, for scripts and replays, with the same checks and the same size rule:
+
+```sh
+$ dexterm follow mirror <addr>                # preview the latest buy's mirror ticket; writes nothing
+$ dexterm follow mirror <addr> --cap 10 --k 1 # preview with your own cap and size factor
+$ dexterm follow mirror <addr> --propose      # write it as an INERT proposed order plan on the O screen
+$ dexterm follow mirror <addr> --json         # machine-readable preview
+```
+
+A refused mirror prints every failed check and exits non-zero. `--propose` writes a plan with status `proposed` and no mandate. The command has no arm, sign or execute path, so the plan can only be armed in the app through the keypress or Phantom gate. A replay test drives a followed wallet's buy through `--propose` and checks that the plan exists, is not armed and that no execute path was reached. This is the copy-trade mirror ticket of the 0.1.3 release (its first copy-trading step in the release notes): **a proposal only. Nothing arms or fires on its own.**

package/dist/packages/mcp/assets/kb/docs/docs-copy-trading-stage-3-capped-auto-mirror-default-off-less.md

@@ -0,0 +1,47 @@
+---
+id: docs-copy-trading-stage-3-capped-auto-mirror-default-off-less
+title: Copy trading (staged, personal, paper by default) › Stage 3: capped auto-mirror (default off, less safe)
+kind: docs
+page: copy-trading
+page_title: Copy trading (staged, personal, paper by default)
+heading: Stage 3: capped auto-mirror (default off, less safe)
+anchor: stage-3-capped-auto-mirror-default-off-less-safe
+url: https://dexterm.xyz/docs/copy-trading#stage-3-capped-auto-mirror-default-off-less-safe
+tags:
+  - docs
+  - copy-trading
+  - stage
+  - capped
+  - auto-mirror
+  - default
+  - off
+  - less
+  - safe
+  - copy
+  - trading
+  - staged
+  - personal
+  - paper
+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/copy-trading.md
+date: 2026-10-16
+---
+
+`A` on a followed wallet raises the **AUTO-MIRROR** prompt. Turning it on is a held physical keypress, and it is refused unless the plan engine's own "this is less safe" popup (`G` on the `O` screen, keypress-only, 24 h expiry) is active. That one gesture drafts and arms a **copy mandate** in the plan engine, the signer trust domain: buy-only, `maxTier: hands-free`, with exactly the policy's caps, clamped to the engine's hard ceilings.
+
+Every later buy by that wallet then runs the Stage 2 checks and, if they pass, is proposed and armed automatically with the **weakest confirmation tier**. The engine therefore sizes it at **¼ of the per-trade cap** (the same rule a spoken confirmation gets) and re-checks the per-trade, per-coin, total and daily-loss caps, the allow-list and the panic state at arming and on every fill. On top, the policy keeps a per-wallet **daily cap** (the mandate's total), **max open mirrors**, a **cooldown** between mirrors, a **size factor** against the leader, and an **auto-disarm streak**: that many refused or failed mirrors in a row turn it off.
+
+What turns it off, always without a gesture: `A` again; the `!` panic key or `dexterm wallet panic`; restoring the keypress gate; the copy mandate expiring or being revoked; the refusal streak; unfollowing the wallet; and **every restart**, after which a copy mandate the engine recovered as armed is revoked on load. Caps can only be changed while it is off, from the shell:
+
+```
+dexterm follow auto <addr> --per-trade 20 --daily 100 --max-open 3 --cooldown 60 --k 1 --disarm 3
+dexterm follow auto            # list policies and their state
+dexterm follow auto <addr> --off
+```
+
+Ceilings: $100 per trade, $500 per day, 10 open, a 10 s minimum cooldown, k ≤ 2. Every policy change, enable, disable, proposal, arm and refusal is appended to a hash-chained journal at `~/.dexterm/copy.journal`, next to the plans journal.

package/dist/packages/mcp/assets/kb/docs/docs-copy-trading-what-is-proven-what-is-not.md

@@ -0,0 +1,36 @@
+---
+id: docs-copy-trading-what-is-proven-what-is-not
+title: Copy trading (staged, personal, paper by default) › What is proven, what is not
+kind: docs
+page: copy-trading
+page_title: Copy trading (staged, personal, paper by default)
+heading: What is proven, what is not
+anchor: what-is-proven-what-is-not
+url: https://dexterm.xyz/docs/copy-trading#what-is-proven-what-is-not
+tags:
+  - docs
+  - copy-trading
+  - proven
+  - copy
+  - trading
+  - staged
+  - personal
+  - paper
+  - default
+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/copy-trading.md
+date: 2026-10-16
+---
+
+Proven on fixtures and a fake clock: the decoder on synthetic histories and the three spike recordings; the tracker's backfill-then-alert replay; every mirror refusal and the size rule; the proposal's inertness; the auto path end to end on the paper executor (enable, ¼-size arming, fill, cooldown, max-open, daily cap, the engine's own refusal of a hand-armed extra plan); the kill paths; the restart rule; and a compromised-model suite in which spoken, agent and forged gestures, a spoofed alert, a widened policy and a plan the service did not create all fail to enable, widen or auto-arm anything.
+
+Not built or not proven: **mirror-sell** (you close every mirror yourself, so auto-disarm counts refusals and failed fills, not realised losses); an early-entry score with the "reached 3×" filter; a live run against real Helius history on this machine; and any mirror on devnet or mainnet.
+
+**Confirmation provenance:** the engine rejects fabricated, copied, modified, cross-engine and reused proof objects. Copy automation receives a private operation scoped to its physically armed mandate; it can create new copy buys, never adopt an existing voice or agent proposal. Automation proofs stay inside the engine. The engine re-checks the less-safe opt-in, mandate lifetime, panic and existing caps. These are in-process checks: the trusted terminal captures physical input; this is not isolation against arbitrary code execution inside that trusted process.
+
+Legal posture (flags for counsel, not advice): self-directed only, no custody, no third parties, no fees, no curated leaders, no inferred identities. See legal (https://dexterm.xyz/legal/).

package/dist/packages/mcp/assets/kb/docs/docs-copy-trading.md

@@ -0,0 +1,31 @@
+---
+id: docs-copy-trading
+title: Copy trading (staged, personal, paper by default)
+kind: docs
+page: copy-trading
+page_title: Copy trading (staged, personal, paper by default)
+url: https://dexterm.xyz/docs/copy-trading
+tags:
+  - docs
+  - copy-trading
+  - copy
+  - trading
+  - staged
+  - personal
+  - paper
+  - default
+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/copy-trading.md
+date: 2026-10-16
+---
+
+Follow a wallet and see its decoded swaps and PnL; turn its buys into a mirror PROPOSAL with one key; or let a capped, keypress-armed auto-mirror propose and arm them for you. Your wallet, your caps, your keys.
+
+Copy trading in dexterm is a **personal tool for your own wallet**. You pick the wallets, you set the caps, your own keys sign (or the paper wallet simulates). dexterm never holds funds, never copies for anyone else, never offers pooled or hosted copying, never publishes a leader list, and takes no fee on a mirrored trade. The whole feature is labelled **in progress**: it is on main and tested on fixtures and the task-1286 spike recordings, but no mirror has moved real funds, and the auto tier fires through the paper executor unless the plans fire path is switched to the devnet fast wallet (see the live fire path (https://dexterm.xyz/docs/paper-trading#the-live-fire-path-devnet-the-fast-wallet)).
+
+It is built in three stages, each behind the previous one's gate.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources-cache.md

@@ -0,0 +1,32 @@
+---
+id: docs-data-sources-cache
+title: Data sources and rate limits › Cache
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+heading: Cache
+anchor: cache
+url: https://dexterm.xyz/docs/data-sources#cache
+tags:
+  - docs
+  - data-sources
+  - cache
+  - data
+  - sources
+  - rate
+  - limits
+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/data-sources.md
+date: 2026-10-16
+---
+
+A persistent SQLite cache (`node:sqlite`, one table, namespaced) makes a restart or a reopen instant and cheap. The analyst's MCP server reads the same file, so a warm dossier needs no network.
+
+(generated from the app: see https://dexterm.xyz/docs/data-sources#cache; app-help has the exact keys and commands)
+
+The last rows shown per preset are also snapshotted so a launch paints instantly, marked `cached Nm old · refreshing`.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources-health-registry.md

@@ -0,0 +1,29 @@
+---
+id: docs-data-sources-health-registry
+title: Data sources and rate limits › Health registry
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+heading: Health registry
+anchor: health-registry
+url: https://dexterm.xyz/docs/data-sources#health-registry
+tags:
+  - docs
+  - data-sources
+  - health
+  - registry
+  - data
+  - sources
+  - rate
+  - limits
+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/data-sources.md
+date: 2026-10-16
+---
+
+Every source goes through a health registry: three consecutive failures or two 429s in a minute mark it degraded for a backoff window (30 s, doubling to 10 min). A panel whose source is down shows `unavailable: <reason>` or `needs key`, the header turns `◐ degraded: <source>`, and the analyst's tool list is built from the healthy sources each session. A screen with no data says why instead of hanging: `connecting to the live feed…`, `offline — can't reach the data feed`, `rate-limited — backing off`. Press `r` to retry. Nothing fabricates a number.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources-rate-limits-and-pacing.md

@@ -0,0 +1,32 @@
+---
+id: docs-data-sources-rate-limits-and-pacing
+title: Data sources and rate limits › Rate limits and pacing
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+heading: Rate limits and pacing
+anchor: rate-limits-and-pacing
+url: https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing
+tags:
+  - docs
+  - data-sources
+  - rate
+  - limits
+  - pacing
+  - data
+  - sources
+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/data-sources.md
+date: 2026-10-16
+---
+
+One token bucket per host with the documented limit as the ceiling and a safety factor of (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands); over-budget requests queue and the column header shows `⌛` instead of blocking. Identical in-flight requests share one promise. The chart the user is waiting on takes a high-priority slot that background work (tape, prefetch, refresh) can never consume.
+
+(generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands)
+
+Refresh cadence, keyless: screener table (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands) s (one DexScreener batch per 30 rows), token screen (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands) s, watchlist (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands) s, positions (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands) s, new pairs push plus a 15 s Jupiter poll and a 30 s RugCheck poll, PAPER quote (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands) s while editing. The fast lane adds zero HTTP requests: it is push, capped at (generated from the app: see https://dexterm.xyz/docs/data-sources#rate-limits-and-pacing; app-help has the exact keys and commands) simultaneous subscriptions (the open token, your watchlist, a few fresh launches); tokens past the cap stay on the polling lane, never dropped.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources-request-budget-meter.md

@@ -0,0 +1,30 @@
+---
+id: docs-data-sources-request-budget-meter
+title: Data sources and rate limits › Request budget meter
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+heading: Request budget meter
+anchor: request-budget-meter
+url: https://dexterm.xyz/docs/data-sources#request-budget-meter
+tags:
+  - docs
+  - data-sources
+  - request
+  - budget
+  - meter
+  - data
+  - sources
+  - rate
+  - limits
+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/data-sources.md
+date: 2026-10-16
+---
+
+Every request is counted per source for the session and for the day (persisted), so usage is visible with `--verbose` and in the header. Optional soft daily caps can bound a source.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources-sources.md

@@ -0,0 +1,47 @@
+---
+id: docs-data-sources-sources
+title: Data sources and rate limits › Sources
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+heading: Sources
+anchor: sources
+url: https://dexterm.xyz/docs/data-sources#sources
+tags:
+  - docs
+  - data-sources
+  - sources
+  - data
+  - rate
+  - limits
+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/data-sources.md
+date: 2026-10-16
+---
+
+| data need | keyless source | free-key upgrade | without it |
+|---|---|---|---|
+| screener pool | DexScreener + Jupiter Tokens v2 | Jupiter free key: 1 rps instead of 0.5 | fully keyless |
+| token market | DexScreener + Jupiter | Jupiter free key: higher rate | fully keyless |
+| candles and chart | GeckoTerminal | none | chart `unavailable` (rare) |
+| trade tape and buy/sell flow | GeckoTerminal tape; DexScreener rolling windows for 5m to 24h | none | tape `unavailable` |
+| mint and freeze authority | public Solana RPC `getAccountInfo` + Jupiter + GoPlus | any free RPC: faster, fewer 429s | Jupiter and GoPlus still answer |
+| top holders | Jupiter aggregate: holder count + top-10 % | any free RPC key (Helius, Alchemy, QuickNode, Ankr): the ranked top-20 list with owners | count and concentration shown; the ranked list says "needs a free RPC key" |
+| security checks | RugCheck + GoPlus | none | one may be `unavailable`, the other covers |
+| new pairs | PumpPortal `subscribeNewToken` + `subscribeMigration`, Jupiter `recent` poll, RugCheck `new_tokens` | Helius: per-curve bonding % | rows from the poll; bonding is a create-time estimate |
+| watchlist prices | DexScreener + Jupiter, persisted in SQLite | Jupiter free key: higher rate | fully keyless |
+| fast-lane live price | public RPC WebSocket `accountSubscribe` on the pump.fun bonding curve, price computed on-chain | free Helius key: lower latency, higher limits (used first) | the polled price (POLL badge) |
+| paper quotes | Jupiter `swap/v1/quote` (quote only; no build, no execute) | Jupiter free key: lower latency | fully keyless |
+| product vetting | the token's own site, RDAP, the GitHub API | none | a claim stays unverifiable |
+| trending board | Jupiter trending and organic-score lists, GeckoTerminal trending pools, DexScreener top boosts (counted against a coin), CoinGecko trending (macro) | none | a failing venue degrades only itself |
+| news | publishers' official RSS: CoinDesk, Cointelegraph, The Block, Decrypt | none | the board works without it |
+| social posts (X) | none keyless: dexterm does not scrape | Login with X (https://dexterm.xyz/docs/login-with-x): your own X app and login read posts about the open coin and from your KOL lists (user-context API, your limits, your bill; the Free tier allows identity only) | the live SOCIAL panel shows on-chain rows and news, and the band says `x-stream ○ logged out` |
+| dev history, snipers, bundles | none keyless (wallet history is not public without an indexer) | Helius | columns dash + `needs Helius`; with a key, a paused or failed read names itself (`Helius paused · r`, `Helius cap today`, `history failed · r`) |
+| holder classes (POOL / CURVE / VAULT / LOCK / CEX / BURN / DEV / LINKED / UNLABELLED) | the owner lookup over any RPC (`getMultipleAccounts`), part of the wallet-intel scan | same | DEV and LINKED need the Helius launch window; the rest work on any RPC that serves the ranked holder list |
+
+The ranked holder list is the one real keyless gap: `getTokenLargestAccounts` is throttled or blocked on every keyless endpoint we probed, and Birdeye and Solscan need keys.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources-the-helius-credit-meter.md

@@ -0,0 +1,30 @@
+---
+id: docs-data-sources-the-helius-credit-meter
+title: Data sources and rate limits › The Helius credit meter
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+heading: The Helius credit meter
+anchor: the-helius-credit-meter
+url: https://dexterm.xyz/docs/data-sources#the-helius-credit-meter
+tags:
+  - docs
+  - data-sources
+  - helius
+  - credit
+  - meter
+  - data
+  - sources
+  - rate
+  - limits
+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/data-sources.md
+date: 2026-10-16
+---
+
+Helius Free is 1M credits a month, budgeted as (generated from the app: see https://dexterm.xyz/docs/data-sources#the-helius-credit-meter; app-help has the exact keys and commands) a day. Each request is charged (1 credit for standard RPC methods, 10 for DAS-class); the header shows `◐ helius credits N%` from 50% of the day, and at 90%, or at the per-run cap (`--max-credits`, default 5000), Helius switches off for the run and the keyless sources take over. Day totals persist in the SQLite file, so a restart keeps counting.

package/dist/packages/mcp/assets/kb/docs/docs-data-sources.md

@@ -0,0 +1,27 @@
+---
+id: docs-data-sources
+title: Data sources and rate limits
+kind: docs
+page: data-sources
+page_title: Data sources and rate limits
+url: https://dexterm.xyz/docs/data-sources
+tags:
+  - docs
+  - data-sources
+  - data
+  - sources
+  - rate
+  - limits
+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/data-sources.md
+date: 2026-10-16
+---
+
+Every source the app reads, what it takes from each, the keyless limits, and what a free key adds.
+
+dexterm must stay usable forever with **no paid data and no shipped keys**: Node, a terminal and your own Claude login are enough. Every data need has a keyless path on a public API and degrades honestly; a free key you make yourself only raises speed or limits or unlocks depth, it never gates a feature. Because every source meters by **your** IP or key, each user has their own quota and there is no shared server in the middle.

package/dist/packages/mcp/assets/kb/docs/docs-getting-started-dexterm-doctor.md

@@ -0,0 +1,33 @@
+---
+id: docs-getting-started-dexterm-doctor
+title: Getting started › dexterm doctor
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: dexterm doctor
+anchor: dexterm-doctor
+url: https://dexterm.xyz/docs/getting-started#dexterm-doctor
+tags:
+  - docs
+  - getting-started
+  - dexterm
+  - doctor
+  - getting
+  - started
+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/getting-started.md
+date: 2026-10-16
+---
+
+Run `dexterm doctor` before anything else. It is non-interactive, never touches your keys, and prints one line per check with the exact fix for anything that is not a pass. Exit code 0 means the app will run (warnings are optional); 1 means something must be fixed.
+
+```console doctor output (this machine, offline probes skipped)
+(generated from the app: see https://dexterm.xyz/docs/getting-started#dexterm-doctor; app-help has the exact keys and commands)
+```
+
+The checks, in order: (generated from the app: see https://dexterm.xyz/docs/getting-started#dexterm-doctor; app-help has the exact keys and commands). The data-source line probes (generated from the app: see https://dexterm.xyz/docs/getting-started#dexterm-doctor; app-help has the exact keys and commands); PumpPortal is a soft dependency (new pairs only).

package/dist/packages/mcp/assets/kb/docs/docs-getting-started-first-run.md

@@ -0,0 +1,34 @@
+---
+id: docs-getting-started-first-run
+title: Getting started › First run
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: First run
+anchor: first-run
+url: https://dexterm.xyz/docs/getting-started#first-run
+tags:
+  - docs
+  - getting-started
+  - first
+  - run
+  - getting
+  - started
+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/getting-started.md
+date: 2026-10-16
+---
+
+The first launch shows the full glitch boot and then a one-screen welcome card: what dexterm is, the keys that get you around, and the safety stance (non-custodial, your keys never enter dexterm, trading is PAPER by default, not financial advice). Press any key to enter the live screener. Later launches boot in about a second.
+
+- `?` on any screen shows every key for that screen.
+- `q` quits. The terminal is always restored, even after a crash or a signal.
+- `1`–`4` switch screens, `j`/`k` move, `⏎` opens a token, `esc` goes back.
+- `a` asks the analyst about what you are looking at. This is the one explicit, paid run; opening a token with `⏎` never starts one.
+
+The screener paints within a second on a cold start: a cached snapshot of the last rows (marked how old it is), or skeleton rows while the first DexScreener list lands. Jupiter fields fill in behind it.

package/dist/packages/mcp/assets/kb/docs/docs-getting-started-install.md

@@ -0,0 +1,71 @@
+---
+id: docs-getting-started-install
+title: Getting started › Install
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: Install
+anchor: install
+url: https://dexterm.xyz/docs/getting-started#install
+tags:
+  - docs
+  - getting-started
+  - install
+  - getting
+  - started
+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/getting-started.md
+date: 2026-10-16
+---
+
+```sh install with npm
+$ npm i -g dexterm-cli
+$ dexterm doctor
+```
+
+The package is named `dexterm-cli` because npm refuses the name `dexterm` as too similar to `xterm`. The command it installs is `dexterm`. The package ships compiled JavaScript, so it needs no build step. Every GitHub release carries a build-provenance attestation and `SHA256SUMS` you can verify (see the trust page (https://dexterm.xyz/trust/)).
+
+```sh install from the release
+$ # download dexterm-0.1.3-src.tar.gz and SHA256SUMS from the releases page, then:
+$ shasum -a 256 -c SHA256SUMS --ignore-missing
+$ gh attestation verify dexterm-0.1.3-src.tar.gz --repo dexterm-xyz/dexterm
+$ tar -xzf dexterm-0.1.3-src.tar.gz && cd dexterm-0.1.3
+$ ./install.sh
+$ dexterm doctor
+```
+
+The releases page is github.com/dexterm-xyz/dexterm/releases (https://github.com/dexterm-xyz/dexterm/releases).
+
+```sh install with Homebrew (macOS)
+$ brew tap dexterm-xyz/dexterm
+$ brew trust dexterm-xyz/dexterm
+$ brew install dexterm
+$ dexterm doctor
+```
+
+Homebrew 7 and newer load a third-party tap only after you trust it; without `brew trust`, `brew install dexterm` stops with "Refusing to load formula … from untrusted tap". Typing the full name, `brew install dexterm-xyz/dexterm/dexterm`, also works, because naming a formula in full trusts that one formula. The formula installs the same release tarball and runs it with Homebrew's Node. Homebrew no longer ships prebuilt packages for Intel Macs, so on Intel it builds Node and its toolchain from source, which takes a long time; the release installer above is much faster there.
+
+The steps below are the same installer, run from a checkout.
+
+```sh install from a checkout
+$ cd dexterm/app
+$ ./install.sh
+$ dexterm doctor
+$ dexterm
+```
+
+`install.sh` is user-level: no `sudo`, no edits to your shell profile. It checks for Node 22.18+, downloads an official build into your home directory only if none is found (verified against Node's published `SHASUMS256.txt`), links the app, builds the native chart window when `cargo` is present, and writes a `dexterm` launcher to `~/.local/bin`. If that directory is not on your PATH it prints the one line to add and does not add it for you.
+
+Already have Node 22.18+? You can skip the installer. dexterm has no third-party runtime dependencies, so it runs straight from the source tree:
+
+```sh run from source
+$ npm run dexterm
+$ node packages/cli/bin/dexterm.mjs doctor
+```
+
+`npm install` is optional and only pulls the dev tooling (TypeScript, `@types/node`).

package/dist/packages/mcp/assets/kb/docs/docs-getting-started-next.md

@@ -0,0 +1,32 @@
+---
+id: docs-getting-started-next
+title: Getting started › Next
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: Next
+anchor: next
+url: https://dexterm.xyz/docs/getting-started#next
+tags:
+  - docs
+  - getting-started
+  - next
+  - getting
+  - started
+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/getting-started.md
+date: 2026-10-16
+---
+
+- Complete beginner guide (https://dexterm.xyz/docs/beginners) for a slower, no-jargon first run and recovery from common mistakes.
+- Screens tour (https://dexterm.xyz/docs/screens) for what each screen shows.
+- Keyboard reference (https://dexterm.xyz/docs/keyboard), generated from the app's keymap.
+- Configuration (https://dexterm.xyz/docs/configuration) for the free RPC key and the files on disk.
+- `dexterm help <topic>` for the app's own how-to on any key or command, offline. The analyst reads the same help (https://dexterm.xyz/docs/analyst#it-knows-the-app).
+- Bring your own agent (https://dexterm.xyz/docs/agents) to connect Claude Code, Codex or a custom bot, and the spectator view (https://dexterm.xyz/docs/spectator) to watch it work live ("watch the agent cook").
+- Troubleshooting (https://dexterm.xyz/docs/troubleshooting) when a line in doctor is not green.

package/dist/packages/mcp/assets/kb/docs/docs-getting-started-requirements.md

@@ -0,0 +1,35 @@
+---
+id: docs-getting-started-requirements
+title: Getting started › Requirements
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: Requirements
+anchor: requirements
+url: https://dexterm.xyz/docs/getting-started#requirements
+tags:
+  - docs
+  - getting-started
+  - requirements
+  - getting
+  - started
+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/getting-started.md
+date: 2026-10-16
+---
+
+| need | why | notes |
+|---|---|---|
+| Node.js 22.18 or newer | dexterm runs its TypeScript sources directly; no build step | `node -v` to check. The installer can fetch a verified Node for you. |
+| a terminal with 24-bit colour | the cyberspace look | iTerm2, WezTerm, Ghostty, Kitty, Alacritty, Windows Terminal. 256-colour and monochrome terminals still work, flattened. |
+| an internet connection | all data is public and keyless | nothing goes through a dexterm server; see data sources (https://dexterm.xyz/docs/data-sources). |
+| optional: Claude Code logged in | only the analyst needs it | `claude` on your PATH, logged in with your own account. Everything else works without it. |
+| optional: a free RPC key | the ranked top-20 holder list and faster chain reads | Helius, Alchemy, QuickNode or Ankr free tier; see configuration (https://dexterm.xyz/docs/configuration). |
+| optional: Rust (`cargo`) | the native docked chart window | without it the chart popup opens in your browser; see popup chart (https://dexterm.xyz/docs/popup-chart). |
+
+> note: dexterm 0.1.3 is out (2026-10-16), open source under AGPL-3.0-only at github.com/dexterm-xyz/dexterm (https://github.com/dexterm-xyz/dexterm). It is early: trading is experimental and has known bugs. The release ships checksums, a build-provenance attestation and an SBOM, and its VirusTotal result (including flags we explain) is on the trust page (https://dexterm.xyz/trust/). It is also on npm as `dexterm-cli` (https://www.npmjs.com/package/dexterm-cli); the command it installs is still `dexterm`.

package/dist/packages/mcp/assets/kb/docs/docs-getting-started-running-the-tests.md

@@ -0,0 +1,34 @@
+---
+id: docs-getting-started-running-the-tests
+title: Getting started › Install › Running the tests
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: Running the tests
+anchor: running-the-tests
+url: https://dexterm.xyz/docs/getting-started#running-the-tests
+tags:
+  - docs
+  - getting-started
+  - running
+  - tests
+  - install
+  - getting
+  - started
+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/getting-started.md
+date: 2026-10-16
+---
+
+From a source checkout, `npm install` and then `npm test` runs the typecheck and three test lanes, in order (from 0.1.4, not in a release yet):
+
+- **parallel**: every `packages/*/test/*.test.ts` file at once, one process each.
+- **serial** (`npm run test:serial`, `packages/*/test/serial/`): the tests that drive a real terminal through a pty, run the real binary, or assert a wall-clock bound (the under-a-second quit, the 50 ms filter fuzz). They run one file at a time after the parallel lane, so they never share the CPU with it.
+- **perf** (`npm run test:perf`, `packages/*/test/perf/`): the render budget, p95 under 16 ms per frame. It is asserted on the main thread's CPU time every run, and on wall-clock time whenever no other process held the core during the measurement.
+
+A serial or perf test that fails gets one automatic retry, and the retry is never hidden: the run prints the first failure in full and ends with a list of every test that needed it. A test that fails twice fails the run. Set `DEXTERM_TEST_NO_RETRY=1` to turn the retry off. The pty tests open a throwaway cache database, never the one in your data directory.