dexterm-cli 0.1.6 → 0.2.0

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-real-mode-receipts-what-your-executor-did.md

@@ -0,0 +1,42 @@
+---
+id: docs-real-mode-receipts-what-your-executor-did
+title: Real mode (LIVE TRADE FIRE signals) › Receipts: what your executor did
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: Receipts: what your executor did
+anchor: receipts-what-your-executor-did
+url: https://dexterm.xyz/docs/real-mode#receipts-what-your-executor-did
+tags:
+  - docs
+  - real-mode
+  - receipts
+  - executor
+  - did
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+dexterm cannot see your executor's wallet trades, so a real position stays **unconfirmed** until a receipt arrives. A receipt is data only: it never makes dexterm buy, sell or change anything.
+
+```
+dexterm autotrade receipt 42 executed --size-sol 0.049 --price 0.00121 --tokens 40500 --tx <signature>
+dexterm autotrade receipt 43 rejected --reason "slippage too high"
+dexterm autotrade receipt list
+```
+
+Your executor can also append one line per signal to `~/.dexterm/autotrade/real/receipts.jsonl`: `{"schema":"dexterm-trade-receipt/1","signalId":"…","nonce":42,"accountId":"main","status":"executed","at":1792000004000,"fill":{"priceUsd":0.00121,"sizeSol":0.049,"tokens":40500,"txSig":"…"},"reason":null,"executor":"my-bot"}`. A receipt for an unknown nonce, another account or a mismatched id is counted and ignored.
+
+The exits keep firing on dexterm's own view of the market whether or not a receipt came. A receipt with a fill also says how far the real fill landed from dexterm's paper fill (paper vs real (https://dexterm.xyz/docs/going-real#paper-vs-real)). The drift between signals and receipts (unconfirmed, rejected, failed, filled size and price against the signal) shows in `receipt list`, `signal status`, `dexterm autotrade audit` and the run file (receipt rows). `dexterm autotrade signal reconcile --wallet <your PUBLIC address>` reads that address's SOL balance and token holdings (two read-only calls) and lists the coins the real book holds that the wallet does not, and back. It never takes a key.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-safety.md

@@ -0,0 +1,34 @@
+---
+id: docs-real-mode-safety
+title: Real mode (LIVE TRADE FIRE signals) › Safety
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: Safety
+anchor: safety
+url: https://dexterm.xyz/docs/real-mode#safety
+tags:
+  - docs
+  - real-mode
+  - safety
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+- **Only you switch a strategy to real**, on your own terminal, with the typed phrase. A model cannot: the mode is on the list of fields only you may change, the agent's decisions have no such verb, no MCP tool arms, and a file edited by hand to `"mode": "real"` is not armed. Arming, an evidence override, disarming, caps and the kill switch are all journaled in `~/.dexterm/autotrade/real/journal.jsonl`.
+- **The limits live outside the model** (all of them (https://dexterm.xyz/docs/going-real#your-limits)). A buy is cut to the per-trade, position, exposure and price-impact limits. A buy over the daily SOL, buys per day, per coin or open positions limit is refused (open positions means every real holding on this machine, whichever run opened it). So is a buy after a loss stop, the drawdown breaker or a loss streak, or while your executor is silent. Sells are never blocked by a limit unless you set the optional sell rate, so an exit always goes out.
+- **The real-mode kill switch**: `dexterm autotrade signal kill` stops every trade-fire signal at once, sells included. It never closes a position: it prints the open ones, and a running real run halts at its next tick and sends one `halted` that lists them for your executor. `dexterm autotrade signal unkill` (typed confirmation) lifts it. The panic switch (`dexterm wallet panic`) halts real runs too: no new entries, exits keep going out.
+- **Chat approvals stay paper.** A one-tap approval never authorises a real signal: a strategy that waits for a tap (`entry.decide: "agent+approve"`, or `dexterm telegram approvals on`) does not start in real mode. Your executor is the last gate.
+- The prompt firewall, the strategy clamp and the session caps apply exactly as on paper.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-set-it-up.md

@@ -0,0 +1,47 @@
+---
+id: docs-real-mode-set-it-up
+title: Real mode (LIVE TRADE FIRE signals) › Set it up
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: Set it up
+anchor: set-it-up
+url: https://dexterm.xyz/docs/real-mode#set-it-up
+tags:
+  - docs
+  - real-mode
+  - set
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+1. **A channel your executor can read** (one or more), saved next to your Telegram setup (https://dexterm.xyz/docs/telegram) in `connectors.json`:
+
+   ```
+   dexterm autotrade signal channels --webhook http://127.0.0.1:8787/fire
+   dexterm autotrade signal channels --signal-cmd '["/usr/local/bin/my-executor","--fast"]'
+   dexterm autotrade signal channels --jsonl on
+   dexterm autotrade signal channels --mcp on
+   dexterm autotrade signal channels --telegram on --ttl 60
+   ```
+
+   `off` turns one off. `dexterm telegram status` shows the channels too.
+2. **A webhook secret** (recommended for the webhook): `dexterm autotrade signal secret generate --out /path/for/your/executor.secret` makes a random secret, keeps it in your keychain (like the bot token) and writes it to that file (0600) for your executor. It is never printed. `secret set` reads one from a pipe; `secret remove` deletes it.
+3. **Your limits**: `dexterm autotrade limits set perTradeSol=0.25 dailySol=1 buysPerDay=20 maxOpenPositions=3 dailyLossSol=0.5`, and any of the others (Going real, safely (https://dexterm.xyz/docs/going-real#your-limits)): per trade in SOL or % of book, exposure, position size, per coin, loss stops, the drawdown breaker, max hold, floors, slippage, TTL, rate. You can set them globally, per mode, per strategy or per account, and the stricter wins. Raising any of them asks for a typed confirmation on your terminal; lowering does not. The numbers shown are placeholders. `signal caps set --per-trade-sol …` still sets the first four.
+4. **Arm the strategy** on your own terminal: `dexterm autotrade signal arm my-strategy [--account main]`. On a first arming it asks for your own limits (Enter keeps a placeholder). Then you see the evidence panel: the last backtest of this version, a forward-test report if there is one, the limits in force for this strategy and account, your executor's health and the channels. Then you type the phrase it shows, which confirms those limits, with its one-time code (`REAL my-strategy 7KQ4`). **The evidence floor**: arming needs a completed forward test of these exact rules with at least 10 closed paper trades (your limit `minForwardTrades`) and a backtest on record. Below it, or when arming now would skip a rung of the ladder (https://dexterm.xyz/docs/build-a-strategy-by-chat#the-ladder), arming refuses and says what is missing; only you can go on anyway, by first typing a separate phrase it shows (`OVERRIDE my-strategy 3HXR`, its own one-time code). The override is journaled. No model, tool, flag or pipe can give it. Arming saves the strategy as a new version in mode `real`, and the arming is bound to that exact version: any later edit disarms it. Presets cannot be armed; copy one with `dexterm autotrade new` first.
+5. **Test the channels**: `dexterm autotrade signal test` sends a `test` signal (`test: true`, no coin: nothing to trade) through each channel and shows, per channel, delivered or not, the latency, and your executor's receipt. The dry-run executor kit (https://dexterm.xyz/docs/going-real#the-executor-kit) answers it out of the box.
+6. **Run it**: `dexterm autotrade run my-strategy --real`. In 0.2.0 real mode runs **in the foreground only**: the always-on service runs paper strategies, never a real one. Real mode runs on live data only (a replay would send old prices to your executor). `--sol-usd N` fixes the SOL price for sizes in SOL; without it dexterm reads SOL/USD from DexScreener (keyless) and refuses to start without one.
+
+`dexterm autotrade signal disarm my-strategy` puts it back on paper. `dexterm autotrade run my-strategy --paper` runs a real strategy's paper twin: no signal goes out. `run --all` stays paper: a real strategy runs on its own.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-the-channels.md

@@ -0,0 +1,42 @@
+---
+id: docs-real-mode-the-channels
+title: Real mode (LIVE TRADE FIRE signals) › The channels
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: The channels
+anchor: the-channels
+url: https://dexterm.xyz/docs/real-mode#the-channels
+tags:
+  - docs
+  - real-mode
+  - channels
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+| Channel | How your executor gets it | What counts as delivered |
+|---|---|---|
+| webhook | `POST` of the line to `http://127.0.0.1`, `localhost` or `[::1]` on any port, or to an `https://` URL of yours. Headers `x-dexterm-signature`, `x-dexterm-nonce`, `idempotency-key`. Redirects are refused. | 2xx; 409 means "already have it". 408, 425, 429, 5xx or no answer is retried; any other 4xx is a rejection. |
+| `--signal-cmd` | Your program is started with its argv (an absolute path; no shell, no PATH lookup), the line on stdin, a minimal environment (`DEXTERM_SIGNAL_NONCE`, `DEXTERM_SIGNAL_ID`, `DEXTERM_SIGNAL_SIGNATURE` when a secret is set; nothing else of dexterm's). 10 seconds per call. | exit 0; exit 3 means "already have it"; exit 2 is a rejection; anything else is retried. |
+| JSONL stream | One line per signal appended to `~/.dexterm/autotrade/real/signals.jsonl` (0600), or the path you set. Tail it. | the line is written. |
+| MCP | The read-only MCP tool `trade_fire_feed` returns the signals after a nonce, plus real mode's state. | the line is written to the feed. |
+| Telegram | A `LIVE TRADE FIRE` message to your paired chat, as plain text. For you to read, not for your executor. | Telegram accepted it. |
+
+**Delivery.** A signal is written to the outbox (`~/.dexterm/autotrade/real/outbox.jsonl`) before its fill is booked, so the book never holds anything a signal did not announce. Each channel gets the signals in nonce order, retried with backoff from 1 second up to 30, until it acks, rejects one, or the signal expires (then it is marked expired and never sent late). A restart picks the outbox up where it stopped; nothing is sent twice on purpose, and your executor dedupes the rest by nonce. One process writes the outbox at a time. `dexterm autotrade signal flush` delivers what is pending, and `signal tail` lists the newest signals with their delivery and receipt state.
+
+**The dead-man.** Every signal carries its TTL. A run that ends, halts or is killed sends one final `halted` signal with its outstanding nonces. A runner that dies without one (a crash, a power cut) gets its `halted`, with the reason `runner-lost`, the next time the outbox opens: the next real run or `dexterm autotrade signal flush`.
+
+**A run that ends holding a position.** Ending a real run (its time limit, Ctrl-C, a stop, the kill switch, a halt, a crash) does not sell anything: what is still open is carried. dexterm keeps its real holdings in `~/.dexterm/autotrade/real/held.json`, across runs. You cannot miss them: the run's last lines print the open coins (`REAL POSITIONS STILL OPEN`), the final `halted` signal lists them in `open`, and its Telegram copy says "these positions are still open: manage them in your executor". **When no real run is running, NO signals go out, sells included**: an open position gets no exit from dexterm until the next real run of its strategy, so manage it in your executor. The next real run of the same strategy and account takes them over and their exits keep firing, so a carried coin still gets its sell signal. A carried coin is never bought again while it is held, it counts against the open-position cap, and a coin another strategy holds is not bought. `dexterm autotrade signal held` lists the holdings; if you closed one yourself in your executor, `dexterm autotrade signal release <mint>` (typed confirmation) forgets it.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-the-signal.md

@@ -0,0 +1,48 @@
+---
+id: docs-real-mode-the-signal
+title: Real mode (LIVE TRADE FIRE signals) › The signal
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: The signal
+anchor: the-signal
+url: https://dexterm.xyz/docs/real-mode#the-signal
+tags:
+  - docs
+  - real-mode
+  - signal
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+One line of JSON, the same bytes on every channel:
+
+```json
+{"schema":"dexterm-trade-fire/1","type":"trade","id":"9f2c…(32 hex)","nonce":42,"issuedAt":1792000000000,"expiresAt":1792000060000,"ttlSec":60,"runId":"…","accountId":"main","strategy":{"id":"my-strategy","version":"1.0.1","hash":"…"},"paper":false,"side":"buy","mint":"…","symbol":"PEPE","sizeSol":0.05,"sizeUsd":10,"pctOfBook":2,"sellFraction":null,"price":{"usd":0.0012,"mcap":1200000,"liqUsd":48000,"solUsd":200},"exitReason":null,"slippageBps":300,"maxImpactPct":3,"positionId":"…"}
+```
+
+- `type`: `trade`, `halted` (the run ended or stopped: `outstanding` lists the nonces it had sent that had not expired, `open` the coins dexterm still counts as held for the account) or `test`.
+- `side` `buy` or `sell`. A buy states `sizeSol` (what to spend) and `pctOfBook`. A sell states `sellFraction`, the share of the position to sell (apply it to what you really hold), and `exitReason` (the exit rule that fired: `hard-stop`, `trail`, `tp-1`, `agent-exit`, `flatten` and so on); its `sizeSol` is dexterm's modelled proceeds and can be 0 for a coin that rugged.
+- `nonce` only ever grows, across runs and restarts. `id` is the idempotency key (a hash of the account, the run and the nonce). `paper` is always `false`.
+- **Firewall**: the only token-made text in a signal is the symbol, reduced to `A-Z a-z 0-9 . _ $ -` (16 characters). No name, no description, no link, no agent text, no path, no key.
+
+**What a well-behaved executor does with each signal:**
+
+1. Check the HMAC (when you set a secret): `x-dexterm-signature: t=<unix seconds>,v1=<hex>`, where `v1` is HMAC-SHA256 of `<t>.<body>` with your secret. Refuse a timestamp more than 5 minutes off.
+2. Ignore it after `expiresAt`. A late signal is never acted on.
+3. Act once per `nonce` (delivery is at least once: a repeat is normal) and ignore a nonce lower than one already acted on.
+4. Act only on the `accountId` it was set up for.
+
+`SignalReceiver` in `@dexterm/autotrade` does these four checks, if your executor is written in Node.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-what-it-is.md

@@ -0,0 +1,35 @@
+---
+id: docs-real-mode-what-it-is
+title: Real mode (LIVE TRADE FIRE signals) › What it is
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: What it is
+anchor: what-it-is
+url: https://dexterm.xyz/docs/real-mode#what-it-is
+tags:
+  - docs
+  - real-mode
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+> **0.2.0, experimental.** Real mode can lead to real trades in a wallet you fund. dexterm never holds a key, never signs and never sends a transaction: your executor does, by its own rules. Not financial advice.
+
+Every strategy runs on **paper** by default. In **real** mode the same strategy runs the same way: the same entry rules, the same clamp on every size, the same exits, the same monitor and the same run file as paper. The difference: every buy and sell it fills on its own model of the market also goes out, first, as a **LIVE TRADE FIRE** signal (`dexterm-trade-fire/1`) to the executor you chose.
+
+- **Your executor** is a Telegram trading bot you trust, or any script of yours. It holds its own wallet and decides whether to act on a signal.
+- **dexterm** holds no key, signs nothing and builds no transaction. It sends the signal, keeps it in an outbox until it is delivered, and records what your executor says it did.
+- **A bot cannot read another bot's messages**, so the signal also goes over a channel your executor can read: a local webhook, a command, a stream file or MCP. The Telegram message to your own chat is the copy for you.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-what-it-will-not-do.md

@@ -0,0 +1,34 @@
+---
+id: docs-real-mode-what-it-will-not-do
+title: Real mode (LIVE TRADE FIRE signals) › What it will not do
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: What it will not do
+anchor: what-it-will-not-do
+url: https://dexterm.xyz/docs/real-mode#what-it-will-not-do
+tags:
+  - docs
+  - real-mode
+  - will
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+- Hold, import or ask for a key or a seed phrase, sign, or send a transaction.
+- Trade on a replay, or let a chat tap authorise a real trade.
+- Promise a fill. Your executor decides, at its own price, with its own fees.
+- Run more than one real strategy per machine at a time, run one inside `run --all`, or run one under the always-on service (in 0.2.0 real runs in the foreground only).
+- Send any signal, sells included, while no real run is running, or close a position by itself.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode-where-you-see-it.md

@@ -0,0 +1,34 @@
+---
+id: docs-real-mode-where-you-see-it
+title: Real mode (LIVE TRADE FIRE signals) › Where you see it
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+heading: Where you see it
+anchor: where-you-see-it
+url: https://dexterm.xyz/docs/real-mode#where-you-see-it
+tags:
+  - docs
+  - real-mode
+  - where
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+- **The run**: every fill and closed trade row of a real run is tagged `real-signal` and names its nonce; the start line says REAL; receipts become rows; the end has a `real_halted` row.
+- **The `Q` screen's runner view**: the mode, the account, the kill switch, the outbox depth, each channel's health, the unconfirmed positions, the limits in force (with a BUYS PAUSED line when a limit or a silent executor stops new buys) and your executor's health.
+- **Telegram**: every message of a real run carries the LIVE badge. A closed trade is a text line (its numbers are dexterm's model, not your executor's fills), never a PnL card.
+- **The trade ledger**: `dexterm ledger` lists a real run's trades with the mode `real` (`--mode real`), never `paper`. Their numbers are dexterm's model of each trade it signalled; your executor's receipts are the real fills, so there is no PnL card for them.
+- **Shared views**: the spectator stream and saved files keep signals and receipts out.

package/dist/packages/mcp/assets/kb/docs/docs-real-mode.md

@@ -0,0 +1,27 @@
+---
+id: docs-real-mode
+title: Real mode (LIVE TRADE FIRE signals)
+kind: docs
+page: real-mode
+page_title: Real mode (LIVE TRADE FIRE signals)
+url: https://dexterm.xyz/docs/real-mode
+tags:
+  - docs
+  - real-mode
+  - real
+  - mode
+  - live
+  - trade
+  - fire
+  - signals
+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/real-mode.md
+date: 2026-10-16
+---
+
+Run a strategy in real mode and every buy and sell it decides goes to your own executor (a Telegram trading bot of your choice, or any script) as a signed, numbered LIVE TRADE FIRE signal. dexterm still holds no key and signs nothing. Experimental; not financial advice.

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.