dsh-ssh-tui 0.7.3 → 0.8.0

package/README.en.md

@@ -6,7 +6,9 @@
 [![dshfind](https://dshfind.com/api/badge/cyjyyd/dsh-ssh-tui)](https://dshfind.com/en/plugins/cyjyyd/dsh-ssh-tui?ref=badge)
 
 A DeepSeek Harness terminal for jump hosts, headless servers, and high-latency
-SSH. Plain ANSI and incremental redraws. No browser required.
+SSH. Plain ANSI and incremental redraws. No browser required. **When the SSH
+session drops mid-turn, the Host keeps the turn; reconnecting with the same
+command attaches back to it, so the session is not lost.**
 
 中文部署指南：[README.md](README.md)
 
@@ -14,6 +16,20 @@ If you mostly work over SSH — a jump host, a test box, a keyboard-only
 session — start here. A local desktop terminal with themes and layout
 you already like can stay as it is.
 
+How this differs from what already exists:
+
+- **Official headless**: the same task prints only its last reply to stdout; the
+  rest stays in the session log.
+- **Official `dsh-ssh` (from 0.1.6)**: the Harness runs locally and files and
+  processes run remotely, which needs a helper installed ahead of time. Use this
+  plugin when you are already SSH'd onto the machine. The two stack; neither
+  replaces the other.
+- **Other terminal skins** (`dsh-TUI` and the like): a good-looking local
+  terminal, competing on themes and layout. This plugin competes on incremental
+  redraws over a slow link, a Host that survives the drop, and a plain line mode.
+
+How to get back in after a drop is under [After an SSH drop](#after-an-ssh-drop).
+
 A SuperGrok / X Premium subscription goes through the standalone plugin
 [dsh-llm-xai-oauth](https://github.com/cyjyyd/dsh-llm-xai-oauth) (headless, web, or this TUI). It reuses a local grok-bridge token; no xAI API key.
 
@@ -31,6 +47,8 @@ dsh --profile tui
 Current `dsh` requires `--profile` (`dsh plugin add …` errors without it).
 Swap `tui` for another profile name.
 
+**On the 0.2.0-rc host line?** 0.8.0 is the release that supports it (older versions are refused by the launcher's version check), but it is published under `next` for now — `latest` is still 0.7.4 until 2026-10-01. Until then install with `dsh plugin --profile tui add dsh-ssh-tui@next`; on the 0.1.7-rc line `@latest` (0.7.4) is enough, and moving to 0.8.0 later costs nothing. **0.1.5 and older hosts are no longer supported as of 0.8.0.**
+
 **Updates must use `@latest`.** `dsh plugin` forwards the rest of the line to
 pnpm in the profile directory. A bare `add dsh-ssh-tui` keeps the version
 already pinned in `pnpm-lock.yaml` (often 0.3.7). Do not put `--profile`
@@ -69,8 +87,12 @@ Reproducible, no model in the loop: `npm run screenshots:slow` writes
 `docs/screenshots/slow-link.json`. This capture is 14 paints, about
 **18.0 KB**, **8.8 s** at 2 kB/s. Byte ledger for this event sequence.
 
-0.7 highlights: drag-select any part of a model reply to copy it (OSC 52 into your local
-clipboard; a tool card still expands on click) · the footer is one priority-ordered chip
+0.7 highlights: drag-select any part of a model reply to copy it (hold the button, or Shift;
+OSC 52 into your local clipboard; a tool card still expands on click; an SSH session copies
+into the local terminal and no longer warns that it cannot) · a reply is a selectable card too:
+one `↑` on an empty input lands on the newest reply-or-card (marked `▶`, in screen order;
+`Alt+4` selects the latest reply), `/copy` then takes that one as written rather than the
+wrapped screen text, and `Enter` opens it full-screen · the footer is one priority-ordered chip
 strip, and `⚠` opens `/doctor` · the quota bar is on screen from the first frame and names
 its window (`5Hr`/`1Wk`/`1Mo`, smallest window by default, `?%` with a 15-second retry until
 a reading arrives) · `/mode` groups presets and filters with `/` · the compact view names
@@ -82,8 +104,10 @@ pins the palette (truecolor / 256 / 8 / none).
 ## Requirements
 
 - Node.js >= 22.19
-- `@deepseek-ai/dsh` CLI: `npm i -g @deepseek-ai/dsh` (CI covers `0.1.5-rc.1` / `0.1.5-rc.3` / `0.1.7-rc.1`: `0.1.5-rc.1` runs typecheck and the unit suite, the other two add the real-PTY probes. `0.1.5-alpha.1` / `0.1.5-alpha.2` / `0.1.3-alpha.2` share the same handle API + `agent/assistant-stream` shims as the 0.1.5-rc line. **`0.1.2-rc` and older are no longer supported** — if the install is refused, upgrade to `0.1.5-rc` or `0.1.7-rc` first. `0.1.3-alpha.1` exists only as a GitHub tag and was never published to npm)
+- `@deepseek-ai/dsh` CLI: `npm i -g @deepseek-ai/dsh` (this repo develops on `0.1.7-rc.1`; CI covers `0.1.5-rc.1` / `0.1.5-rc.3` / `0.1.7-rc.1` / `0.1.7-rc.2`: `0.1.5-rc.1` runs typecheck and the unit suite, the other three add the real-PTY probes, and every non-default leg rewrites the manifest with `scripts/ci-pin-line.mjs` before installing from scratch. `0.1.5-alpha.1` / `0.1.5-alpha.2` / `0.1.3-alpha.2` share the same handle API + `agent/assistant-stream` shims as the 0.1.5-rc line. **`0.1.2-rc` and older are no longer supported** — if the install is refused, upgrade to `0.1.5-rc` or `0.1.7-rc` first. `0.1.3-alpha.1` exists only as a GitHub tag and was never published to npm)
 - pnpm (used by `dsh plugin` to manage profile dependencies)
+- an ANSI terminal (SSH directly, or PowerShell / Windows Terminal on Windows)
+- **Windows**: install, troubleshooting and how to read `/doctor` are in [docs/windows.md](docs/windows.md)
 
 ## Install
 
@@ -114,7 +138,7 @@ dsh --profile headless "Reply with exactly: tui-install-ok. Do not use tools."
 dsh --profile tui
 ```
 
-From a checkout: `bash scripts/smoke-headless.sh` (prints an outcome summary, never a token).
+From a checkout: `node scripts/smoke-headless.mjs` (or `bash scripts/smoke-headless.sh`; prints an outcome summary, never a token).
 
 ### After an SSH drop
 
@@ -130,6 +154,22 @@ dsh --profile tui --resume                 # picker (live hosts first)
 dsh --profile tui --resume <session-id>    # attach if live, else resume the log
 ```
 
+The picker gives every live session one of two words and the Host's pid:
+**attachable** (one keystroke in) or **occupied** (another window has it). When it
+says occupied, `--resume <session-id>` is refused rather than kicking that window:
+take it over from the **picker** instead — select the row and confirm with `y` /
+Enter, and the other window exits.
+
+**A cut link does not block you.** When SSH dies the server usually does not
+know yet: sshd waits for TCP keepalive (which can be hours), the launcher stays
+connected to the display channel, and the lock still reads `attached`. So the
+Host asks the **terminal itself** (a cursor round trip through the relay — see
+`scripts/tui-cut-probe.mjs`). A terminal that cannot answer means that window is
+gone, the picker says **attachable**, one keystroke attaches, and so does
+`--resume <session-id>`. Only a terminal that confirms it is still there needs
+the takeover question above — and that answer is resolved *before* the list is
+painted, so a row never says occupied and then changes its mind.
+
 A second Host on the same `sessionId` is refused (it would steal the jsonl
 and approvals). Locks live under `$DSH_HOME/tui-locks/`; the display socket
 under `$DSH_HOME/tui-socks/`. A leftover lock from a crash is stolen if the
@@ -155,8 +195,11 @@ New sessions inherit the directory you launched from. Resuming a session
 `目录:srv` (last path segment); click it to print the full path.
 
 On start, if npm has a newer `dsh-ssh-tui`, a first-launch picker offers
-**Update now / Later / Skip this version**. Update now runs
-`dsh plugin --profile tui add dsh-ssh-tui@latest` and asks you to restart.
+**Update now / Later / Skip this version**. Update now installs the exact
+version just looked up (`dsh plugin --profile tui add dsh-ssh-tui@<version>`),
+not `@latest`: pnpm resolves `@latest` a second time, and a release still inside
+its `minimumReleaseAge` window is then skipped silently — the install succeeds
+and you are left on the old one. It asks you to restart afterwards.
 Set `DSH_TUI_NO_UPDATE_CHECK=1` to skip. `/status` also shows the plugin version, the link chip, the quota window, and whether the subagent model is in the same family as the parent route.
 
 From git:
@@ -164,9 +207,12 @@ From git:
 ```sh
 git clone https://github.com/cyjyyd/dsh-ssh-tui.git
 cd dsh-ssh-tui
-bash scripts/install.sh          # installs into the `tui` profile
+node scripts/install.mjs          # installs into the `tui` profile
 ```
 
+`bash scripts/install.sh` is a thin wrapper around that script, so it does the
+same thing where bash exists. On Windows run the Node form — there is no bash.
+
 Or manually:
 
 ```sh
@@ -175,6 +221,14 @@ npm run build
 dsh plugin --profile tui add "link:$(pwd)"
 ```
 
+The PowerShell equivalent, since `$(pwd)` is a POSIX substitution:
+
+```powershell
+npm install --no-audit --no-fund
+npm run build
+dsh plugin --profile tui add "link:$((Get-Location).Path)"
+```
+
 ### The preset roster `/mode` needs
 
 A terminal profile built on `dsh-base` composes no preset roster (only the Web
@@ -191,8 +245,8 @@ Three ways to repair it (idempotent, pick one):
 1. **In-app**: `/mode fix` writes the block below and tells you to restart.
    This is the generic path — an npm install and the in-app "Update now" both go
    through `dsh plugin add` and never run the repository scripts.
-2. From a checkout: `bash scripts/ensure-profile-rows.sh [profile]`
-   (default `tui`).
+2. From a checkout: `node scripts/profile-rows.mjs [profile]`
+   (default `tui`; `bash scripts/ensure-profile-rows.sh` is the same command).
 3. By hand, in `$DSH_HOME/profiles/<profile>/cordis.patch.yml`:
 
 ```yaml
@@ -213,7 +267,7 @@ this block lists the roster row twice, and the second mount fails with
 
 Without the row, the TUI prints a boot line ("No agent-preset roster is
 composed…"), `/mode` reports the patch path plus the `/mode fix` entry point,
-and `scripts/verify.sh` says the same. Preset identity is per module instance,
+and `node scripts/verify.mjs` (`scripts/verify.sh`) says the same. Preset identity is per module instance,
 so a dsh install tree carrying two copies of `@deepseek-ai/dsh-scope` (an
 npm-nested checkout can) fails the mount with `refusing to compose an unscoped
 context`; a global `npm i -g` install is not affected.
@@ -221,7 +275,7 @@ context`; a global `npm i -g` install is not affected.
 For the optional **智能路由模式 (routing-suite)** mode, also run:
 
 ```sh
-bash scripts/install-routing-suite.sh
+node scripts/install-routing-suite.mjs
 ```
 
 The script adds `dsh-routing-suite`, registers its preset for the `/mode`
@@ -238,8 +292,8 @@ dsh --profile tui
 Verify and uninstall:
 
 ```sh
-bash scripts/verify.sh
-bash scripts/uninstall.sh
+node scripts/verify.mjs
+node scripts/uninstall.mjs
 ```
 
 ## First-launch setup
@@ -348,14 +402,15 @@ You can reopen the wizard at any time with:
 
 | Key | Action |
 | --- | --- |
-| `Enter` | send; while running, steer; with empty input, toggle the selected card. Oversized tool bodies open a dedicated inspect view; `Esc` returns |
+| `Enter` | send; while running, steer; with empty input, toggle the selected card, or open the full view when the selected row is a reply (`Esc` returns). Oversized tool bodies open a dedicated inspect view too |
 | `Tab` | complete the highlighted slash command |
-| `↑` / `↓` | empty input: move among cards; otherwise history (↓ past the newest item restores the live draft). Same as `Ctrl+N` / `Ctrl+P` |
-| `Ctrl+R` | expand the latest card; once a card is selected, expand or collapse all |
+| `↑` / `↓` | empty input with cards in the session: walk up from the newest **reply or card** in screen order (the `▶` marker is only ever on the selected row); with no card at all (plain Q&A, or right after `/clear`) the key keeps its history meaning — select a reply there with `Alt+4` or `Ctrl+N`/`Ctrl+P`. Otherwise history (↓ past the newest item restores the live draft) |
+| `Ctrl+R` | expand the latest card; once something is selected, expand or collapse all (a selected reply keeps its selection) |
 | `Ctrl+T` | fold the input box (display-only) |
-| `Alt+1` / `2` / `3` / `4` | jump to latest thinking / plan / subagent / reply |
-| `/find [kind] query` | search and jump to the full matching message (`thinking` `plan` `subagent` `reply` `prompt` `tool`). `Ctrl+/` or `Alt+/` opens it |
-| `/copy` | copy the focused card as plain text to the local clipboard (latest reply if none; OSC 52) |
+| `Alt+1` / `2` / `3` / `4` | jump to latest thinking / plan / subagent / reply (a reply is selected, ready for `/copy`) |
+| `/find [kind] query` | search and jump to the full matching message (`thinking` `plan` `subagent` `reply` `prompt` `tool`), which is also selected. `Ctrl+/` or `Alt+/` opens it |
+| `/copy` | copy the selected card or reply **as written** to the local clipboard (latest reply if none is selected; OSC 52). The selection survives, so pressing it twice copies the same thing. Inside a full view the copy key (`Ctrl+Shift+C`) takes **the body on screen** — a tool body, a changes diff, or the reply as written — and the overlay echoes the confirmation |
+| `/retryauth [on\|off]` | auto-retry once when the *provider* rejects a request (HTTP 401/403 while a local credential is configured); off by default. The three-step diagnosis is in [`docs/remote-ops.md`](docs/remote-ops.md) §4.8 |
 | `Ctrl+G` / `Alt+N` | next search hit; `Alt+P` previous |
 | `Esc` | drop selection → scroll to bottom → cancel the running turn |
 | `Ctrl+C` | cancel the running turn; press twice when idle to exit |
@@ -623,8 +678,11 @@ skips token chunks and lays out only the visible tail on the first paint.
 
 Each paint is one `stdout.write` of dirty rows only, so a jump host or
 corporate proxy does not see one SSH packet per line. Local ttys use 80 ms.
-Over SSH the TUI probes CSI 6n once and picks 80 / 160 / 250 / 400 ms from
-the round-trip. `DSH_TUI_PAINT_MS` always wins (40–1000). The stats line
+Over SSH the TUI probes CSI 6n and picks 80 / 160 / 250 / 400 ms from the
+round-trip. It keeps measuring — 8 s after the attach, then every 20 s (a
+measurement that moved is confirmed 5 s later) — and both the chip and the paint
+tier follow the median of the last three, so a jittery entry cannot pin either
+at the slowest tier. `DSH_TUI_PAINT_MS` always wins (40–1000). The stats line
 starts with `SSH ●●●○ 90ms` (1 pip red, 2 yellow, 3+ green). The probe
 does not write into the transcript.
 
@@ -639,13 +697,16 @@ Find your symptom; each answer is what to do, not a change log.
 
 - **`dsh-ssh-tui: both stdin and stdout must be TTYs`** — start it from a real terminal or
   SSH session; a pipe, CI, or `&` background job will not do.
+- **Windows install, the scripts, and how to read `/doctor`** — [docs/windows.md](docs/windows.md)
+  has a 30-second install, a "what to check first when it will not start" table, and what the
+  `●` / `⚠` / `✖` marks in a `/doctor` report mean.
 - **Windows: `host display socket did not appear`** — upgrade
   (`dsh plugin --profile tui add dsh-ssh-tui@latest`); older builds waited 15 seconds and
   timed out on the named pipe. If it still fails, attach `/diag` to an issue.
 - **Windows: the in-app update reports `spawn dsh ENOENT`** — an older updater spawned a
-  bare `dsh`, which on Windows is a `dsh.cmd` shim. Run the same upgrade once from the
-  command line (`dsh plugin --profile tui add dsh-ssh-tui@latest`); the in-app update works
-  from then on.
+  bare `dsh`, which on Windows is a `dsh.cmd` shim. Run
+  `dsh plugin --profile tui add dsh-ssh-tui@latest` once from the command line; the in-app
+  update works from then on, and it installs the version it looked up rather than `@latest`.
 - **pnpm refuses to run the build script of a git dependency** — add the key pnpm prints to
   `allowBuilds` in the profile's `pnpm-workspace.yaml`, then reinstall.
 - **After an upgrade `/mode` reports a missing service, or the preset tools vanish** — run
@@ -686,8 +747,17 @@ Find your symptom; each answer is what to do, not a change log.
   painter asks for the narrow text form; a font without the glyph still makes the terminal
   fall back to a wider colour emoji.
 - **The screen cannot keep up on a slow link** — `DSH_TUI_PAINT_MS` sets the paint interval
-  (40–1000 ms: smaller is snappier and sends more); unset, it follows the round-trip
-  measured at start-up (80 / 160 / 250 / 400 ms).
+  (40–1000 ms: smaller is snappier and sends more); unset, it follows the round-trip,
+  which is re-measured while the session runs (80 / 160 / 250 / 400 ms, median of the last
+  three) — see `scripts/tui-rtt-probe.mjs`.
+- **The model “thinks, then says it is done”** — that is an **empty turn from upstream**: some
+  gateways map a Gemini/Claude thought part onto `reasoning_content` and then finish with
+  `finish_reason: stop` and no content at all, so the harness assembles a reply that is only
+  thinking and the turn legitimately ends. The TUI now says so in the transcript
+  (“upstream ended this turn after thinking only … it is not really done — press Enter or send
+  another message to continue”) instead of letting 完成 read as an answer. Measured on one
+  gateway (`google-ai-pro` / `gemini-3.8-flash-high`): about **29%** of turns, with the rest of
+  the same session replying normally.
 - **Screen reader, or you want a log** — start with `DSH_TUI_LINE_MODE=1`: plain appended
   lines, no cursor control, safe to `tee`.
 - **Title bar or bell does nothing** — the terminal needs OSC 0 and BEL; `DSH_TUI_NO_BELL=1`
@@ -695,6 +765,10 @@ Find your symptom; each answer is what to do, not a change log.
 - **Whole-row backgrounds are too loud on a dark terminal** — `DSH_TUI_COLOR_DEPTH=none`
   drops them; diffs still read through `+`/`-`.
 
+- **Box drawing and dots render as garbage** — the console code page is not UTF-8. The UI
+  redraws its chrome in ASCII automatically (rules as `-`, status dots as `*`, the warning as
+  `!`) and `/diag` says so on its terminal line; `chcp 65001` or Windows Terminal restores the
+  glyphs. `DSH_TUI_ASCII=1` forces ASCII, `=0` forces Unicode. See [docs/windows.md](docs/windows.md).
 - **Terminal compatibility** — what each terminal is allowed and promised (Windows Terminal,
   conhost, GNOME, XFCE, Konsole, xterm, tmux, screen, the Linux console) is tabulated in
   [docs/terminals.md](docs/terminals.md); `/diag` prints the verdict it used, and

package/README.md

@@ -6,13 +6,21 @@
 [![dshfind](https://dshfind.com/api/badge/cyjyyd/dsh-ssh-tui)](https://dshfind.com/zh/plugins/cyjyyd/dsh-ssh-tui?ref=badge)
 
 给跳板机、无桌面服务器、高延迟 SSH 用的 DeepSeek Harness 终端。纯 ANSI、增量重绘，
-不需要浏览器。
+不需要浏览器。**SSH 掉线时，正在跑的回合留在 Host 里，重连用同一条命令接回，会话不丢。**
 
 English: [README.en.md](README.en.md)
 
 如果你主要在 SSH 里写代码——公司跳板、测试机、只有键盘的会话——可以从这里开始。
 本机桌面终端若更在意主题和布局，也可以继续用你已经习惯的界面。
 
+和现成的东西不重叠：
+
+- **官方 headless**：同一条任务只把最后一条回复打到 stdout，过程全在日志里。
+- **官方 `dsh-ssh`（0.1.6 起）**：本机跑 Harness、远端跑文件和进程，要预装 helper。人已经 SSH 在那台机器上时用本插件；两者可以叠用，不是替代。
+- **其它终端皮肤**（`dsh-TUI` 等）：本机漂亮终端，比主题和布局。本插件比的是弱网下的增量重绘、掉线后 Host 留下、纯文本行模式。
+
+掉线之后怎么接回来，见下面的[「SSH 断了之后」](#ssh-断了之后)。
+
 已经在付 SuperGrok / X Premium 的话，用独立插件 [dsh-llm-xai-oauth](https://github.com/cyjyyd/dsh-llm-xai-oauth) 把订阅接进 dsh（headless / web / 本 TUI 都能用），复用本机 grok-bridge token，不需要 xAI API Key。
 
 本插件已被 [dshfind 插件目录](https://dshfind.com/zh/plugins/cyjyyd/dsh-ssh-tui) 收录：
@@ -28,6 +36,11 @@ dsh --profile tui
 
 当前 `dsh` 必须带 `--profile`（`dsh plugin add …` 会报缺选项）。装进别的 profile 把 `tui` 换成那个名字即可。
 
+> **宿主已升到 0.2.0-rc 的用户请看这里**：0.8.0 支持 `0.2.0-rc` 线（旧版会因声明窗口不符被 launcher 拒绝），
+> 但它目前只挂在 `next` 上——`latest` 仍是 0.7.4，2026-10-01 起才切到 0.8.0。这段时间请用
+> `dsh plugin --profile tui add dsh-ssh-tui@next` 安装；还在 `0.1.7-rc` 线的话 `@latest`(0.7.4) 就够用，
+> 等 0.8.0 上 `latest` 再升也不迟。**0.1.5 及更早的宿主从 0.8.0 起不再支持**。
+
 **更新必须带 `@latest`。** `dsh plugin` 只是把后面的参数转给 profile 目录里的 pnpm。写成 `add dsh-ssh-tui`（没有版本）时，pnpm 会沿用 `pnpm-lock.yaml` 里已经钉死的版本（常见就是一直停在 0.3.7）。也不要把 `--profile` 写到 `add` 后面：`dsh plugin add --profile tui add dsh-ssh-tui` 不是合法用法。卸载：`dsh plugin --profile tui remove dsh-ssh-tui`。
 
 ## 官方 headless 和这个 TUI
@@ -88,7 +101,11 @@ dsh --profile tui
   标题（还没出现就保持「处理中」），运行中的工具摘要在 `└` 下自动折行（最多 3 行，末行
   加省略号），带计时和 Esc 中断；回复开始流式输出时自动让位。
 
-- 0.7 起：模型回复可**拖选自由复制**（按住拖过一段，走 OSC 52 写回本机剪贴板；工具卡仍是点击展开）；
+- 0.7 起：模型回复可**拖选自由复制**（按住鼠标拖过一段，走 OSC 52 写回本机剪贴板；按住 Shift 拖选
+  结果相同；工具卡仍是点击展开）。回复也是**可选中卡片**：空输入 `↑` 落到最新的一条回复或卡片（`▶` 标记，
+  走屏幕顺序；`Alt+4` 直接选中最新回复），
+  `/copy` 复制的是选中的那一条（原文，不是折行后的屏幕文本），`Enter` 打开全文；
+  SSH 会话里复制落到本机终端，不再误报「本终端不接收 OSC 52」；
   底栏收敛成一条带优先级的芯片带（先丢文字后丢组，`⚠` 可点击打开 `/doctor`）；**额度条常驻**并标注窗口
   （`5Hr`/`1Wk`/`1Mo`，默认显示最小窗口，未取到时显示 `?%` 并每 15 秒重试）；`/mode` 分组显示并可用 `/` 过滤；
   极简视图逐文件列 `+/-`；工具 diff 为**行级**、只高亮变化字符、≥100 列时并排显示；
@@ -98,10 +115,10 @@ dsh --profile tui
 ## 环境要求
 
 - Node.js ≥ 22.19
-- DeepSeek Harness CLI：`npm i -g @deepseek-ai/dsh`（CI 覆盖 `0.1.5-rc.1` / `0.1.5-rc.3` / `0.1.7-rc.1`：`0.1.5-rc.1` 跑 typecheck 与单元套件，另两条连真 PTY 探针一起跑。`0.1.5-alpha.1` / `0.1.5-alpha.2` / `0.1.3-alpha.2` 与 0.1.5-rc 线共用同一套 handle API + `agent/assistant-stream` 兼容层。**`0.1.2-rc` 及更早的线不再支持**，装不上请先升到 `0.1.5-rc` 或 `0.1.7-rc`。`0.1.3-alpha.1` 只在 GitHub 有 tag，npm 未发布，无法本地装包验证）
+- DeepSeek Harness CLI：`npm i -g @deepseek-ai/dsh`（本仓库默认开发线是 `0.2.0-rc.1`，CI 覆盖 `0.1.7-rc.1` / `0.1.7-rc.2` / `0.2.0-rc.1` 三条 dsh 线加一条 Windows 腿：`0.1.7-rc.1` 跑 typecheck 与单元套件，另两条连真 PTY 探针一起跑；非默认腿由 `scripts/ci-pin-line.mjs` 改写 manifest 后从零安装。**`0.1.5` 及更早的线自 0.8.0 起不再支持**（`dshReleases` 里保留 `incompatible` 的明确表态，装不上请升到 `0.1.7-rc` 或 `0.2.0-rc`；`0.1.5` 那条线需要的是 `<0.1.6` 的旧代 API）。`0.1.3-alpha.1` 只在 GitHub 有 tag、npm 未发布，无法本地装包验证）
 - pnpm（`dsh plugin` 通过 pnpm 管理 profile 依赖）
 - 支持 ANSI 的终端（推荐 SSH 直连；Windows 用 PowerShell / Windows Terminal）
-- Windows：Host 与显示端之间的本地通道使用命名管道
+- Windows：安装、排障与 `/doctor` 的读法见 [docs/windows.md](docs/windows.md)。Host 与显示端之间的本地通道使用命名管道
   `\\.\pipe\dsh-tui-<DSH_HOME 摘要 8 位>-<会话名>-<会话摘要 8 位>`（Windows 只能监听命名管道，
   不能监听 `.sock` 文件；名字里同时带 DSH_HOME 与会话 id 的摘要，所以不同 home、不同会话都不会撞名，
   结束进程即自动回收）。Host 的 stderr 记录在 `%USERPROFILE%\.dsh\tui-socks\<会话名>-<摘要>.err`，
@@ -150,6 +167,17 @@ dsh --profile tui --resume                 # 选择器（活进程优先接入
 dsh --profile tui --resume <session-id>    # 有活进程则接入，否则从日志恢复
 ```
 
+选择器里每个活着的会话只标两个词：**可接入**（一键接入）或**已占用**（别的窗口在用）。
+后面跟的是 Host 的 pid。被标成「已占用」时 `--resume <session-id>` 会被拒绝而不是把对方踢掉——
+要接管就在**选择器里**选中它，再按 `y` / Enter 确认（那个窗口随即退出）。
+
+**断线残留不会挡住你**：SSH 被切断时服务端常常还不知道（sshd 要等 TCP keepalive 才发现，可能几小时），
+那个窗口的 launcher 仍然连着显示通道，锁里写的还是 `attached`。所以 Host 会反过来向**终端本身**要答案
+（经 relay 做一次光标往返，见 `scripts/tui-cut-probe.mjs`）：终端答不上来就说明那个窗口已经没了，
+选择器直接标「可接入」，一键接入；`--resume <session-id>` 也直接接入。
+只有终端确认还活着时才需要上面的接管确认。这个判断在**首帧之前**完成，所以列表不会先显示「已占用」
+再改口。
+
 同一 `sessionId` 不能同时开第二份 Host（会抢 jsonl 和审批）。锁在
 `$DSH_HOME/tui-locks/`，显示通道在 `$DSH_HOME/tui-socks/`。进程死后残留锁会在
 下次启动时核对 pid，已死则自动从日志接管。调试可设 `DSH_TUI_NO_SESSION_LOCK=1`。
@@ -163,6 +191,11 @@ dsh --profile tui --resume <session-id>    # 有活进程则接入，否则从
 倍以上的（那是别人请求的回复，相对判定所以 `ssh localhost` 的 2ms 链路照样算得出来）。
 代价是每次接入多约 0.4–0.6 秒探测时间，换来的是 50ms 链路不再出现 2ms / 1900ms 的跳变。
 
+**链路会一直重测，不是只测一次**：接入 8 秒后补测一次，之后每 20 秒一次（变化超过 50ms 时
+5 秒后再确认一次），footer 芯片与绘制档位取**最近三次的中位数**——单次抖动（或接入那一刻正好
+在抖）不会把芯片和绘制预算钉在最慢一档，真正的变化两次就能定下来。终端完全不答 DSR 时退避到
+10 分钟一次。见 `scripts/tui-rtt-probe.mjs`（CI 的 0.1.7 腿）。
+
 这些回复也不可能再进输入框：relay 整条 stdin 管道常驻过滤（含跨 read 拆分的），Host 键
 处理前再过滤一次；连 Host 启动那几百毫秒里敲的键也会被暂存、接入后补发，不再被丢掉。
 `DSH_TUI_DEBUG=1` 时会打印每次采样与丢弃原因。
@@ -182,22 +215,25 @@ Host 在后台跑完这一轮；审批和提问等接上后再弹。空闲断线
 完全没有显示器且一直空闲的兜底仍由 `DSH_TUI_DETACHED_IDLE_MS`（默认 6 小时）负责。可选：用 tmux 包一层。
 常驻与接管的可复制配方（tmux / screen / systemd --user / 长任务）见 [`docs/remote-ops.md`](docs/remote-ops.md)；重连后转录里的「已重连 N 次 · 断开 Xs」与「离开 …」两行的语义也在那里。
 
-启动时若 npm 上有更新，会弹出选单（类似 Codex / Claude Code 首启）：**现在更新 / 稍后 / 跳过此版本**。选「现在更新」会运行 `dsh plugin --profile tui add dsh-ssh-tui@latest`，完成后提示退出再启动。`DSH_TUI_NO_UPDATE_CHECK=1` 可关掉。`/status` 里也能看到当前插件版本、链路芯片、额度窗口，以及子代理模型是否与父路由同族。
+启动时若 npm 上有更新，会弹出选单（类似 Codex / Claude Code 首启）：**现在更新 / 稍后 / 跳过此版本**。选「现在更新」安装的是刚才查到的那个版本号（`dsh plugin --profile tui add dsh-ssh-tui@<版本>`），不写 `@latest`：pnpm 对 `@latest` 会再解析一次，刚发布、还在 `minimumReleaseAge` 窗口里的版本会被静默跳过、装成旧的还显示成功。完成后提示退出再启动。`DSH_TUI_NO_UPDATE_CHECK=1` 可关掉。`/status` 里也能看到当前插件版本、链路芯片、额度窗口，以及子代理模型是否与父路由同族。
 
-仓库内也可：`bash scripts/smoke-headless.sh`（记录出口摘要，不打印 token）。
+仓库内也可：`node scripts/smoke-headless.mjs`（`bash scripts/smoke-headless.sh` 等价；记录出口摘要，不打印 token）。
 
 ### 方式一：从 git clone 安装
 
 ```bash
 git clone https://github.com/cyjyyd/dsh-ssh-tui.git
 cd dsh-ssh-tui
-bash scripts/install.sh            # 默认安装到 tui profile
+node scripts/install.mjs           # 默认安装到 tui profile（bash scripts/install.sh 等价）
 ```
 
+Windows 没有 bash，用同一条 `node scripts/install.mjs`；完整的 Windows 步骤、
+「装不上先看什么」和 `/doctor` 的读法见 [docs/windows.md](docs/windows.md)。
+
 安装到其它 profile（例如自定义 `work` profile）：
 
 ```bash
-bash scripts/install.sh work
+node scripts/install.mjs work
 ```
 
 脚本会依次：安装依赖 → 构建 `lib/` → 通过 `dsh plugin --profile <name> add link:<repo>`
@@ -216,7 +252,8 @@ bash scripts/install.sh work
 
 1. **运行中的应用内修复**：`/mode fix` 写入下面这段并提示重启。npm 安装和
    「现在更新」走的是 `dsh plugin add`，不会执行仓库脚本，所以这是最通用的一条。
-2. 仓库安装：`bash scripts/ensure-profile-rows.sh [profile]`（默认 `tui`）。
+2. 仓库安装：`node scripts/profile-rows.mjs [profile]`（默认 `tui`；
+   `bash scripts/ensure-profile-rows.sh` 是它的薄封装，两者等价）。
 3. 手动在该 profile 的 `$DSH_HOME/profiles/<profile>/cordis.patch.yml` 里加入：
 
 ```yaml
@@ -234,7 +271,7 @@ profile（例如同时装了 `@deepseek-ai/dsh-web-app` 的 profile）。改完
 会以 `service "agentPresets" has been registered` 失败），先把 profile 补丁里的这段删掉。
 
 名单缺席时，TUI 启动会打一行提示（中文界面：「未挂载 agent-presets 名单…」），
-`/mode` 会打印补丁路径和 `/mode fix` 修复入口，`scripts/verify.sh` 也会给出提示。
+`/mode` 会打印补丁路径和 `/mode fix` 修复入口，`node scripts/verify.mjs`（`scripts/verify.sh` 等价）也会给出提示。
 另外，preset 的 scope 身份按模块实例判定：一个 dsh 安装树里若存在两份
 `@deepseek-ai/dsh-scope`（npm 嵌套安装的 checkout 可能如此），名单挂载会以
 `refusing to compose an unscoped context` 失败；全局安装（`npm i -g`）不受影响。
@@ -248,7 +285,15 @@ npm run build
 dsh plugin --profile tui add "link:$(pwd)"
 ```
 
-Windows（PowerShell）等价写法；仓库里的 `scripts/*.sh` 是 POSIX 脚本，Windows 直接用下面三条命令：
+Windows（PowerShell）不用 bash，直接跑 Node 脚本（`scripts/*.sh` 只是转去调用它们的薄封装）：
+
+```powershell
+cd dsh-ssh-tui
+node scripts/install.mjs            # 装依赖、构建、链接进 tui profile、挂上 /mode 需要的行
+node scripts/verify.mjs             # 检查组合是否生效
+```
+
+不想用脚本时，三条命令等价：
 
 ```powershell
 cd dsh-ssh-tui
@@ -261,8 +306,8 @@ dsh plugin --profile tui add "link:$((Get-Location).Path)"
 
 ```bash
 dsh plugin --profile work add dsh-ssh-tui
-# 或仓库脚本
-bash scripts/install-npm.sh work
+# 或仓库脚本（bash scripts/install-npm.sh 等价）
+node scripts/install-npm.mjs work
 ```
 
 ### 智能路由模式（dsh-routing-suite）
@@ -270,8 +315,8 @@ bash scripts/install-npm.sh work
 需要“智能路由模式”时，安装 `dsh-routing-suite` 并注册其 preset：
 
 ```bash
-bash scripts/install-routing-suite.sh          # 默认 tui profile
-bash scripts/install-routing-suite.sh work     # 其它 profile
+node scripts/install-routing-suite.mjs          # 默认 tui profile
+node scripts/install-routing-suite.mjs work     # 其它 profile（bash scripts/install-routing-suite.sh 等价）
 ```
 
 脚本会执行 `dsh plugin --profile <name> add dsh-routing-suite`，并把包内的
@@ -300,16 +345,17 @@ dsh --profile tui --no-color
 
 | 键 | 作用 |
 | --- | --- |
-| `Enter` | 发送；运行中则插入指示；空输入且已选卡片时展开/收起。工具正文超出窗口则单独全览，`Esc` 返回 |
+| `Enter` | 发送；运行中则插入指示；空输入且已选中卡片时展开/收起，选中的是回复则打开全文（`Esc` 返回）。工具正文超出窗口也单独全览 |
 | `1..9` / `Enter` | 回答 `ask_user_question` 提问：`1..9` 直接选，`Enter` 取当前高亮项（默认第一项），`Esc` 才取消 |
-| `↑` / `↓` | 空输入：在卡片间移动；有输入：历史（↓ 越过最新一条会回到当前草稿）。与 `Ctrl+N` / `Ctrl+P` 相同 |
-| `Ctrl+R` | 展开最新一条卡片；已用 ↑/↓ 选中时全部展开或全部收起 |
+| `↑` / `↓` | 空输入且会话里已有卡片时：在当前屏幕顺序的最新一条（**回复或卡片**）开始往上走，标记 `▶` 只出现在选中的那一条；没有卡片时（纯问答、或刚 `/clear`）仍是有输入时的历史召回——那种会话用 `Alt+4` 或 `Ctrl+N`/`Ctrl+P` 选回复。有输入：历史（↓ 越过最新一条会回到当前草稿） |
+| `Ctrl+R` | 展开最新一条卡片；已选中时全部展开或全部收起（选中的回复不会被抢走焦点，打开覆盖层时该键交给覆盖层） |
 | `Ctrl+T` | 折叠输入框（只影响显示） |
-| `Alt+1` / `2` / `3` / `4` | 跳到最新思考 / 计划 / 子代理 / 回复 |
-| `/find [类] 关键字` | 搜索并跳到该条完整消息（反色高亮）。类：`思考` `计划` `子代理` `回复` `提示词`。`Ctrl+/` 或 `Alt+/` 打开 |
+| `Alt+1` / `2` / `3` / `4` | 跳到最新思考 / 计划 / 子代理 / 回复（回复会被选中，可直接 `/copy`） |
+| `/find [类] 关键字` | 搜索并跳到该条完整消息（反色高亮），命中的那条同时成为选中项。类：`思考` `计划` `子代理` `回复` `提示词`。`Ctrl+/` 或 `Alt+/` 打开 |
 | `Ctrl+G` / `Alt+N` | 下一条搜索结果；`Alt+P` 上一条 |
-| `/copy` | 把焦点卡片纯文本写入本机剪贴板（无焦点则最近一条回复；支持 OSC 52 的终端/tmux） |
-| 鼠标左键 | 点击卡片标题展开/收起；点 markdown 链接则复制 URL |
+| `/copy` | 把选中的卡片或回复按**原文**写入本机剪贴板（无选中则最近一条回复；支持 OSC 52 的终端/tmux）。复制后保留选中，连按两次拿到的是同一条。在「全文」覆盖层里按复制键（`Ctrl+Shift+C`）复制的是**屏幕上那份正文**——工具卡是工具全文、改动卡是那份 diff、回复是原文；覆盖层底部会回显「已复制 …（全文）」 |
+| `/retryauth [on\|off]` | "提供商侧鉴权失败"（HTTP 401/403，且本机凭据已配）时要不要自动重试一次；默认关。判断口诀与排查三步见 [`docs/remote-ops.md`](docs/remote-ops.md) 4.8 |
+| 鼠标左键 | 点击卡片标题展开/收起；点 markdown 链接则复制 URL；**拖过回复**按屏幕所见复制（不含选中标记 `▶`） |
 | `PgUp` / `PgDn`、滚轮 | 转录回看 |
 | `Esc` | 取消选择 → 回底部 → 取消当前轮次 |
 | `Ctrl+C` | 中断当前轮次；空闲连按两次退出 |
@@ -471,7 +517,7 @@ DeepSeek 上、B 会话跑在 xAI 上；只记软件级默认值的话，resume
 ## 验证
 
 ```bash
-bash scripts/verify.sh              # 检查 profile 组合与 CLI 语法
+node scripts/verify.mjs             # 检查 profile 组合与 CLI 语法（bash scripts/verify.sh 等价）
 npm test                            # 单元 + 集成（含屏幕网格护栏、重连接管、选择器首帧）
 python3 scripts/pty-acceptance.py   # 真 PTY：模拟 40ms SSH 链路 + 滞留的光标回复
 node scripts/tui-probe.mjs          # 真 PTY：真 dsh --profile tui 走一遍启动/缩放//diag/打字//exit
@@ -509,8 +555,8 @@ PROBE_HOME=$H node scripts/tui-probe.mjs --session <id>   # 只读式驱动已
 ## 卸载
 
 ```bash
-bash scripts/uninstall.sh           # 默认 tui profile
-bash scripts/uninstall.sh work      # 指定 profile
+node scripts/uninstall.mjs          # 默认 tui profile（bash scripts/uninstall.sh 等价）
+node scripts/uninstall.mjs work     # 指定 profile
 ```
 
 卸载只移除 profile 中的插件依赖与 bundle 层，不会删除会话数据。
@@ -568,10 +614,12 @@ npm run build
 ### 启动与安装
 
 - **`dsh-ssh-tui: both stdin and stdout must be TTYs`**：必须在真实终端 / SSH 会话里启动；管道、CI、`&` 后台都不行。
+- **Windows 安装、脚本与 `/doctor` 的读法**：[docs/windows.md](docs/windows.md) 有 30 秒安装、
+  「装不上先看什么」的对照表，以及 `/doctor` 报告里 `●` / `⚠` / `✖` 各代表什么。
 - **Windows 报 `host display socket did not appear`**：升级到最新版：
   `dsh plugin --profile tui add dsh-ssh-tui@latest`。仍失败请附 `/diag` 输出提 issue。
 - **Windows 上应用内更新报 `spawn dsh ENOENT`**：旧的更新器直接 `spawn dsh`，而 Windows 上装的是 `dsh.cmd` 垫片；
-  在命令行跑一次同样的升级即可（`dsh plugin --profile tui add dsh-ssh-tui@latest`），之后应用内更新正常。
+  在命令行跑一次 `dsh plugin --profile tui add dsh-ssh-tui@latest`，之后应用内更新正常（它装的是查到的版本号，不再写 `@latest`）。
 - **pnpm 拒绝 git 依赖的构建脚本**：把 pnpm 打印的 key 加进 profile 的 `pnpm-workspace.yaml` 的 `allowBuilds`，再重装。
 - **升级后 `/mode` 报「服务不可用」、preset 工具消失**：敲 `/doctor`。它逐项判定部署组合（补丁能否解析、
   名单与 code-runtime 是否组合、有没有行被挂载两次、dsh 版本是否在兼容表内、是否装着两份 `@deepseek-ai/dsh-scope`），
@@ -597,11 +645,19 @@ npm run build
 - **中文 / emoji 挤压相邻字符**：换一款覆盖这些字形的等宽字体（如 Noto Sans Mono CJK）。程序按 2 格预算这些符号
   并请求文本字形；字体缺字时终端会回退到彩色 emoji 字形，视觉上仍可能偏宽。
 - **弱网下画面跟不上**：`DSH_TUI_PAINT_MS` 控制发画间隔（40–1000 ms，越小越快也越费流量）；
-  不设时按启动测得的 RTT 自动取 80 / 160 / 250 / 400 ms。
+  不设时按测得的 RTT 自动取 80 / 160 / 250 / 400 ms；链路每 20 秒重测（刚变化过就 5 秒后再测一次），
+  取最近三次的中位数，所以接入那一刻的抖动不会把绘制档位钉在最慢一档。
+- **模型“只思考一下就说完成”**：这是**上游返回了空回合**——有些网关把 Gemini/Claude 的 thought 部分映射成
+  `reasoning_content`，然后以 `finish_reason: stop` 收尾却没有任何正文，harness 如实组装成“只含思考的助手消息”，
+  回合就合法结束了。TUI 现在会显式写一行「上游只返回了思考…这不是真正的完成（finish_reason: stop）；按 Enter 或再输入一句即可继续」，
+  不再让你以为它答完了。实测某网关（`google-ai-pro` / `gemini-3.8-flash-high`）约 **29%** 的回合如此（同会话其它回合正常）。
 - **要给屏幕阅读器或日志用**：`DSH_TUI_LINE_MODE=1` 启动纯行模式——只追加纯文本行、不发光标控制，可直接 `tee` 存档。
 - **标题栏 / 铃声不生效**：终端需支持 OSC 0 与 BEL；`DSH_TUI_NO_BELL=1` 可关闭铃声。
 - **深色终端下整行底色太抢眼**：`DSH_TUI_COLOR_DEPTH=none` 去掉底色，diff 仍用 `+`/`-` 区分。
 
+- **框线、圆点显示成乱码**：控制台代码页不是 UTF-8。界面会自动改画 ASCII（横线 `-`、状态点 `*`、
+  警告 `!`），`/diag` 的「终端」一行会注明；想要原字形就 `chcp 65001` 或改用 Windows Terminal。
+  `DSH_TUI_ASCII=1` 强制 ASCII，`=0` 强制 Unicode。详见 [docs/windows.md](docs/windows.md)。
 - **终端兼容性**：每个终端允许发什么、承诺什么（Windows Terminal / conhost / GNOME / XFCE / Konsole /
   xterm / tmux / screen / Linux 控制台）见 [docs/terminals.md](docs/terminals.md)；
   判定依据写在 `/diag` 的「终端」一行，判定错了用 `DSH_TUI_TERM_CAPS` 覆盖。