dexterm-cli 0.1.3 → 0.1.5

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -0,0 +1,44 @@
+---
+id: docs-getting-started-supported-platforms
+title: Getting started › Supported platforms
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: Supported platforms
+anchor: supported-platforms
+url: https://dexterm.xyz/docs/getting-started#supported-platforms
+tags:
+  - docs
+  - getting-started
+  - supported
+  - platforms
+  - getting
+  - started
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/getting-started.md
+date: 2026-10-16
+---
+
+This table says what each platform has actually been through, not what we expect to work. "Tested" means the typecheck, the full offline test suite and an install smoke (`npm pack`, `npm i -g` of that tarball into an empty prefix with a fresh home, then `dexterm --version` and `dexterm doctor`) have passed there.
+
+| platform | status | what has run on it |
+|---|---|---|
+| Linux x64, Node 22 and 24 | tested | the full suite on every push in CI (Ubuntu), and the same steps in Docker (`node:22-bookworm`, `node:24-bookworm`), including the install smoke |
+| macOS on Intel | tested | the full suite on every change, the install smoke, and a Homebrew install (slow: Homebrew builds Node from source on Intel) |
+| macOS on Apple Silicon | tested in CI (0.1.4) | the full suite on an Apple Silicon runner (`macos-14`) passed on the 0.1.4 release candidate. The manual Homebrew job (tap, trust, install, `brew test`) has not run yet |
+| Windows x64 | experimental, tested in CI (0.1.4) | the `windows-latest` leg runs the full suite and it passed on the 0.1.4 release candidate (a few tests that need POSIX file permissions or Unix-only tools are skipped, and ACL-based file isolation is not verified). Known gaps are listed below |
+| WSL2 | not tested separately | it is Linux, so expect the Linux behaviour |
+
+Known gaps on Windows (none of them affect key safety: dexterm never holds a wallet key on any platform):
+
+- Files dexterm keeps private (tokens, the optional RPC key) are written with POSIX mode `0600`. Windows ignores that mode, so on Windows they are protected only by your user profile's normal permissions.
+- The analyst runs `claude` without a shell, so it can start Claude Code's native installer build (`claude.exe`) but not the `claude.cmd` script an npm install creates. Doctor counts only `claude.exe` as found, so with an npm install it reports the Claude CLI as missing.
+- Voice mode has no Windows speech engine (see voice (https://dexterm.xyz/docs/voice#linux-and-windows)).
+- Opening a token's links and the PnL card's "share to X" do not start a browser on Windows; dexterm shows the URL to open yourself.
+- `doctor` prints its fixes as POSIX shell commands (`mkdir -p`, `chmod`); in PowerShell, do the equivalent by hand.
+- `dexterm kb edit` and `dexterm skill edit` do not open `$EDITOR`; they print the file to edit instead.

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

@@ -0,0 +1,28 @@
+---
+id: docs-getting-started-updating
+title: Getting started › Updating
+kind: docs
+page: getting-started
+page_title: Getting started
+heading: Updating
+anchor: updating
+url: https://dexterm.xyz/docs/getting-started#updating
+tags:
+  - docs
+  - getting-started
+  - updating
+  - getting
+  - started
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/getting-started.md
+date: 2026-10-16
+---
+
+`dexterm update` asks npm and GitHub for the latest release and prints the exact command for how this copy was installed (npm, Homebrew, the release tarball or a git checkout). It never upgrades anything by itself.
+
+A live, interactive run also checks once a day in the background and shows one quiet toast when a newer version exists. The check is two anonymous GET requests with the same fixed headers for everyone (no version, no OS, no ids). Turn it off with `dexterm update --off` (and back on with `--on`), or set `DEXTERM_NO_UPDATE_CHECK=1` or `NO_UPDATE_NOTIFIER=1`. It never runs with `--fixtures`, `--replay`, `CI` or `DEXTERM_OFFLINE`. The trust page (https://dexterm.xyz/trust/#endpoints) lists the hosts.

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

@@ -0,0 +1,27 @@
+---
+id: docs-getting-started
+title: Getting started
+kind: docs
+page: getting-started
+page_title: Getting started
+url: https://dexterm.xyz/docs/getting-started
+tags:
+  - docs
+  - getting-started
+  - getting
+  - started
+confidence: high
+owner: maintainers
+origin: docs-generated
+reviewed_by: generated@2026-10-16
+generated_from: dexterm/site content/docs (task-1420)
+sources:
+  - site/content/docs/getting-started.md
+date: 2026-10-16
+---
+
+Requirements, install, first run and dexterm doctor.
+
+dexterm is a terminal screener for Solana memecoins with a local Claude analyst. It runs on your machine, reads public data with no key and never holds a wallet key. Trading is PAPER by default; any live swap is signed in your own Phantom wallet after you approve it (see paper trading (https://dexterm.xyz/docs/paper-trading)). This page gets you from nothing to the live screener.
+
+> note: Never used a terminal before? Start with the complete beginner guide (https://dexterm.xyz/docs/beginners). It defines every term, shows exactly what to copy on macOS, Linux and Windows, and ends with a ten-minute read-only coin review.

package/dist/packages/mcp/assets/kb/docs/docs-keyboard-global-keys.md

@@ -0,0 +1,26 @@
+---
+id: docs-keyboard-global-keys
+title: Keyboard reference › Global keys
+kind: docs
+page: keyboard
+page_title: Keyboard reference
+heading: Global keys
+anchor: global-keys
+url: https://dexterm.xyz/docs/keyboard#global-keys
+tags:
+  - docs
+  - keyboard
+  - global
+  - keys
+  - reference
+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/keyboard.md
+date: 2026-10-16
+---
+
+(generated from the app: see https://dexterm.xyz/docs/keyboard#global-keys; app-help has the exact keys and commands)

package/dist/packages/mcp/assets/kb/docs/docs-keyboard-keys-handled-by-the-loop.md

@@ -0,0 +1,29 @@
+---
+id: docs-keyboard-keys-handled-by-the-loop
+title: Keyboard reference › Keys handled by the loop
+kind: docs
+page: keyboard
+page_title: Keyboard reference
+heading: Keys handled by the loop
+anchor: keys-handled-by-the-loop
+url: https://dexterm.xyz/docs/keyboard#keys-handled-by-the-loop
+tags:
+  - docs
+  - keyboard
+  - keys
+  - handled
+  - loop
+  - reference
+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/keyboard.md
+date: 2026-10-16
+---
+
+These are not keymap bindings; the interactive loop handles them in context. Each row is verified against the source by `docs:check`.
+
+(generated from the app: see https://dexterm.xyz/docs/keyboard#keys-handled-by-the-loop; app-help has the exact keys and commands)

package/dist/packages/mcp/assets/kb/docs/docs-keyboard-per-screen-keys.md

@@ -0,0 +1,26 @@
+---
+id: docs-keyboard-per-screen-keys
+title: Keyboard reference › Per-screen keys
+kind: docs
+page: keyboard
+page_title: Keyboard reference
+heading: Per-screen keys
+anchor: per-screen-keys
+url: https://dexterm.xyz/docs/keyboard#per-screen-keys
+tags:
+  - docs
+  - keyboard
+  - per-screen
+  - keys
+  - reference
+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/keyboard.md
+date: 2026-10-16
+---
+
+(generated from the app: see https://dexterm.xyz/docs/keyboard#per-screen-keys; app-help has the exact keys and commands)

package/dist/packages/mcp/assets/kb/docs/docs-keyboard-what-shows.md

@@ -0,0 +1,27 @@
+---
+id: docs-keyboard-what-shows
+title: Keyboard reference › What ? shows
+kind: docs
+page: keyboard
+page_title: Keyboard reference
+heading: What ? shows
+anchor: what-shows
+url: https://dexterm.xyz/docs/keyboard#what-shows
+tags:
+  - docs
+  - keyboard
+  - shows
+  - reference
+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/keyboard.md
+date: 2026-10-16
+---
+
+The in-app help card lists exactly the rows below for each screen (global keys shadowed by a screen-specific binding are attributed to the screen):
+
+(generated from the app: see https://dexterm.xyz/docs/keyboard#what-shows; app-help has the exact keys and commands)

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

@@ -0,0 +1,26 @@
+---
+id: docs-keyboard
+title: Keyboard reference
+kind: docs
+page: keyboard
+page_title: Keyboard reference
+url: https://dexterm.xyz/docs/keyboard
+tags:
+  - docs
+  - keyboard
+  - reference
+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/keyboard.md
+date: 2026-10-16
+---
+
+Every key, generated from the app's keymap and the help overlay at build time.
+
+Generated at build time from `packages/tui/src/keymap.ts` (the keymap) and `packages/cli/src/screens/overlay.ts` (the `?` overlay, which adds the keys the interactive loop handles itself). `npm run docs:check` fails if this page and the app disagree.
+
+Conventions: keys are case-sensitive (`g` and `G` differ). A key listed under a screen overrides the global binding on that screen only (on the token screen `1`–`6` are timeframes, not screen switches). While the chat input, the filter line, the sort menu or a PAPER ticket has the keys, printable keys type instead of acting, so `q` or `1` can never quit or navigate out from under a half-typed order.

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

@@ -0,0 +1,53 @@
+---
+id: docs-larp-measured-accuracy
+title: LARP detector › Measured accuracy
+kind: docs
+page: larp
+page_title: LARP detector
+heading: Measured accuracy
+anchor: measured-accuracy
+url: https://dexterm.xyz/docs/larp#measured-accuracy
+tags:
+  - docs
+  - larp
+  - measured
+  - accuracy
+  - 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 part of the LARP check that can be replayed on history is weak, and the model stage cannot be replayed at all. dexterm prints only what it measured, including the weak numbers.**
+
+**Skills backtest (0.1.2).** `dexterm backtest --subject skills` replays the replayable parts of the default analyst skills on recorded history: 1,054 coins from the project's recorder, labelled by a 72 h keyless outcome (bad = rug or dead). Tuning only ever sees the train split; the numbers below are the later, held-out test split of 328 coins, of which 18.6 % went bad.
+
+- **LARP check, links only.** The links-based baseline is a weak signal: MCC 0.039 before tuning, 0.054 after. Its tuned `LARP` grade caught 4 of 14 bad coins, too few to rate. `EARLY_BUT_REAL` coins still went bad 10.3 % of the time, and coins with no website 29.2 %. The skill now treats the baseline as a weak prior and never calls `LARP` from links alone.
+- **Rug check.** The verdict rules improved from MCC 0.043 to 0.159. Liquidity under $5k is the one strong signal (`SPECULATIVE` coins went bad 54.8 % of the time, `WATCH` 14.4 %). Dev percentage, organic score and top-10 share did not predict a worse 72 h outcome and now only lower confidence.
+- **Not measured.** The model stage (fetched pages, RDAP, GitHub) cannot be replayed: a past page cannot be fetched as it was. It is measured going forward with `dexterm backtest --subject larp`, below.
+
+The method, every number and the limits are in the repository at `packages/packs/eval/README.md`. A grade is a risk flag, not a certificate.
+
+Measured 2026-10-12 with `dexterm backtest --subject larp` over this project's labelled history:
+
+| history | outcome labels at 1 h (observed) | LARP verdicts recorded | matched |
+|---|---|---|---|
+| research recorder (task-1287 prototype DB) | 149 (137 flat · 9 fade · 2 runner · 1 dead; 29 unobserved) | 0 | 0 |
+| the app's recorder on the development machine | 0 | 0 | 0 |
+| the same, re-measured later that day after the recorder fix | 401 (361 flat · 18 dead · 13 runner · 5 fade · 4 rug; 1,206 unobserved) | 0 | 0 |
+
+There were no verdicts to score because, before this release, a settled verdict was only kept in memory. From this release on, each settled verdict is written to your local recorder (`verdicts`, pack `larp-check`), so the measurement can grow on your own machine. The app recorder's 0 outcomes had a second cause, fixed the same day: its outcome sweeps and labels never ran in short sessions (see history recorder (https://dexterm.xyz/docs/configuration#history-recorder)). The outcome side now fills in on its own; the verdict side only grows when you run the LARP check on tokens, and no accuracy figure is printed until 50 verdicts match.
+
+**Method.** Run `dexterm backtest --subject larp [--horizon SEC] [--json]` to reproduce it.
+
+- **Join.** Each recorded verdict is joined to the outcome label of the latest recorder snapshot of the same coin, taken at most 10 % of the horizon before the verdict. A later snapshot is never used, and an `unobserved` label is not matched.
+- **Bad outcome.** `rug` or `dead` on keyless data, or `rug` alone when chain-verified.
+- **Scoring.** `LARP` is scored against `REAL_PRODUCT` and `EARLY_BUT_REAL`. `UNVERIFIABLE` is counted separately.
+- **Gate.** Below 50 matched verdicts the command prints counts only. At 50 or more it adds P(bad | LARP), P(bad | real) and P(LARP | bad), each with a 95 % Wilson interval.
+
+> warn: even when it can be computed, this number is **agreement with a bad price outcome**, not a measure of whether a product is real. Outcome labels are the only ground truth dexterm records. A real product can rug, and a LARP can run.

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

@@ -0,0 +1,26 @@
+---
+id: docs-larp-open-link-keys
+title: LARP detector › Open-link keys
+kind: docs
+page: larp
+page_title: LARP detector
+heading: Open-link keys
+anchor: open-link-keys
+url: https://dexterm.xyz/docs/larp#open-link-keys
+tags:
+  - docs
+  - larp
+  - open-link
+  - keys
+  - 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
+---
+
+`W`, `X` and `T` open the advertised website, X and Telegram in your browser; `L` lists every advertised link (including secondary socials from DexScreener) in a menu. The URL is drawn on screen before anything launches; only `http` and `https` links are ever passed to the opener (`open` on macOS, `xdg-open` on Linux, as a single argument, no shell). The footer shows these keys only when the token actually advertises links.

package/dist/packages/mcp/assets/kb/docs/docs-larp-paste-a-coin-on-the-web.md

@@ -0,0 +1,35 @@
+---
+id: docs-larp-paste-a-coin-on-the-web
+title: LARP detector › Paste a coin on the web
+kind: docs
+page: larp
+page_title: LARP detector
+heading: Paste a coin on the web
+anchor: paste-a-coin-on-the-web
+url: https://dexterm.xyz/docs/larp#paste-a-coin-on-the-web
+tags:
+  - docs
+  - larp
+  - paste
+  - coin
+  - web
+  - 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
+---
+
+A no-install version is in preview at the preview checker (https://dexterm-larp-preview.dexterm-site.workers.dev/check/), not deployed to dexterm.xyz. Paste a Solana mint or a DexScreener / pump.fun / Solscan link and get the grade in your browser, read-only, no wallet. It runs on a Cloudflare Worker and reuses the app's tuned link-shape grade (`larp-links-v1`) and the same prompt firewall, so a hostile coin name or symbol is stripped and shown as inert text, never obeyed.
+
+What the web checker shows, each datum with its source and the age of the reading: the **LARP grade** from the coin's advertised link shape (`LARP` / `REAL?` / `UNKNOWN`), **top-10 holder concentration** and **holder count** (Jupiter), and **liquidity** in USD (DexScreener). It never shows a price, a market cap or a buy/sell call. A **shareable PNG card** carries the grade, those facts, the heuristic label and a dexterm.xyz link.
+
+The preview defaults to the **keyless** tier. The full in-app LARP check above — fetching the website (SSRF-safe), the RDAP domain lookup and the GitHub read, graded by the analyst — is not part of the web checker. The bundle / sniper checkbox runs the app's wallet-intel rules and Helius history adapter as an optional second step, only when a dedicated site key and real Turnstile configuration are present. The visible preview test mode disables paid deep scans. Missing credentials refuse scans or disable the deep step; there is no silent test-secret fallback.
+
+The deep step samples the top 20 accounts, up to seven funding histories and the first 100 launch transactions. Complete immutable launch windows and funding facts stay in durable storage without expiration; incomplete launch windows are fetched again. Market results expire after 45 seconds. Every scan, including a cache hit, is rate-limited per IP and globally. A serialized daily credit budget reserves 84 credits before deep RPCs and refunds only counted unused credits. Synthetic replay measures 84 cold / 4 with facts cached; these are call-based estimates, not independently measured provider billing. Real deep-scan latency, billing and Worker CPU are still unverified pending dedicated credentials. Refusals display "busy, try again"; a deep-budget refusal keeps the keyless grade with an explicit note. No trackers or analytics; the pasted input is not logged.
+
+> warn: the web grade is the links-only baseline, a weak signal measured on a held-out set (see measured accuracy (https://dexterm.xyz/docs/larp#measured-accuracy) above). It is a risk flag, not a certificate, and not financial advice.