dexterm-cli 0.1.6 → 0.1.7

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-order-plans-and-standing-mandates.md

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-order-plans-and-standing-mandates
-title: Paper trading, live trading and the safety model › Order plans and standing mandates
+title: Paper trading and the safety model › Order plans and standing mandates
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: Order plans and standing mandates
 anchor: order-plans-and-standing-mandates
 url: https://dexterm.xyz/docs/paper-trading#order-plans-and-standing-mandates
@@ -16,7 +16,6 @@ tags:
   - mandates
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -29,7 +28,7 @@ sources:
 date: 2026-10-16
 ---
 
-Merged 2026-10-11 (`task-1355`) and labelled **in progress**: the engine, the typed and spoken proposal paths, the `O` screen, the popup and the audit journal are on main and every default run is **paper**. Since 2026-10-12 (`task-1363`) a **live fire path on devnet** exists behind a held keypress: fills go through the signer process and a separate capped fast wallet, described in the live fire path (https://dexterm.xyz/docs/paper-trading#the-live-fire-path-devnet-the-fast-wallet) below. No plan has moved mainnet funds; there is no mainnet fast wallet.
+Labelled **in progress**: the engine, the typed and spoken proposal paths, the `O` screen, the popup and the audit journal are on main, and every plan fills on **paper**. There is no live fire path: plans never sign or send anything.
 
 An **order plan** is "buy this coin if it dips to 300k market cap, sell half at 600k, keep the rest as a moon bag", written down once: one entry trigger (market cap or price, below or above, or immediate), a ladder of take-profit tranches (each an above-trigger with a fraction; whatever the fractions leave is the moon bag), an optional stop (a below-trigger, below the entry), slippage and impact ceilings and an expiry (4 h by default, 7 days at most). `dexterm plan propose --mint M --size 20 --entry mc-below:300k --tp mc-above:600k:50% --stop mc-below:150k` writes one; so does saying it to Jarvis (https://dexterm.xyz/docs/voice) or an agent's `propose_order_plan` tool. All three produce the same thing: an **inert proposal** with a SHA-256 hash of its material fields and a plain-language read-back. A proposal fires nothing.
 

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

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-panic
-title: Paper trading, live trading and the safety model › Live trading (devnet first) › Panic
+title: Paper trading and the safety model › Panic
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: Panic
 anchor: panic
 url: https://dexterm.xyz/docs/paper-trading#panic
@@ -11,11 +11,8 @@ tags:
   - docs
   - paper-trading
   - panic
-  - live
-  - trading
-  - devnet
-  - first
   - paper
+  - trading
   - safety
   - model
 confidence: high
@@ -28,4 +25,4 @@ sources:
 date: 2026-10-16
 ---
 
-`/wallet panic` in the app, or `dexterm wallet panic` from any shell, any time: it writes a kill-switch file every signer re-reads on every plan and confirm, locks the shared cap ledger so no reservation can be taken, tells the running signer to forget its plans and flips an open LIVE ticket to refused. The only way back is `dexterm wallet resume` in a real terminal: it needs a physical keypress on a TTY and refuses piped input.
+`/wallet panic` in the app, or `dexterm wallet panic` from any shell, any time: it writes a kill-switch file that every autotrade runner and the paper agent desk re-read on every step, so they halt at once. The only way back is `dexterm wallet resume` in a real terminal: it needs a physical keypress on a TTY and refuses piped input.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-paper-only-mandates.md

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-paper-only-mandates
-title: Paper trading, live trading and the safety model › Order plans and standing mandates › Paper-only mandates
+title: Paper trading and the safety model › Order plans and standing mandates › Paper-only mandates
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: Paper-only mandates
 anchor: paper-only-mandates
 url: https://dexterm.xyz/docs/paper-trading#paper-only-mandates
@@ -17,7 +17,6 @@ tags:
   - standing
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -30,12 +29,12 @@ sources:
 date: 2026-10-16
 ---
 
-`dexterm mandate draft --paper` drafts a **paper-only** mandate for agent paper trading (https://dexterm.xyz/docs/agents#agent-paper-trading). It has its own, higher paper ceilings ($10,000 total, $2000 per trade, $2000 per coin, $10,000 daily loss, 10% price impact) so an agent can practise at a realistic size, and it still needs your physical keypress to arm. Only the agent paper desk reads it: the plan engine refuses to arm a plan into it, fire a plan under it or run copy trading through it, so it can never reach a signer, and every other mandate keeps the ceilings above. The agent still gets a quarter of its per-trade cap, and every fill is priced on a live quote, so a bigger simulated size pays its real price impact.
+`dexterm mandate draft --paper` drafts a **paper-only** mandate for agent paper trading (https://dexterm.xyz/docs/agents#agent-paper-trading). It has its own, higher paper ceilings ($10,000 total, $2000 per trade, $2000 per coin, $10,000 daily loss, 10% price impact) so an agent can practise at a realistic size, and it still needs your physical keypress to arm. Only the agent paper desk reads it: the plan engine refuses to arm a plan into it, fire a plan under it or run copy trading through it, and every other mandate keeps the ceilings above. The agent still gets a quarter of its per-trade cap, and every fill is priced on a live quote, so a bigger simulated size pays its real price impact.
 
-**Arming** a plan under a mandate is the only step that lets anything fire, and it is a physical gesture: a key held at the terminal on the `O` screen (`a`) or `dexterm plan arm <id> --mandate <id>` on a real TTY, which refuses a pipe or a subprocess. The gesture proof is bound to the plan hash, single-use and expiring, so an edited plan voids every earlier confirmation. Once armed, a monitor fed by the prices the terminal already shows (the screener rows, the watchlist, the open token; never fixture data) fires the entry, each take-profit tranche and the stop **only inside the armed plan and only through the executor**, which re-checks the mandate caps on every fill (and, on the live path, the signer re-checks its own caps, allow-lists and the panic marker on top). `dexterm plan amend <id> --size 25 --entry mc-below:280k` edits a **proposed** plan: the edit is a new plan with a new hash, the old proposal is superseded and every earlier confirmation is void, so arming it is a new keypress; an armed plan cannot be edited (cancel it first). Cancel (`c`), revoke (`r`) and panic (`!`, or `dexterm wallet panic`) stop a plan at once; nothing resumes a paused plan without a new keypress.
+**Arming** a plan under a mandate is the only step that lets anything fire, and it is a physical gesture: a key held at the terminal on the `O` screen (`a`) or `dexterm plan arm <id> --mandate <id>` on a real TTY, which refuses a pipe or a subprocess. The gesture proof is bound to the plan hash, single-use and expiring, so an edited plan voids every earlier confirmation. Once armed, a monitor fed by the prices the terminal already shows (the screener rows, the watchlist, the open token; never fixture data) fires the entry, each take-profit tranche and the stop **only inside the armed plan and only through the paper executor**, which re-checks the mandate caps and the panic marker on every fill. `dexterm plan amend <id> --size 25 --entry mc-below:280k` edits a **proposed** plan: the edit is a new plan with a new hash, the old proposal is superseded and every earlier confirmation is void, so arming it is a new keypress; an armed plan cannot be edited (cancel it first). Cancel (`c`), revoke (`r`) and panic (`!`, or `dexterm wallet panic`) stop a plan at once; nothing resumes a paused plan without a new keypress.
 
-Two **confirmation tiers** beyond the keypress exist in the model and are off by default: `ptt-held` (push-to-talk held while you speak the confirmation) fires at 0.5× the per-trade cap and `hands-free` at 0.25×, and neither can arm a mandate or a batch. Turning hands-free on is the only "less safe" switch in dexterm: `G` on the `O` screen raises a prompt that says so, it is accepted by a keypress only (a spoken, agent or Phantom "yes" is refused), it is journaled, it expires after 24 h and `G` again restores the gate.
+Two **confirmation tiers** beyond the keypress exist in the model and are off by default: `ptt-held` (push-to-talk held while you speak the confirmation) fires at 0.5× the per-trade cap and `hands-free` at 0.25×, and neither can arm a mandate or a batch. Turning hands-free on is the only "less safe" switch in dexterm: `G` on the `O` screen raises a prompt that says so, it is accepted by a keypress only (a spoken or agent "yes" is refused), it is journaled, it expires after 24 h and `G` again restores the gate.
 
 The **journal** (`~/.dexterm/plans.journal`) is append-only and hash-chained; every proposal, arm, fire, fill, cancel, revoke, gate change and refusal is a row, `dexterm plan journal --verify` recomputes the chain and `--export` dumps it, and it is the source the service recovers from after a crash. The popup is a read-only HUD fed view models only (never a key, a secret or an arm capability); its single write is "cancel this plan", re-validated at the server allow-list and again at the terminal.
 
-What is proven, on fixtures and a fake clock: the north-star plan fills end to end on the paper executor; a replayed price stream fires each leg once; and a compromised-model suite shows that spoken text, agent text, a forged proof, a replayed proof, a widened mandate and an edited plan with an old confirmation all fail to arm, raise a cap, widen a mandate, resume a paused plan, accept the risk prompt or switch the fire path.
+What is proven, on fixtures and a fake clock: the north-star plan fills end to end on the paper executor; a replayed price stream fires each leg once; and a compromised-model suite shows that spoken text, agent text, a forged proof, a replayed proof, a widened mandate and an edited plan with an old confirmation all fail to arm, raise a cap, widen a mandate, resume a paused plan, or accept the risk prompt.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-pnl-cards.md

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-pnl-cards
-title: Paper trading, live trading and the safety model › PnL cards
+title: Paper trading and the safety model › PnL cards
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: PnL cards
 anchor: pnl-cards
 url: https://dexterm.xyz/docs/paper-trading#pnl-cards
@@ -14,7 +14,6 @@ tags:
   - cards
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -27,11 +26,12 @@ sources:
 date: 2026-10-16
 ---
 
-`H` on a token, on the positions screen (`P`) or on the followed-wallets screen (`U`) opens a preview of a **PnL card** for a coin you have fills for: ticker and image, average entry and exit (or the mark for an open position), the PnL %, hold time, size, the dates, and a dexterm footer. It is saved as a 1200×675 PNG (the X card size), a 1080×1080 PNG and a text file in `~/.dexterm/exports/`.
+`H` on a token, on the positions screen (`P`) or on the followed-wallets screen (`U`) opens a preview of a **PnL card** for a coin you have fills for: ticker and image, entry and exit as the coin's **market cap** (or the mark for an open position), the PnL %, hold time, size, the dates, and a dexterm footer. It is saved as a 1200×675 PNG (the X card size), a 1080×1080 PNG and a text file in `~/.dexterm/exports/`.
 
-- **The stamp cannot be removed.** A card says where its numbers came from: **PAPER** (the simulated wallet, no real funds), **LIVE** (transactions your own wallet signed, confirmed on chain; a devnet fill says *DEVNET TEST FUNDS*) or **TRACKED WALLET** (a followed wallet's public history, read-only). The stamp is a solid block, the frame colour and a repeating strip, and no option hides it.
+- **The stamp cannot be removed.** A card says where its numbers came from: **PAPER** (the simulated wallet, no real funds) or **TRACKED WALLET** (a followed wallet's public history, read-only). The stamp is a solid block, the frame colour and a repeating strip, and no option hides it.
 - **Numbers come only from the records.** The PnL is computed from the fills, net of fees (realized for a closed position; realized plus unrealized at the latest price mark for an open one, which waits for a mark). You cannot type a number into a card. Each card prints its time window, the fee basis, what it leaves out (a tracked wallet's token-to-token swaps, transfers or airdrops) and the age of its data.
-- **Private by default.** The wallet address and LIVE transaction signatures are hidden, and the size shows as a band (`0.5-1 SOL`). `a` shows the wallet and signatures, `z` the exact size; no balance or key is ever on a card.
+- **Market cap or price.** When dexterm knows the coin's supply, entry and exit are shown as market cap: the average fill price times the supply, never a quoted market cap. The supply is the coin's recorded FDV ÷ price, or pump.fun's fixed 1 billion for a pump.fun coin. The card names that source and the USD rate it used (the current SOL price for a paper or tracked card). Exit is the **blended** average of every sell; with two or more sells, the **last sell** gets its own row. `m` in the preview switches to the SOL price per token and back. A coin with no known supply stays on the price view, and the card says why.
+- **Private by default.** The wallet address is hidden, and the size shows as a band (`0.5-1 SOL`). `a` shows the wallet, `z` the exact size; no balance or key is ever on a card.
 - **Sharing is yours.** `x` saves the card, copies the image to the clipboard where your OS allows it (macOS; Linux with `wl-copy` or `xclip`) and opens X's compose page in your browser with a short neutral text (the stamp in words, no coin and no numbers). You paste the image and post. dexterm does not post, has no X credentials for this and sends nothing. `t` copies the text version, `s` only saves; `f` flips 16:9 and 1:1, `←`/`→` move between coins, `esc` closes.
 
-A card shows one position's own fills. It is not a track record, and trading in dexterm is still experimental; the footer says so, along with "not financial advice".
+A card shows one position's own fills. It is not a track record, and paper trading is not a result; the footer says so, along with "not financial advice".

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-the-safety-model.md

@@ -0,0 +1,34 @@
+---
+id: docs-paper-trading-the-safety-model
+title: Paper trading and the safety model › The safety model
+kind: docs
+page: paper-trading
+page_title: Paper trading and the safety model
+heading: The safety model
+anchor: the-safety-model
+url: https://dexterm.xyz/docs/paper-trading#the-safety-model
+tags:
+  - docs
+  - paper-trading
+  - safety
+  - model
+  - paper
+  - trading
+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/paper-trading.md
+date: 2026-10-16
+---
+
+These are the invariants; hold us to them:
+
+1. **No custody.** dexterm holds no private key, has no trading wallet and has no signing code. The Phantom link stores only your public key, from a signed message.
+2. **Nothing is sent.** dexterm builds no transaction and sends none. Every ticket, plan, autotrade run and agent fill is paper.
+3. **Keypress gate on by default.** Models and voice create proposals; arming a plan or confirming a ticket needs a physical keypress. Opting out, if ever offered, needs an explicit "this is less safe" confirmation and is local, logged and reversible.
+4. **The AI has no trading interface.** No build, sign or send tool exists for the model. Its write-shaped tools are paper only: `open_ticket` opens a PAPER ticket, and (only if you start `--agent-paper` on a mandate you armed) an agent you connected can use the `paper_*` tools to book the **simulated** ledger inside that mandate. A registry test enumerates every MCP tool and fails if any could reach a signing or sending path.
+
+> warn: paper results are not predictive. Paper fills take the quote at its word; a real fill pays real slippage, priority fees and failed transactions, and most memecoins go to zero. Nothing here is financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-the-ticket.md

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-the-ticket
-title: Paper trading, live trading and the safety model › The ticket
+title: Paper trading and the safety model › The ticket
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: The ticket
 anchor: the-ticket
 url: https://dexterm.xyz/docs/paper-trading#the-ticket
@@ -13,7 +13,6 @@ tags:
   - ticket
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -26,6 +25,6 @@ sources:
 date: 2026-10-16
 ---
 
-`B` or `S` on a token opens a buy or sell ticket. It shows the side, the size (SOL or % of balance when buying; % of the position when selling), slippage in bps, and a rolling Jupiter quote refreshed every (generated from the app: see https://dexterm.xyz/docs/paper-trading#the-ticket; app-help has the exact keys and commands) s while you edit: what you pay, what you receive, price in SOL and USD, price impact (as a percent; Jupiter reports a 0..1 fraction and the app converts it once), the simulated fee, the route and the minimum received. Keys: digits type, `tab` switches field, `←`/`→` flips the side, `u` toggles the unit, `⏎` reviews, `esc` cancels, `L` flips PAPER ⇄ LIVE (see below). Token amounts are shown as quantities, so a small buy of an expensive token reads `0.0144 AVGOx`, never `0`; until the token's decimals are known the ticket says so instead of printing a guess.
+`B` or `S` on a token opens a buy or sell ticket. It shows the side, the size (SOL or % of balance when buying; % of the position when selling), slippage in bps, and a rolling Jupiter quote refreshed every (generated from the app: see https://dexterm.xyz/docs/paper-trading#the-ticket; app-help has the exact keys and commands) s while you edit: what you pay, what you receive, price in SOL and USD, price impact (as a percent; Jupiter reports a 0..1 fraction and the app converts it once), the simulated fee, the route and the minimum received. Keys: digits type, `tab` switches field, `←`/`→` flips the side, `u` toggles the unit, `⏎` reviews, `esc` cancels. Token amounts are shown as quantities, so a small buy of an expensive token reads `0.0144 AVGOx`, never `0`; until the token's decimals are known the ticket says so instead of printing a guess.
 
 The **confirm gate** is on by default. `⏎` arms the order; `y` (or `⏎` again) confirms. For a notional above (generated from the app: see https://dexterm.xyz/docs/paper-trading#the-ticket; app-help has the exact keys and commands) SOL you must type the size back digit for digit before the confirm counts. Any other key during the confirm step cancels the arm: a stray key can never confirm, and `q` or a screen number cannot navigate out from under an armed order. The fill is computed from a **fresh quote at confirm time**, never from the quote on screen, and is booked into the paper wallet in one SQLite transaction. If Jupiter rate-limits during the confirm the ticket says so, retries for up to 8 s, then lands in an error state you can retry or cancel; it never hangs.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-the-trade-ledger.md

@@ -0,0 +1,42 @@
+---
+id: docs-paper-trading-the-trade-ledger
+title: Paper trading and the safety model › The trade ledger
+kind: docs
+page: paper-trading
+page_title: Paper trading and the safety model
+heading: The trade ledger
+anchor: the-trade-ledger
+url: https://dexterm.xyz/docs/paper-trading#the-trade-ledger
+tags:
+  - docs
+  - paper-trading
+  - trade
+  - ledger
+  - paper
+  - trading
+  - safety
+  - model
+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/paper-trading.md
+date: 2026-10-16
+---
+
+`dexterm ledger` puts every trade dexterm booked in one table: the paper ticket, the agent paper desk and autotrade runs. One row is one round trip: the strategy and its version, the **exit profile** and entry reason the trade was opened with, the **exit reason**, size and share of the book, entry and exit as price and **market cap**, fees, hold time, the best and worst move while held (MFE / MAE, from the fills), and whether it rugged. Every row dexterm books is PAPER.
+
+- `dexterm ledger trades` lists them, newest first; `positions` shows what is open.
+- `dexterm ledger summary` gives the win rate with its 95% interval, P/L, profit factor, max drawdown, rug rate and hold time, broken down by profile, exit reason, strategy, source and mode. `equity` draws the realized equity curve.
+- `dexterm ledger compare` puts strategy versions side by side, which is how you read strategies you forward-test in parallel.
+- `dexterm ledger export csv|json|parquet-lite` writes the rows out for your own spreadsheet or notebook.
+- `dexterm ledger card <tradeId>` makes a PnL card (https://dexterm.xyz/docs/paper-trading#pnl-cards) from a ledger row, with market cap at entry and exit.
+- Filters: `--source`, `--mode`, `--strategy id[@version]`, `--profile`, `--exit`, `--mint`, `--run`, `--account`, `--days`, `--status`. `--account ID` keeps the trades of the strategies on one paper account (https://dexterm.xyz/docs/autotrade#paper-accounts); the export has an `account` column.
+
+**Declared, not guessed.** An agent declares its exit profile when it buys and its exit reason when it sells, as typed fields on the paper desk (or a PROFILE / EXIT line), and the ledger shows where each tag came from: declared with the fill, from an exit rule, from a tag line, declared later, or missing. Undeclared trades are counted, not filled in.
+
+**Your file, append-only.** Reads never write. `dexterm ledger sync` appends what the sources hold to `~/.dexterm/ledger/trades.jsonl`, where every line is sha256-chained to the one before; `dexterm ledger verify` recomputes the chain and names the first edited line, and an edited file is never appended to. No network, no model, no key.
+
+PAPER rows are simulated. A small number of trades says little, and the summary says so. Not financial advice.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-the-wallet.md

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-the-wallet
-title: Paper trading, live trading and the safety model › The wallet
+title: Paper trading and the safety model › The wallet
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: The wallet
 anchor: the-wallet
 url: https://dexterm.xyz/docs/paper-trading#the-wallet
@@ -13,7 +13,6 @@ tags:
   - wallet
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -29,6 +28,6 @@ date: 2026-10-16
 - starts at (generated from the app: see https://dexterm.xyz/docs/paper-trading#the-wallet; app-help has the exact keys and commands) SOL (configurable), persisted in the same SQLite file as the cache and watchlist (`--db`; `:memory:` for a throwaway session);
 - books every fill append-only with the simulated fee (5 000 lamports per fill, labelled as a simulation);
 - marks positions from DexScreener's USD price over the live SOL price every (generated from the app: see https://dexterm.xyz/docs/paper-trading#the-wallet; app-help has the exact keys and commands) s on the positions screen;
-- shows a `◈ POSITION · PAPER` row under the chart on any token you hold, and the same row plus entry line and fill markers in the chart popup (https://dexterm.xyz/docs/popup-chart). A confirmed LIVE fill shows the same way, marked live, read from the signer's own ledger.
+- shows a `◈ POSITION · PAPER` row under the chart on any token you hold, and the same row plus entry line and fill markers in the chart popup (https://dexterm.xyz/docs/popup-chart).
 
-The analyst can open a PAPER ticket for you (`open_ticket`, pre-filled, editing phase) when you ask it to buy or sell. It cannot size it past what you typed, arm it, confirm it, or flip it LIVE; it tells you to confirm yourself.
+The analyst can open a PAPER ticket for you (`open_ticket`, pre-filled, editing phase) when you ask it to buy or sell. It cannot size it past what you typed, arm it or confirm it; it tells you to confirm yourself.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-trade-moments.md

@@ -1,9 +1,9 @@
 ---
 id: docs-paper-trading-trade-moments
-title: Paper trading, live trading and the safety model › Trade moments
+title: Paper trading and the safety model › Trade moments
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 heading: Trade moments
 anchor: trade-moments
 url: https://dexterm.xyz/docs/paper-trading#trade-moments
@@ -14,7 +14,6 @@ tags:
   - moments
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -27,6 +26,6 @@ sources:
 date: 2026-10-16
 ---
 
-The cyberspace look reacts to a trade, but only to its **result**. A confirmed buy fires a green shockwave from the ticket with coins streaming up; a profitable sell a gold burst and gold rain; a loss red static that collapses down the screen (no shake, no mockery); a signer refusal or a failed send a red lockout flicker in the bands; and while a send is in flight a neutral cyan scanning sweep that is never a verdict. Normal and fever tiers differ in length and density; `--calm` shows none of it and the result card still lands at once; any key skips a running moment.
+The cyberspace look reacts to a trade, but only to its **result**. A confirmed buy fires a green shockwave from the ticket with coins streaming up; a profitable sell a gold burst and gold rain; a loss red static that collapses down the screen (no shake, no mockery); and a refused or failed order a red lockout flicker in the bands. Normal and fever tiers differ in length and density; `--calm` shows none of it and the result card still lands at once; any key skips a running moment.
 
-Two things are mechanical, not conventions. **Only a settled outcome can fire a moment:** the ticket reports exactly one outcome per booked paper fill, confirmed live fill, signer refusal or send failure, and the effects engine refuses anything without a confirmed-or-failed status; a quote, a PLAN, an armed order or a `send-unknown` (the chain may still confirm it) fires nothing, and a test checks the one call site. **The ticket is shielded:** every cell of the ticket and the PAPER / LIVE banner is marked off-limits on the cell buffer, so rain, glitch, datamosh, scanlines and the moments cannot write a glyph, a colour or a background into it in any phase (tested byte-identical against a calm render at 176, 120 and 90 columns). `--sound` (or `DEXTERM_SOUND=1`) adds short synthesized cues after the same outcome: a buy chirp, a sell sweep then a chime or a thud, a buzz on a failure. Muted by default; the WAVs are written once to `~/.dexterm/sounds` and played detached so the render loop never waits.
+Two things are mechanical, not conventions. **Only a settled outcome can fire a moment:** the ticket reports exactly one outcome per booked paper fill or failure, and the effects engine refuses anything without a confirmed-or-failed status; a quote or an armed order fires nothing, and a test checks the one call site. **The ticket is shielded:** every cell of the ticket and the PAPER banner is marked off-limits on the cell buffer, so rain, glitch, datamosh, scanlines and the moments cannot write a glyph, a colour or a background into it in any phase (tested byte-identical against a calm render at 176, 120 and 90 columns). `--sound` (or `DEXTERM_SOUND=1`) adds short synthesized cues after the same outcome: a buy chirp, a sell sweep then a chime or a thud, a buzz on a failure. Muted by default; the WAVs are written once to `~/.dexterm/sounds` and played detached so the render loop never waits.

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

@@ -1,16 +1,15 @@
 ---
 id: docs-paper-trading
-title: Paper trading, live trading and the safety model
+title: Paper trading and the safety model
 kind: docs
 page: paper-trading
-page_title: Paper trading, live trading and the safety model
+page_title: Paper trading and the safety model
 url: https://dexterm.xyz/docs/paper-trading
 tags:
   - docs
   - paper-trading
   - paper
   - trading
-  - live
   - safety
   - model
 confidence: high
@@ -23,10 +22,10 @@ sources:
 date: 2026-10-16
 ---
 
-The PAPER ticket, the simulated wallet, the confirm gate; the LIVE path behind a separate signer process (devnet first), and the invariants it keeps.
+The PAPER ticket, the simulated wallet, the confirm gate, order plans on paper, PnL cards and the trade ledger. dexterm holds no key and signs nothing.
 
 Trading in dexterm is **PAPER by default**: a simulated wallet priced from live, keyless Jupiter quotes. Nothing is signed, no key is held, no transaction is sent, and the paper code imports no wallet or signing library of any kind. Every ticket and positions frame says so in a banner that is never hidden.
 
-A **LIVE** path exists on main, devnet first and labelled in progress: your own Phantom signs, a separate signer process holds the caps, and a Jupiter swap (a mainnet transaction) is refused unless you start dexterm with `--mainnet`. It is described in Live trading (devnet first) (https://dexterm.xyz/docs/paper-trading#live-trading-devnet-first) below.
+dexterm has no live trading path of its own: it holds no key, has no trading wallet and builds or sends no transaction. Live trading happens in a Telegram trading bot of your choice; see Live trading (https://dexterm.xyz/docs/live-trading).
 
 PAPER positions on sample data

package/dist/packages/mcp/assets/kb/docs/docs-popup-chart-buy-and-sell-markers.md

@@ -0,0 +1,37 @@
+---
+id: docs-popup-chart-buy-and-sell-markers
+title: Popup chart › Buy and sell markers
+kind: docs
+page: popup-chart
+page_title: Popup chart
+heading: Buy and sell markers
+anchor: buy-and-sell-markers
+url: https://dexterm.xyz/docs/popup-chart#buy-and-sell-markers
+tags:
+  - docs
+  - popup-chart
+  - buy
+  - sell
+  - markers
+  - popup
+  - chart
+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/popup-chart.md
+date: 2026-10-16
+---
+
+Every fill of the coin in your ledgers is marked on the chart: the **paper ledger** (your PAPER trades and an agent's PAPER trades) and the **live ledger** (confirmed real swaps from a linked wallet). Nothing is fetched to draw them, and they show whether or not you still hold the coin.
+
+- A buy is a triangle pointing up with `B` under it, its tip on the fill price; a sell points down with `S` above it. **Hollow** triangles (`△ ▽`) are PAPER, **solid** ones (`▲ ▼`) are live, and the colour only adds to that.
+- Each fill sits on the bar whose period contains its time, on every timeframe: switch from 1m to 1h and the markers move to their 1h bars. Two fills of one side in one bar make one marker with a count (`S×2`) at their size-weighted price, so a position sold in three parts shows three sells on 1m and fewer, counted ones on 1h. Zoom far out and neighbouring markers merge the same way, so they never pile up.
+- Hover a marker for its time, price (market cap with the price in brackets on the market cap axis), size in tokens and SOL, and the ledger it came from. A sell that left tokens says `partial`; the one that closed the position says `closed`.
+- While a position is open, the average entry is a dashed line. A closed round trip gets a faint wash from the entry bar to the exit bar (green when it sold above the entry).
+- A fill outside the candles on screen is never moved onto another bar. The legend says how many are off the chart and why: older than the first candle, newer than the last one (the candle feed lags a minute or two), or in a minute with no trades.
+- **MARKERS** in the toolbar, or `k`, turns them off and on for both charts; the terminal saves it as `display.chartMarkers` (see chart markers (https://dexterm.xyz/docs/configuration#chart-markers)). A fill with no recorded USD price is drawn against its bar and says `price not recorded`.
+
+Display only: no marker can arm, size, sign or confirm anything.

package/dist/packages/mcp/assets/kb/docs/docs-popup-chart-what-it-shows.md

@@ -26,6 +26,7 @@ date: 2026-10-16
 - candles, line or area; a volume pane; crosshair with the OHLCV, change and indicator values of the bar under it; wheel and pinch zoom, drag pan; auto, log or percent scale; local-time axis.
 - the last-price line, and a dotted **LIVE** price line while the terminal's fast lane is streaming the coin; a `◌ STALE Ns` badge when no tick has arrived for 20 s.
 - buy and sell markers from the trade tape, EMA 9/21, VWAP (anchored to the UTC day), a volume 20-MA, horizontal and trend lines you draw (page memory only; they go when the popup closes).
-- when you hold a PAPER position in the coin: an ENTRY line labelled with size and PnL %, BUY and SELL fill markers for the current position, STOP and TARGET lines when a ledger sets them, and the same position row the terminal shows under its chart.
+- **your own buys and sells** on every timeframe: every fill of the coin from the paper ledger and the live ledger, open position or closed, as BUY and SELL markers (https://dexterm.xyz/docs/popup-chart#buy-and-sell-markers).
+- when you hold a position in the coin: a dashed **AVG ENTRY** line labelled with size and PnL %, STOP and TARGET lines when a ledger sets them, and the same position row the terminal shows under its chart.
 - while an auto mode runs and a position is open (an agent you follow holds a PAPER position, or AI scan mode with your own position), the PnL chip (https://dexterm.xyz/docs/spectator#the-brain-view-and-the-pnl-chip) under the toolbar, with the same fields as the terminal's. It is about the held coin, which need not be the coin on the chart. Display only.
 - the six timeframes are the popup's own. 5m and 15m are derived from the cached 1m base, 4h and 1d from the cached 1h base, so switching costs no fetch; a base the terminal has not fetched yet shows an honest "warming … no extra requests" banner until it lands. **1s is not offered:** the only trade source is a ≤60-trade tape refreshed at most every 20 s, so 1-second bars would be sparse and stale.

package/dist/packages/mcp/assets/kb/docs/docs-screens-autotrade-paper.md

@@ -0,0 +1,26 @@
+---
+id: docs-screens-autotrade-paper
+title: Screens tour › Autotrade (paper)
+kind: docs
+page: screens
+page_title: Screens tour
+heading: Autotrade (paper)
+anchor: autotrade-paper
+url: https://dexterm.xyz/docs/screens#autotrade-paper
+tags:
+  - docs
+  - screens
+  - autotrade
+  - paper
+  - 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
+---
+
+`Q` from anywhere opens AUTOTRADE: your strategies and the presets, a strategy editor that re-validates on every change, a side-by-side compare, backtests and held-out sweeps on your recorded history, and the runner view. `tab` moves between them. Everything on it is paper; nothing on it can switch a strategy to live or touch a wallet. The views and keys are in Autotrade (paper) (https://dexterm.xyz/docs/autotrade#on-the-q-screen).

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

@@ -23,4 +23,4 @@ sources:
 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).
+`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 plan'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).

package/dist/packages/mcp/assets/kb/docs/docs-screens-token-screen.md

@@ -29,6 +29,8 @@ Everything about one coin: candles (1m to 1d, `1`–`6`), market stats, mint and
 
 The price badge says **LIVE** only while a fresh on-chain push is flowing for that coin over the fast lane (one WebSocket on its pump.fun bonding curve), otherwise **POLL**. When you hold a PAPER position in the coin a `◈ POSITION · PAPER` row renders under the chart with side, size, value, average entry, price and unrealized PnL.
 
+**Your buys and sells on the chart.** Every fill of the coin in your paper ledger and live ledger is marked on its candle: `△B` / `▽S` for PAPER, `▲B` / `▼S` for live, with a count when one candle holds several (each partial sell of a position gets its own marker on a fine timeframe). While a position is open a dashed `avg` line marks the average entry, and a closed round trip gets a faint wash from entry to exit. A fill outside the candles on screen is not moved; the legend says how many are off the chart. See chart markers (https://dexterm.xyz/docs/configuration#chart-markers).
+
 **Who holds it.** Once the wallet-intel scan (https://dexterm.xyz/docs/screens#bubble-map) lands (about 1.5 s after the token opens), every row of the HOLDERS panel carries a class read from the chain, never guessed: **POOL** (an AMM / CLMM / DLMM pool vault: Raydium, Orca, Meteora, PumpSwap), **CURVE** (a bonding curve: pump.fun, Meteora DBC for Jupiter Studio and Meteora launches, Raydium LaunchLab), **VAULT** (Meteora dynamic and Alpha vaults), **LOCK** (a Streamflow or Jupiter Lock escrow), **CEX** (seed-list exchange wallet, always *unverified*), **BURN** (the incinerator), **DEV** (the creator), **LINKED** (tied to another top holder by a funder, bundle or transfer rule) and **UNLABELLED** for everything else, including an account of a program dexterm does not list. The class comes from the token account's owner and the owner account's program (the same account lookup the scan already makes, no new request); the constant pool-authority addresses are re-derived in the tests. The single Top 10 holders row then becomes two: **Top 10 ex-pool** drops POOL / CURVE / VAULT / LOCK / BURN owners and is what the colour reads, **Top 10 raw** is what explorers show, so a fresh launch whose curve still holds 70 % no longer reads as a 78 % whale. Unlabelled owners are always counted. When a counted owner holds more than 30 % the panel says so on its first line (`⚠ main risk: UNLABELLED Ab12…Cd34 holds 71.6%`); when the biggest holder is a venue it says which (`· top holder 70.0% is CURVE (Meteora DBC): not counted in ex-pool`). A lock or vault names its escrow and program; dexterm does not decode the unlock schedule yet and says so.
 
 When the Snipers and Bundled supply rows have no number they give the reason: `needs Helius key` only when no key is configured, otherwise `Helius paused · r` (rate-limited), `Helius cap today` (the daily credit budget is spent), `history failed · r` (the history call errored) or `no launch txs read`. `r` on the token screen re-runs a scan whose launch window did not land.

package/dist/packages/mcp/assets/kb/docs/docs-spectator-the-brain-view-and-the-pnl-chip.md

@@ -35,7 +35,7 @@ While the agent is active (it made a call in the last 3 minutes, or it holds a P
 
 - **REASONING.** The agent's thoughts (from `--spectate-thoughts`) typing in, newest at the bottom, each with its clock time and the phase it was in (`SCANNING`, `VETTING`, `SIZING`, ...). Older lines dim, and long lines are clipped. With no thoughts feed, the header says `dexterm narration · no thoughts feed` and the lines are dexterm's own narration of each call. Lines a demo or stand-in feed marks as scripted (`"demo": true`) carry the coral `claude lines: demo text` tag.
 - **VETTING $COIN.** The checklist for the coin on screen: momentum, liquidity against the $10K floor, tape buys/sells and wallet count, top-10 concentration, mint/freeze authority, LP lock, dev history, LARP flags, the rug heuristic and the verdict. Each box shows the number the app computed and `pass`, `warn`, `fail` or `pending` (pending = that number is not in yet). `◆` marks the checks the agent itself ran.
-- **DATA.** Market cap, price, liquidity, 5m and 1h moves, buy/sell flow and holders, with a candle trace. These are the numbers already on screen; there is no extra fetch.
+- **DATA.** Market cap, price, liquidity, 5m and 1h moves, buy/sell flow and holders, with a candle trace. A `B` or `S` cell on the trace marks the candle of each fill of the coin in your ledgers (the chart markers (https://dexterm.xyz/docs/configuration#chart-markers)). These are the numbers already on screen; there is no extra fetch.
 - **PLAN / POSITION** (while a PAPER ticket or position is open): entry, size, the take-profit and stop the agent *said* (labelled `agent's plan`, or `no stop`), mark PnL in % and paper $, peak, drawdown from the peak, time held, and what it is waiting for. A desk refusal is stamped here.
 - **DECISIONS.** The session log (`rejected DECOY · verdict AVOID`, `entered`, `sold`, `desk refused`) and a scoreboard: `PAPER simulated · vetted · entries · closed · realized SOL`.
 

package/dist/packages/mcp/assets/kb/docs/docs-telegram-approve-one-tap-entries.md

@@ -0,0 +1,50 @@
+---
+id: docs-telegram-approve-one-tap-entries
+title: Telegram (your own bot) › Approve: one-tap entries
+kind: docs
+page: telegram
+page_title: Telegram (your own bot)
+heading: Approve: one-tap entries
+anchor: approve-one-tap-entries
+url: https://dexterm.xyz/docs/telegram#approve-one-tap-entries
+tags:
+  - docs
+  - telegram
+  - approve
+  - one-tap
+  - entries
+  - own
+  - bot
+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/telegram.md
+date: 2026-10-16
+---
+
+Approvals are on for a strategy whose `entry.decide` is `"agent+approve"`, and for every strategy after `/approvals on` (or `dexterm telegram approvals on`). Your agent still decides and your strategy still clamps the size; the entry then becomes a **proposal** instead of an order:
+
+```
+PAPER · PROPOSAL · moonbag v1.0.0 (67fc4c95)
+token "SYM" abcd…wxyz
+buy $20.00 (2.0% of book) @ 0.0001645 · liq $36.6K · impact ~0.40%
+plan: moonbag: cost back at +100%, then a 55% bag trail, out after 7 days, no hard stop
+why (the agent's words, unverified): "Fresh pair 34 min old, buyers 1.6x sellers."
+expires in 90 s · #k3Jd9aQx
+Only these buttons approve. Replies are ignored.
+[Approve] [Half size] [Skip]
+```
+
+- **No answer is a skip.** A proposal expires after 90 seconds (set 60 to 120 with `dexterm telegram set expiry`), on your computer's clock. There is no auto-approve.
+- **[Half size]** only ever halves. **[Skip]** skips.
+- **The price is checked again at your tap.** If it moved more than 3 % (never more than the strategy's own slippage), the liquidity fell more than 10 %, or the impact would pass the strategy's cap, the card is re-quoted with fresh numbers and new buttons and you confirm once more. A second move is a skip.
+- **Your limits are checked again at your tap**, against the book as it is then: the size can shrink, or the entry is refused.
+- **One tap, once.** Every button is bound to a one-time code, the proposal's exact numbers, its expiry, your account and your private chat. A double tap, a second device or an old button gets "Already handled"; a forwarded card tapped by someone else, or in a group, is refused.
+- **A kill, a pause or a halt** cancels every open proposal and removes its buttons. If the runner restarts, open proposals expire; they are never brought back.
+- **Exits never wait for chat.** Stops, take-profits, trails and rug exits run on their own, and a [Sell] on `/positions` only ever sells.
+- At most as many proposals are open at once as the strategy allows sessions; the rest are skipped and counted.
+
+The order then goes through the paper book with a single-use approval for exactly that order (bound to its hash and the proposal): a different order, a different coin, a bigger size or a second use is refused.

package/dist/packages/mcp/assets/kb/docs/docs-telegram-control-the-commands.md

@@ -0,0 +1,43 @@
+---
+id: docs-telegram-control-the-commands
+title: Telegram (your own bot) › Control: the commands
+kind: docs
+page: telegram
+page_title: Telegram (your own bot)
+heading: Control: the commands
+anchor: control-the-commands
+url: https://dexterm.xyz/docs/telegram#control-the-commands
+tags:
+  - docs
+  - telegram
+  - control
+  - commands
+  - own
+  - bot
+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/telegram.md
+date: 2026-10-16
+---
+
+The list is closed. Anything else gets the help text.
+
+| command | what it does | from chat |
+|---|---|---|
+| `/status` | the runner state, strategy, open positions, the day's P/L %, spend, approvals | always |
+| `/positions` | each open position with a [Sell] button | always |
+| `/pause` | no new entries; exits keep running | always |
+| `/resume` | lifts a **pause** | only a pause: never a kill, the panic switch, a loss-limit halt or a guard; those clear on your computer |
+| `/kill` (or `/stop`) | the same as `dexterm autotrade stop`: no new entries, sessions closed, pending orders dropped, exits keep running until nothing is held | always |
+| `/flatten` | stop, then sell every position at its next tick | after a [Yes, flatten] button |
+| `/strategies` | your validated strategies and the presets, marked when `/use` may pick them | always |
+| `/use <strategy>` | switch to another strategy | only to one that is **equal or tighter** than the running one, after a [Yes, switch] button. Any change dexterm cannot rank (a field with no safety rule, or a value it cannot compare) counts as looser, and so do a bigger bankroll and a dip-buying ladder. New entries stop at once; the new strategy starts once the open positions have closed. It never changes paper or live |
+| `/approvals on` | every new entry waits for your tap | always. `off` is local only: `dexterm telegram approvals off` |
+
+Never from chat, because no such command exists: live mode, looser caps or strategies, approvals off, resuming after a kill or the panic switch, moving funds.
+
+Chat writes the same control file `dexterm autotrade stop` and the AUTOTRADE screen write, so it is a remote control for the runner on your computer and adds no way around its limits. Commands are limited to 10 a minute; `/kill`, `/stop`, `/pause` and `/flatten` are never limited. A command sent while nothing was polling is not acted on when the bot comes back. Commands count only in your private chat, and a forwarded message or one sent through an inline bot is never a command.

package/dist/packages/mcp/assets/kb/docs/docs-telegram-if-something-goes-wrong.md

@@ -0,0 +1,30 @@
+---
+id: docs-telegram-if-something-goes-wrong
+title: Telegram (your own bot) › If something goes wrong
+kind: docs
+page: telegram
+page_title: Telegram (your own bot)
+heading: If something goes wrong
+anchor: if-something-goes-wrong
+url: https://dexterm.xyz/docs/telegram#if-something-goes-wrong
+tags:
+  - docs
+  - telegram
+  - something
+  - goes
+  - wrong
+  - own
+  - bot
+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/telegram.md
+date: 2026-10-16
+---
+
+- **Telegram is down, or a message cannot be sent:** the proposal is a skip. Notifications retry. The runner never waits on chat, and your exits are unaffected.
+- **Someone else uses your token** (a webhook appears on the bot, or another program polls it): the bot stops every approval, you are warned on your computer, and every local control keeps working (`dexterm autotrade stop`, the AUTOTRADE screen, `dexterm wallet panic`). Messages from accounts that are not paired get no answer; five in an hour raise a "possible token leak" warning on your computer.
+- **Revoke it:** `dexterm telegram revoke` removes the token from your computer and forgets every paired chat. If the token may have leaked, also send `/revoke` to @BotFather for that bot and run setup again.