dexterm-cli 0.1.3 → 0.1.5

package/dist/packages/mcp/assets/kb/docs/docs-larp-the-verdict.md

@@ -0,0 +1,29 @@
+---
+id: docs-larp-the-verdict
+title: LARP detector › The verdict
+kind: docs
+page: larp
+page_title: LARP detector
+heading: The verdict
+anchor: the-verdict
+url: https://dexterm.xyz/docs/larp#the-verdict
+tags:
+  - docs
+  - larp
+  - verdict
+  - detector
+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/larp.md
+date: 2026-10-16
+---
+
+The `larp-check` skill returns a structured assessment: `REAL_PRODUCT` · `EARLY_BUT_REAL` · `LARP` · `UNVERIFIABLE` · `AMBIGUOUS`, with a confidence, a status per claim (supported, contradicted, unverifiable), `missing_data`, the facts and flags it used, `injection_detected` and a short summary. It is separate from the dossier's risk verdict and does not replace it.
+
+Once computed, a badge appears in the screener's FLAGS column and in the token screen's title strip for that mint only: **LARP** (red), **REAL** (green), **REAL?** (mixed), **UNKNOWN** for unverifiable or ambiguous. Nothing shows before you vet a coin. A `LARP` verdict also vetoes an AI scan (https://dexterm.xyz/docs/scan) lock on that coin.
+
+> warn: a LARP verdict is a risk flag, not a certificate. Public HTML cannot prove a working product, a team's identity or who owns an account; domain age, a clean script scan and a GitHub with commits are evidence, not proof, and a real product can still go to zero.

package/dist/packages/mcp/assets/kb/docs/docs-larp-timestamped-follow-up-drafts.md

@@ -0,0 +1,35 @@
+---
+id: docs-larp-timestamped-follow-up-drafts
+title: LARP detector › Timestamped follow-up drafts
+kind: docs
+page: larp
+page_title: LARP detector
+heading: Timestamped follow-up drafts
+anchor: timestamped-follow-up-drafts
+url: https://dexterm.xyz/docs/larp#timestamped-follow-up-drafts
+tags:
+  - docs
+  - larp
+  - timestamped
+  - follow-up
+  - drafts
+  - detector
+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/larp.md
+date: 2026-10-16
+---
+
+`dexterm larp-detected --out DIR` is a local, offline review pipeline over your recorder history. The cron-ready equivalent is `node scripts/larp-detected.mjs --out DIR`; dexterm does not install a schedule. It does not connect to X, open a composer, upload, schedule or post.
+
+For each coin, the command scores only the point-in-time recorder row with the named `H1-v0.1` heuristic, then joins it only to a later recorder outcome at the chosen horizon (72 hours by default). It keeps one flag per short-mint identifier. Every PNG and text report carries the original UTC timestamp, model label, source, evidence age, outcome tier and follow-up horizon. The batch line states both sides of the same dataset: how many flagged coins met the follow-up condition and how many did not. Below 50 unique flags, the sample is thin and the command writes no drafts.
+
+By default it writes at most three Markdown drafts and three cards. Coin names, tickers and full addresses are omitted; the identifier is first four plus last four mint characters. The copy says “recorder label” rather than asserting what a project or person did. `node scripts/scan-larp-detected.mjs DIR` scans every draft and report for full addresses, handles, cashtags, identity/path leaks, trading language, accusations and market claims.
+
+`dexterm larp-detected --live MINT --out DIR` performs one read-only, keyless market lookup and writes a **graded now** card. It explicitly says there is no later outcome yet. This path does not touch a wallet, trading, the signer, arming, voice or agents.
+
+> warn: H1 is a heuristic model output and a risk flag, not a certificate. The files are drafts for human review. Nothing is posted automatically.

package/dist/packages/mcp/assets/kb/docs/docs-larp-what-it-looks-at.md

@@ -0,0 +1,33 @@
+---
+id: docs-larp-what-it-looks-at
+title: LARP detector › What it looks at
+kind: docs
+page: larp
+page_title: LARP detector
+heading: What it looks at
+anchor: what-it-looks-at
+url: https://dexterm.xyz/docs/larp#what-it-looks-at
+tags:
+  - docs
+  - larp
+  - looks
+  - detector
+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/larp.md
+date: 2026-10-16
+---
+
+| evidence | source | what counts |
+|---|---|---|
+| the advertised links | DexScreener info + Jupiter metadata (`get_links`), de-duplicated and classified; a note when the two sources disagree | a mismatch across sources is a flag in itself |
+| the website | one SSRF-safe, read-only GET (`fetch_page`): no JavaScript, no cookies, no downloads, 512 KiB and 8 s caps, `robots.txt` honoured on every redirect hop, private and loopback addresses refused, DNS re-validated at connect time | site-builder or default-page signals, a live app or demo, docs, wallet-connect patterns, drainer and approval signatures in scripts, external script hosts, whether the symbol and name appear, team-claim and stock-placeholder text |
+| the domain | RDAP lookup of the exact advertised domain (`check_domain`) | registration age, registrar, registrant privacy. A days-old domain behind privacy is a mild signal, not proof. Novelty TLDs without an RDAP server come back as unverifiable. |
+| GitHub | the keyless GitHub API (`check_github`) for a `github.com/owner/repo` link | created and last-push dates, stars, open issues, archived or fork, up to five real commit hashes with dates |
+| pump.fun metadata | the metadata URI GoPlus reports, through the same safe fetch | the advertised description and links, when they exist |
+
+X is usually login-walled keyless, so account age and follower counts are reported as unverifiable rather than guessed. Every fetched string reaches the model through the prompt firewall: normalised, control and bidi characters stripped, URLs and addresses masked, wrapped as untrusted data, tags stripped so a planted closing tag cannot break out.

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

@@ -0,0 +1,24 @@
+---
+id: docs-larp
+title: LARP detector
+kind: docs
+page: larp
+page_title: LARP detector
+url: https://dexterm.xyz/docs/larp
+tags:
+  - docs
+  - larp
+  - detector
+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/larp.md
+date: 2026-10-16
+---
+
+Vet the product behind a coin: its website, domain registration and GitHub, read-only, only when you ask.
+
+A memecoin's advertised website, X and Telegram are claims. The LARP detector fetches what it can, reads it mechanically, and lets the analyst grade the claims against what it found. It runs only when you press `V` on a live token; nothing is fetched automatically.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-degraded-states-you-will-see.md

@@ -0,0 +1,36 @@
+---
+id: docs-login-with-x-degraded-states-you-will-see
+title: Login with X › Degraded states you will see
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: Degraded states you will see
+anchor: degraded-states-you-will-see
+url: https://dexterm.xyz/docs/login-with-x#degraded-states-you-will-see
+tags:
+  - docs
+  - login-with-x
+  - degraded
+  - states
+  - will
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+| header | meaning | what happens |
+|---|---|---|
+| `x-stream ○ logged out` | no login | keyless venues, news and on-chain rows only |
+| `x-stream ●4s @you` | reading | the age is the last successful read |
+| `x-stream ◐ rate limited 5m` | X answered 429 or the window is exhausted | reads resume after X's reset time |
+| `x-stream ◐ daily budget 3h` | your dexterm budget is spent | reads resume at the next UTC day |
+| `x-stream ◐ app tier (no search)` | the app is on the Free tier | identity only; upgrade the app in the X console |
+| `x-stream ◐ error` | transport or 5xx | retried with backoff, up to 10 minutes |
+
+Nothing is ever shown as fresh when it is not, and nothing is invented to fill a gap.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-free-vs-paid-x-api-tiers-your-bill-your-limits.md

@@ -0,0 +1,37 @@
+---
+id: docs-login-with-x-free-vs-paid-x-api-tiers-your-bill-your-limits
+title: Login with X › Free vs paid X API tiers (your bill, your limits)
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: Free vs paid X API tiers (your bill, your limits)
+anchor: free-vs-paid-x-api-tiers-your-bill-your-limits
+url: https://dexterm.xyz/docs/login-with-x#free-vs-paid-x-api-tiers-your-bill-your-limits
+tags:
+  - docs
+  - login-with-x
+  - free
+  - paid
+  - api
+  - tiers
+  - bill
+  - limits
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+Login with X gives dexterm **your** per-user rate windows and compliant user-authorized access. It does **not** move cost anywhere: X's pay-per-use pricing bills the developer account that owns the app, and with this design that account is yours. Facts as published by X (check the console; they change):
+
+| tier | what it means for dexterm |
+|---|---|
+| **Free** | login and identity work (`/2/users/me`), but **search and list timelines are not included**: the app's tier answers `403 client-not-enrolled`, dexterm shows `x-stream ◐ app tier (no search)` and reads nothing. KOL list *import* (`owned_lists`, `members`) is also tier-gated; expect it to fail on Free. |
+| **Pay-per-use / Basic and up** | search/recent (300 requests per 15 minutes per user, last 7 days) and list timelines (900 per 15 minutes) work. X bills about **$0.005 per post read** and **$0.01 per user read**, deduplicated per UTC day. |
+
+dexterm keeps its own estimate and a hard stop: the SOURCES panel (`s` on the trending board) shows `@handle · 12/300 search · $0.12 of $10 today`. The default daily budget is **$10** (`DEXTERM_X_DAILY_USD=5` lowers it; `0` means "never read X"); when it is reached the header says `x-stream ◐ daily budget` and reads resume at the next UTC day. The estimate uses X's list prices and counts a post only the first time its id is seen in a day; the X console is the actual bill, so **set a spending limit there too**. At the design cadence a watched coin costs roughly $6 a day and KOL list polling roughly $7 a day on Basic; the 15-minute cache, `since_id` and the 24-hour dedupe table are what keep it there.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-kol-lists-and-the-per-handle-filter.md

@@ -0,0 +1,28 @@
+---
+id: docs-login-with-x-kol-lists-and-the-per-handle-filter
+title: Login with X › KOL lists and the per-handle filter
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: KOL lists and the per-handle filter
+anchor: kol-lists-and-the-per-handle-filter
+url: https://dexterm.xyz/docs/login-with-x#kol-lists-and-the-per-handle-filter
+tags:
+  - docs
+  - login-with-x
+  - kol
+  - lists
+  - per-handle
+  - filter
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+`K` opens your lists. `X` there (or `dexterm kol import-x`) imports the lists your X account **owns** as `X LIST` entries: handles only, never posts, and they count as tier A for credibility like your own manual lists. `o` on a handle narrows the trending board and the SOCIAL panel to that handle's posts (press `o` again, or `f`, to clear). Muting a handle (`m`) drops its posts before they are stored.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-tests.md

@@ -0,0 +1,25 @@
+---
+id: docs-login-with-x-tests
+title: Login with X › Tests
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: Tests
+anchor: tests
+url: https://dexterm.xyz/docs/login-with-x#tests
+tags:
+  - docs
+  - login-with-x
+  - tests
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+The whole flow runs in the test suite against a **mock X server on 127.0.0.1**: PKCE and state checks, single-use 30-second codes, refresh rotation, revoke, 401/429/403 and budget stops, list import, and the firewall on an injection tweet. No test ever contacts x.com, and the default suite blocks `fetch` entirely.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-what-is-read-and-when.md

@@ -0,0 +1,35 @@
+---
+id: docs-login-with-x-what-is-read-and-when
+title: Login with X › What is read, and when
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: What is read, and when
+anchor: what-is-read-and-when
+url: https://dexterm.xyz/docs/login-with-x#what-is-read-and-when
+tags:
+  - docs
+  - login-with-x
+  - read
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+| what | endpoint (user context) | when | cached |
+|---|---|---|---|
+| posts about the open coin | `GET /2/tweets/search/recent` with `$SYMBOL OR <mint>` (`-is:retweet -is:reply`) | every 60 s while the token screen is open, only newer posts after the first page | 15 min per query |
+| your own X lists as KOL feeds | `GET /2/lists/:id/tweets` | every 5 min per enabled list | 15 min |
+| manual KOL lists and packs | `GET /2/tweets/search/recent` with `from:` handles, 20 per query | every 5 min | 15 min |
+| importing your lists | `GET /2/users/:id/owned_lists` + `GET /2/lists/:id/members` | only when you press `X` on the KOL screen or run `dexterm kol import-x` | – |
+| who you are | `GET /2/users/me` | once at login | – |
+
+Never: a filtered stream (economically unbounded), cashtag firehoses, search for every coin on the board, x.com pages, third-party mirrors. `⏎` on a post opens its URL in your browser; dexterm itself never fetches it.
+
+Every response goes through the rate limiter (one bucket for X, and every `x-rate-limit-*` header updates a per-endpoint window) and the health registry; a `429` pauses reads until X's reset time and the header shows `x-stream ◐ rate limited 5m`. Posts then flow through the social layer exactly like news and on-chain rows: near-duplicates collapse, account bursts are marked spam, cashtag squats are hidden, instruction-like posts are withheld from the model and flagged `INJ` for you.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-what-you-set-up-once.md

@@ -0,0 +1,40 @@
+---
+id: docs-login-with-x-what-you-set-up-once
+title: Login with X › What you set up, once
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: What you set up, once
+anchor: what-you-set-up-once
+url: https://dexterm.xyz/docs/login-with-x#what-you-set-up-once
+tags:
+  - docs
+  - login-with-x
+  - set
+  - once
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+1. **An X developer account** at developer.x.com (https://developer.x.com) (log in with the X account you want to read as).
+2. **A Project with an App** of type **Native App** (a *public* client: PKCE only, no client secret ever exists, so nothing secret ships with dexterm).
+3. In the app's **User authentication settings**: OAuth 2.0 on, type *Native App*, callback URL **exactly** `http://127.0.0.1:41287/callback` (X requires `127.0.0.1`, not `localhost`, and an exact match), any website URL, and a name/description for the consent screen.
+4. Copy the app's **Client ID** and store it (prompted on your terminal; never on the command line):
+
+```sh
+$ dexterm x set-client-id       # paste the Client ID when prompted
+$ dexterm x login               # opens your browser on x.com; approve; the tab says "linked"
+$ dexterm x status              # @handle, scopes, token age, file modes
+$ dexterm x logout              # revokes both tokens at X and deletes the local record
+```
+
+`dexterm doctor` has a **Login with X** line that tells you which of these is missing.
+
+Scopes requested: `tweet.read users.read list.read offline.access`. Nothing with `write` or `dm` is ever requested, and the app refuses to build an authorize URL with such a scope.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x-where-the-tokens-live.md

@@ -0,0 +1,27 @@
+---
+id: docs-login-with-x-where-the-tokens-live
+title: Login with X › Where the tokens live
+kind: docs
+page: login-with-x
+page_title: Login with X
+heading: Where the tokens live
+anchor: where-the-tokens-live
+url: https://dexterm.xyz/docs/login-with-x#where-the-tokens-live
+tags:
+  - docs
+  - login-with-x
+  - where
+  - tokens
+  - live
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+`~/.dexterm/x/tokens.json` (mode `600`, directory `700`; `DEXTERM_HOME` moves it) next to `client-id`. The access token lasts two hours and is refreshed with the refresh token when needed; X may rotate the refresh token, so the record is rewritten. Tokens are never printed, never written to any log or recording, never put on a command line, and never part of what the analyst sees (the analyst gets firewalled post text inside `<untrusted>` blocks, nothing else). If X answers `401`, the header says `login revoked or expired at X · dexterm x login` and nothing is read until you log in again. You can also revoke at `x.com/settings/connected_apps`.

package/dist/packages/mcp/assets/kb/docs/docs-login-with-x.md

@@ -0,0 +1,26 @@
+---
+id: docs-login-with-x
+title: Login with X
+kind: docs
+page: login-with-x
+page_title: Login with X
+url: https://dexterm.xyz/docs/login-with-x
+tags:
+  - docs
+  - login-with-x
+  - login
+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/login-with-x.md
+date: 2026-10-16
+---
+
+Read X posts in the SOCIAL panel and on the trending board with your own X app and your own login; what to set up, what the free and paid API tiers allow, and what dexterm never does.
+
+dexterm can read X (Twitter) posts about the open coin and from the people you follow as KOLs. It does this **only through your own X developer app and your own X login** (OAuth 2.0 with PKCE, user context). There is no shared key, no dexterm account in the loop, no scraping, and dexterm never posts, likes, follows or reads DMs. Every tweet passes the same prompt firewall (https://dexterm.xyz/docs/analyst) as every other untrusted text before it is stored, shown or summarised.
+
+Without a login nothing breaks: the trending board runs on the keyless venues, the SOCIAL panel shows on-chain rows and news, and the header says `x-stream ○ logged out`.

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

@@ -0,0 +1,42 @@
+---
+id: docs-paper-trading-a-live-ticket
+title: Paper trading, live trading and the safety model › Live trading (devnet first) › A LIVE ticket
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: A LIVE ticket
+anchor: a-live-ticket
+url: https://dexterm.xyz/docs/paper-trading#a-live-ticket
+tags:
+  - docs
+  - paper-trading
+  - live
+  - ticket
+  - trading
+  - devnet
+  - first
+  - paper
+  - 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
+---
+
+`L` on a ticket flips it LIVE when a wallet is linked and the signer is alive (otherwise the ticket says why and stays PAPER). The header shows `◉ LIVE · DEVNET`, or `⚠ LIVE · MAINNET — REAL FUNDS` in red with the caps. `⏎` asks the signer for a **PLAN**:
+
+1. **Quote** from Jupiter, bound to your order: the input and output mints, the mode and the exact input amount must match or the plan is refused (`quote-mismatch`).
+2. **Build** the unsigned transaction; **decode** it with dexterm's own wire decoder (legacy and v0, lookup tables included).
+3. **Policy**: every top-level instruction must fit the shape of a Jupiter swap: exactly one route-family instruction (by Anchor discriminator), token operations limited to SyncNative, InitializeAccount for your wallet and CloseAccount back to your wallet, a System transfer only into your own wrapped-SOL account that is synced and closed in the same transaction, associated-token creation only for your wallet. Transfers, burns, approvals, authority changes, direct DEX calls and unknown programs are refused by name.
+4. **Binding**: the route's `in_amount`, `quoted_out_amount` and `slippage_bps` must equal the quote; the platform fee must be zero with the "none" sentinel account (dexterm takes no fee); the transfer authority must be your wallet; the source and destination must be your own associated token accounts for the two mints.
+5. **Simulation** against the RPC, with your wallet **and your token accounts** in the requested post-state: the SOL leaving your wallet must not exceed the plan plus a fee allowance nor the SOL cap; a buy may not decrease any of your token balances; a sell may spend only the order mint's account and only up to the order amount (an address a lookup table loads counts as part of the transaction). If the balances cannot be read, the plan is refused rather than guessed.
+6. **Price**: the SOL leg times the signer's own SOL/USD, never Jupiter's `swapUsdValue`; on mainnet an unknown or $0 price refuses.
+
+The PLAN screen lists what will be signed instruction by instruction, what you pay and receive, the minimum received, the impact as a percent, the fee including any priority fee, the route, the simulation result, the SOL/USD price and its sources, the policy verdict and the caps verdict ("will be refused: …" when it would be).
+
+`Y` (or `⏎`) is the keypress gate. The signer re-checks the caps, **reserves** the USD against the daily ledger (atomically, so two trades cannot both pass), opens the sign page, and hands the bytes to Phantom. What comes back must be the **same message** with a valid Ed25519 signature by the linked wallet; the only tolerated difference is a Lighthouse assertion tail appended by Phantom. The signed bytes are decoded, policy-checked and bound again, **re-simulated** with fresh token balances, and only then submitted. A transport error after the send keeps the charge and shows the signature with "do not resend"; a definite rejection before broadcast refunds. Plans are single-use and expire after 90 s.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-before-you-press-size-vs-caps.md

@@ -0,0 +1,34 @@
+---
+id: docs-paper-trading-before-you-press-size-vs-caps
+title: Paper trading, live trading and the safety model › Live trading (devnet first) › Before you press ⏎: size vs caps
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: Before you press ⏎: size vs caps
+anchor: before-you-press-size-vs-caps
+url: https://dexterm.xyz/docs/paper-trading#before-you-press-size-vs-caps
+tags:
+  - docs
+  - paper-trading
+  - before
+  - press
+  - size
+  - caps
+  - live
+  - trading
+  - devnet
+  - first
+  - paper
+  - 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
+---
+
+Since 2026-10-12 (`task-1368`) a LIVE buy ticket prices your size **at the signer's own SOL/USD** (the price its caps are enforced with) while you type, and shows it against the per-trade cap and what is left of the daily cap: `0.04 SOL ≈ $4.32 at SOL $108 · cap $5/trade · $20 left of $20 today`. When the size is over, the line turns red before you build anything: `0.05 SOL = $5.40 > $5 cap: use ≤ 0.043 SOL (f fits it; fees + token-account rent counted)`. `f` sets that size. The fit is the cap divided by the price minus 0.0025 SOL, rounded down to three decimals: the signer prices the *larger* of your planned SOL leg and the SOL the simulation actually moves out of the wallet, and a first buy of a token adds a token-account rent (0.00204 SOL) plus the fees on top of the size, so a size that is exactly the cap in USD would be refused at precheck. The daily remainder binds when it is smaller than the per-trade cap; with no SOL/USD from the signer the line says `$?` and the signer will refuse an unpriced trade on mainnet. The ticket's verdict is a preview; the signer still decides at precheck and again at confirm.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-devnet-signer-mainnet-token.md

@@ -0,0 +1,35 @@
+---
+id: docs-paper-trading-devnet-signer-mainnet-token
+title: Paper trading, live trading and the safety model › Live trading (devnet first) › Devnet signer, mainnet token
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: Devnet signer, mainnet token
+anchor: devnet-signer-mainnet-token
+url: https://dexterm.xyz/docs/paper-trading#devnet-signer-mainnet-token
+tags:
+  - docs
+  - paper-trading
+  - devnet
+  - signer
+  - mainnet
+  - token
+  - live
+  - trading
+  - first
+  - paper
+  - 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
+---
+
+Jupiter has no devnet. A Jupiter route is built on **mainnet state** (its accounts, address-lookup tables and blockhash), so a devnet signer can never simulate or fill a swap of a real token: the simulation fails with an RPC error such as `invalid transaction: Transaction loads an address table account that doesn't exist`, and the caps refuse it (`simulation-failed`). The ticket now says this **before** you press ⏎ on any token while the signer is on devnet (`DEVNET cannot fill mainnet tokens: paper trade (L) or restart with --mainnet (real funds, caps $5/$20)`), and when a simulation does fail the PLAN shows the **full** RPC error over several lines (it used to be cut to `invalid transaction: Tr…`) with a plain-English hint when the pattern is this mismatch; the signer also writes the full error to the app log. Your two options are exactly those: paper trade the token with `L`, or run `dexterm --mainnet` with a funded mainnet wallet inside the caps (next section). The devnet signing path itself is proven by the probe, which is built for devnet on purpose.
+
+On **devnet** a Jupiter swap is refused at the caps step (`mainnet-not-enabled`): Jupiter has no devnet, so a real swap is a mainnet action. The signing path is proven on devnet instead by **`dexterm wallet probe`** (or `/wallet probe`): a transaction dexterm builds itself that wraps 0.001 SOL into your own wrapped-SOL account and closes it back, fees only, through exactly the same keypress → Phantom → verify → re-simulate → submit → confirm path, with its own policy (no route allowed) and never on mainnet.

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

@@ -0,0 +1,33 @@
+---
+id: docs-paper-trading-jupiter-rate-limits
+title: Paper trading, live trading and the safety model › Live trading (devnet first) › Jupiter rate limits
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: Jupiter rate limits
+anchor: jupiter-rate-limits
+url: https://dexterm.xyz/docs/paper-trading#jupiter-rate-limits
+tags:
+  - docs
+  - paper-trading
+  - jupiter
+  - rate
+  - limits
+  - live
+  - trading
+  - devnet
+  - first
+  - paper
+  - 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
+---
+
+Jupiter's keyless API allows about five requests per ten seconds per IP, answers `429` with no `Retry-After` but with a reset time, and its alternate host (`lite-api.jup.ag`) can answer `503` (both recorded on 2026-10-12 and kept as fixtures). A limit used to kill the plan (`build-failed: HTTP 429`) and park the preview on "fetching…" for half a minute. Now every keyless Jupiter call on the trade path is retried on the **other host** after the server's own reset (or `Retry-After`, with a jittered backoff), at most three attempts inside ten seconds; a `5xx` or a dropped connection alternates the same way; the LIVE preview, the signer's re-quote and the build go through the signer's **one** rate limiter and a quote fetched for the preview is reused by the build a moment later (two calls, not three). When the budget is spent, or the data layer's health gate is cooling the source down after two 429s in a minute, the ticket **keeps the plan**: it shows `Jupiter is rate limiting this IP (429 from api.jup.ag), retrying in Ns`, retries by itself when the wait ends, `r` retries now and `esc` cancels. Nothing is built or signed while it waits.

package/dist/packages/mcp/assets/kb/docs/docs-paper-trading-letting-an-agent-paper-trade-experimental.md

@@ -0,0 +1,32 @@
+---
+id: docs-paper-trading-letting-an-agent-paper-trade-experimental
+title: Paper trading, live trading and the safety model › Letting an agent paper trade (experimental)
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: Letting an agent paper trade (experimental)
+anchor: letting-an-agent-paper-trade-experimental
+url: https://dexterm.xyz/docs/paper-trading#letting-an-agent-paper-trade-experimental
+tags:
+  - docs
+  - paper-trading
+  - letting
+  - agent
+  - paper
+  - trade
+  - experimental
+  - trading
+  - live
+  - 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
+---
+
+If you want to, you can let an agent connected over `dexterm mcp` run the whole PAPER loop (open, size, confirm and close) inside a **trading mandate** you armed, by starting `dexterm --spectate-mcp --agent-paper <mandate-id>`. It is paper only. The agent can never sign, send a real transaction, touch keys or raise a cap, a size over your caps is refused, and you can pause, take over or stop it at any time. See Agent paper trading (https://dexterm.xyz/docs/agents#agent-paper-trading). It is experimental and off by default, and simulated figures are not a result.

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

@@ -0,0 +1,32 @@
+---
+id: docs-paper-trading-link-a-wallet
+title: Paper trading, live trading and the safety model › Live trading (devnet first) › Link a wallet
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: Link a wallet
+anchor: link-a-wallet
+url: https://dexterm.xyz/docs/paper-trading#link-a-wallet
+tags:
+  - docs
+  - paper-trading
+  - link
+  - wallet
+  - live
+  - trading
+  - devnet
+  - first
+  - paper
+  - 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 wallet link` (or `/wallet link` typed on the screener's `/` line or in the chat box) starts a one-shot server on `127.0.0.1:41291` (a fixed loopback port since `task-1368`; a random one only if it is busy, and the page then says so) with a single-use token, and opens your browser to it. The page asks Phantom to **connect** and **sign a message** (a dexterm nonce): no transaction, no approval of funds. The port is fixed because Phantom remembers which **origins** it trusts: link and every later sign page share `http://127.0.0.1:41291`, so after the first Connect prompt Phantom connects silently. dexterm verifies the Ed25519 proof and stores **only your public key** in `~/.dexterm/wallet-link.json`. `dexterm wallet status`, `unlink`, `/wallet`, `/wallet unlink` show or remove it. No private key, seed or password ever reaches dexterm; it has no code that could hold one.

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

@@ -0,0 +1,30 @@
+---
+id: docs-paper-trading-live-trading-devnet-first
+title: Paper trading, live trading and the safety model › Live trading (devnet first)
+kind: docs
+page: paper-trading
+page_title: Paper trading, live trading and the safety model
+heading: Live trading (devnet first)
+anchor: live-trading-devnet-first
+url: https://dexterm.xyz/docs/paper-trading#live-trading-devnet-first
+tags:
+  - docs
+  - paper-trading
+  - live
+  - trading
+  - devnet
+  - first
+  - paper
+  - 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
+---
+
+**Status: in progress.** The code is on main and verified against fakes, a hand-built attack suite and a real recorded Jupiter transaction; the one thing not yet observed is a transaction signed by the real Phantom extension on devnet, which the maintainers' probe run will settle. Nothing here has touched mainnet.