dsh-dbhub-live 5.2.0-dev.3 → 6.0.0-rc.1

package/README.en.md

@@ -15,7 +15,7 @@ Install it and you can simply tell the AI "show me the last 10 rows of the order
 <details>
 <summary>📷 Preview: Settings → DBHub Database Tools</summary>
 
-![DBHub Database Tools configure page](doc/images/settings-page.png)
+![DBHub Database Tools configure page](https://raw.githubusercontent.com/mr-mihu/dsh-dbhub-live/dev/doc/images/settings-page.png)
 
 </details>
 
@@ -33,26 +33,24 @@ Install it and you can simply tell the AI "show me the last 10 rows of the order
 
 Supports **MySQL · PostgreSQL · MariaDB · SQLite · SQL Server**.
 
-<!-- release-test:versions:begin -->
-## Supported version range
-
-**From DSH 0.1.5 (lines 0.1.5 / 0.1.6 / 0.1.7 / 0.2.0 / 0.2.1, prereleases included)** — 6 declared versions verified (last verified 2026-10-24).
-
-<details>
-<summary>Per-version verification details (expand)</summary>
-
-| DSH version | UI | Boot | Hard checks | Result | Last verified |
-| --- | --- | --- | --- | --- | --- |
-| `0.1.5-rc.3` | legacy | 7.3s | 19 | ⚠️ pass with notes · manual | 2026-10-24 · 4f6a854a |
-| `0.1.6-alpha.2` | legacy | 3.5s | 19 | ⚠️ pass with notes · manual | 2026-10-24 · 4f6a854a |
-| `0.1.7-rc.2` | legacy | 4.7s | 20 | ⚠️ pass with notes · manual | 2026-10-24 · 4f6a854a |
-| `0.2.0-rc.2` | legacy | 4.9s | 20 | ⚠️ pass with notes · manual | 2026-10-24 · 4f6a854a |
-| `0.2.1-alpha.1` | modern | 5.1s | 20 | ⚠️ pass with notes · manual | 2026-10-24 · 4f6a854a |
-| `0.2.1-rc.2` | modern | 5.3s | 20 | ⚠️ pass with notes · manual | 2026-10-24 · 4f6a854a |
-
-</details>
-
-Full evidence, review rules and known drift live in [doc/SUPPORT-MATRIX.md](doc/SUPPORT-MATRIX.md).
+<!-- release-test:versions:begin -->
+## Supported version range
+
+**From DSH 0.2.1 (lines 0.2.1 / 0.2.2, prereleases included)** — 4 declared versions not all verified yet (last verified 2026-10-24).
+
+<details>
+<summary>Per-version verification details (expand)</summary>
+
+| DSH version | UI | Boot | Hard checks | Result | Last verified |
+| --- | --- | --- | --- | --- | --- |
+| `0.2.1-rc.2` | modern | 16.9s | 20 | ⚠️ pass with notes · manual | 2026-10-24 · 91642fa2 |
+| `0.2.1-rc.5` | modern | — | — | — | 未验证 |
+| `0.2.2-rc.1` | modern | — | — | — | 未验证 |
+| `0.2.2-rc.2` | modern | — | — | — | 未验证 |
+
+</details>
+
+Full evidence, review rules and known drift live in [doc/SUPPORT-MATRIX.md](https://github.com/mr-mihu/dsh-dbhub-live/blob/dev/doc/SUPPORT-MATRIX.md).
 <!-- release-test:versions:end -->
 
 ## Installation
@@ -73,7 +71,7 @@ On desktop you can also **install entirely through the UI**: **left menu → Plu
 
 Once installed, **restart `dsh web`** and open **Settings → DBHub Database Tools** to see the configure page (there is also a sidebar shortcut, and the Configure control on the plugin's row on the Plugins page — all three entries lead to the same page).
 
-> Requirements: every `dsh` release line from 0.1.5 on (0.2.x included); **the new UI needs 0.2.1+** (0.2.1 prereleases included) — the wide full page, the version/update header and the inline read-only switch only render on 0.2.1 and later; **0.1.x is still supported but keeps the old layout and behaviour**. Node.js ≥ 18 is recommended locally (it is used to install dbhub automatically). **Read-only mode and SSH tunnels need dbhub 1.4.0+** — the plugin detects this and gives you upgrade guidance. Per-version verification results live in [doc/SUPPORT-MATRIX.md](doc/SUPPORT-MATRIX.md) (generated by the release test, which must pass before every release).
+> Requirements: **DSH 0.2.1 or later** (0.2.1 prereleases included; **0.1.x and 0.2.0 are no longer supported**). On an older host the plugin does not go blank: the configure page shows one bilingual notice naming the required and the running version, and every tool, connection and setting keeps working — but upgrade DSH soon. Node.js ≥ 18 is recommended locally (it is used to install dbhub automatically). **Read-only mode and SSH tunnels need dbhub 1.4.0+** — the plugin detects this and gives you upgrade guidance. Per-version verification results live in [doc/SUPPORT-MATRIX.md](https://github.com/mr-mihu/dsh-dbhub-live/blob/dev/doc/SUPPORT-MATRIX.md) (generated by the release test, which must pass before every release).
 
 ## Updating
 
@@ -87,9 +85,9 @@ Then **restart `dsh web`**.
 
 **Desktop**: uninstall the plugin on the **left menu → Plugins** page and reinstall the latest version (desktop updates go through the visual Plugins page). **Connections and credentials survive the reinstall** — they live in `~/.dsh/storages/dsh-dbhub-live`, independent of the module directory.
 
-**No need to remember version numbers**: the configure page header shows the plugin name and the current version; when a newer version exists a quiet "**↑ Upgrade to <latest>**" text link appears and **clicking it copies** `dsh-dbhub-live@<latest>`; the "Check for updates" button next to it checks on demand. Opening the page also triggers one automatic check (throttled, so it does not hit the network on every open). Checks use the **npm registry first, with GitHub Releases as the fallback**; release notes live in [GitHub Releases](https://github.com/mr-mihu/dsh-dbhub-live/releases).
+**No need to remember version numbers**: the configure page header shows the plugin name and the current version; when a newer version exists a quiet "**↑ Upgrade to <latest>**" text link appears and **clicking it opens a panel where you copy** `dsh-dbhub-live@<latest>`; the "Check for updates" button next to it checks on demand. Opening the page also triggers one automatic check (throttled, so it does not hit the network on every open). Checks use the **npm registry first, with GitHub Releases as the fallback**; release notes live in [GitHub Releases](https://github.com/mr-mihu/dsh-dbhub-live/releases).
 
-> The version/update hint is part of the new UI and needs plugin 5.2.0+ and DSH 0.2.1+; on 0.1.x it is not shown (see "Configure Page").
+> The version/update hint needs plugin 5.2.0+ and DSH 0.2.1+ (see "Configure Page").
 
 ## Quick Start
 
@@ -105,7 +103,7 @@ AI:  … (query results)
 <details>
 <summary>📷 In action: ask the AI, get the query results</summary>
 
-![Asking the AI and getting query results](doc/images/chat-query.png)
+![Asking the AI and getting query results](https://raw.githubusercontent.com/mr-mihu/dsh-dbhub-live/dev/doc/images/chat-query.png)
 
 </details>
 
@@ -149,11 +147,11 @@ While the plugin is enabled it contributes a **system-prompt section** (about 40
 <details>
 <summary>📷 Row editor: read-only mode and SSH tunnel</summary>
 
-![Connection row and "Test SSH tunnel"](doc/images/row-editor.png)
+![Connection row and "Test SSH tunnel"](https://raw.githubusercontent.com/mr-mihu/dsh-dbhub-live/dev/doc/images/row-editor.png)
 
 </details>
 
-The same component offers **three layouts**, picked automatically from the host surface and the window width (the new UI needs plugin 5.2.0+ and **DSH 0.2.1+**; on DSH 0.1.x the old layout and behaviour are kept, see the end of this section):
+The same component offers **three layouts**, picked automatically from the host surface and the window width (needs plugin 5.2.0+ and **DSH 0.2.1+**, see the end of this section):
 
 | Layout | How to reach it | Shape |
 | --- | --- | --- |
@@ -163,16 +161,17 @@ The same component offers **three layouts**, picked automatically from the host
 
 **Header: version and upgrade entry**: the title is the plugin name with the current version (small, muted) right next to it; when a newer version exists a quiet "**↑ Upgrade to <latest>**" text link appears on the right, and **clicking it expands** the update notes — the `dsh-dbhub-live@<latest>` spec (click to copy), the update command / steps for this deployment, and a link to the release notes; the "↻" button checks on demand. Opening the page also triggers an automatic check (throttled). Checks use the npm registry first, with GitHub Releases as the fallback. **An update is neutral news, never styled as an error.**
 
-- **Status line**: it shows only "running / disabled · N connections". Implementation facts — tool count, one-shot execution mode, dbhub version — live in the collapsed "ⓘ Details & diagnostics" block at the bottom of the page.
+- **Status line**: it shows only "running / disabled · N connections". Implementation facts — tool count, one-shot execution mode, dbhub version — live in the collapsed "ⓘ Details" block below the status line.
 - **Connection list**: organised by workspace. When every workspace has a single environment the rows render as flat cards; as soon as one workspace owns several environments they fold into per-workspace groups (click a group head to expand; the most recently used one is open by default). Each connection takes one line: environment name · type / host / port / **database** · **read-only switch** · the `source` handle (click it to copy) · test / edit / delete. In a narrow window the host and port are truncated first, while **the database name always stays visible**.
 - **Settings (DSH-native style, deliberately quiet)**: on the wide page the four controls collapse into **one compact settings line** — `Plugin settings · Enable plugin [enabled] · Sidebar entry [shown] · Access policy [on] · Auto-update [7] days [save] · ⓘ details`; the modal and the phone use compact stacked rows. Fonts and switches are kept small so the **connection list** stays the main content. The controls are DSH's own switches (theme/skin aware, with state words); every explanatory paragraph lives in "ⓘ Details & diagnostics".
 - **Read-only switch (outside the edit form in all three layouts)**: right next to the datasource on every connection row there is a small "RO" toggle — one click flips it (open lock + "Writable" = writable; closed lock + "RO" = read-only) without opening the edit form; the modal and the phone layout have it too. The tick-box in the edit form stays as well; both are the same state. **The connection string itself no longer carries a lock icon** — it used to read like "this row needs a password" and clashed with the read-only lock.
-- **Add / edit / delete**: use ✏ on a row to change the connection string or the environment name; "＋ Add connection" accepts Chinese environment names. **Saving onto an environment name that already exists asks "overwrite?" first** — cancel and not a single byte is written.
-- **Connection test**: runs `SELECT 1` over **the effective connection that environment will really use** (read-only / tunnel included) and shows the elapsed time while it runs. The result is one-shot feedback: nothing is persisted and no connection state changes.
+- **Add / edit / delete**: use ✏ on a row to change the connection string or the environment name; "＋ Add connection" accepts Chinese environment names. **Saving onto an environment name that already exists asks "overwrite?" first** — cancel and not a single byte is written. **Deleting asks first too** (it cannot be undone; cancelling writes nothing either).
+- **A failed write is always visible**: when a save / switch / delete is refused (401, offline, a Host refusal) the page shows an error line and **never** claims "Saved ✓"; fixing it and clicking again is the retry. A failed plugin-state read shows its own error line plus "Retry" instead of silently turning into "no connections". "Auto-update interval" only accepts a whole number of days from 0 to 365 — an empty box or a fraction is rejected on the spot and no request is sent.
+- **Connection test**: runs `SELECT 1` over **the effective connection that environment will really use** (read-only / tunnel included) and shows the elapsed time while it runs. The result is one-shot feedback: nothing is persisted and no connection state changes. When the command never reaches the Host (bridge 401 / offline) it says "the test command never reached the host" immediately instead of reporting a timeout 30 seconds later.
 
 **"Show the sidebar entry" is not disabling the plugin**: switching it off merely hides the sidebar shortcut — the plugin keeps working and the model can still query; use "Disable" to stop the plugin as a whole (a disabled plugin always hides the entry). In either state, **the settings page and the Plugins row's Configure control always stay reachable**, so the change can be undone at any time.
 
-**Compatibility path for DSH 0.1.x**: the header version / upgrade entry, the wide full page, the row read-only chip and the settings rows all render only on **DSH 0.2.1+** (prereleases included); on 0.1.x the plugin keeps its previous layout and behaviour and **shows no upgrade hint** — that is deliberate, not a defect.
+**When DSH is too old**: the configure page gains one warning at the top (naming "DSH 0.2.1 or later" and the running version); the page, connections, read-only switches and tools all keep working — the plugin is not broken, the host just needs an upgrade.
 
 ## 🔒 Read-only Mode and SSH Tunnels
 
@@ -238,14 +237,18 @@ On desktop you can also uninstall directly on the **left menu → Plugins** page
 | The read-only / SSH controls are greyed out, or dbhub is reported as too old | Both need dbhub 1.4.0+: upgrade dbhub, or delete `~/.dsh/storages/dsh-dbhub-live` so the plugin installs a version that satisfies it. |
 | A connection test fails and you cannot tell why | Read the **end** of the message (the diagnostic is the tail of dbhub's output and marks the layer: [SSH layer] / [database layer] / [plugin layer]). **A [database layer] report means the tunnel is already up**; with a tunnel configured, press "Test SSH tunnel" first to verify the SSH layer on its own. |
 | The configure page is not visible | Check the plugin is installed: restart `dsh web` on the web side; on desktop use the Configure control on the Plugins row or the DBHub entry in the left menu. The page only shows in the Web / desktop UI and does not affect tool usage in terminal environments. |
-| The old UI is still shown after upgrading | The new UI needs **DSH 0.2.1+** (prereleases included) and plugin 5.2.0+; restart after upgrading dsh. On DSH 0.1.x the plugin deliberately keeps the old layout and behaviour and shows no update hint. |
+| The configure page says the DSH version is too old | The plugin needs **DSH 0.2.1+** (prereleases included); upgrade dsh and restart. The tools and the page keep working until you do — the notice is only a reminder. |
 | No "Upgrade to …" hint appears in the header | You may already be on the latest version, or this check could not reach the npm registry / GitHub Releases; press "Check for updates" to retry. A failed check is only a hint and does not affect plugin functionality. |
 | How do I upgrade on desktop | Uninstall on the **left menu → Plugins** page, then reinstall the latest version; connections and credentials live in `~/.dsh/storages/dsh-dbhub-live` and are still there after the reinstall. |
-| After a dsh upgrade the plugin is reported as incompatible | Upgrade the plugin to 5.0.0+ (it supports both 0.1.x and 0.2.x); forcing it through with `allow-version` buys nothing. |
+| After a dsh upgrade the plugin is reported as incompatible | Check that dsh is 0.2.1 or later, then upgrade the plugin to the latest version; forcing it through with `allow-version` buys nothing. |
 | Automatic dbhub updates are not wanted | Set "Auto-update interval (days)" to `0` on the configure page and save, or set `DSH_DBHUB_UPDATE_DAYS=0`. |
 
 **Environment variables** (only these two, not exposed in the UI): `DSH_DBHUB_PACKAGE` (the package that gets auto-installed, default `@bytebase/dbhub`), `DSH_DBHUB_UPDATE_DAYS` (the seed for the auto-update interval, default `7`, overridden by the value saved on the configure page).
 
+## Changelog
+
+Highlights of every released version live in [doc/CHANGELOG.md](https://github.com/mr-mihu/dsh-dbhub-live/blob/dev/doc/CHANGELOG.md); per-release notes are on [GitHub Releases](https://github.com/mr-mihu/dsh-dbhub-live/releases).
+
 ## License
 
 [MIT](./LICENSE)

package/README.md

@@ -15,7 +15,7 @@
 <details>
 <summary>📷 界面预览：设置 → DBHub 数据库工具</summary>
 
-![DBHub 数据库工具配置页](doc/images/settings-page.png)
+![DBHub 数据库工具配置页](https://raw.githubusercontent.com/mr-mihu/dsh-dbhub-live/dev/doc/images/settings-page.png)
 
 </details>
 
@@ -33,26 +33,24 @@
 
 支持 **MySQL · PostgreSQL · MariaDB · SQLite · SQL Server**。
 
-<!-- release-test:versions:begin -->
-## 支持的版本范围
-
-**DSH 0.1.5 起（0.1.5 / 0.1.6 / 0.1.7 / 0.2.0 / 0.2.1 共 5 条版本线，含预发布）** — 6 个声明版本已实测通过（最近验证 2026-10-24）。
-
-<details>
-<summary>逐版本实测明细（点开查看）</summary>
-
-| DSH 版本 | 界面 | 启动 | 硬检查 | 结论 | 最近验证 |
-| --- | --- | --- | --- | --- | --- |
-| `0.1.5-rc.3` | 旧版 | 7.3s | 19 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 4f6a854a |
-| `0.1.6-alpha.2` | 旧版 | 3.5s | 19 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 4f6a854a |
-| `0.1.7-rc.2` | 旧版 | 4.7s | 20 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 4f6a854a |
-| `0.2.0-rc.2` | 旧版 | 4.9s | 20 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 4f6a854a |
-| `0.2.1-alpha.1` | 新版 | 5.1s | 20 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 4f6a854a |
-| `0.2.1-rc.2` | 新版 | 5.3s | 20 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 4f6a854a |
-
-</details>
-
-完整证据、判定规则与已知偏差见 [doc/SUPPORT-MATRIX.md](doc/SUPPORT-MATRIX.md)。
+<!-- release-test:versions:begin -->
+## 支持的版本范围
+
+**DSH 0.2.1 起（0.2.1 / 0.2.2 共 2 条版本线，含预发布）** — 4 个声明版本尚未全部通过（最近验证 2026-10-24）。
+
+<details>
+<summary>逐版本实测明细（点开查看）</summary>
+
+| DSH 版本 | 界面 | 启动 | 硬检查 | 结论 | 最近验证 |
+| --- | --- | --- | --- | --- | --- |
+| `0.2.1-rc.2` | 新版 | 16.9s | 20 | ⚠️ 通过（有告警） · 手工装配 | 2026-10-24 · 91642fa2 |
+| `0.2.1-rc.5` | 新版 | — | — | — | 未验证 |
+| `0.2.2-rc.1` | 新版 | — | — | — | 未验证 |
+| `0.2.2-rc.2` | 新版 | — | — | — | 未验证 |
+
+</details>
+
+完整证据、判定规则与已知偏差见 [doc/SUPPORT-MATRIX.md](https://github.com/mr-mihu/dsh-dbhub-live/blob/dev/doc/SUPPORT-MATRIX.md)。
 <!-- release-test:versions:end -->
 
 ## 安装
@@ -73,7 +71,7 @@ npx @deepseek-ai/dsh plugin --profile desktop add dsh-dbhub-live
 
 装完 web 端**重启 `dsh web`**，打开 **设置 → DBHub 数据库工具** 即可看到配置页（也有左侧栏快捷入口和插件页那行的「配置」，三个入口是同一个页面）。
 
-> 环境要求：`dsh` 0.1.5 起的全部版本线（含 0.2.x）；**新界面需要 0.2.1+**（含 0.2.1 的预发布版）——宽屏整页、页头版本与升级提示、行内只读开关都只在 0.2.1 及以上出现；**0.1.x 仍受支持，但保持旧版布局与行为**。建议本机有 Node.js ≥ 18（用于自动安装 dbhub）。**只读模式与 SSH 隧道需要 dbhub 1.4.0+**，插件会自动检测并给出升级指引。每个版本的实测记录见 [doc/SUPPORT-MATRIX.md](doc/SUPPORT-MATRIX.md)（由发布测试自动生成，发版前必跑）。
+> 环境要求：**DSH 0.2.1 或更高版本**（含 0.2.1 的预发布版；**0.1.x 与 0.2.0 不再支持**）。宿主版本过旧时插件不会变成空白：配置页顶部会显示一条中英双语提示（写明所需版本与当前版本），工具、连接与设置照常可用——但请尽快升级 DSH。建议本机有 Node.js ≥ 18（用于自动安装 dbhub）。**只读模式与 SSH 隧道需要 dbhub 1.4.0+**，插件会自动检测并给出升级指引。每个版本的实测记录见 [doc/SUPPORT-MATRIX.md](https://github.com/mr-mihu/dsh-dbhub-live/blob/dev/doc/SUPPORT-MATRIX.md)（由发布测试自动生成，发版前必跑）。
 
 ## 更新
 
@@ -87,9 +85,9 @@ dsh plugin --profile web up dsh-dbhub-live@<最新版本号>
 
 **桌面端**：在 **左侧菜单 → 插件** 页里卸载该插件，再重新安装最新版本（桌面端更新走可视化插件页）。**连接与凭据不会被重装清掉**——它们都在 `~/.dsh/storages/dsh-dbhub-live`，与模块目录无关。
 
-**不用自己记版本号**：配置页页头显示插件名与当前版本，检测到更新时会出现一行低调的「**↑ 可升级到 <latest>**」文字链接，**点一下就会复制** `dsh-dbhub-live@<latest>`；旁边的「检查更新」按钮可以随时手动检查。打开页面时也会自动检查一次（有节流，不会每次打开都打网络）。检查以 **npm registry 为主、GitHub Releases 为兜底**，发布说明见 [GitHub Releases](https://github.com/mr-mihu/dsh-dbhub-live/releases)。
+**不用自己记版本号**：配置页页头显示插件名与当前版本，检测到更新时会出现一行低调的「**↑ 可升级到 <latest>**」文字链接，**点开后在面板里点一下即可复制** `dsh-dbhub-live@<latest>`；旁边的「检查更新」按钮可以随时手动检查。打开页面时也会自动检查一次（有节流，不会每次打开都打网络）。检查以 **npm registry 为主、GitHub Releases 为兜底**，发布说明见 [GitHub Releases](https://github.com/mr-mihu/dsh-dbhub-live/releases)。
 
-> 版本与升级提示属于新界面，需要插件 5.2.0+ 且 DSH 0.2.1+；0.1.x 上不显示（见「配置页」）。
+> 版本与升级提示需要插件 5.2.0+ 且 DSH 0.2.1+（见「配置页」）。
 
 ## 快速开始
 
@@ -105,7 +103,7 @@ AI：…（返回查询结果）
 <details>
 <summary>📷 实际效果：向 AI 提问，直接拿到查询结果</summary>
 
-![向 AI 提问并拿到查询结果](doc/images/chat-query.png)
+![向 AI 提问并拿到查询结果](https://raw.githubusercontent.com/mr-mihu/dsh-dbhub-live/dev/doc/images/chat-query.png)
 
 </details>
 
@@ -149,11 +147,11 @@ AI：…（返回查询结果）
 <details>
 <summary>📷 连接行编辑器：只读模式与 SSH 隧道</summary>
 
-![连接行与「测试 SSH 隧道」](doc/images/row-editor.png)
+![连接行与「测试 SSH 隧道」](https://raw.githubusercontent.com/mr-mihu/dsh-dbhub-live/dev/doc/images/row-editor.png)
 
 </details>
 
-同一套组件提供**三种布局**，按承载位与窗口宽度自动切换（新界面需要插件 5.2.0+ 且 **DSH 0.2.1+**；DSH 0.1.x 上保持旧版布局与行为，见本节末尾）：
+同一套组件提供**三种布局**，按承载位与窗口宽度自动切换（需要插件 5.2.0+ 且 **DSH 0.2.1+**，见本节末尾）：
 
 | 布局 | 进入方式 | 形态 |
 | --- | --- | --- |
@@ -163,16 +161,17 @@ AI：…（返回查询结果）
 
 **页头：版本与升级入口**：标题是插件名，紧跟当前版本（灰色小字）；有更新时右侧出现一行低调的「**↑ 可升级到 <latest>**」文字链接，**点开才展开**更新说明——里面是 `dsh-dbhub-live@<latest>`（点击复制）、按部署方式给的更新命令 / 步骤，以及更新说明链接；「↻」按钮随时手动检查一次。打开页面时也会自动检查（有节流）。检查以 npm registry 为主、GitHub Releases 为兜底。**更新是中性提示，不会用报错红。**
 
-- **状态行**：只显示「运行中 / 已停用 · N 个连接」。工具数量、一次性执行模式、dbhub 版本这类实现细节收进页面底部的「ⓘ 说明与技术详情」折叠区，默认不展开。
+- **状态行**：只显示「运行中 / 已禁用 · N 个连接」。工具数量、一次性执行模式、dbhub 版本这类实现细节收进状态行下方的「ⓘ 说明」折叠区，默认不展开。
 - **连接列表**：按工作区组织。所有工作区都只有一个环境时用平铺卡片；任一工作区有多个环境时按工作区分组折叠（点组头展开，默认展开最近使用的那个）。每个连接只占一行：环境名 · 类型 / 主机 / 端口 / **库名** · **只读开关** · `source` 句柄（点它即复制） · 测试 / 修改 / 删除。窄窗口下先截断主机端口，**库名始终可见**。
-- **设置区（DSH 主体样式，刻意弱化）**：宽屏把四项收成**一行紧凑设置条**——`插件设置 · 启用插件[启用] · 侧边栏入口[显示] · 访问策略[开启] · 自动更新[7]天[保存] · ⓘ说明`；弹窗与手机是紧凑设置行。字号与开关都收小，让**连接列表**成为页面主体。控件用 DSH 自己的开关（跟随主题 / 皮肤，带汉字状态词）；解释性长文字都在「ⓘ 说明与技术详情」里。
+- **设置区（DSH 主体样式，刻意弱化）**：宽屏把四项收成**一行紧凑设置条**——`插件设置 · 启用插件[启用] · 侧边栏入口[显示] · 访问策略[开启] · 自动更新[7]天[保存] · ⓘ说明`；弹窗与手机是紧凑设置行。字号与开关都收小，让**连接列表**成为页面主体。控件用 DSH 自己的开关（跟随主题 / 皮肤，带汉字状态词）；解释性长文字都在「ⓘ 说明」里。
 - **只读开关（三种布局都在外面）**：每条连接行的数据源旁边就是该环境的「只读」小开关，点一下即改（开锁图标 + 「可写」= 可写；闭锁图标 + 「只读」= 已只读），不必打开编辑表单；弹窗 / 手机同样可用。编辑表单里的勾选也保留，两处是同一个状态。**连接串本身不再带锁形图标**——过去容易被误读成"需要密码"，也和只读锁冲突。
-- **增删改**：行内 ✏ 改连接串或环境名；「＋ 添加连接」支持中文环境名。**同名环境保存前会先问「是否覆盖」**，取消则一个字都不写。
-- **连接测试**：按该环境**真正会被使用的有效连接**（含只读 / 隧道）执行 `SELECT 1`，测试中显示已耗时。结果是一次性反馈，不持久化、不改变连接状态。
+- **增删改**：行内 ✏ 改连接串或环境名；「＋ 添加连接」支持中文环境名。**同名环境保存前会先问「是否覆盖」**，取消则一个字都不写。**删除也要先确认**（这条不可撤销，取消同样零写入）。
+- **写失败一定看得见**：保存 / 开关 / 删除被拒（401、离线、宿主拒绝）时页面上会出现一行错误提示，**不会**再显示「已保存 ✓」，改好后再点一次就是重试；读取不到插件状态时也会给出错误行 + 「重试」，不会悄悄变成"没有连接"。「自动更新间隔」只接受 0–365 的整数天，留空或填小数会当场提示、不发请求。
+- **连接测试**：按该环境**真正会被使用的有效连接**（含只读 / 隧道）执行 `SELECT 1`，测试中显示已耗时。结果是一次性反馈，不持久化、不改变连接状态。命令没能送到宿主（例如桥接 401 / 离线）时会立刻说「测试命令未能送达宿主」，而不是等 30 秒后报「测试超时」。
 
 **「在侧边栏显示入口」不是禁用插件**：关掉它只是隐藏左侧栏的快捷入口，插件照常工作、模型照常可以查询；想整体停用才用「禁用」（禁用后入口一律隐藏）。无论哪种状态，**设置页与插件页那行的「配置」始终能进**，随时可以撤销。
 
-**DSH 0.1.x 的兼容路径**：页头版本 / 升级提示、宽屏整页、行内只读开关与开关样式的设置区都只在 **DSH 0.2.1+**（含预发布版）渲染；0.1.x 上插件保持原有布局与行为，**不显示升级提示**——这是刻意保留的，不是缺陷。
+**DSH 版本过低时**：配置页顶部会多出一条警告（写明「需要 DSH 0.2.1 或更高版本」与本机版本），页面、连接、只读开关与工具全部照常工作——这不是"插件坏了"，只需升级 DSH。
 
 ## 🔒 只读模式与 SSH 隧道
 
@@ -238,14 +237,18 @@ dsh plugin --profile desktop remove dsh-dbhub-live
 | 只读 / SSH 控件是灰的，或提示 dbhub 版本过旧 | 两项都需要 dbhub 1.4.0+：升级 dbhub，或删除 `~/.dsh/storages/dsh-dbhub-live` 让插件自动装一个满足要求的版本。 |
 | 连接测试失败，看不出原因 | 读提示的**末尾**（诊断给的是 dbhub 输出的尾部，会标出【SSH 层】/【数据库层】/【插件层】）。**报【数据库层】就说明隧道已经通了**；有隧道时先点「测试 SSH 隧道」把 SSH 层单独验一遍。 |
 | 看不到配置页 | 确认插件已安装：web 端重启过 `dsh web`；桌面端在「插件」页该行点「配置」，或从左侧菜单的 DBHub 入口进。配置页只在 Web / 桌面界面显示，终端环境下不影响工具使用。 |
-| 升级到新版本后仍是旧界面 | 新界面需要 **DSH 0.2.1+**（含其预发布版）且插件 5.2.0+；升级 dsh 后重启。DSH 0.1.x 上插件有意保持旧布局与行为，也不显示升级提示。 |
+| 配置页顶部提示「DSH 版本过旧」 | 插件最低支持 **DSH 0.2.1**（含其预发布版）；升级 dsh 后重启即可。升级前工具与页面仍可用，提示只是提醒。 |
 | 页头没有出现「升级到 …」提示 | 可能已是最新版本，或这次检查没连上 npm registry / GitHub Releases；点「检查更新」重试即可。检查失败只是提示，不影响插件功能。 |
 | 桌面端怎么升级 | 在 **左侧菜单 → 插件** 页卸载后重装最新版本；连接与凭据在 `~/.dsh/storages/dsh-dbhub-live`，重装后仍在。 |
-| 升级 dsh 后提示插件与本版不兼容 | 升级插件到 5.0.0+（同时支持 0.1.x 与 0.2.x）；用 `allow-version` 强行豁免没有意义。 |
+| 升级 dsh 后提示插件与本版不兼容 | 先确认 dsh ≥ 0.2.1，再把插件升级到最新版；用 `allow-version` 强行豁免没有意义。 |
 | 不希望自动更新 dbhub | 配置页「自动更新间隔(天)」填 `0` 保存，或设环境变量 `DSH_DBHUB_UPDATE_DAYS=0`。 |
 
 **环境变量**（仅这两项，不在 UI 暴露）：`DSH_DBHUB_PACKAGE`（自动安装的包名，默认 `@bytebase/dbhub`）、`DSH_DBHUB_UPDATE_DAYS`（自动更新间隔种子，默认 `7`，被配置页保存的值覆盖）。
 
+## 版本历史
+
+每个正式版本的变更摘要见 [doc/CHANGELOG.md](https://github.com/mr-mihu/dsh-dbhub-live/blob/dev/doc/CHANGELOG.md)；逐版本的发布说明在 [GitHub Releases](https://github.com/mr-mihu/dsh-dbhub-live/releases)。
+
 ## 许可证
 
 [MIT](./LICENSE)

package/lib/adhoc.mjs

@@ -18,12 +18,14 @@
 //                               file holds placeholders only; the real secrets
 //                               ride the CHILD's environment (see toml.mjs).
 
-import { DATA_DIR, connLabel, scrubSecrets, normalizeSshOptions, expandHome, withDefaultSshKey, DEFAULT_SSH_KEY_PATH } from './config.mjs'
+import { DATA_DIR, connLabel, scrubSecrets, normalizeSshOptions, expandHome, withDefaultSshKey, DEFAULT_SSH_KEY_PATH, warnOnce } from './config.mjs'
 import { buildSpawnArgv, resolveDbhubExe } from './runtime.mjs'
-import { createMcpClient, disabledMessage } from './mcp.mjs'
+import { createMcpClient, disabledMessage, MCP_INIT_TIMEOUT_MS, MCP_CALL_TIMEOUT_MS } from './mcp.mjs'
 import { buildDbhubToml, writeTempToml, removeTempToml } from './toml.mjs'
 import { detectDbhubCapabilities } from './capability.mjs'
+import { readPluginVersion } from './meta.mjs'
 import { currentT } from './i18n.mjs'
+import { StringDecoder } from 'node:string_decoder'
 import { existsSync } from 'node:fs'
 import { connect } from 'node:net'
 import * as state from './state.mjs'
@@ -70,6 +72,14 @@ export function secretsOf(conn) {
 export const PROBE_TIMEOUT_MS = 25000
 export const PROBE_TIMEOUT_SSH_MS = 45000
 
+/**
+ * How long a finished call waits for the child to actually exit before it stops
+ * waiting and simply warns. `waitForExit` never settles when a descendant escaped
+ * the managed process group (the host documents that as out of its control), and
+ * an unbounded await there would hang the call the timeouts above just bounded.
+ */
+export const EXIT_WAIT_MS = 5000
+
 /** Host-side probe cap for one connection (tunnelled connections get more). */
 export function hostTimeoutFor(conn) {
   return needsToml(conn) && normalizeConn(conn).ssh ? PROBE_TIMEOUT_SSH_MS : PROBE_TIMEOUT_MS
@@ -383,11 +393,18 @@ export async function probeSshTunnel(subprocess, ssh, timeoutMs) {
 
 /**
  * Run ONE MCP tool call against a disposable dbhub process.
+ *
+ * Both requests carry a request-level budget (see lib/mcp.mjs): `exec.signal` only
+ * fires on a user cancel / turn interruption, so a dbhub that is alive but silent
+ * would otherwise hold this call — and the whole conversation round — forever.
+ * `exec.mcpTimeoutMs` shrinks the CALL budget (the robustness test proves the
+ * timeout path in milliseconds); production passes no value.
+ *
  * @param subprocess - host subprocess service.
  * @param conn - `{ dsn, ro, ssh }` (a bare DSN string means "no options").
  * @param rawName - the MCP tool name (`execute_sql` / `search_objects`).
  * @param mcpArgs - the tool arguments.
- * @param exec - `{ signal, agent? }`.
+ * @param exec - `{ signal, agent?, mcpTimeoutMs? }`.
  * @param label - optional pre-localized header line.
  * @returns `{ ok, text }` (already scrubbed and metadata-labelled).
  */
@@ -422,7 +439,14 @@ export async function runAdhoc(subprocess, conn, rawName, mcpArgs, exec, label)
       const built = buildDbhubToml({ dsn: c.dsn, ro: c.ro, ssh: c.ssh })
       tomlPath = writeTempToml(built.text)
       // Secrets travel in the CHILD's environment; the file only holds `${VAR}`.
-      childEnv = { ...process.env, ...built.env }
+      // ONLY the generated names: spreading `process.env` here would hand the
+      // spawn a scrubbed-away ambient environment all over again (the host
+      // subprocess service strips `*KEY|PASSWORD|SECRET|TOKEN*` and `DSH_*` from
+      // the inherited env, and merges an explicit `env` AFTER that scrub), so the
+      // child — and every third-party package inside dbhub — could read the
+      // agent's own API keys. Absent names simply resolve from the scrubbed
+      // parent env the service provides.
+      childEnv = { ...built.env }
       argv = ['--transport', 'stdio', '--config', tomlPath]
     } catch (e) {
       removeTempToml(tomlPath)
@@ -447,17 +471,30 @@ export async function runAdhoc(subprocess, conn, rawName, mcpArgs, exec, label)
     return { ok: false, text: currentT('result.dbhubSpawnFailed', { msg: String((e && e.message) || e) }) }
   }
   let stderrTail = ''
+  const callTimeoutMs = Number.isFinite(exec && exec.mcpTimeoutMs) && exec.mcpTimeoutMs > 0
+    ? exec.mcpTimeoutMs
+    : MCP_CALL_TIMEOUT_MS
   try {
+    // Decode across chunk boundaries: dbhub's banner and connection errors are
+    // often non-ASCII, and a split multibyte character would surface as U+FFFD in
+    // the diagnostic tail the user has to read.
+    const stderrDecoder = new StringDecoder('utf8')
     const client = createMcpClient(handle, (chunk) => {
-      stderrTail = (stderrTail + String(chunk)).slice(-2000)
+      const piece = typeof chunk === 'string' ? chunk : stderrDecoder.write(chunk)
+      stderrTail = (stderrTail + piece).slice(-2000)
     })
     await client.request('initialize', {
       protocolVersion: '2025-03-26',
       capabilities: {},
-      clientInfo: { name: 'dsh-dbhub-adhoc', version: '3.0.0' },
-    })
+      // dbhub logs this in its own diagnostics. The literal '3.0.0' that used to
+      // sit here named a version this plugin never was — a report from a user on
+      // 5.x pointed the maintainer at the wrong code. `meta` is a LEAF, so reading
+      // the installed version here cannot create a cycle; a detached copy of the
+      // package (no readable package.json) degrades to '0.0.0'.
+      clientInfo: { name: 'dsh-dbhub-adhoc', version: readPluginVersion() || '0.0.0' },
+    }, { timeoutMs: MCP_INIT_TIMEOUT_MS })
     client.notify('notifications/initialized')
-    const res = await client.request('tools/call', { name: rawName, arguments: mcpArgs })
+    const res = await client.request('tools/call', { name: rawName, arguments: mcpArgs }, { timeoutMs: callTimeoutMs })
     const textOf = (r) => {
       if (r && Array.isArray(r.content)) {
         const parts = []
@@ -469,16 +506,45 @@ export async function runAdhoc(subprocess, conn, rawName, mcpArgs, exec, label)
     // Zero-knowledge surface: the header carries metadata only (host/port/db),
     // and every line — including dbhub's own error text — is scrubbed before
     // it can reach the model (the SSH password / passphrase included).
-    const prefix = (label !== undefined && label !== null
+    // The prefix itself goes through the same scrubber: it is built from
+    // `connLabel` AND from a caller-supplied `label`, and a caller that ever
+    // pastes a DSN into it must not bypass the gate the body passes through.
+    const header = label !== undefined && label !== null
       ? String(label)
-      : currentT('label.adhocConn', { dsn: connLabel(c.dsn) })) + '\n'
+      : currentT('label.adhocConn', { dsn: connLabel(c.dsn) })
+    const prefix = scrubSecrets(header, c.dsn, extraSecrets) + '\n'
     if (res && res.isError) return { ok: false, text: prefix + scrubSecrets(textOf(res), c.dsn, extraSecrets) }
     if (res && res.structuredContent !== undefined) {
       return { ok: true, text: prefix + scrubSecrets(JSON.stringify(res.structuredContent, null, 2), c.dsn, extraSecrets) }
     }
     return { ok: true, text: prefix + scrubSecrets(textOf(res), c.dsn, extraSecrets) }
   } catch (e) {
-    let detail = String((e && e.message) || e)
+    const code = e && e.code
+    let detail
+    if (code === 'MCP_TIMEOUT' || code === 'MCP_TOO_LARGE') {
+      // Kill the wedged process BEFORE the report is assembled: `finally` runs
+      // after this frame, and a dbhub that ignored one request will ignore the
+      // next. The temp TOML is still removed by `finally`.
+      try {
+        handle.terminate()
+      } catch (err) {
+        /* ignore */
+      }
+    }
+    if (code === 'MCP_TIMEOUT') {
+      const sec = Math.max(1, Math.round((Number(e.timeoutMs) || 0) / 1000))
+      detail = currentT('result.mcpTimeout', { sec: String(sec) })
+    } else if (code === 'MCP_TOO_LARGE') {
+      const limitBytes = Number(e.limitBytes) || 0
+      detail = currentT('result.mcpTooLarge', {
+        what: currentT(e.limitKind === 'line' ? 'result.mcpTooLargeLine' : 'result.mcpTooLargeTotal'),
+        limit: String(Math.round((limitBytes / (1024 * 1024)) * 10) / 10) + ' MiB',
+      })
+    } else {
+      detail = String((e && e.message) || e)
+    }
+    // Never echo a query/params/DSN: only the localized sentence plus (already
+    // length-capped) stderr, which the scrubber below rewrites.
     if (stderrTail) detail += '\n[dbhub stderr] ' + stderrTail
     return { ok: false, text: scrubSecrets(detail, c.dsn, extraSecrets) }
   } finally {
@@ -487,10 +553,40 @@ export async function runAdhoc(subprocess, conn, rawName, mcpArgs, exec, label)
     } catch (e) {
       /* ignore */
     }
+    let exited
+    // The host contract answers `false` when the signal was already aborted and
+    // the process is STILL alive. The return value used to be dropped, so the
+    // temp config was deleted as if the child had exited (Windows: EBUSY) and
+    // the only trace was a once-per-process warnOnce.
+    //
+    // The wait itself is bounded: a descendant that escaped the managed process
+    // group can make `waitForExit` never settle, which would hang the very call
+    // this batch set out to make bounded. A timeout here is treated exactly like
+    // `false` (try once more, then warn).
+    let exitTimer = null
+    const exitWaitMs = Number.isFinite(exec && exec.exitWaitMs) && exec.exitWaitMs > 0
+      ? exec.exitWaitMs
+      : EXIT_WAIT_MS
     try {
-      await handle.waitForExit(exec.signal)
+      exited = await Promise.race([
+        Promise.resolve(handle.waitForExit(exec.signal)).catch(() => undefined),
+        new Promise((resolve) => {
+          exitTimer = setTimeout(() => resolve('timeout'), exitWaitMs)
+        }),
+      ])
     } catch (e) {
       /* ignore */
+    } finally {
+      if (exitTimer) clearTimeout(exitTimer)
+    }
+    if (exited === false || exited === 'timeout') {
+      try {
+        handle.terminate()
+      } catch (e) {
+        /* ignore */
+      }
+      // No path, no DSN: just the fact (said once per process).
+      warnOnce('adhoc-exit-pending', currentT('result.processStillRunning'))
     }
     // Best effort: the temp file holds no secret, but it must not accumulate.
     removeTempToml(tomlPath)