dsh-sidecard-ask 1.9.1 → 2.0.0

package/CHANGELOG.md

@@ -1,5 +1,83 @@
 # Changelog
 
+## 2.0.0
+
+**主题：追问卡片标题栏的 `×` 从「隐藏整个浮层」改成「删除这条追问对话」——一次 Breaking 的语义重定义，顺带把「隐藏浮层」这套能力整体下线，并移除反馈表单里「用邮件客户端发送」这条出口。**
+
+`×` 原来是全局开关：点一下整个浮层缩成一个带计数的圆点，再点圆点恢复。用户实际想要的是**删掉眼前这条追问**，
+而当时删除只能绕两条路走（卡片底部按钮 / 设置页历史管理器），且 `×` 的「隐藏」在多卡场景下会连着别的卡片一起收走。
+2.0.0 把 `×` 直接对齐到用户心智，并**不再保留**「隐藏整个浮层」这套能力（不是挪位置，是不留替代入口）。
+
+### Breaking
+
+- **`×` 语义变更**：卡片标题栏最右侧的 `×` 由「隐藏整个浮层」改为「**删除这条追问对话**」，`title` / `aria-label`
+  改用新键 `cardDelete`。删除会同时从活动卡片列表与持久历史里移除该卡片，**不可撤销**。
+- **`floatMode` 移除 `off`**：枚举从 `['capsule', 'full', 'off']` 收窄为 `['capsule', 'full']`，设置页该下拉只剩两项。
+  旧配置里存过 `'off'` 的**无需手工迁移**：宿主 `sanitizeLayer` 判定为非法值 → 忽略并在 `problems` 里提示，
+  回退默认 `capsule`（不写迁移代码，也不静默改写用户配置）。
+- **小圆点 launcher 删除**：浮层不再有「只剩一个计数圆点」的形态，相关渲染分支、样式与恢复入口一并删除。
+  浮层只剩 `capsule`（一行高胶囊）与 `full`（完整卡片栈，铺满右栏 dock 时为 `dock`）。
+- **删除 4 个 i18n 键**：`setFloatModeOff`（设置页「隐藏」项）、`floatHide`（`×` 的旧 title）、
+  `floatRestore`（从圆点恢复浮层的入口）、`floatCount`（圆点计数）。`floatStreaming` / `floatDone` 保留（胶囊仍在用）。
+
+### 新增：删除交互
+
+- **空卡直接删**：该卡无任何已完成追问轮（`history.length === 0`）且主回答正文与思考过程都为空、且不在作答中
+  （非 `pending` / `streaming`）时，点 `×` **直接删除，不弹确认**。
+- **其余情况弹插件内轻量确认层**（`DeleteConfirmDialog`，不使用 `window.confirm`）：标题「删除这条追问对话？」，
+  正文说明会同时从浮层与追问历史里移除、不可撤销；已有追问轮次时追加一行「含 {n} 轮追问」；
+  两个按钮「取消」/「删除」（删除为危险色 `.dsa-btn-danger`）。
+- **无障碍与误触防护**：`role="dialog"` / `aria-modal="true"` / `aria-label` 取标题；默认焦点固定在被标记 `autoFocus`
+  的「取消」上（不落在危险按钮，防连按 Enter）；`Esc` 取消（`stopPropagation`，不冒泡到卡片自身的 Esc 处理）、
+  点遮罩取消（仅当 `event.target === event.currentTarget`）；确认层打开时卡片的 `R` / `C` / `Esc` 快捷键全部失效。
+- **流式中删除**：先 `abort()` 中止请求 + 通知宿主 `cancel`，丢弃该卡进行中的增量缓冲（`pendingDeltas` / `pendingReasonings`），再执行删除。
+- **删除动作顺序固定**：按同一 `id` 从 `history` 与 `cards` 双移除 → 立即写盘持久化 → 关闭该卡已打开的侧栏 / host tab 表面
+  → 浮层 toast「已删除这条追问对话」（2600ms 自动消失）。
+- **删除后重排**：剩余卡片按原顺序塌缩补位；删掉最后一张时 `total === 0` → 浮层整体不渲染（无空态）。
+- **上下文隔离**：每张卡的追问上下文本就按卡隔离，删除不影响其它卡片；后续生成只读取剩余卡片自身历史。
+
+### 移除：反馈表单的「用邮件客户端发送」出口
+
+- **UI**：反馈弹窗从三条出口减到两条（`发送` / `复制内容`），删掉 `data-feedback-mailto` 按钮与
+  `sendFeedbackByMailApp()`；没有发信服务时弹窗仍按两种就绪状态说明缺什么，并指向「复制内容」。
+- **Host**：删掉 `POST /feedback-mailto` 路由、`buildMailtoUrl()` 构造器与 `API_METHODS` 里的条目。
+  未命中的方法由既有兜底返回 `404 not-found`（`error.message` 带方法名），旧页面调用会明确失败而不是静默。
+- **`/state`**：`capabilities.feedback.transport` 在未配置时由 `'mailto'` 改为 `'none'`；`reason` 只回 SMTP 的原因。
+- **i18n**：`feedbackMailto` 删除，`feedbackMailtoOnly` 重命名为 `feedbackNoCredentials`（文案改指向「复制内容」），
+  `feedbackUnconfigured` 同步改写；zh/en 两侧键集仍然完全一致。
+- **理由**：这条出口只是把同一封邮件交给系统邮件应用，与「复制内容」的实际效果重叠，却让 Host 多出一个
+  任何人都能调的 URL 构造接口（还会把明文收件地址拼进 URL）。删掉它，反馈的发送面只剩 SMTP 一条。
+- **测试**：`test/contract-test.mjs` 删除 `buildMailtoUrl` / 路由 200 / 按钮存在三类断言，改为断言
+  `transport === 'none'`、`/feedback-mailto` 两次 404（有/无收件人）、`data-feedback-mailto` 不存在、
+  两个退役 i18n 键在 zh/en 都是 `undefined`（`node test/verify.mjs` 的 `t()` 键扫描同时覆盖新键名）。
+
+### 清理：1.9.1 遗留的 10 个死 i18n 键
+
+- **删掉 10 个 `feedbackSmtp*` 标签键**：`feedbackSmtpShow` / `feedbackSmtpHide` / `feedbackSmtpEnvNote` /
+  `feedbackSmtpHost` / `feedbackSmtpSecure` / `feedbackSmtpPassSaved` / `feedbackSmtpPass` / `feedbackSmtpFrom` /
+  `feedbackSmtpHint` / `feedbackSmtpSaveHint`。它们只属于 1.9.1 删掉的设置页 SMTP 表单，全仓已无任何
+  `t('feedbackSmtp…')` 调用点，留着只是让翻译者以为这些输入框还在。
+- **配置键不动**：`feedbackSmtpHost` / `feedbackSmtpPort` / `feedbackSmtpSecure` / `feedbackSmtpUser` /
+  `feedbackSmtpPass` / `feedbackSmtpFrom` 作为 `config.json` 字段与 `client.js` 的 `CLIENT_DEFAULTS` 继续存在，
+  按环境变量或用户层配置生效；删的只是同名的**界面标签**。
+- **zh/en 同步删**，键集仍完全一致；`test/contract-test.mjs` 的退役键断言扩到 12 个键（含上一节的两个），
+  两个字典都必须取到 `undefined`。
+
+### 兼容性与边界
+
+- **不涉及**：无服务端会话存储、无多端同步、无遥测埋点（这些维度 N/A）；删除不进「回收站」，**不提供撤销**
+  （无 Undo、无快照、无 5 秒窗口）。
+- **承载面差异**：`×` 只出现在**浮层 / 内嵌浮层**（含 dock 到右侧栏的浮层卡片）上。被宿主 tab 承载的同一张卡
+  （`better-sidebar` / `native-rightbar` 独立标签页）**不提供 `×`**，沿用它自己的标签关闭 + 底部「关闭」——
+  「关闭」只把卡片摘离浮层、**历史仍保留**在设置页历史管理器里，与「删除」是两种真实需求。
+- **版本号**：`1.9.1 → 2.0.0`，三处同步（`package.json` 的 `version`、`index.js` 的 `PLUGIN_VERSION`、`client.js` 的 `CLIENT_VERSION`）。
+- **测试**：`test/float-placement.mjs` 增补 2.0.0 行为断言（无 `dsa-launcher` / `floatRestore`、`floatControl('capsule')` 存在、
+  `onDelete` 已接线、无 `mode === 'off'` 渲染分支、`floatMode` 默认 `capsule`）；`test/contract-test.mjs` 增补
+  `sanitizeLayer` 丢弃 `'off'`、设置页 option 序列为 `['capsule','full']`、卡片头恰有一枚 `aria-label === cardDelete` 的按钮、
+  `deleteCard` 的四类行为、4 个已删键为 `undefined`。
+- **文档**：README 的配置表 / dock 形态说明 / 自测第 8–9 条同步改写，反馈章节的「三条出口」表改为两条并记下移除理由；
+  `docs/PRD-followup-delete.md` 出 v3 修订（D0 定稿 + 隐藏能力下线 + 规格逐条对齐已交付代码，路由清单去掉 `feedback-mailto`）。
+
 ## 1.9.1
 
 **主题：反馈入口重做——从「设置页里一整块常驻表单」改成「顶部一行横幅 + 居中弹窗」。**

package/README.md

@@ -22,7 +22,8 @@
 
 > **1.5.0 增强一览**（详见 CHANGELOG）：内置浮层不再压住主对话——宽度改由纯函数 `floatPlacement`
 > 按「对话区右侧可用带宽」计算（旧实现是固定 400px，在用户截图上压入正文约 113px）；浮层默认是**一行高的胶囊**，
-> 可随时「收起 / 隐藏」，运行时的形态切换不写回配置；新增 `floatMode`（默认 `capsule`）与
+> 可随时「收起为胶囊」，运行时的形态切换不写回配置；卡片标题栏右侧的 `×` 自 2.0.0 起是**删除这条追问对话**
+> （连同追问历史一起删），不再是隐藏浮层；新增 `floatMode`（默认 `capsule`）与
 > `floatMaxWidth`（默认 340）两项设置；卡片阴影减半。
 
 > **1.4.0 增强一览**（详见 CHANGELOG）：卡片**思考过程**（reasoning）可折叠展示并随答案流式渲染；
@@ -163,9 +164,9 @@ plugin_manager(action="install_bundle", target="D:\\Users\\34332\\AI\\dsh-sideca
 | `defaultCarrier` | `main` \| `side` | `side` | **默认作答位置**：提问框里仍可临时切换 | 立即 |
 | `sideSurface` | `auto` \| `native-rightbar` \| `better-sidebar` \| `flow` | `auto` | **窗口模式（侧边承载面）**：自动挑选（先 dsh-better-sidebar，再内置浮层卡片）/ 强制 DSH 原生右侧栏（不参与自动）/ 强制 dsh-better-sidebar / 强制内置浮层卡片 | 立即 |
 | `maxChars` | 200–60000 | `4000` | **最大字符数**：超出部分头尾保留、中间截断并标注 | 立即 |
-| `floatMode` | `capsule` \| `full` \| `off` | `capsule` | **内置浮层的默认形态**：胶囊（一行，最小遮挡）/ 完整卡片栈 / 只留一个计数圆点。运行时可即时收起、隐藏，但不写回本项——刷新后仍回到这里设的默认 | 立即 |
+| `floatMode` | `capsule` \| `full` | `capsule` | **内置浮层的默认形态**：胶囊（一行，最小遮挡）/ 完整卡片栈。运行时可即时收起为胶囊，但不写回本项——刷新后仍回到这里设的默认。旧配置里存过 `off` 的会在启动时校验失败、回退为 `capsule`，并在 `problems` 里给出提示（`index.js` 的 `sanitizeLayer`），无需手工迁移 | 立即 |
 | `floatMaxWidth` | 240–560 | `340` | **内置浮层宽度上限**（px）：实际宽度 = `min(本项, 对话区右侧可用带宽)`，可用带宽不足 240px 时才会压入对话区 | 立即 |
-| `dockRail` | 布尔 | `true` | **右侧栏打开时占满它**：答案卡铺满右栏标签条下方的内容区，读起来像栏内的一页，而不是 340px 的小浮层。收起为胶囊、关闭浮层、右栏宽度 < 280px 或高度 < 240px 时自动回到常规浮层；实现靠测量右栏 DOM 矩形，**没有**走 DSH 的右栏 API（见 §4.2 与 §6.1） | 立即 |
+| `dockRail` | 布尔 | `true` | **右侧栏打开时占满它**：答案卡铺满右栏标签条下方的内容区，读起来像栏内的一页，而不是 340px 的小浮层。收起为胶囊、点卡片底部「关闭」、右栏宽度 < 280px 或高度 < 240px 时自动回到常规浮层；实现靠测量右栏 DOM 矩形，**没有**走 DSH 的右栏 API（见 §4.2 与 §6.1） | 立即 |
 | `shortcut` | 形如 `Alt+Q`、`Ctrl+Shift+K` | `Alt+Q` | **快捷键**：唤起提问框（`trigger` 允许时） | 立即 |
 | `captureZones` | `auto` \| `chat` \| `task` \| `chat+task` | `auto` | 只在哪些区域触发 | 立即 |
 | `showInUnclassified` | 布尔 | `true` | 无法归类的区域是否也触发 | 立即 |
@@ -181,7 +182,7 @@ plugin_manager(action="install_bundle", target="D:\\Users\\34332\\AI\\dsh-sideca
 | `answerStyle` | `concise` \| `standard` \| `detailed` | `standard` | **回答风格档位**：只给最小完整答案 / 现状 / 必要时展开并给出依据。指令追加在人格之后，**不会**覆盖"用提问的语言作答"与"选中文本是数据"这两条 | 下一次提问 |
 | `customPersona` | 字符串，≤500 码点 | `''` | **自定义指令**：追加在风格档位之后，以 `Additional user instruction:` 标注随每次提问发送（例如"尽量给可验证来源"） | 下一次提问 |
 | `followUpSuggestions` | 布尔 | `false` | **模型生成的建议追问**：让模型在答案末尾用 `<followups>问1 \| 问2</followups>` 给出 2–3 个可点的下一步问题（客户端剥离该块并渲染为芯片，**不额外发请求**） | 下一次提问 |
-| `feedbackAddress` | 字符串（邮箱或 `b64:` 编码）\| `''` | 维护者收件箱（`b64:` 混淆存储） | **反馈收件邮箱**：设置页「反馈」弹窗把问题与建议发到这里。默认值指向维护者自己的邮箱，以 `b64:<base64>` 形式打包——**这是混淆不是加密**，`decodeAddress()` 就在同包里，只能挡住正则抓取；环境变量 `DSH_SIDECARD_FEEDBACK_TO` / `DSH_CRB_FEEDBACK_TO` **优先于**本项，置空则只留「用邮件客户端发送」回退路径 | 立即 |
+| `feedbackAddress` | 字符串（邮箱或 `b64:` 编码）\| `''` | 维护者收件箱（`b64:` 混淆存储） | **反馈收件邮箱**：设置页「反馈」弹窗把问题与建议发到这里。默认值指向维护者自己的邮箱，以 `b64:<base64>` 形式打包——**这是混淆不是加密**，`decodeAddress()` 就在同包里，只能挡住正则抓取；环境变量 `DSH_SIDECARD_FEEDBACK_TO` / `DSH_CRB_FEEDBACK_TO` **优先于**本项，置空则反馈弹窗只留「复制内容」 | 立即 |
 | `feedbackSmtpHost` | 字符串，≤255 | `''` | **SMTP 服务器**。1.9.1 起只从**环境变量或用户层配置**读。**环境变量优先于配置**（`DSH_SIDECARD_SMTP_URL` / `DSH_CRB_SMTP_URL` 等能凑出完整端点时，配置里的整段不生效）；只有用户层配置会存它，**不进仓库** | 立即 |
 | `feedbackSmtpPort` | 数字，1–65535 | `465` | SMTP 端口。465 配隐式 TLS，587 配 STARTTLS（服务器没声明 STARTTLS 时不会硬升级） | 立即 |
 | `feedbackSmtpSecure` | 布尔 | `true` | 隐式 TLS（465）。关掉则按 STARTTLS 处理 | 立即 |
@@ -223,7 +224,7 @@ bleeds = 对话区右边界 - left > 1          // 只有带宽 < 240px 时才
 - 位置 = 右栏**标签条之下**的内容区矩形，宽度取右栏宽度，高度取到底部；右栏自己的标签条仍然露出、可点。
 - 卡片在这个形态下没有圆角/描边/阴影（`.dsa-card` 的装饰被 `[data-dsa-float-mode="dock"]` 覆盖），只有一条左边线与右栏内容区分界。
 - 标题栏（追问 + 徽标 + ⇥ / ×）与底部操作行固定上下两端，中间 `AnswerBody` 独立滚动——长答案不再把操作行推出视野。
-- 收起为胶囊（⇥）、关闭（×）、或把 `dockRail` 关掉，都立即回到常规浮层；右栏宽度 < 280px 或高度 < 240px 时也回退（窄栏里铺满会把正文挤成每行 8–9 字）。
+- 收起为胶囊（⇥）、删除这条追问对话（×）、或把 `dockRail` 关掉，都立即回到常规浮层；右栏宽度 < 280px 或高度 < 240px 时也回退（窄栏里铺满会把正文挤成每行 8–9 字）。注意 × 是**删除**：卡片从浮层与追问历史里一并移除；只想摘离浮层、保留历史请用底部的「关闭」。
 - 折叠的右栏不会被误用：`railOnScreen()` 会拒绝停在帧外（`left >= frameWidth - 1`）或尺寸不足的面板，量不到就回退，绝不把卡片画到帧外。
 - 矩形从哪来：**优先量本插件自己渲染在右栏里的 `CardHost` 节点**（`[data-dsa-rail-host]`）——它所在的位置按定义就是「一页正文」，不依赖任何未被文档承诺的标记；找不到时再按 `data-sidebar-right-*`、dockkit 世代、`.rightbar`、`sidebar.right` 槽逐代回退。
 - 什么时候重算：窗口改宽、右栏开合（只盯属性的 `MutationObserver`）、右栏自身改宽（`ResizeObserver`），以及挂载后的四次延时重测（罩住右栏的滑入动画）。流式刷新不会触发几何重算。
@@ -242,7 +243,7 @@ bleeds = 对话区右边界 - left > 1          // 只有带宽 < 240px 时才
 | `no-rail` | 没找到已展开的右栏（右栏关着，或这个构建的标记与预期不同） |
 | `rail-too-small` | 找到了，但宽 < 280px / 高 < 240px，或它停在帧外（折叠态被拒绝） |
 | `off` | 设置里的 `dockRail` 被关掉了 |
-| `mode` | 当前不是完整卡片形态（胶囊 / 隐藏），本来就不该铺满 |
+| `mode` | 当前不是完整卡片形态（胶囊 / 折叠态），本来就不该铺满 |
 
 ### 4.3 选区旁的动作条（外观）
 
@@ -269,14 +270,17 @@ bleeds = 对话区右边界 - left > 1          // 只有带宽 < 240px 时才
 它把真正的设置项全挤到屏幕外，被否掉后重做成现在这种「一条横幅 + 一个弹窗」。表单字段：类型（问题 / 建议 / 疑问 / 其他）、
 标题、详细描述、可选的**你的邮箱**（填了就写进邮件的 `Reply-To:`，维护者按「回复」能直接回给你；留空即匿名）。
 **设置页上没有任何 SMTP 输入框**：发信凭据属于部署方/维护者，走环境变量或用户层配置（见下），填报人不用管。
-三条出口，从首选到兜底：
+两条出口，从首选到兜底：
 
 | 出口 | 何时可用 | 说明 |
 |---|---|---|
 | **发送**（推荐） | 收件邮箱已配置 **且** SMTP 凭证可用（环境变量或用户层配置） | 插件直接把邮件投给 SMTP 服务器；成功后清空草稿 |
-| **用邮件客户端发送** | 只要有收件邮箱 | 拼一个 `mailto:` 交给系统邮件应用，**不需要任何凭证** |
 | **复制内容** | 总是 | 把同样的纯文本（含版本与环境）放进剪贴板，用户自己粘到任意渠道 |
 
+> 1.9.x 曾有的第三条出口「用邮件客户端发送」（`POST /feedback-mailto` 返回拼好的 `mailto:` URL）已在
+> 2.0.0 整体移除：它让插件多出一条谁都可以调的出口，却只是把同一封邮件交给系统邮件应用，与「复制内容」的
+> 实际效果重叠。现在没有发信服务时，弹窗直接说明缺什么，并指向「复制内容」。
+
 **收件邮箱默认可用，也可被环境变量接管。** 打包默认值是维护者邮箱（`b64:` 混淆存储，见上表）；
 环境变量 `DSH_SIDECARD_FEEDBACK_TO` 或 `DSH_CRB_FEEDBACK_TO`（与 dsh-conversation-recycle-bin 共用）
 **优先**于它。用户层配置落在 `$DSH_HOME/sidecard-ask/config.json`
@@ -331,20 +335,19 @@ DSH_SIDECARD_SMTP_FROM="user@example.com"   # 可选，默认等于 USER
   - `/state` 的 `config` 里也**删掉了** `feedbackAddress`，页面拿不到它；
   - 设置页不显示收件人的任何形式——没有掩码行、没有更换入口、没有地址输入框。收件人只由用户层配置
     `feedbackAddress` 或环境变量 `DSH_SIDECARD_FEEDBACK_TO` 提供，那是部署方/维护者的事，填写者不用管；
-  - 「用邮件客户端发送」点击时向 Host 要一条**拼好的** `mailto:` URL（`POST /feedback-mailto`），
-    浏览器只负责跳转，不自己拼地址。
+  - 页面也**不会**拿到 `mailto:` URL：2.0.0 删掉了 `/feedback-mailto` 路由与其 URL 构造器，
+    未命中的方法一律得到 `404 not-found`。
 - **`From:` 仍是维护者自己的 SMTP 账号，但填报人的邮箱会写进 `Reply-To:`**：QQ/163 会拒收不属于本账号的
   `From:`（553），所以发件身份不变；填报人在「你的邮箱」里填了地址，Host 就把它作为 `Reply-To:` 写进邮件头，
   维护者按「回复」直接回到填报人。该值在 Host 侧先过邮箱格式校验且不含 CR/LF，因此无法注入头字段；
-  留空则整行不写（匿名反馈）。`mailto:` 回退路径里没有 `Reply-To` 可用，同一个地址同时留在正文 `Contact:` 行。
+  留空则整行不写（匿名反馈）。
 
-- 三种就绪状态在界面上分开说，不混成一个「未配置」：没有收件人 → 提示配置；有收件人但没有 SMTP →
-  提示「缺的只是发信凭据，现在可用『用邮件客户端发送』」；齐全 → 什么都不提示。
+- 两种就绪状态在界面上分开说，不混成一个「未配置」：没有收件人 → 说没有可用发信服务；有收件人但没有 SMTP
+  凭证 → 说「只缺发信凭据」；齐全 → 什么都不提示。两种情况都指向「复制内容」，不再留一条邮件应用捷径。
 - **关于「加密」的实话**：这里的邮箱只是一次 SMTP 的收件地址，插件必须能解出明文才能发信，任何随插件
   分发的「加密」都等于把钥匙一起发出去，只能算混淆——打包默认值用的 `b64:` 就是这种混淆，只挡正则抓取。
   真正有效的保护是**只存本机配置 + 明文不进浏览器 + 日志打码 + 可被环境变量整体接管**——这四条都已实现。
-  仍然避免不了的两处：`mailto:` URL 本身必然含明文（由 Host 组好直接交给系统邮件应用，不经页面渲染），
-  以及**已经提交进 git 历史的作者邮箱**（见下文）。
+  仍然避免不了的一处是**已经提交进 git 历史的作者邮箱**（见下文）。
 
 失败排查顺序：`/state` 的 `capabilities.feedback.reason`（它会直接说「账号或密码还没填全」这类话）→
 用户层配置是否整行都在（服务器/端口/账号/密码；**端口必须是数字**，字符串会被判非法）→ 环境变量是否
@@ -369,7 +372,7 @@ DSH_SIDECARD_SMTP_FROM="user@example.com"   # 可选，默认等于 USER
   这是 `auto` 的**第一选择**。
 - 没装：自动使用内置浮层卡片，功能完全一致——**这条路径是第二选择，也是保底路径**。
   浮层默认是**贴帧右边缘的胶囊**（一行高，只有状态与问题首句），点击才展开成完整卡片，
-  标题栏右侧的「收起 / 隐藏」可随时收回；它的宽度由 `floatPlacement` 计算，
+  标题栏右侧的 ⇥ 可随时收起为胶囊、× 则删除这条追问对话（连同追问历史，不可撤销）；它的宽度由 `floatPlacement` 计算，
   只会占用**对话区右侧那条预留带**，不会压住正文（细节见 §4.1）。
 - **原生右侧栏为什么退出 `auto`**：卡片被塞进右栏只是一个 tab，而这个 tab 的生命周期不归插件管——
   卡片关闭后右栏仍留着一条读作「该卡片已关闭」的空标签，和你自己的右栏标签抢位置，
@@ -712,16 +715,19 @@ node tools/compat-probe.mjs --json tools/.cache/matrix.json
    「第 1 版」；点它 → 显示**旧问题 + 旧答案**并标注"正在查看历史版本（只读）"，点「返回最新」回到新答案。
    刷新页面后历史卡片仍能切版本（v3 持久化）。连续改问 6 次后只保留最近 5 版。
 8. **浮层形态与位置（1.5.0）**：默认应是一个**一行高的胶囊**（状态 + 问题首句），点它才展开成完整卡片；
-   展开后标题栏右侧有「收起为胶囊」（⇥）与「隐藏浮层」（×）——隐藏后只剩一个带计数的圆点，点它恢复。
+   展开后标题栏右侧有**收起为胶囊（⇥）**与**删除这条追问对话（×）**——× 会把该卡片从浮层与追问历史里
+   一并移除，**无法撤销**（有内容时会先弹插件内确认层；点浮层底部的「关闭」则只把它摘离浮层、历史仍保留在
+   设置页的历史管理器里）。2.0.0 起不再有「隐藏整个浮层 / 只留一个计数圆点」这套形态。
    用 F12 选中浮层根节点（`[data-dsa-root]`）读两个值自检：
-   - `data-dsa-float-mode` 应为 `capsule` / `full` / `off`；
+   - `data-dsa-float-mode` 应为 `capsule` / `full`（铺满右栏时为 `dock`）；
    - `data-layer-width` 应等于 `min(floatMaxWidth, 对话区右边界到帧右边缘的可用带宽)`。
    **关键判据：胶囊/卡片的左边缘不得越过对话区（`[data-slot^="conversation"]`）的右边界**。
    把窗口从 1920px 拖到 900px、再开关一次右侧栏，浮层应随之变窄而不是往左压住正文；
    只有窗口窄到可用带宽不足 240px 时才允许压入（此时是设计内的降级，不是 bug）。
 9. **占满右侧栏（1.8.3，`dockRail`）**：先把右侧栏打开（任意面板，例如「团队任务板」），再追问一次 →
    答案卡应铺满**标签条下方**的整块内容区：右边缘贴帧边、下边缘贴窗口底，右栏的标签条仍然露出可点。
-   点卡片标题栏的 ⇥（收起为胶囊）或 × → 卡片立即退出占满、回到常规浮层，右栏内容区恢复。
+   点卡片标题栏的 ⇥（收起为胶囊）→ 卡片立即退出占满、回到常规浮层，右栏内容区恢复；点 × 则是删除这条
+   追问对话（同样退出占满，但卡片与历史都不再存在）。
    自检：F12 读浮层根节点，`data-dsa-float-mode` 应为 `dock`，`data-dsa-dock` 也应为 `dock`；
    `.dsa-stack` 上的 `data-dsa-dock-body` 应等于卡片宽度（px）。**没铺满就看 `data-dsa-dock`**：
    `no-rail` = 没找到右栏，`rail-too-small` = 找到了但太窄或在帧外，`off` = 开关关了，`mode` = 不是完整形态。

package/client.js

@@ -47,7 +47,7 @@ window.__ModuleLoader__.load({
      * the Host and the module's `api.version` both read it, so a report can
      * never claim a generation the browser is not actually running.
      */
-    const CLIENT_VERSION = '1.9.1'
+    const CLIENT_VERSION = '2.0.0'
 
     /**
      * Tab kind served by the DSH native right rail (also its implementation id).
@@ -476,6 +476,12 @@ window.__ModuleLoader__.load({
         answerEmpty: '（没有内容）',
         cardClosed: '该卡片已关闭',
         cardMovedToFlow: '该卡片已移至浮层显示',
+        cardDelete: '删除这条追问对话',
+        cardDeleteTitle: '删除这条追问对话？',
+        cardDeleteBody: '会同时从浮层和追问历史里移除，且不可撤销。',
+        cardDeleteRounds: '含 {n} 轮追问',
+        cardDeleteConfirm: '删除',
+        cardDeleted: '已删除这条追问对话',
         reasoningTitle: '思考过程',
         copy: '复制',
         copied: '已复制',
@@ -528,7 +534,6 @@ window.__ModuleLoader__.load({
         setFloatMode: '浮层默认形态',
         setFloatModeCapsule: '胶囊（不遮挡对话，可随时展开）',
         setFloatModeFull: '直接展开成卡片',
-        setFloatModeOff: '关闭浮层（只留小圆点）',
         setFloatModeHint: '浮层贴右侧边缘，只在空间不足时才可能压到对话区',
         setFloatMaxWidth: '浮层宽度上限（px）',
         setFloatMaxWidthHint: '空间不足时自动收窄，不会硬顶',
@@ -537,9 +542,6 @@ window.__ModuleLoader__.load({
         floatDocked: '已占满右侧栏',
         floatExpand: '展开侧边卡片',
         floatCollapse: '收起为胶囊（不遮挡对话）',
-        floatHide: '隐藏浮层（只留小圆点）',
-        floatRestore: '恢复浮层',
-        floatCount: '{n} 条追问回答',
         floatStreaming: '正在作答…',
         floatDone: '已完成 {n} 条',
         setShortcut: '快捷键',
@@ -709,26 +711,15 @@ window.__ModuleLoader__.load({
         feedbackSend: '发送邮件',
         feedbackSending: '发送中…',
         feedbackSent: '已发送，谢谢反馈',
-        feedbackMailto: '用邮件客户端发送',
         feedbackCopy: '复制内容',
         feedbackCopied: '已复制到剪贴板',
-        feedbackUnconfigured: '没有可用的发信服务，可用“用邮件客户端发送”自行寄出',
-        feedbackMailtoOnly: '收件人已填好，只缺发信凭据（SMTP 账号与授权码，由环境变量或用户层配置提供）；现在也可以“用邮件客户端发送”',
+        feedbackUnconfigured: '没有可用的发信服务，暂时不能直接寄出；可用“复制内容”自己发给我',
+        feedbackNoCredentials: '收件人已填好，只缺发信凭据（SMTP 账号与授权码，由环境变量或用户层配置提供）；可用“复制内容”自己发给我',
         feedbackNeedsTitle: '标题至少 4 个字',
         feedbackNeedsBody: '详细描述至少 10 个字',
         feedbackContactTooLong: '联系方式太长（≤{n} 字）',
         feedbackFailed: '发送失败：{message}',
         feedbackEnvNote: '自动附带：插件版本、Node/平台、发送时间',
-        feedbackSmtpShow: '设置邮件发送（SMTP）',
-        feedbackSmtpHide: '收起邮件发送设置',
-        feedbackSmtpEnvNote: '当前凭证来自环境变量（优先级高于用户层配置）',
-        feedbackSmtpHost: 'SMTP 服务器',
-        feedbackSmtpSecure: 'SSL/TLS（465 端口）',
-        feedbackSmtpPassSaved: '已保存，留空则不改动',
-        feedbackSmtpPass: '密码 / 授权码',
-        feedbackSmtpFrom: '发件邮箱（留空＝同账号）',
-        feedbackSmtpHint: 'QQ、163 等邮箱要用「授权码」而不是登录密码；密码只写进本地 config.json，页面读不回来，也不会随插件发布',
-        feedbackSmtpSaveHint: '填完点「保存」（会把本页设置一起保存）；不保存就点发送，密码不会被记住',
         feedbackTooFast: '刚发过一封，请稍等半分钟',
         feedbackTooMany: '发送过于频繁，请稍后再试',
       },
@@ -761,6 +752,12 @@ window.__ModuleLoader__.load({
         answerEmpty: '(empty)',
         cardClosed: 'This card was closed',
         cardMovedToFlow: 'This card moved to the floating stack',
+        cardDelete: 'Delete this follow-up conversation',
+        cardDeleteTitle: 'Delete this follow-up conversation?',
+        cardDeleteBody: 'It will be removed from both the floating layer and the follow-up history. This cannot be undone.',
+        cardDeleteRounds: 'Includes {n} follow-up turn(s)',
+        cardDeleteConfirm: 'Delete',
+        cardDeleted: 'Deleted this follow-up conversation',
         reasoningTitle: 'Reasoning',
         copy: 'Copy',
         copied: 'Copied',
@@ -813,7 +810,6 @@ window.__ModuleLoader__.load({
         setFloatMode: 'Floating layer default',
         setFloatModeCapsule: 'Capsule (never covers the conversation)',
         setFloatModeFull: 'Expanded card stack',
-        setFloatModeOff: 'Hidden (small launcher only)',
         setFloatModeHint: 'The layer is anchored to the right edge and only overlaps on very narrow frames',
         setFloatMaxWidth: 'Floating layer max width (px)',
         setFloatMaxWidthHint: 'Narrows automatically when there is not enough room',
@@ -822,9 +818,6 @@ window.__ModuleLoader__.load({
         floatDocked: 'Filled the right rail',
         floatExpand: 'Expand the side cards',
         floatCollapse: 'Collapse to a capsule (stops covering the conversation)',
-        floatHide: 'Hide the layer (leaves a small launcher)',
-        floatRestore: 'Restore the floating layer',
-        floatCount: '{n} follow-up answers',
         floatStreaming: 'Answering…',
         floatDone: '{n} done',
         setShortcut: 'Shortcut',
@@ -994,26 +987,15 @@ window.__ModuleLoader__.load({
         feedbackSend: 'Send mail',
         feedbackSending: 'Sending…',
         feedbackSent: 'Sent — thank you',
-        feedbackMailto: 'Send with my mail app',
         feedbackCopy: 'Copy text',
         feedbackCopied: 'Copied to the clipboard',
-        feedbackUnconfigured: 'No mail service is configured; use “Send with my mail app” instead',
-      feedbackMailtoOnly: 'The recipient is set; only the SMTP credentials (environment variables) are missing, so use “Send with my mail app”',
+        feedbackUnconfigured: 'No mail service is configured, so the report cannot be sent from here; use “Copy text” and send it yourself',
+        feedbackNoCredentials: 'The recipient is set; only the SMTP credentials (environment variables or the user config) are missing, so use “Copy text” and send it yourself',
         feedbackNeedsTitle: 'The title needs at least 4 characters',
         feedbackNeedsBody: 'The details need at least 10 characters',
         feedbackContactTooLong: 'The contact line is too long (max {n} characters)',
         feedbackFailed: 'Send failed: {message}',
         feedbackEnvNote: 'Attached automatically: plugin version, Node/platform, send time',
-        feedbackSmtpShow: 'Set up mail delivery (SMTP)',
-        feedbackSmtpHide: 'Hide mail delivery settings',
-        feedbackSmtpEnvNote: 'Credentials come from the environment right now (it outranks this page), so the fields below have no effect.',
-        feedbackSmtpHost: 'SMTP server',
-        feedbackSmtpSecure: 'SSL/TLS (port 465)',
-        feedbackSmtpPassSaved: 'Saved — leave empty to keep it',
-        feedbackSmtpPass: 'Password / app code',
-        feedbackSmtpFrom: 'From address (empty = the account)',
-        feedbackSmtpHint: 'QQ/163 need an app-specific code, not the login password. The password is written to this machine\'s config.json only; the page never reads it back and it never ships with the plugin.',
-        feedbackSmtpSaveHint: 'Press “Save” after filling this in (it saves the whole page). Without saving, the code is not remembered and sending keeps failing.',
         feedbackTooFast: 'One mail just went out — wait half a minute',
         feedbackTooMany: 'Too many reports for now — try again later',
       },
@@ -1238,8 +1220,8 @@ window.__ModuleLoader__.load({
         surface: 'flow',
         surfaceNote: null,
         /**
-         * In-session override of `config.floatMode`, set by the layer's own
-         * collapse/hide buttons. `null` = follow the configured default.
+         * In-session override of `config.floatMode`, set by the card header's
+         * collapse button. `null` = follow the configured default.
          */
         floatMode: null,
         sessionId: null,
@@ -1384,10 +1366,10 @@ window.__ModuleLoader__.load({
      * NOT persisted: the settings page owns the durable default, and a reload
      * should return to it (a pill hidden by accident must not stay hidden
      * across sessions).
-     * @param {string} mode - `capsule` | `full` | `off`.
+     * @param {string} mode - `capsule` | `full`.
      */
     function setFloatMode(mode) {
-      if (mode !== 'capsule' && mode !== 'full' && mode !== 'off') return
+      if (mode !== 'capsule' && mode !== 'full') return
       store.set({ floatMode: mode })
     }
 
@@ -1789,7 +1771,7 @@ window.__ModuleLoader__.load({
       return { ok: true }
     }
 
-    /** One-line subject for the report (also used by the `mailto:` fallback). */
+    /** One-line subject for the report. */
     function feedbackSubjectFor({ version, draft }) {
       const title = typeof draft?.title === 'string' ? draft.title.trim() : ''
       const kind = typeof draft?.kind === 'string' && draft.kind !== '' ? draft.kind : 'other'
@@ -2216,7 +2198,7 @@ window.__ModuleLoader__.load({
    (\`html[data-platform] body>[data-dsh-better-sidebar]{-webkit-app-region:initial}\`
    plus \`[data-dsh-panel-host]>*{-webkit-app-region:no-drag}\`).
    Every surface we draw declares it. The property is inert in a browser. */
-.dsa-layer,.dsa-trigger,.dsa-quickbar,.dsa-pop,.dsa-ctxmenu,.dsa-float,.dsa-stack,.dsa-card,.dsa-toast,.dsa-settings{-webkit-app-region:no-drag}
+.dsa-layer,.dsa-trigger,.dsa-quickbar,.dsa-pop,.dsa-ctxmenu,.dsa-float,.dsa-stack,.dsa-card,.dsa-toast,.dsa-settings,.dsa-confirm{-webkit-app-region:no-drag}
 .dsa-layer{pointer-events:none;position:relative;z-index:60}
 .dsa-trigger{pointer-events:auto;position:fixed;display:flex;align-items:center;gap:4px;
   padding:4px 8px;border-radius:8px;border:1px solid var(--dsw-alias-border-l2, rgba(127,127,127,.35));
@@ -2334,9 +2316,16 @@ body[data-ds-dark-theme] .dsa-quickbar .dsa-trigger-embedded{color:#0a1428}
 html[data-ds-dark-theme] .dsa-btn-primary,
 body[data-ds-dark-theme] .dsa-btn-primary{color:#0a1428}
 .dsa-btn:disabled{opacity:.55;cursor:default}
-/* Icon-only variant (the floating layer's collapse/hide controls): square and
-   quiet so the card title bar stays one line and the title keeps the weight. */
+/* Icon-only variant (the floating layer's collapse / delete controls): square
+   and quiet so the card title bar stays one line and the title keeps the weight. */
 .dsa-btn-icon{padding:4px 7px;line-height:1;font-size:13px;color:var(--dsw-alias-label-secondary, #666)}
+/* Destructive confirmation only: the irreversible button carries the error token
+   so it can never be mistaken for the safe one rendered next to it. Placed after
+   .dsa-btn-icon on purpose — same specificity, so source order decides. */
+.dsa-btn-danger{border-color:var(--dsw-alias-state-error-primary, #c0392b);
+  background:var(--dsw-alias-state-error-primary, #c0392b);color:#fff;font-weight:500}
+.dsa-btn-danger:hover{border-color:var(--dsw-alias-state-error-primary, #c0392b);
+  background:var(--dsw-alias-state-error-primary, #c0392b)}
 /* Segmented control (main chat / side card). These are the two destinations an
    answer can land in, so the pair has to read as a radio choice, not as two
    quiet labels: the group gets a recessed track with an explicit mid-grey edge
@@ -2422,11 +2411,18 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
 .dsa-capsule-q{min-width:0;flex:1;color:var(--dsw-alias-label-secondary, #666);
   white-space:nowrap;overflow:hidden;text-overflow:ellipsis}
 .dsa-capsule-chev{flex:none;color:var(--dsw-alias-label-secondary, #888)}
-.dsa-launcher{display:inline-flex;align-items:center;gap:6px;align-self:flex-start;padding:6px 11px;
-  border-radius:999px;cursor:pointer;font:inherit;font-size:12px;line-height:18px;
-  border:1px dashed var(--dsw-alias-border-l2, rgba(127,127,127,.45));
-  background:var(--dsw-alias-bg-overlay, #fff);color:var(--dsw-alias-label-secondary, #666)}
-.dsa-launcher:hover{border-color:var(--dsw-alias-brand-primary, #4c8dff)}
+/* Delete confirmation (2.0.0). Fixed, not inline: a card docked into the right
+   rail lives inside an overflow:hidden page, which would clip a sheet anchored
+   to the card. Same backdrop recipe as the feedback dialog. */
+.dsa-confirm-backdrop{position:fixed;inset:0;z-index:1100;display:flex;align-items:center;
+  justify-content:center;padding:24px;background:rgba(0,0,0,.42)}
+.dsa-confirm{display:flex;flex-direction:column;gap:8px;width:min(360px, 100%);padding:14px 16px;
+  border-radius:12px;border:1px solid var(--dsw-alias-border-l1, rgba(127,127,127,.3));
+  background:var(--dsw-alias-bg-overlay, #fff);color:var(--dsw-alias-label-primary, #111);
+  box-shadow:0 18px 48px rgba(0,0,0,.28)}
+.dsa-confirm-title{font-size:13px;font-weight:600}
+.dsa-confirm-body{font-size:12px;line-height:18px;color:var(--dsw-alias-label-secondary, #666)}
+.dsa-confirm > .dsa-row{justify-content:flex-end}
 .dsa-answer{max-height:44vh;overflow:auto;word-break:break-word}
 .dsa-answer .dsa-p{margin:0 0 6px}
 .dsa-answer .dsa-ul{margin:0 0 6px;padding-left:18px}
@@ -4007,15 +4003,70 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
         }, t('close')))
     }
 
+    /**
+     * The confirmation gate for an irreversible action.
+     *
+     * A component rather than an inline block for two reasons: every
+     * destructive control can reuse it, and the test harness cannot drive a
+     * click-driven state change, so rendering it directly is the only way this
+     * markup gets asserted (same seam as {@link FeedbackDialog}).
+     *
+     * The safe choice is the default: Cancel takes focus, Escape aborts, and
+     * only a click on the backdrop itself dismisses — a click that lands on the
+     * dialog must not throw away the decision the user is making.
+     */
+    function DeleteConfirmDialog({ title, body, detail, cancelLabel, confirmLabel, onCancel, onConfirm }) {
+      return h('div', {
+        className: 'dsa-confirm-backdrop',
+        onClick: event => {
+          if (event.target === event.currentTarget) onCancel()
+        },
+        onKeyDown: event => {
+          if (event.key !== 'Escape') return
+          // Escape is the safe exit, so it stops here: the card's own Esc
+          // handler and the global shortcut layer must not also react.
+          event.stopPropagation()
+          onCancel()
+        },
+      },
+      h('div', {
+        className: 'dsa-confirm',
+        role: 'dialog',
+        'aria-modal': 'true',
+        'aria-label': title,
+      },
+      h('strong', { className: 'dsa-confirm-title' }, title),
+      h('div', { className: 'dsa-confirm-body' }, body),
+      detail !== null && detail !== undefined && detail !== '' ? h('div', { className: 'dsa-muted' }, detail) : null,
+      h('div', { className: 'dsa-row' },
+        h('button', {
+          type: 'button',
+          className: 'dsa-btn',
+          // Safe default: a stray Enter on an unreviewed dialog must not
+          // destroy anything.
+          autoFocus: true,
+          onClick: onCancel,
+        }, cancelLabel),
+        h('button', {
+          type: 'button',
+          className: 'dsa-btn dsa-btn-danger',
+          onClick: onConfirm,
+        }, confirmLabel))))
+    }
+
     /**
      * One answer card; `embedded` is true inside a host's tab.
      *
-     * `onFloatMode` is passed ONLY by the floating layer: it renders the
-     * collapse/hide controls that let the user get the layer out of the way
-     * (the layer is the only surface that can cover the conversation). A host
-     * tab that embeds the same card passes no callback and gets no buttons.
+     * `onFloatMode` / `onDelete` are passed ONLY by the floating layer. The
+     * first renders the "collapse to a capsule" control that gets the layer out
+     * of the way (the layer is the only surface that can cover the
+     * conversation); the second renders the × that DELETES this follow-up
+     * conversation — its live card *and* its durable history entry — after a
+     * confirmation. A host tab that embeds the same card passes neither and
+     * keeps its own tab close plus the footer Close button, which by design
+     * detaches the card without touching the history.
      */
-    function AnswerCard({ card, surfaceLabel, onCopy, onFollowUp, onRetry, onRetryEdit, onClose, onCancel, onSendToMain, onFloatMode, onLocate, onExport, onInsert, onReplace, onViewVersion }) {
+    function AnswerCard({ card, surfaceLabel, onCopy, onFollowUp, onRetry, onRetryEdit, onClose, onCancel, onSendToMain, onFloatMode, onDelete, onLocate, onExport, onInsert, onReplace, onViewVersion }) {
       const [followOpen, setFollowOpen] = React.useState(false)
       const [draft, setDraft] = React.useState('')
       // Edit-&-retry editor: prefilled with the card's CURRENT question and
@@ -4023,6 +4074,12 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
       // edit-retry regenerates THIS turn, keeping the card's earlier turns).
       const [editOpen, setEditOpen] = React.useState(false)
       const [editDraft, setEditDraft] = React.useState('')
+      // Deleting a follow-up conversation is irreversible, so it goes through an
+      // in-plugin confirmation — EXCEPT for a card that holds nothing: no
+      // follow-up turn, no answer text, no reasoning, no run in flight. There is
+      // nothing to lose there, and prompting on an empty card only trains the
+      // user to dismiss the prompt that matters.
+      const [deleteOpen, setDeleteOpen] = React.useState(false)
       const answerRef = React.useRef(null)
       const config = store.state.config
       // P2-5b: an older version is READ-ONLY content swapped into the same
@@ -4057,6 +4114,9 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
       // without modifiers and never while composing or inside an editor.
       const onCardKeyDown = (event) => {
         if (event.ctrlKey || event.altKey || event.metaKey || event.isComposing) return
+        // The confirmation is modal: R/C must not act on a card the user is
+        // currently deciding to delete.
+        if (deleteOpen) return
         const tag = String(event.target?.tagName ?? '')
         if (tag === 'INPUT' || tag === 'TEXTAREA' || tag === 'BUTTON'
           || event.target?.closest?.('[contenteditable=""],[contenteditable="true"]') !== null) {
@@ -4085,6 +4145,19 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
       if (typeof card.elapsedMs === 'number' && Number.isFinite(card.elapsedMs) && formatElapsed(card.elapsedMs) !== '') {
         metaBits.push(`${t('metaElapsed')} ${formatElapsed(card.elapsedMs)}`)
       }
+      // "Empty" is judged on the card's own content, never on how it got here.
+      const turns = Array.isArray(card.history) ? card.history.length : 0
+      const busy = card.status === 'pending' || card.status === 'streaming'
+      const nothingToLose = turns === 0
+        && String(card.text ?? '').trim() === ''
+        && String(card.reasoning ?? '').trim() === ''
+      const requestDelete = () => {
+        if (!busy && nothingToLose) {
+          onDelete?.()
+          return
+        }
+        setDeleteOpen(true)
+      }
       return h('section', {
         className: 'dsa-card',
         'aria-label': t('answerTitle'),
@@ -4097,10 +4170,20 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
           h('span', { className: 'dsa-badge' }, zoneLabel(card)),
           surfaceLabel !== null ? h('span', { className: 'dsa-badge' }, surfaceLabel) : null,
           card.truncated ? h('span', { className: 'dsa-badge dsa-badge-warn' }, t('truncatedBadge', { n: card.droppedChars })) : null,
-          typeof onFloatMode === 'function'
+          typeof onFloatMode === 'function' || typeof onDelete === 'function'
             ? h('span', { className: 'dsa-row', style: { marginLeft: 'auto' } },
-              floatControl('capsule', 'floatCollapse', '⇥'),
-              floatControl('off', 'floatHide', '×'))
+              typeof onFloatMode === 'function'
+                ? floatControl('capsule', 'floatCollapse', '⇥')
+                : null,
+              typeof onDelete === 'function'
+                ? h('button', {
+                  type: 'button',
+                  className: 'dsa-btn dsa-btn-icon',
+                  title: t('cardDelete'),
+                  'aria-label': t('cardDelete'),
+                  onClick: () => requestDelete(),
+                }, '×')
+                : null)
             : null),
         h('pre', { className: 'dsa-quote' }, shown.question),
         versions.length > 0
@@ -4251,17 +4334,34 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
           onFollowUp: () => setFollowOpen(open => !open),
           onClose,
         }),
-        surfaceLabel === null ? h('div', { className: 'dsa-muted' }, `${t('carrierSide')} · max ${config.maxChars}`) : null)
+        surfaceLabel === null ? h('div', { className: 'dsa-muted' }, `${t('carrierSide')} · max ${config.maxChars}`) : null,
+        deleteOpen
+          ? h(DeleteConfirmDialog, {
+            title: t('cardDeleteTitle'),
+            body: t('cardDeleteBody'),
+            detail: turns > 0 ? t('cardDeleteRounds', { n: turns }) : null,
+            cancelLabel: t('askCancel'),
+            confirmLabel: t('cardDeleteConfirm'),
+            onCancel: () => setDeleteOpen(false),
+            onConfirm: () => {
+              setDeleteOpen(false)
+              onDelete?.()
+            },
+          })
+          : null)
     }
 
     /**
      * The flow surface, i.e. the floating layer (A).
      *
-     * Three shapes, all sharing one right-anchored container:
+     * Two shapes, both sharing one right-anchored container:
      *   - `capsule`: a single ~34px pill (status + truncated question). The
      *     default, because a one-line pill cannot bury the conversation.
      *   - `full`: the classic card stack, collapsed on demand.
-     *   - `off`: only a small launcher, so nothing covers the page until asked.
+     *
+     * The former `off` shape (hide the layer behind a small launcher) is gone
+     * as of 2.0.0: the card header's × deletes that follow-up conversation
+     * instead, and "hide everything" was never a state this layer needed.
      *
      * The width comes from {@link floatPlacement}, so the layer stops growing
      * left as soon as it would cross the conversation column's right boundary.
@@ -4462,17 +4562,9 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
         onReplace: target => actions.insertAnswer(target ?? card, { replace: true }),
         onViewVersion: index => actions.viewVersion(card, index),
         onFloatMode: setFloatMode,
+        onDelete: () => actions.deleteCard(card),
       }))
 
-      if (mode === 'off') {
-        return container(h('button', {
-          type: 'button',
-          className: 'dsa-launcher',
-          title: t('floatRestore'),
-          onClick: () => setFloatMode('full'),
-        }, dot, t('floatCount', { n: total })))
-      }
-
       if (mode === 'capsule') {
         return container(h('button', {
           type: 'button',
@@ -4486,8 +4578,8 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
 
       // Docked: the card takes the rail's whole rectangle, so it reads as one of
       // the rail's pages rather than a 340px card hovering over it. The card
-      // keeps its own header (title + badges + collapse/hide controls), which is
-      // what makes the page dismissible without leaving the rail.
+      // keeps its own header (title + badges + collapse / delete controls),
+      // which is what makes the page dismissible without leaving the rail.
       return container(h('div', {
         className: 'dsa-stack',
         'data-dsa-dock-body': docked ? String(dock.width) : undefined,
@@ -4554,7 +4646,7 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
     function FeedbackDialog(props) {
       const {
         t, limits, draft, onChange, status, error, ready, reason, hasRecipient,
-        onClose, onSubmit, onMailto, onCopy,
+        onClose, onSubmit, onCopy,
       } = props
       const sending = status === 'sending'
       // Escape closes it: a modal without a keyboard exit is a trap.
@@ -4641,15 +4733,15 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
       })),
       h('span', { className: 'dsa-feedback-dialog-hint' }, t('feedbackContactHint')),
       h('span', { className: 'dsa-feedback-dialog-hint' }, t('feedbackEnvNote')),
-      // Readiness: three states, not two. No recipient at all, recipient but no
-      // usable transport (the mail-app path still works), fully ready. When the
-      // Host explains why, print its sentence verbatim.
+      // Readiness: two states, not one. No recipient at all, or a recipient
+      // but no usable transport. When the Host explains why, print its
+      // sentence verbatim.
       ready === true
         ? null
         : h('span', { className: 'dsa-feedback-dialog-hint', 'data-feedback-readiness': 'unready' },
           String(reason ?? '') !== ''
             ? String(reason)
-            : (hasRecipient === true ? t('feedbackMailtoOnly') : t('feedbackUnconfigured'))),
+            : (hasRecipient === true ? t('feedbackNoCredentials') : t('feedbackUnconfigured'))),
       h('div', { className: 'dsa-feedback-dialog-actions' },
         h('button', {
           type: 'button',
@@ -4659,12 +4751,6 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
           title: ready === true ? undefined : t('feedbackUnconfigured'),
           onClick: onSubmit,
         }, sending ? t('feedbackSending') : t('feedbackSend')),
-        h('button', {
-          type: 'button',
-          className: 'dsa-btn',
-          'data-feedback-mailto': '',
-          onClick: onMailto,
-        }, t('feedbackMailto')),
         h('button', {
           type: 'button',
           className: 'dsa-btn',
@@ -4758,32 +4844,6 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
         }
       }
 
-      /**
-       * Fallback that needs no credentials: hand the draft to the mail app.
-       *
-       * The URL is built by the Host — deliberately, so the plaintext recipient
-       * is never held or rendered by this page. If the Host has no recipient,
-       * it answers 503 and the failure is shown like any other.
-       */
-      const sendFeedbackByMailApp = async () => {
-        try {
-          const value = await postJson('feedback-mailto', {
-            kind: feedbackDraft.kind,
-            title: feedbackDraft.title.trim(),
-            body: feedbackDraft.body.trim(),
-            contact: feedbackDraft.contact.trim(),
-            userAgent: feedbackUserAgent,
-          })
-          const url = typeof value?.url === 'string' ? value.url : ''
-          if (url === '') throw new Error('no mailto url')
-          if (typeof window !== 'undefined' && typeof window.open === 'function') window.open(url, '_self')
-          else if (typeof location !== 'undefined') location.href = url
-        } catch (error) {
-          setFeedbackStatus('error')
-          setFeedbackError(t('feedbackFailed', { message: localizeError(error) }))
-        }
-      }
-
       const copyFeedbackDraft = async () => {
         const text = feedbackPlainTextFor({
           version: state.version ?? CLIENT_VERSION,
@@ -5025,8 +5085,8 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
       // form. Nothing else about feedback lives on this page: the transport is
       // the Host's business (environment / user config), so an end user has
       // nothing to fill in before writing a report. The banner also works when
-      // no SMTP endpoint is configured — the `mailto:` path needs nothing but a
-      // recipient — so the dialog says that in one line instead of looking broken.
+      // no SMTP endpoint is configured — the dialog says so in one line and
+      // points at the copy path instead of looking broken.
       const feedbackConfigured = feedbackInfo !== null && feedbackInfo.configured === true
       const feedbackBanner = h('div', { className: 'dsa-feedback-bar', 'data-dsa-feedback-section': '' },
         h('div', { className: 'dsa-feedback-bar-text' },
@@ -5055,7 +5115,6 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
           hasRecipient: feedbackInfo?.hasRecipient === true,
           onClose: () => setFeedbackOpen(false),
           onSubmit: () => { void submitFeedback() },
-          onMailto: sendFeedbackByMailApp,
           onCopy: () => { void copyFeedbackDraft() },
         })
 
@@ -5094,7 +5153,6 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
           field(t('setFloatMode'), select('floatMode', [
             ['capsule', t('setFloatModeCapsule')],
             ['full', t('setFloatModeFull')],
-            ['off', t('setFloatModeOff')],
           ]), t('setFloatModeHint')),
           field(t('setFloatMaxWidth'), number('floatMaxWidth', 240, 560), t('setFloatMaxWidthHint')),
           field(t('setMinChars'), number('minChars', 0, 200)),
@@ -5565,7 +5623,7 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
             } else {
               store.set({ cards: [historyEntryToCard(entry), ...store.state.cards] })
             }
-            // A hidden (off/capsule) layer would swallow the restored card;
+            // A collapsed (capsule) layer would swallow the restored card;
             // this is a session-only override, exactly like clicking expand.
             setFloatMode('full')
             toast(t('historyRestored'))
@@ -5583,6 +5641,57 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
             })
             toast(t('historyDeleted'))
           },
+          /**
+           * Delete ONE follow-up conversation: the live card AND its durable
+           * history entry. This is the card header's ×.
+           *
+           * Deliberately stronger than {@link actions.close}: closing only
+           * detaches the card from the live surface and keeps the history entry
+           * on purpose (#6), while this removes the same id from both stores and
+           * persists immediately, so a reload cannot resurrect it.
+           *
+           * An in-flight run is released first: the browser stream is aborted,
+           * the Host child is told to cancel, and the card's buffered deltas are
+           * dropped — a late flush would otherwise re-append text to a card that
+           * no longer exists.
+           */
+          deleteCard(card) {
+            const id = card?.id
+            if (typeof id !== 'string' || id === '') return false
+            const controller = controllers.get(id)
+            if (controller !== undefined) {
+              controller.abort()
+              void postJson('cancel', { id }).catch(() => {})
+            }
+            controllers.delete(id)
+            pendingDeltas.delete(id)
+            pendingReasonings.delete(id)
+            // Every surface gets the same chance to close its own container as
+            // it does on close(): an orphaned tab reads to the user as a card
+            // that refused to die.
+            if (card.surface === 'better-sidebar') {
+              try {
+                surfaces.better.close(card)
+              } catch { /* the host may already be gone */ }
+            } else if (card.surface === 'native-rightbar') {
+              try {
+                surfaces.native.close(card)
+              } catch { /* the right rail owns its lifecycle */ }
+            }
+            const next = store.state.history
+              .filter(item => item.id !== id)
+              .slice(0, historyCap())
+            // cap === 0 means "nothing is persisted": leave the stored key alone
+            // rather than writing an empty payload over it (same rule as
+            // syncPersisted).
+            if (historyCap() > 0) writePersisted(next)
+            store.set({
+              history: next,
+              cards: store.state.cards.filter(item => item.id !== id),
+            })
+            toast(t('cardDeleted'))
+            return true
+          },
           /**
            * Empty the durable history without touching running cards.
            *
@@ -6755,11 +6864,11 @@ body[data-ds-dark-theme] .dsa-seg button[data-on="true"]:hover{
 
       /**
        * Test seam: components that can be rendered on their own. The feedback
-       * dialog lives here because the settings page mounts it only while open and
-       * the test shim has no working setState, so a simulated click cannot reach
-       * it.
+       * dialog and the delete confirmation both live here because their host
+       * mounts them only while open and the test shim has no working setState,
+       * so a simulated click cannot reach them.
        */
-      components: Object.freeze({ FeedbackDialog }),
+      components: Object.freeze({ FeedbackDialog, DeleteConfirmDialog }),
 
       /**
        * Test seam: pure helpers, frozen. The DSH client runtime only reads

package/index.js

@@ -44,7 +44,7 @@ export const name = 'dsh-sidecard-ask'
 export const inject = ['webServer']
 
 /** Version of this plugin (kept in step with package.json by test/verify.mjs). */
-export const PLUGIN_VERSION = '1.9.1'
+export const PLUGIN_VERSION = '2.0.0'
 
 /** Route prefix of the plugin's own API. */
 export const ROUTE_PREFIX = '/sidecard-ask/api'
@@ -77,10 +77,12 @@ export const DEFAULT_CONFIG = {
   sideProvider: 'auto',
   /**
    * Floating-layer (A) surface. `capsule` = one-line pill that never covers
-   * the conversation, `full` = the classic card stack, `off` = hidden behind a
-   * small launcher. The geometry for all three lives in `client.js`:
-   * the layer is anchored to the frame's right edge and never crosses the
-   * conversation column's right boundary (see `FLOAT_*` there).
+   * the conversation, `full` = the classic card stack. (The former `off`
+   * "hidden behind a small launcher" shape was removed in 2.0.0; a stored
+   * `off` now fails validation and falls back to this default.) The geometry
+   * for both shapes lives in `client.js`: the layer is anchored to the frame's
+   * right edge and never crosses the conversation column's right boundary
+   * (see `FLOAT_*` there).
    */
   floatMode: 'capsule',
   /** Hard cap, in CSS px, for the floating layer's width. */
@@ -208,7 +210,7 @@ const ENUMS = {
   sideSurface: ['auto', 'native-rightbar', 'better-sidebar', 'flow'],
   captureZones: ['auto', 'chat', 'task', 'chat+task'],
   sideTools: ['readonly', 'inherit'],
-  floatMode: ['capsule', 'full', 'off'],
+  floatMode: ['capsule', 'full'],
   answerStyle: ['concise', 'standard', 'detailed'],
 }
 
@@ -586,7 +588,7 @@ export function buildSidePrompt(input) {
 //   2. No dependency is added: the SMTP dialogue below runs on `node:net` and
 //      `node:tls` only, because the Host half may import nothing but node:
 //      built-ins (see the module header). A plugin that cannot reach an SMTP
-//      relay still works: the Client offers a `mailto:` fallback.
+//      relay still works: the Client offers to copy the report text.
 // ────────────────────────────────────────────────────────────────────────────
 
 /** Bounds for one feedback mail, mirrored by the Client's own form checks. */
@@ -769,8 +771,7 @@ export function readSmtpFromEnv(env = process.env) {
 /**
  * Resolve the plaintext recipient. SERVER-SIDE ONLY: this value must never be
  * put into a response body or rendered by the Client — the settings page only
- * ever receives `toMasked` plus the `hasRecipient` flag, and asks for a finished
- * `mailto:` URL when the user actually clicks the mail-app button.
+ * ever receives `toMasked` plus the `hasRecipient` flag.
  * @param {Record<string, unknown>} config - the effective config.
  * @param {Record<string, string|undefined>} [env] - the process environment.
  * @returns {string} the address, or '' when unconfigured.
@@ -842,7 +843,7 @@ export function describeSmtpSettings(config = {}, env = process.env) {
 export function describeFeedback(config = {}, env = process.env) {
   const to = feedbackRecipient(config, env)
   const base = {
-    transport: 'mailto',
+    transport: 'none',
     configured: false,
     hasRecipient: to !== '',
     toMasked: maskEmail(to),
@@ -854,7 +855,7 @@ export function describeFeedback(config = {}, env = process.env) {
   if (to === '') return { ...base, reason: '未配置收件邮箱：设置 feedbackAddress 或 DSH_SIDECARD_FEEDBACK_TO / DSH_CRB_FEEDBACK_TO' }
   if (!looksLikeEmail(to)) return { ...base, reason: '收件邮箱格式不合法' }
   const smtp = resolveSmtp(config, env)
-  if (smtp.ok !== true) return { ...base, reason: `${smtp.reason}（可用“用邮件客户端发送”）` }
+  if (smtp.ok !== true) return { ...base, reason: smtp.reason }
   return { ...base, transport: 'smtp', configured: true, fromMasked: maskEmail(smtp.endpoint.from), reason: '' }
 }
 
@@ -920,26 +921,6 @@ export function describeEnvironment({ version, dshVersion = '', now = new Date()
   ].join('\n')
 }
 
-/**
- * Build the `mailto:` URL the mail-app button navigates to.
- *
- * Lives on the Host on purpose: the plaintext recipient must not be rendered or
- * held by the page. The Client asks for a finished URL and only follows it.
- * @returns {string} a `mailto:` URL with encoded subject and body.
- */
-export function buildMailtoUrl({ to, version, input, userAgent = '' }) {
-  const subject = `[dsh-sidecard-ask ${version}] ${input.kind}: ${input.title}`
-  const text = [
-    `plugin: ${version}`,
-    `kind: ${input.kind}`,
-    input.body,
-    '',
-    `contact: ${input.contact === '' ? '(not provided)' : input.contact}`,
-  ]
-  if (userAgent !== '') text.push(`user agent: ${userAgent}`)
-  return `mailto:${to}?subject=${encodeURIComponent(subject)}&body=${encodeURIComponent(text.join('\n'))}`
-}
-
 /**
  * Send-rate gate: one mail per `minGapMs`, at most `maxPerWindow` per window.
  * Every send is recorded only after it actually went out, so a relay outage
@@ -2092,8 +2073,8 @@ export function apply(ctx, patchConfig) {
   /** `/state` — the Client's single source of truth at boot and after a save. */
   const handleState = (res) => {
     // Two secrets never reach the page: the recipient stays server-side (the page
-    // gets `hasRecipient` and asks for a finished `mailto:` URL), and the SMTP
-    // password is write-only (the page only learns whether one is stored).
+    // gets `hasRecipient` and `toMasked` only), and the SMTP password is
+    // write-only (the page only learns whether one is stored).
     const publicConfig = { ...state.config }
     delete publicConfig.feedbackAddress
     delete publicConfig.feedbackSmtpPass
@@ -2151,9 +2132,8 @@ export function apply(ctx, patchConfig) {
    * `/feedback` — mail one settings-page report to the configured recipient.
    *
    * Failure codes are the Client's contract: `feedback-unconfigured` (no
-   * recipient or no SMTP — the Client then offers `mailto:`),
-   * `feedback-invalid` (bounds), `feedback-too-fast` / `feedback-too-many`
-   * (gate), `feedback-send-failed` (relay refused). The report body is never
+   * recipient or no SMTP), `feedback-invalid` (bounds), `feedback-too-fast` /
+   * `feedback-too-many` (gate), `feedback-send-failed` (relay refused). The report body is never
    * logged; only kind, masked recipient and outcome are.
    */
   const handleFeedback = async (req, res) => {
@@ -2208,44 +2188,6 @@ export function apply(ctx, patchConfig) {
     }
   }
 
-  /**
-   * `/feedback-mailto` — hand the Client a finished `mailto:` URL.
-   *
-   * This exists so the plaintext recipient never has to enter the page: the
-   * settings form shows a mask, and when the user clicks "send with my mail app"
-   * the Host builds the URL and the Client only navigates to it.
-   */
-  const handleFeedbackMailto = async (req, res) => {
-    let body
-    try {
-      body = await readJsonBody(req)
-    } catch (error) {
-      writeError(res, 400, toWireError(error, 'bad-request').code, toWireError(error).message)
-      return
-    }
-    const input = sanitizeFeedbackInput(body)
-    if (input.ok !== true) {
-      writeError(res, 400, 'feedback-invalid', input.message)
-      return
-    }
-    const to = feedbackRecipient(state.config)
-    if (to === '') {
-      writeError(res, 503, 'feedback-unconfigured', '未配置收件邮箱：在设置页填写，或设置 DSH_SIDECARD_FEEDBACK_TO')
-      return
-    }
-    if (!looksLikeEmail(to)) {
-      writeError(res, 503, 'feedback-unconfigured', '收件邮箱格式不合法')
-      return
-    }
-    const url = buildMailtoUrl({
-      to,
-      version: PLUGIN_VERSION,
-      input: input.value,
-      userAgent: typeof body.userAgent === 'string' ? body.userAgent : '',
-    })
-    writeOk(res, { url, toMasked: maskEmail(to) })
-  }
-
   /** `/ask` — one SSE stream per side answer. */
   const handleAsk = async (req, res) => {
     let body
@@ -2338,7 +2280,7 @@ export function apply(ctx, patchConfig) {
    * The HTTP methods the plugin serves; kept in one place because the route
    * registration has two shapes (see below).
    */
-  const API_METHODS = ['state', 'ask', 'cancel', 'config', 'reset', 'diagnose', 'feedback', 'feedback-mailto']
+  const API_METHODS = ['state', 'ask', 'cancel', 'config', 'reset', 'diagnose', 'feedback']
 
   /** One request → one response; the dispatcher owns path parsing and the fence. */
   const routeHandler = async (req, res) => {
@@ -2373,7 +2315,6 @@ export function apply(ctx, patchConfig) {
       else if (method === 'reset') handleReset(req, res)
       else if (method === 'diagnose') await handleDiagnose(req, res)
       else if (method === 'feedback') await handleFeedback(req, res)
-      else if (method === 'feedback-mailto') await handleFeedbackMailto(req, res)
       else writeError(res, 404, 'not-found', `未知接口 "${method}"`)
     } catch (error) {
       const wire = toWireError(error)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-sidecard-ask",
-  "version": "1.9.1",
+  "version": "2.0.0",
   "description": "DSH 划词追问（侧边卡片作答）：在聊天区与任务区选中文本就地追问，答案由独立子代理在侧边卡片里流式呈现，也可选择落回主对话。",
   "type": "module",
   "main": "index.js",