dexterm-cli 0.1.3 → 0.1.5

package/dist/packages/mcp/assets/kb/docs/docs-configuration-the-optional-free-rpc-key.md

@@ -0,0 +1,42 @@
+---
+id: docs-configuration-the-optional-free-rpc-key
+title: Configuration and files on disk › The optional free RPC key
+kind: docs
+page: configuration
+page_title: Configuration and files on disk
+heading: The optional free RPC key
+anchor: the-optional-free-rpc-key
+url: https://dexterm.xyz/docs/configuration#the-optional-free-rpc-key
+tags:
+  - docs
+  - configuration
+  - optional
+  - free
+  - rpc
+  - key
+  - files
+  - disk
+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/configuration.md
+date: 2026-10-16
+---
+
+Keyless, the holders panel shows the holder count and the top-10 share from Jupiter; the ranked top-20 list with owner wallets needs a free RPC key (a 2-minute signup with no card at Helius, Alchemy, QuickNode or Ankr). Configure one of:
+
+```sh
+$ mkdir -p ~/.dexterm && printf %s "<your-key>" > ~/.dexterm/helius.key && chmod 600 ~/.dexterm/helius.key
+```
+
+```sh any read-only RPC URL; the first wins, extras join the rotation pool
+$ export DEXTERM_RPC_URL="https://<provider>/<path>"
+$ export DEXTERM_RPC_URLS="https://rpc-a/...,https://rpc-b/..."
+```
+
+Resolution order: `DEXTERM_RPC_URL`, else `~/.dexterm/helius.key`, else the public RPC pool. All configured endpoints rotate by health score; a 429 pauses one endpoint (honouring `Retry-After`) and fails over to the next. Every URL in an error, a `--verbose` line or a `--record` file passes a redactor; a recording that still carries a key refuses to save. `dexterm doctor` reports the provider name only, never the key.
+
+> warn: never paste a key into a command line argument, a shell history, a chat or a repository. The file above is the only place dexterm reads it from.

package/dist/packages/mcp/assets/kb/docs/docs-configuration-themes-and-keymaps.md

@@ -0,0 +1,29 @@
+---
+id: docs-configuration-themes-and-keymaps
+title: Configuration and files on disk › Themes and keymaps
+kind: docs
+page: configuration
+page_title: Configuration and files on disk
+heading: Themes and keymaps
+anchor: themes-and-keymaps
+url: https://dexterm.xyz/docs/configuration#themes-and-keymaps
+tags:
+  - docs
+  - configuration
+  - themes
+  - keymaps
+  - files
+  - disk
+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/configuration.md
+date: 2026-10-16
+---
+
+`~/.dexterm/themes/<name>.json` is `{ "extends": "cyberspace", "tokens": { "accent": "#ffb02e", … } }`: a built-in base plus hex overrides. At load every value must be a hex colour, ramps exactly four, unknown tokens are refused, and two semantic checks protect you from a shared theme: a **contrast floor** (text on background, muted on panel, the up / down / warn colours) and an **up / down guard** (`up` must read green/cyan and `down` red/pink by hue, both must carry real colour — an HSL saturation floor — and they must sit a minimum perceptual distance apart, so neither an amber pair nor a near-grey pair can make a loss look like a gain). A theme that fails loads as `paper` with a toast naming the token. `config.theme.overrides` is the same for one-off tokens; `dexterm theme list | show | init <name> | check <name>`.
+
+`config.keymap` re-binds the app's actions: `"global": { "screen.watchlist": ["3", "W"] }` and `"screens": { "screener": { "preset.next": ["]"] } }`, chords as `"ctrl+w s"`. Refused by name, whatever the file says: assigning `ctrl+c`, `esc`, `enter`, `y` / `Y` or `!` to anything; changing the keys of quit, back, the alert confirm / dismiss, arm, panic or the gate; two actions on one key within one scope; a chord prefix bound on its own; more than four keys per action. Any error keeps the defaults (a half-applied keymap is worse than none) and names the path. `dexterm keymap [screen]` prints the effective keys with overrides marked `·`; the `?` overlay marks them the same way.

package/dist/packages/mcp/assets/kb/docs/docs-configuration-themes-and-look.md

@@ -0,0 +1,27 @@
+---
+id: docs-configuration-themes-and-look
+title: Configuration and files on disk › Themes and look
+kind: docs
+page: configuration
+page_title: Configuration and files on disk
+heading: Themes and look
+anchor: themes-and-look
+url: https://dexterm.xyz/docs/configuration#themes-and-look
+tags:
+  - docs
+  - configuration
+  - themes
+  - look
+  - files
+  - disk
+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/configuration.md
+date: 2026-10-16
+---
+
+`--theme cyberspace|midnight|ember|paper` or `t` at runtime. `--intensity off|normal|fever`, `--fps N`, `--no-boot`, `--ascii-rain`, `--tz ZONE` for the header clock (default America/New_York; `local` for the machine zone). Details in the CLI reference (https://dexterm.xyz/docs/cli#flags). User themes join the `t` cycle: see themes and keymaps (https://dexterm.xyz/docs/configuration#themes-and-keymaps).

package/dist/packages/mcp/assets/kb/docs/docs-configuration-widgets.md

@@ -0,0 +1,31 @@
+---
+id: docs-configuration-widgets
+title: Configuration and files on disk › Widgets
+kind: docs
+page: configuration
+page_title: Configuration and files on disk
+heading: Widgets
+anchor: widgets
+url: https://dexterm.xyz/docs/configuration#widgets
+tags:
+  - docs
+  - configuration
+  - widgets
+  - files
+  - disk
+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/configuration.md
+date: 2026-10-16
+---
+
+A pack widget is an html page the popup host serves in a loopback HUD window, the same window technology as the popup chart (https://dexterm.xyz/docs/popup-chart). It is the only way third-party UI gets into dexterm, and it is small on purpose: a widget can **receive and render**; it cannot fetch, import, run anything in the terminal process, or send anything but close / focus / drag.
+
+- `widgets/<name>/widget.json` declares pages and their topics, a subset of `rows · token · narrative · positions · alerts · theme`: the screener's public columns, the open coin, the narrative board, your positions (symbol, size, PnL), the alert log, the theme. Nothing in a view model names a key, a signer, a cap, a mandate or the gate; pair / source ids and provenance internals are not sent.
+- The window is two documents: the host's own wrapper page (it owns the connection to the terminal, the title strip and the close button) and, inside it, the pack page in a sandboxed frame. The pack page runs under a hash-only CSP: the html is served exactly as installed (nothing is substituted into it, there is no nonce), and every inline `<script>` and `<style>` block runs because its sha256 is in the header — only the text you read before enabling the widget. It has no network of its own at all (no fetch, no socket, no remote scripts, styles, images or fonts), no cookies or storage (an opaque origin), no inline handlers, no eval, no runtime script injection where the engine supports Trusted Types, and no way to navigate anywhere: a document may always navigate itself, which a sandbox alone cannot stop, so the wrapper's `frame-src` names the one document the frame may show and the engine refuses any other before a request exists — the wrapper then closes the widget and logs why. Verified in headless Chromium and WebKit. One kind of connection no content-security directive covers — a `<link rel=preconnect>` built at run time makes WebKit open a bare TCP connection to a host and port the page chose — so the SDK, which runs first in the frame, seals the DOM: the insertion methods, every HTML-parsing entry point (the static `Document.parseHTMLUnsafe` included), `adoptNode` / `importNode`, the element-taking setters and WebRTC are locked on the prototypes before any pack script runs, a click on a link that targets another window (and any form submit) is cancelled before the engine can open a connection for it, a MutationObserver closes the widget if a loader element ever appears anyway, and none of it depends on Trusted Types, which the system WebKit of macOS 14 and 15 lacks (verified inside the real native shell on that WebKit, and in headless Chromium and WebKit with Trusted Types stripped, with a raw TCP sink). Widgets open only in the native popup shell (macOS 14 or newer), whose windows are routed through a loopback sink proxy of the host's as a further backstop for named hosts. A page that carries a loader (`<script src>`, `<link>`, a frame, `<meta http-equiv>`, `@import`, or a `__NONCE__` placeholder) is refused at install, again at open and again when the host issues the window's ticket. A frozen `dexterm` object is injected ahead of the pack markup: `dexterm.on(topic, fn)`, `dexterm.theme` (also CSS variables), `dexterm.close()`, `dexterm.log()`; the frame can say only ready / log / close back, and the terminal's socket accepts nothing but the generic events from a widget.
+- Consent is yours and re-checked: a widget installs disabled; `dexterm pack widget <pack> <name> --enable` after you read the page; at every open the app re-hashes the installed pack and refuses a page edited since. A workspace can list a widget popup (`{ "kind": "widget", "widget": "<pack>/<name>" }`) but cannot enable it.
+- **Beta.** One example widget (`packs/example-widgets`, the MOVERS tiles), a popup window only. The in-process plugin sandbox from the design (terminal columns and panels, host-mediated fetch, per-plugin storage) is not built. API and limits: `packages/popup/WIDGETS.md` in the repo.

package/dist/packages/mcp/assets/kb/docs/docs-configuration-workspaces.md

@@ -0,0 +1,30 @@
+---
+id: docs-configuration-workspaces
+title: Configuration and files on disk › Workspaces
+kind: docs
+page: configuration
+page_title: Configuration and files on disk
+heading: Workspaces
+anchor: workspaces
+url: https://dexterm.xyz/docs/configuration#workspaces
+tags:
+  - docs
+  - configuration
+  - workspaces
+  - files
+  - disk
+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/configuration.md
+date: 2026-10-16
+---
+
+A workspace is one JSON file, `~/.dexterm/workspaces/<name>.json`: the screen to land on, the theme and intensity, the screener preset / filter / sort, the token-screen panel toggles, optional per-screen pane trees for the layout solver (weights, fixed widths, priorities, what collapses at which width), and the HUD popups to open together. The shipped `default` reproduces the five screens exactly; `morning-hud` is "show me everything": the narrative board, the feeds, order plans and the chart of the selected coin as windows beside the terminal.
+
+- In the app: `ctrl+w` then `w` list · `n` / `N` next / previous · `s` save the current layout under a typed name · `m` the morning HUD · `o` open the active workspace's popups · `d` default · `1`–`9` pick a slot. `--workspace <name>` starts in one. The footer shows the active workspace.
+- On the command line: `dexterm workspace list | show <name> | remove <name> | init` (`init` writes `default` as an editable file with the shipped trees).
+- A switch is a UI action and nothing more. It can navigate, re-theme and open the same read-only windows the keys open; it cannot open a ticket, confirm, arm or sign, and a workspace file has no field for any of that (the schema refuses unknown keys by name). Jarvis proposes workspace switches through the same proposal card as everything else.

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

@@ -0,0 +1,25 @@
+---
+id: docs-configuration
+title: Configuration and files on disk
+kind: docs
+page: configuration
+page_title: Configuration and files on disk
+url: https://dexterm.xyz/docs/configuration
+tags:
+  - docs
+  - configuration
+  - files
+  - disk
+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/configuration.md
+date: 2026-10-16
+---
+
+Environment variables, the files dexterm writes, the optional free RPC key, and how to delete everything.
+
+dexterm has no config server, no account and no telemetry. Everything it remembers is in a handful of local files you can read and delete.

package/dist/packages/mcp/assets/kb/docs/docs-copy-trading-stage-1-follow-a-wallet-see-what-it-does.md

@@ -0,0 +1,51 @@
+---
+id: docs-copy-trading-stage-1-follow-a-wallet-see-what-it-does
+title: Copy trading (staged, personal, paper by default) › Stage 1: follow a wallet, see what it does
+kind: docs
+page: copy-trading
+page_title: Copy trading (staged, personal, paper by default)
+heading: Stage 1: follow a wallet, see what it does
+anchor: stage-1-follow-a-wallet-see-what-it-does
+url: https://dexterm.xyz/docs/copy-trading#stage-1-follow-a-wallet-see-what-it-does
+tags:
+  - docs
+  - copy-trading
+  - stage
+  - follow
+  - wallet
+  - does
+  - 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
+---
+
+Press `U` anywhere for the **FOLLOWED WALLETS** screen, or use the shell:
+
+```
+dexterm follow add <addr> --name "my label"
+dexterm follow list | stats <addr> | trades <addr> | remove <addr> | purge --yes
+```
+
+- **Your list, your labels.** A label is whatever you type, passed through the prompt firewall (an instruction-shaped label is refused, control characters are stripped, 24 characters at most). dexterm never infers who a wallet is, never scrapes X or Telegram to attribute one, and never exports the list. `purge` deletes every follow and label; the file is `~/.dexterm/follows.json` (mode 600).
+- **Decoded swaps.** The tracker reads the wallet's own recent history (Helius `getTransactionsForAddress`, 10 credits a call, newest first, through the data layer's limiter and credit meter) and classifies each transaction from the wallet's own balances: tokens up and SOL down is a **buy**, tokens down and SOL up a **sell**, tokens moved without a SOL leg a **transfer** (an airdrop is flagged as cost 0), tokens and SOL moving the *same* way is **lp-like** (an LP add or removal, never a swap), and two mints in one transaction is a **token-swap** with no SOL split, so nothing unpriceable is priced. Wrapped SOL is never a mint. The POPCAT recording from the wallet-intel spike is the regression case for the lp-like rule: its busiest launch signer *receives* tokens and SOL together.
+- **Numbers with their sample.** Realised PnL is FIFO by token amount over the history fetched, in SOL exactly and in USD at today's rate (the rate is printed). Fees and tips are inside the SOL leg. Win rate is wins over closed positions and stays hidden under n = 10 (the row shows `n<10 (2/4)`). The early-entry score needs the token's launch-window buyer ranks (a bubble-map scan) and shows `—` with the reason otherwise; it has no "reached 3×" filter yet and says so. Every figure carries `all N txs` or `last N txs only · older history not fetched`.
+- **Alerts, not news.** The first look at a wallet backfills history silently. Only transactions that appear *after* that raise an alert, as a toast anywhere in the app and on the screen's ALERTS tape with the lag between the block and the moment dexterm saw it. Keyless, the tracker is honestly **unavailable** and says how to get the free Helius key; a failed poll shows on the row and the next poll retries.
+
+- **Hold time.** The median time from first buy to last sell over the wallet's **closed** positions. A position counts only when both of those trades carry a real block time. Otherwise hold time shows `—` with the reason. It appears in `dexterm follow stats` and the detail view.
+- **Buy and sell alerts, pushed if you want.** A new trade by a followed wallet raises the in-app alert as before. If you have enabled a push channel (https://dexterm.xyz/docs/configuration#push-alerts-and-dexterm-watch) (desktop, your own Telegram bot or Discord webhook), the alert is delivered there too, marked buy or sell and "not a recommendation". This happens only while the dexterm terminal is running: `dexterm watch` runs your rules headless but does not follow wallets. Delivery is read-only: an alert cannot open, arm or sign anything.
+- **Per-wallet detail.** `⏎` on a followed wallet opens its detail view: recent decoded trades, positions, realised PnL, win rate with its n, hold time, early-entry score and open positions. Each figure is labelled with its source (Helius history) and data age. `↑`/`↓` scroll, `⏎` or `esc` close.
+
+Nothing on this stage trades. A wallet's past fills say nothing about its next one, and the screen says so.
+
+`H` on this screen makes a PnL card (https://dexterm.xyz/docs/paper-trading#pnl-cards) for the selected wallet's coins, stamped **TRACKED WALLET** (read-only observation), with the wallet address hidden unless you show it. To mark an open position it looks up the coin's public decimals and price (the same keyless lookup the mirror ticket uses).

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.