dsh-client-ui-quote 0.12.4 → 0.12.5-lab.44

package/CHANGELOG.md

@@ -2,7 +2,10 @@
 
 ## Unreleased (lab)
 
-_（下一轮）_
+### Fixed
+
+- 草稿里的引用删掉后原文高亮还在：主会话「添加到对话 / 评论」把引用写成芯片时，坐标是当作「已发出」存进 `dsh-client-ui-quote:v2:quote-source` 的，读者随后在聚合条点 `×`（或直接退格删掉芯片）表示「不想添加了」，那张表却没有任何改动，于是原句上的淡黄高亮与序号一直留着——明明这条引用从没发出去。现在芯片写进草稿的坐标多带一个 `chip` 标记；`syncDraftBars` 每次扫描草稿时按卡片比对上一次看到的芯片，发现某颗芯片离开了一张**仍挂在页面上**的卡片、而页面上又没有它发出的胶囊时，就把对应坐标降级成 `draft`（`paintAnchors` 的既有跳过规则），高亮与序号随即收回并落库，刷新不会复活；芯片回来（宿主慢一拍才渲染回来、或读者又把同一句加回草稿）时 `restoreChipSource` 立刻补画。已经作为胶囊发出去过的同一段文字不受影响：`chip` 只写在草稿这次保存上，胶囊出现时 `promoteSource` 会清掉它；整个输入框离开页面（切会话）也不算删除。纯文本兜底（宿主没有芯片面）不会留下 `chip` 标记。
+- 离线断言 **686 组**（check 12 + capsule 470 + panel 160 + host 44）；新增 11 组断言：「添加到对话写进草稿的坐标带 `chip` 且落库」「芯片还在草稿时照常落色」「删掉芯片（未发送）高亮收回」「收回状态落库、刷新不复活」「芯片回来时补画」「胶囊出现后转正补画」「页面上已有胶囊时不误收」「整个输入框离页不算删除」「两个草稿共用同一坐标时删一颗不收回、删最后一颗才收回」。
 
 ## 0.12.4 — 2026-10-26
 

package/README.md

@@ -44,8 +44,8 @@
 | **添加到对话** | 直接把引用加进输入框，不弹评论框。输入框里已经写好的文字会留在原位：引用落到草稿**最上方**，你的文字另起一行接在下面，光标停在末尾，接着写正式提问即可。 |
 | **侧边对话** | 把引用写进一条**独立的侧边对话**的输入框。默认走**内置隐藏线程**：本插件的宿主半用 `agents.create` 建一个 `origin: "subagent"` 子会话（会话列表不显示它），主会话最近几轮的原话作为**一条可折叠的隐性上下文**注进去，而不是把整条历史铺出来，用宿主内置的 `subagentchat` 页签打开——聊天记录、输入框、流式输出与工具调用全是 DSH 原生的。宿主半不可用（旧宿主 / 父会话不在线 / 创建被拒）时自动退回 `sessions.fork` + 本插件 `quote-sidechat` 页签；把 `sideChatBackend` 设成 `"better"` 才优先走 dsh-better-sidebar。**不装 better-sidebar 也有隐藏线程**；装了也不会冲突，两边共享 `Side: ` 持久约定但路由、存储与 descriptor 各自独立。所有后端都**什么都不发送**，线程独立运行、不污染主会话，页签自动在右侧栏打开。同一条主会话只开一条线程，之后每次点都在同一条线程的草稿后面接着追加。鲸鱼蓝（`#4d6bfe`）的图标是它在浮层里的标识。浮层里**只有一项**「侧边对话」——两个长得一样的入口只会让人犹豫；早期版本按引用分过线程的记录仍会被识别并复用。引用清单页底部会列出这个会话的**全部侧边线程**，每条都能重新打开。 |
 | **键盘直达** | `Alt+Q` 引用 / `Alt+C` 评论 / `Alt+B` 侧边对话——同一个浮层的三个动作，不弹浮层直接办。走 DSH 的快捷键服务注册，所以出现在设置里、可改键、与宿主键位冲突会在注册时报错；没有选区时返回 `pass`，按键不会被吞掉。 |
-| **原文侧高亮** | 引用落进草稿或发出后，被引用的原句回到**来源消息**里留下淡黄高亮与**序号角标**（序号就是坐标里的同句序号，和 `「引用N」` 对得上）。支持 `CSS.highlights` 的宿主由浏览器**直接绘制高亮**，滚动、流式输出、虚拟列表重排都跟手，不靠逐帧重画去追；不支持时才退回浮层矩形（只画序号徽章）。行不在视口里、文字已经变了、宿主不给 `Range` 时就静默跳过，**不改宿主的 DOM**（高亮不包 `mark`，也不搬节点）。表格单元格、表格行、段落、列表项、`<br>` 这些块级边界按浏览器选区报告的 `\t` / `\n` 对齐，所以跨单元格、跨行、跨段落的引用也能画回来。 |
-| **聚合引用条** | 输入框上方一条 **`引用 ×N`**：每颗芯片一个摘要胶囊，点一下跳回原文（跳不到就把光标放到芯片上，一次退格删掉），悬停就是完整卡片；每条末尾有 **`✎` 编辑**与 **`×` 移除**：编辑把原引用与评论回填进注释框，确认后旧芯片让位、新芯片原地插入；移除优先走宿主自己的 `consumeToken`（按芯片的 detect 区间与 `draftRev` 做 CAS 精确删除，不会碰错别的文本），宿主没有这个读取面或同名芯片无法区分时才退回「聚焦芯片 + 退格」并提示。**整条索引存在本机**：宿主会跨刷新恢复草稿里的芯片，插件的索引也一起恢复，所以刷新后条、卡片与「打开文件」都还在。主会话与侧边线程各自的输入框各有一条；芯片删光时条自己消失。整条带 `role=toolbar`，每颗胶囊的可访问名是完整引用+评论，不是截断后的标签。 |
+| **原文侧高亮** | 引用落进草稿或发出后，被引用的原句回到**来源消息**里留下淡黄高亮与**序号角标**（序号就是坐标里的同句序号，和 `「引用N」` 对得上）。**芯片被移出草稿（没有发送）时，这块高亮与序号一起收回**——不想添加了就不该在原文上留标记；已经作为胶囊发过的引用不受影响。支持 `CSS.highlights` 的宿主由浏览器**直接绘制高亮**，滚动、流式输出、虚拟列表重排都跟手，不靠逐帧重画去追；不支持时才退回浮层矩形（只画序号徽章）。行不在视口里、文字已经变了、宿主不给 `Range` 时就静默跳过，**不改宿主的 DOM**（高亮不包 `mark`，也不搬节点）。表格单元格、表格行、段落、列表项、`<br>` 这些块级边界按浏览器选区报告的 `\t` / `\n` 对齐，所以跨单元格、跨行、跨段落的引用也能画回来。 |
+| **聚合引用条** | 输入框上方一条 **`引用 ×N`**：每颗芯片一个摘要胶囊，点一下跳回原文（跳不到就把光标放到芯片上，一次退格删掉），悬停就是完整卡片；每条末尾有 **`✎` 编辑**与 **`×` 移除**：编辑把原引用与评论回填进注释框，确认后旧芯片让位、新芯片原地插入；移除优先走宿主自己的 `consumeToken`（按芯片的 detect 区间与 `draftRev` 做 CAS 精确删除，不会碰错别的文本），宿主没有这个读取面或同名芯片无法区分时才退回「聚焦芯片 + 退格」并提示。**移除（或直接退格删掉芯片）之后，如果这条引用从没真正发出去，原句上的高亮与序号也一起收回**；页面上已经有它发出的胶囊时则照旧保留。**整条索引存在本机**：宿主会跨刷新恢复草稿里的芯片，插件的索引也一起恢复，所以刷新后条、卡片与「打开文件」都还在。主会话与侧边线程各自的输入框各有一条；芯片删光时条自己消失。整条带 `role=toolbar`，每颗胶囊的可访问名是完整引用+评论，不是截断后的标签。 |
 | **来源头** | 发送块尾部的坐标行前面多一段人可读的出处：**`※ 引自第 12 轮 · 助手 │q1:…`**，模型不解码也知道来自哪一轮、谁说的；角色属性宿主没给时就只写轮次。胶囊悬停卡片里同样显示 `引自第 12 轮 · 助手`，按界面语言本地化。 |
 | **Diff 划选** | 在 diff / 每轮改动面板里划选也走同一个浮层：引用按**代码块**发，围栏信息位带探测到的文件路径与行号（`src/app.ts#L12`）；路径、行号是宿主 DOM 上的探测，拿不到就只带代码，不影响引用本身。有路径时卡片/清单可直接打开文件并定位到起始行。 |
 | **清单多选插入** | 引用清单每行一个勾选框，`插入所选` 一次把多条引用写进输入框——每条各成一颗芯片、各自带坐标，不合并；芯片通路不可用时退回一段包含多个引用块的文本。这一栏是只读导航 + 批量插入，不做就地删除——删除与编辑在**草稿上方的聚合条**里做（宿主暴露了按区间消费 token 的 `consumeToken`；旧宿主没有这个读取面时才退回退格路径）。 |
@@ -139,7 +139,7 @@ link 的优点是改完刷新即生效；**日常运行请用方式一**，不
 
 本机切换这三档（这台开发机专用的辅助脚本，不在仓库里）：`node .dsh-quote-work/profile-mode.mjs link|lab|stable|status`。换完在窗口里 `Ctrl+Shift+R` 生效；只有宿主半有改动时才需要重启桌面端。
 
-两条线的断言入口相同：`npm test`（675 项：check 12 + capsule 459 + panel 160 + host 44）；`.github/workflows/test.yml` 在每次 push / PR 上用 Node 18/20/22 各跑一遍，`publish.yml` 里 `prepublishOnly` 再跑一次才发。
+两条线的断言入口相同：`npm test`（686 项：check 12 + capsule 470 + panel 160 + host 44）；`.github/workflows/test.yml` 在每次 push / PR 上用 Node 18/20/22 各跑一遍，`publish.yml` 里 `prepublishOnly` 再跑一次才发。
 
 **推送通道**：`git push` 优先，但本机 `github.com:443` **时通时不通**（2026-10-19 实测：短时可用、随后连续超时，每次失败等约 21 秒）。日常用工作区根的 `promote.ps1`：先试 git，失败自动转 REST 兜底（`.dsh-quote-work/publish-release.mjs`、`.dsh-quote-work/push-branch.mjs`，`-Channel rest` 可跳过探测），并核对远端 SHA。**别混用两条通道**：REST 重建的提交时区归一到 `+0000`，内容相同但 SHA 不同，同一分支混推会分叉（`git status` 看着干净，远端却多一条平行提交）；恢复就先 `git fetch`、确认 `git diff <本地> <远端>` 为空，再把本地线 reset 到远端。
 
@@ -328,7 +328,7 @@ transcript 侧的 `.dshq-cap` 胶囊：一颗胶囊同时装引用与评论，`
 1. **语义而不是机制**：引用与评论是同一颗节点（对齐 Kimi 的 `quote` 节点 `{text, comment}`），一颗芯片 → 一个块 → 一颗胶囊 → 一张卡片 → 一次复制；机制（reference chip、DOM 增强）谁都能抄，这条链子不好抄。
 2. **引用是带坐标的活对象**：`跳回原文` 在自己的会话面板里找行、按宿主的方式对齐到 24px，行被虚拟列表藏起来或没挂载都能找回来；坐标以「人可读来源头 + base64 尾巴」随消息走——前者让模型知道出处，后者让插件跨刷新回读。base64 确实占一点 prompt，这是用「不依赖本地表」换来的取舍。
 3. **引用有下落**：清单页（搜索 / 跳转 / 导出 Markdown）+ 侧边线程回流（结论写回主会话草稿 / 导出线程），这两件事在同类里仍是少数。
-4. **工程化**：675 项离线断言（含真跑 `sessions.retain` / `setDraft` / `agents.create` 参数 / 下载链路）、每个宿主契约都在 README 里写明出处、每个版本都有可回读的 release。同类里做到同等断言规模的仍是少数。
+4. **工程化**：686 项离线断言（含真跑 `sessions.retain` / `setDraft` / `agents.create` 参数 / 下载链路）、每个宿主契约都在 README 里写明出处、每个版本都有可回读的 release。同类里做到同等断言规模的仍是少数。
 
 反过来也要说清楚：**本插件不做的**——不做翻译/解释/改写/飞书投递类选区动作；不做图片/截图引用（**明确取舍**：图片引用要的是另一套胶囊/卡片/附件语义，是第二个产品的量级，塞进这里只会把「文本引用带坐标」这条主线冲淡；`dsh-selection-toolbar` 与 Kimi 桌面端已经做了，真要做建议独立成插件）；不做完整 Topic 系统；不做常显大块引用。它只把「引用」这一件事做穿——但「做穿」包括发送后的管理、来源闭环和审阅，不只是浮层。
 
@@ -365,9 +365,9 @@ locale/zh.json        插件页卡片文案（中文）
 locale/en.json        插件页卡片文案（英文）
 test/check.mjs        离线自检（清单 + 组件契约）
 test/dom.mjs          给离线自检用的最小 DOM / MutationObserver 垫片
-test/capsule.mjs      离线自检（发送后胶囊 + 悬停卡片 + 跳回原文 + 键位 + 改这条引用 + 代码引用 + 文件路径打开 + 聊天代码块划选 + 选区保结构 + 回合级引用 + 逐条回应双语 + 草稿引用编辑/持久化 + 聚合条移除/无障碍 + 行范围标记 + 浮层不随座位失效，459 项断言）
+test/capsule.mjs      离线自检（发送后胶囊 + 悬停卡片 + 跳回原文 + 键位 + 改这条引用 + 代码引用 + 文件路径打开 + 聊天代码块划选 + 选区保结构 + 回合级引用 + 逐条回应双语 + 草稿引用编辑/持久化 + 聚合条移除/无障碍/移除后原文标记收回 + 行范围标记 + 浮层不随座位失效，470 项断言）
 test/panel.mjs        离线自检（引用清单：解析 / 搜索 / Markdown / 读取 / 导出 / 页面注册 + 文件路径打开 + 侧边线程回流 + 审阅工作台（状态 / 标签 / 批量）+ JSON 导出 + 本地索引，160 项断言）
-test/host.mjs         离线自检（宿主半：标签 / 隐性上下文种子（切点 + 一个收口回合包着上下文消息 + descriptor；只带用户与助手的原话、8000 字上限、跳过注入上下文）/ 空日志兜底 / 继承切点与 descriptor 顺序 / agents.create 参数 / 探针 / 围栏 / 路由注册与卸载，43 项断言）
+test/host.mjs         离线自检（宿主半：标签 / 隐性上下文种子（切点 + 一个收口回合包着上下文消息 + descriptor；只带用户与助手的原话、8000 字上限、跳过注入上下文）/ 空日志兜底 / 继承切点与 descriptor 顺序 / agents.create 参数 / 探针 / 围栏 / 路由注册与卸载，44 项断言）
 test/capsule.html     真浏览器里跑同一套胶囊断言（51 项，可选）
 ```
 
@@ -419,7 +419,7 @@ React 重渲染不会出现第二颗、引用变了就地重建、消息被删
 **浮层不跟着座位生死**（`conversation.input.overlay` 没挂载也能选中出栏、挂上两个会话座位既不叠加也不丢监听、
 座位不在时用输入框自己的 `actions` 落芯片、无处可插时给 toast 而不是静默返回、effect 卸载/重装后监听恰好一份、
 **放弃动作不留高亮**（浮层 `mousedown` 保住的选区在 `Esc` / 取消退场时被还回去））；
-（共 459 项，含文件路径与逐条回应的线上形态、`parseCodeSource`/`fileAddressFor` 与「卡片/清单点击打开 session 文件并带上起始行」、**表格单元格 / 表格行 / 段落 / 列表项 / `<br>` 边界的引用高亮**、**侧聊坐标在发出前不着色、`promoteSource` 转正后才补画**、**输入框已有文字时引用置顶并将原文另起一行**、聊天代码块划选的语言探测与跨界降级、选区的链接/行内代码保真与纯文本回退、回合级引用的取文与坐标、英文逐条指令与「Quote N」徽章、草稿芯片索引的跨刷新恢复与聚合条编辑/移除、回复徽章的建立/重建/卸载与悬停卡片复用、原生 `quote-sidechat` 页签的注册 / 地址 / 标题 / retain-release、内置 subagentchat 的降级与复用，以及评论框两个输入区的自适应高度——引用正文那格曾经在被挂进栏之前就量高，读到 0 后被写成 `height:0`，首行因此被裁掉）。
+（共 470 项，含文件路径与逐条回应的线上形态、`parseCodeSource`/`fileAddressFor` 与「卡片/清单点击打开 session 文件并带上起始行」、**表格单元格 / 表格行 / 段落 / 列表项 / `<br>` 边界的引用高亮**、**侧聊坐标在发出前不着色、`promoteSource` 转正后才补画**、**草稿芯片删掉（没发送）后原文高亮与序号收回、芯片回来或胶囊出现才补画（已有胶囊/整个输入框离页不误收）**、**输入框已有文字时引用置顶并将原文另起一行**、聊天代码块划选的语言探测与跨界降级、选区的链接/行内代码保真与纯文本回退、回合级引用的取文与坐标、英文逐条指令与「Quote N」徽章、草稿芯片索引的跨刷新恢复与聚合条编辑/移除、回复徽章的建立/重建/卸载与悬停卡片复用、原生 `quote-sidechat` 页签的注册 / 地址 / 标题 / retain-release、内置 subagentchat 的降级与复用，以及评论框两个输入区的自适应高度——引用正文那格曾经在被挂进栏之前就量高，读到 0 后被写成 `height:0`，首行因此被裁掉）。
 `test/capsule.html` 是同一套断言的真浏览器版（51 项），用 `file://` 打开即可（页面会把结果写进标题与 `#probe-out`）。这一版修好了它**缺失的 `<body>` 标签**——脚本在 `<head>` 里执行时 `document.body` 为 null，这个页面以前在真浏览器里是直接坏的；并补上真 `Range` 的链接/行内代码断言（真浏览器的 `cloneContents()` 返回的是 DocumentFragment，不是元素——序列化器只认元素的话，链接在真浏览器里会退化成纯文本；离线桩现在也用真片段，不再放过这一类），另外补了 `CSS.highlights` 选区保持与关闭清理。
 
 `test/panel.mjs` 单独跑引用清单页与侧边线程回流（160 项）：只认**持久**的 `user/message`（`transient`、助手消息、`data: null` 都跳过）、
@@ -440,7 +440,7 @@ Markdown 的标题/编号/块引用/评论行/时间戳与空列表兜底、超
 
 `test/host.mjs` 不需要浏览器：它直接 import 宿主半，用桩 `agents` / `agentPresets` / `sessionTitle` / `webServer` 驱动。断言包括：`Side: ` 标签的前缀与截断；种子固定三件事（`session/end-seed{inherited:true}` → 一条 `source.kind="session-context"` 的 `user/message` → `subagent/descriptor`）、`inheritedEventCount` 恒为 0、上下文字段只收用户与助手的原话（最新在后、8000 字上限、跳过 `runtime-context` 与工具事件）、空日志也有可读文案；descriptor 排在切点之后且 seq 连续；`agents.create` 收到 `origin: "subagent"` / `parentSession` / `isSeeded` / `inheritedEventCount` / 父会话当前模型路由 / preset setup / 清空继承 inbox / 固定标题；探针、409、503、403、405、404 与 `apply` 的注册/卸载全部有断言。
 
-合计 **675 组**（check 12 + capsule 459 + panel 160 + host 44），`npm test` 全绿。
+合计 **686 组**（check 12 + capsule 470 + panel 160 + host 44），`npm test` 全绿。
 
 ## 已知限制
 
@@ -469,13 +469,14 @@ Markdown 的标题/编号/块引用/评论行/时间戳与空列表兜底、超
 - 更新**之前**发出的老消息不会被变成胶囊：它们的文本里没有 `❝` 标记，插件无从辨认（重新引用一次即可）。
 - **原文高亮用完整引用文本定位**：页面刚刷新、那颗胶囊还没渲染时，插件手里只有坐标表里的前 120 字身份键，长引用会先亮前 120 字；胶囊进入视口后补上全文并自动重画。行不在视口、被虚拟列表收起、或文字已经变了就不画，绝不改宿主 DOM。支持 `CSS.highlights` 时高亮由浏览器绘制（跟手、不逐帧追滚动），不支持时退回浮层矩形；两种模式都不包 `mark`。
 - **侧边对话的坐标要等它真的发出去才落色**：第三项存坐标时带 `draft` 标记，`paintAnchors` 跳过它，所以原文上不会先亮一块——放弃或关掉侧边对话都不留痕迹。转正靠胶囊：那句引用以胶囊形态出现在某条 transcript（同一个 ref）时才 `promoteSource` 并补画。因此**在另一个窗口**里把侧聊引用发出去时，本窗口要等下一次刷新（重新读 `localStorage` 里的表）才会补上这块高亮，而不是立刻出现。
+- **草稿里的芯片删掉后，原文标记会跟着收回**：主会话「添加到对话 / 评论」写进草稿的坐标以 `chip` 记在表里；聚合条的 `×` 或直接退格让芯片离开草稿、而页面上又没有它发出的胶囊时，坐标转成 `draft`（同样的跳过规则），高亮与序号随即收起，落库后刷新也不会复活。已经作为胶囊发出去过的同一段文字不受影响。收回是**按草稿卡片观察**的：整个输入框离开页面（切会话）不算删除；**在另一个窗口**里删掉的芯片，本窗口要等下一次刷新（重新读表）才收回。
 - **跨消息的选区不带来源头**：选区起点与终点落在不同消息行时，引用照常发出（原文、评论、代码形态都在），但不写 `引自第 N 轮 · 助手`，也不带可跳回的坐标——一句话横跨两轮时，任何单一轮次都是错的。想要带来源，就分两次引用。
 - **评论框期间的原选区高亮依赖 `CSS.highlights`**：Chromium/Electron 支持；不支持时静默跳过，评论框里仍有引用正文，不影响引用本身。
 - **聚合引用条的移除与编辑优先用宿主的 `consumeToken`**（实测 DSH 0.2.1-rc.2 的 conversation shell）：宿主把每个芯片投影成一条 occurrence（`offset`/`length`/`label`/`source`），`consumeToken({kind:"span", span:{start,end,draftRev}})` 在 `draftRev` 仍是当前版本时精确删掉这段区间；本插件据此计算 detect 区间（芯片在前面的 occurrence 会把坐标左移 `length - 1`）并带上紧跟的一个空格。宿主没有 `compose()`/`consumeToken`（旧版）或两条同标签芯片无法区分时，才退回「聚焦芯片 + 派发一次 Backspace」；两步都不成功时提示手动按一次退格，绝不做半删除的草稿。`✎` 编辑走同一条移除路径——旧芯片先让位，新芯片再原地插入。草稿芯片的索引存在本机（`dsh-client-ui-quote:v1:chip-index`），所以**刷新后**条、悬停卡与「打开文件」都还在——宿主本来就会恢复草稿里的芯片，索引跟着恢复，它们才重新算是本插件的引用。
 
 - **回合级引用依赖宿主的回合尾槽位**：宿主把每条回合的尾部做成一个列表子槽位（`conversation.chat.turnTail`，`kind:"list"`、`scope:"session"`），本插件往里加一条。宿主没有这个槽位时按钮不出现——功能缺失，其它能力不受影响。
 - **引用清单的本机索引只在本机**：它兜的是「上下文压缩把消息裁掉」这一种丢失，记录不进模型上下文、不跨设备、不跨浏览器；没读过的引用它当然也不知道。
-- **侧边对话有一条内置主路 + 三条退路**：默认是宿主半创建的内置隐藏线程（`origin: "subagent"` + 宿主 `subagentchat` 页，会话列表不显示）；父会话不在线 / 宿主半不可用时退回 `sessions.fork` + 本插件 `quote-sidechat` 页签（线程作为普通 fork 出现在会话列表）；再不行才走 dsh-better-sidebar（仅显式 `sideChatBackend: "better"` 或最后兜底）。隐藏线程与 better-sidebar 共享 `Side: ` 标题约定，所以两边的线程列表可以互相看见，但存储键、路由与 descriptor provider 各自独立。未在侧聊里提问前执行「带回主会话」，可能取到复制过来的最后一轮，先在侧聊里问一句即可。所有后端都不可用时浮层里没有侧边对话那两行。
+- **侧边对话有一条内置主路 + 三条退路**：默认是宿主半创建的内置隐藏线程（`origin: "subagent"` + 宿主 `subagentchat` 页，会话列表不显示）；父会话不在线 / 宿主半不可用时退回 `sessions.fork` + 本插件 `quote-sidechat` 页签（线程作为普通 fork 出现在会话列表）；再不行才走 dsh-better-sidebar（仅显式 `sideChatBackend: "better"` 或最后兜底）。隐藏线程与 better-sidebar 共享 `Side: ` 标题约定，所以两边的线程列表可以互相看见，但存储键、路由与 descriptor provider 各自独立。未在侧聊里提问前执行「带回主会话」，可能取到复制过来的最后一轮，先在侧聊里问一句即可。所有后端都不可用时浮层里没有侧边对话那一行。
 
 ## 下一步
 
@@ -485,7 +486,7 @@ Markdown 的标题/编号/块引用/评论行/时间戳与空列表兜底、超
 - **Markdown 预览的行号**：要精修就得读源文件，而客户端必须声明 `remote` 才能拿到它；声明错会让 client bundle 在不匹配的宿主上**静默失效**（`dsh-quote-annotate` 上游就是这么死的）。所以先不声明——文件仍然打开，只是落在顶部而不是行上。
 - **表格/列表/LaTeX 的结构保真**：链接与行内代码已做；表格要还原成 Markdown 表格，列表要还原成缩进，成本明显更高，留到有人真的需要时再做。
 - **图片/截图引用**：明确不做（理由见「本插件不做的」）。真要做请独立成插件：图片引用要的是另一套胶囊/卡片/附件语义。
-- **真机验证**：这一轮的宿主契约全部来自 `app.asar` 的一手文档，功能路径有 675 项离线断言；隐藏线程的 `agents.create` / 种子格式已在**隔离的 DSH web 实例**（临时 `DSH_HOME`，端口 8791，CLI 0.2.1-rc.3）里确认：宿主半通过 `ctx.inject(["webServer"])` 晚到注册，`POST /ui-quote/api/sidechat.start` 的探针返回 `{"ok":true,"value":{"available":true,"version":1}}`，说明 `agents` 服务与同源围栏都就绪。本轮又在**运行中的桌面端**（link 模式，重启后加载 `lib/index.js`）核对过一次：`/ui-quote/api/*` 下任意路径都先被围栏拦成 `403 {"code":"forbidden"}`，而同样方法打一个不存在的顶层路径是 `404`，说明前缀路由确实挂上了、并且先过围栏。原生侧聊页签的 `SessionProvider` / `conversation.content` 嵌入契约还需要在真实窗口里重开一次侧边对话确认（离线桩只覆盖注册、地址、标题与 retain/release，不渲染宿主组件）。真浏览器（1600×2000 视口）同一套断言本轮复核 **51/51**。欢迎页的交互点击被安全闸门拦下，因此下面四条仍需在真实窗口逐项点：聚合条编辑、回合尾的两个按钮、打开文件与行范围标记、JSON 导出。
+- **真机验证**：这一轮的宿主契约全部来自 `app.asar` 的一手文档，功能路径有 686 项离线断言；隐藏线程的 `agents.create` / 种子格式已在**隔离的 DSH web 实例**（临时 `DSH_HOME`，端口 8791，CLI 0.2.1-rc.3）里确认：宿主半通过 `ctx.inject(["webServer"])` 晚到注册，`POST /ui-quote/api/sidechat.start` 的探针返回 `{"ok":true,"value":{"available":true,"version":1}}`，说明 `agents` 服务与同源围栏都就绪。本轮又在**运行中的桌面端**（link 模式，重启后加载 `lib/index.js`）核对过一次：`/ui-quote/api/*` 下任意路径都先被围栏拦成 `403 {"code":"forbidden"}`，而同样方法打一个不存在的顶层路径是 `404`，说明前缀路由确实挂上了、并且先过围栏。原生侧聊页签的 `SessionProvider` / `conversation.content` 嵌入契约还需要在真实窗口里重开一次侧边对话确认（离线桩只覆盖注册、地址、标题与 retain/release，不渲染宿主组件）。真浏览器（1600×2000 视口）同一套断言本轮复核 **51/51**。欢迎页的交互点击被安全闸门拦下，因此下面四条仍需在真实窗口逐项点：聚合条编辑、回合尾的两个按钮、打开文件与行范围标记、JSON 导出。
 - **市场收录与首屏**：README 已有截图、徽章、「30 秒上手」与 24 秒静态轮播 GIF；还差把插件提交到 dsh.market / dsh-plugin.org / dsh.pub / awesome-deepseek-harness —— 这些需要外部账号，是人工动作。
 
 ## 变更记录
@@ -521,7 +522,7 @@ Screenshots: [floating bar](docs/screenshots/bar.png) · [comment box](docs/scre
 Install with `dsh plugin --profile desktop add dsh-client-ui-quote` (published on npm; DSH >= 0.2.0-rc.2, web/desktop client).
 Test with `npm test`. MIT licensed.
 
-Kimi Code is where the interaction started, not the whole comparison. As of 2026-10 the DSH market has at least a dozen quote/annotation plugins — `dsh-annotation`, `dsh-sidenote`, `CiteCiter`, `dsh-quote-annotate-pro`, `dsh-select-quote`, `dsh-selection-toolbar`, and others. The floating bar is table stakes; the differentiator here is what happens after the quote is sent: a source highlight and ordinal, jump-back, a searchable review list, side-thread bring-back, revisions, and per-quote reply badges. The draft's `引用 ×N` bar removes a quote through the host's `consumeToken` span CAS (exact occurrence coordinates, draft-revision guarded), falling back to the editor's own Backspace path on hosts without that face, with a manual-backspace hint if neither applies. A preview/diff quote's file now appears as a clickable `path#Lx-Ly` line in the hover card and the quote list; clicking it opens the right sidebar's document preview at the range's first line through `sidebarRight.openResource`, focusing an already-open tab instead of duplicating it. A selection inside one rendered chat code block is quoted as a fenced block carrying the renderer's language, and degrades to a plain blockquote when the selection crosses the block boundary. A quote that is still in the draft can be edited or removed from the aggregate bar, and the chip index is kept locally so a reload does not lose the bar, the hover card or the file it points at. A code quote shows its source (`文件预览 · src/app.ts · L12-L48`) and opens the sidebar's document preview at that line. Side chats are bound per quote — the overlay offers “Open another side chat”, and the quote list shows every thread of the session; by default the same flow creates a hidden seeded subagent thread through the plugin's host half and opens it in the host's built-in chat, with a fork in the plugin's own page as the fallback and better-sidebar as an opt-in backend. Built-in threads share better-sidebar's durable `Side: ` convention, so the two plugins can see each other's threads without sharing storage, routes or descriptors. The quote list exports Markdown and JSON, keeps a local index so a context compaction cannot empty it, and a small whitelisted set of switches plus a `window.__dshQuote` handle sits behind it all. The Chinese section above carries the current 2026-10 market comparison; this plugin is not a Kimi Code clone.
+Kimi Code is where the interaction started, not the whole comparison. As of 2026-10 the DSH market has at least a dozen quote/annotation plugins — `dsh-annotation`, `dsh-sidenote`, `CiteCiter`, `dsh-quote-annotate-pro`, `dsh-select-quote`, `dsh-selection-toolbar`, and others. The floating bar is table stakes; the differentiator here is what happens after the quote is sent: a source highlight and ordinal, jump-back, a searchable review list, side-thread bring-back, revisions, and per-quote reply badges. The draft's `引用 ×N` bar removes a quote through the host's `consumeToken` span CAS (exact occurrence coordinates, draft-revision guarded), falling back to the editor's own Backspace path on hosts without that face, with a manual-backspace hint if neither applies. A preview/diff quote's file now appears as a clickable `path#Lx-Ly` line in the hover card and the quote list; clicking it opens the right sidebar's document preview at the range's first line through `sidebarRight.openResource`, focusing an already-open tab instead of duplicating it. A selection inside one rendered chat code block is quoted as a fenced block carrying the renderer's language, and degrades to a plain blockquote when the selection crosses the block boundary. A quote that is still in the draft can be edited or removed from the aggregate bar, and the chip index is kept locally so a reload does not lose the bar, the hover card or the file it points at. A code quote shows its source (`文件预览 · src/app.ts · L12-L48`) and opens the sidebar's document preview at that line. A main session keeps exactly one side thread: the floating bar offers a single 侧边对话 row (a second, identical-looking entry was dropped — threads created by older per-quote builds are still recognised and reused), later quotes append to the same thread's draft, and the quote list shows every thread of the session; by default the same flow creates a hidden seeded subagent thread through the plugin's host half and opens it in the host's built-in chat, with a fork in the plugin's own page as the fallback and better-sidebar as an opt-in backend. Built-in threads share better-sidebar's durable `Side: ` convention, so the two plugins can see each other's threads without sharing storage, routes or descriptors. The quote list exports Markdown and JSON, keeps a local index so a context compaction cannot empty it, and a small whitelisted set of switches plus a `window.__dshQuote` handle sits behind it all. The Chinese section above carries the current 2026-10 market comparison; this plugin is not a Kimi Code clone.
 
 Two wire-only extras ride on the same pipeline: a per-quote reply toggle in the comment box (the block carries a
 transport-only instruction, the model answers `「引用N」` by `「引用N」`, and each label becomes a badge that reopens

package/docs/distribution.md

@@ -8,7 +8,7 @@
 | --- | --- |
 | npm | `dsh-client-ui-quote` |
 | 仓库 | https://github.com/BangBang-03/dsh-client-ui-quote |
-| 版本 | `0.12.1` |
+| 版本 | `0.12.4`（发版时同步；最终以 `package.json` 为准） |
 | License | MIT |
 | 图标 | `icon.svg` |
 
@@ -67,8 +67,8 @@ awesome-deepseek-harness 的列表条目（英文，一行）：
 ## 发布前
 
 1. 把 `CHANGELOG.md` 顶部的 `Unreleased (lab)` 改成正式版本号（`## X.Y.Z — YYYY-MM-DD`），在 lab 上提交。
-2. 推 `lab`（CI 发一个 `-lab.N` 预发布），在真实 DSH 窗口点一遍：聚合条编辑/移除、回合尾按钮、打开文件与行范围、另开侧边对话、JSON 导出。
+2. 推 `lab`（CI 发一个 `-lab.N` 预发布），在真实 DSH 窗口点一遍：聚合条编辑/移除、回合尾按钮、打开文件与行范围、侧边对话（内置隐藏线程）、JSON 导出。
 3. 发正式版：`main` 快进到 `lab` 并推送 → 在 `main` 头上打 `vX.Y.Z` 标签并推送。标签会同时触发两件事：**npm `latest` 发布** 与 **GitHub Release 创建**（正文取自 CHANGELOG 同名小节；已存在则更新 notes，重跑安全）。
 4. 发完确认三处一致：`npm view dsh-client-ui-quote dist-tags` 的 `latest`、仓库 Releases 页的最新一条、`git ls-remote --tags` 的标签指向同一个提交。
 
-已复核：`npm test` 549 组离线断言；真浏览器（1600×2000 视口）51/51；隔离 DSH web 实例中工作区 link 与 npm lab 发布包均加载成功，`__dshQuote` 可用、conversation/inputTriggers/sidebarRight/sidebarRightTabs 可见、`probe().nativeSideChat === true`（betterSidebar 缺失）；`npm pack --dry-run` 包含 README、截图、GIF 与本文件。真实窗口的五条交互路径仍需人工点击。
+已复核：`npm test` 686 组离线断言；真浏览器（1600×2000 视口）51/51；隔离 DSH web 实例中工作区 link 与 npm lab 发布包均加载成功，`__dshQuote` 可用、conversation/inputTriggers/sidebarRight/sidebarRightTabs 可见、`probe().nativeSideChat === true`（betterSidebar 缺失）；`npm pack --dry-run` 包含 README、截图、GIF 与本文件。真实窗口的四条交互路径仍需人工点击（聚合条编辑、回合尾按钮、打开文件与行范围、JSON 导出）。

package/lib/client.js

@@ -2455,6 +2455,8 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 		let chipWireBudget = 0;
 		/** Composer card -> its aggregate quote bar; at most one bar per composer. */
 		const draftBars = new Map();
+		/** Composer card -> the refs of the quote chips it held on the last pass. */
+		const cardChips = new Map();
 		let draftBarTimer = null;
 		/** Below this many pills the bar shows them all; beyond it, a `+N`. */
 		const DRAFTBAR_LIMIT = 5;
@@ -2764,6 +2766,7 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 			// Absent, not `false`, when it is not a draft: the stored table stays
 			// the shape older builds wrote.
 			if (value.draft === true) candidate.draft = true;
+			if (value.chip === true) candidate.chip = true;
 			return candidate;
 		}
 
@@ -3021,11 +3024,17 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 		 * sent anywhere yet — the side thread's chip. The row still resolves (the
 		 * card and the jump need its ordinal) but it is not painted on the source
 		 * until the quote turns up in a transcript; see `promoteSource`.
+		 *
+		 * `options.chip` marks a coordinate minted by a chip in a composer. Unlike
+		 * a draft it may paint right away (the quote is in a visible draft), but it
+		 * remembers that a chip is what holds it: `syncDraftBars` retracts the mark
+		 * when that chip leaves the draft without sending (see `retractChipSource`).
 		 */
 		function saveSource(quote, sessionId, source, options) {
 			const key = sourceKeyOf(quote);
 			if (key.length < 4 || source === null || typeof source !== "object") return null;
 			const draft = options !== null && typeof options === "object" && options.draft === true;
+			const chip = options !== null && typeof options === "object" && options.chip === true;
 			const owner = typeof source.sessionId === "string" && source.sessionId !== "" ? source.sessionId : sessionId;
 			if (typeof owner !== "string" || owner === "") return null;
 			const attr = source.attr;
@@ -3045,6 +3054,7 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 				for (const entry of list) ordinal = Math.max(ordinal, (Number(entry.n) || 0) + 1);
 				candidate = { sessionId: owner, attr, key: rowKey, turn, quote: key, at, n: ordinal, role, origin };
 				if (draft) candidate.draft = true;
+				if (chip) candidate.chip = true;
 				list.push(candidate);
 			} else {
 				const kept = role === "" && ROLE_CODES.has(list[index].role) ? list[index].role : role;
@@ -3056,6 +3066,10 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 				// The other direction is the promotion — a plain save (a send)
 				// simply drops the mark.
 				if (draft === true && list[index].draft === true) candidate.draft = true;
+				// The chip mark survives every later save while it is set: a save
+				// means the quote is still in some draft, and only a capsule
+				// (`promoteSource`) proves the chip that minted it is gone.
+				if (list[index].chip === true) candidate.chip = true;
 				list[index] = candidate;
 			}
 			// Re-insert so the Map's own order agrees with "this was just used".
@@ -3163,30 +3177,125 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 			return out;
 		}
 
+		/**
+		 * Drop the given bookkeeping marks from every stored coordinate with this
+		 * ref. The identity is the ref alone (`session\0attr\0row\0turn\0ordinal`):
+		 * the ordinal already tells one quoted sentence in a row from another,
+		 * while the wording can be spelled differently on the way back (a code
+		 * quote loses its marks on save) and must not stop the write.
+		 *
+		 * @returns {boolean} true when something changed (the caller repaints).
+		 */
+		function dropSourceMarks(ref, names) {
+			const wire = normalizeRef(ref);
+			if (wire === null) return false;
+			const id = refTextKeyOf(wire);
+			if (id === "") return false;
+			let dropped = false;
+			for (const list of sourceIndex.values()) {
+				for (const entry of list) {
+					if (refTextKeyOf(entry) !== id) continue;
+					for (const name of names) {
+						if (entry[name] !== true) continue;
+						delete entry[name];
+						dropped = true;
+					}
+				}
+			}
+			if (dropped) persistSources();
+			return dropped;
+		}
+
 		/**
 		 * A coordinate saved for a draft becomes permanent the moment the quote
 		 * shows up in a transcript: a capsule carrying the ref is proof the reader
 		 * actually sent it. Until then `saveSource(..., { draft: true })` keeps it
 		 * out of `paintAnchors`, so a side chat the reader backs out of leaves no
-		 * mark on the source.
+		 * mark on the source. A `chip` mark rides along (a chip in a draft is
+		 * visible, so it paints) and is dropped here too: a capsule means the chip
+		 * is gone and no retraction may hide the sent quote.
 		 *
-		 * @returns {boolean} true when a draft was promoted (the caller repaints).
+		 * @returns {boolean} true when a draft or a chip mark was promoted (the
+		 * caller repaints).
 		 */
 		function promoteSource(ref, quote) {
+			return dropSourceMarks(ref, ["draft", "chip"]);
+		}
+
+		/** Whether a capsule for this coordinate is already drawn in a transcript. */
+		function capsuleOnSourcePage(ref) {
 			const wire = normalizeRef(ref);
 			if (wire === null) return false;
-			const id = [wire.s, wire.a, wire.k, wire.t, sourceKeyOf(quote)].join("\u0000");
-			let promoted = false;
+			if (typeof document === "undefined" || typeof document.querySelectorAll !== "function") return false;
+			const key = capsuleJumpKey("", null, wire);
+			for (const element of document.querySelectorAll("[data-dshq-jump]")) {
+				if (typeof element.getAttribute !== "function") continue;
+				if (element.getAttribute("data-dshq-jump") === key) return true;
+			}
+			return false;
+		}
+
+		/**
+		 * Mark (or unmark) the coordinate a composer chip minted as retracted.
+		 * `paintAnchors` skips a draft coordinate, so marking is what makes the
+		 * source mark disappear when the reader takes the chip back out; the
+		 * chip's own ordinal and card stay usable throughout. Only a coordinate
+		 * minted with `saveSource(..., { chip: true })` is touched, so a passage
+		 * that was sent earlier keeps its highlight even when the same passage
+		 * is quoted into the draft and deleted again.
+		 *
+		 * @returns {boolean} true when the state changed (the caller repaints).
+		 */
+		function setChipRetracted(info, retracted) {
+			if (info === null || info === undefined) return false;
+			if (info.ref === null || info.ref === undefined) return false;
+			const id = refTextKeyOf(info.ref);
+			if (id === "") return false;
+			let changed = false;
 			for (const list of sourceIndex.values()) {
 				for (const entry of list) {
-					if (entry.draft !== true) continue;
-					if (sourceCandidateId(entry) !== id) continue;
-					delete entry.draft;
-					promoted = true;
+					if (entry.chip !== true) continue;
+					if (refTextKeyOf(entry) !== id) continue;
+					if (retracted === true) {
+						if (entry.draft === true) continue;
+						entry.draft = true;
+					} else {
+						if (entry.draft !== true) continue;
+						delete entry.draft;
+					}
+					changed = true;
 				}
 			}
-			if (promoted) persistSources();
-			return promoted;
+			if (changed) {
+				persistSources();
+				scheduleAnchors();
+			}
+			return changed;
+		}
+
+		/**
+		 * A chip that was in a live draft is gone, and no capsule carries its
+		 * coordinate: the reader took the quote back out instead of sending it.
+		 * The mark the chip minted has to go with it, or the source keeps a
+		 * highlight (and ordinal) for a quote nothing holds any more. Marking the
+		 * coordinate as a draft is exactly the state `paintAnchors` already skips,
+		 * and it stays reversible: a later send promotes it again through
+		 * `promoteSource`, and a chip that comes back (a slow host render, the
+		 * reader re-adding the same quote) lifts the mark through
+		 * `restoreChipSource`.
+		 *
+		 * @returns {boolean} true when a mark was retracted.
+		 */
+		function retractChipSource(info) {
+			// A capsule with this coordinate means the quote did leave the draft.
+			if (info === null || info === undefined || info.ref === null || info.ref === undefined) return false;
+			if (capsuleOnSourcePage(info.ref)) return false;
+			return setChipRetracted(info, true);
+		}
+
+		/** The chip is back in the draft (or never really left): paint again. */
+		function restoreChipSource(info) {
+			return setChipRetracted(info, false);
 		}
 
 		/**
@@ -4034,19 +4143,27 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 		function syncDraftBars() {
 			if (typeof document === "undefined" || typeof document.querySelectorAll !== "function") return;
 			const seen = new Set();
+			const open = new Set();
+			const present = new Map();
 			for (const card of document.querySelectorAll(CARD_SELECTOR)) {
+				open.add(card);
 				const chips = Array.from(card.querySelectorAll("*")).filter((node) => node.getAttribute("data-dshq-chip") !== null);
+				const pairs = [];
+				const held = new Map();
+				for (const chip of chips) {
+					const info = chipInfoFor(chip);
+					if (info === null) continue;
+					pairs.push({ chip, info });
+					const key = info.ref === null || info.ref === undefined ? "" : refTextKeyOf(info.ref);
+					if (key !== "") held.set(key, info);
+				}
+				present.set(card, held);
 				if (chips.length === 0) {
 					removeDraftBar(card);
 					continue;
 				}
 				seen.add(card);
 				const bar = ensureDraftBar(card);
-				const pairs = [];
-				for (const chip of chips) {
-					const info = chipInfoFor(chip);
-					if (info !== null) pairs.push({ chip, info });
-				}
 				const signature = chips.length + "|" + pairs.map(({ info }) => (info.ref === null ? "" : encodeQuoteRef(info.ref)) + ":" + info.quote + ":" + info.comment).join("\u0001");
 				if (bar.dataset.signature === signature) continue;
 				bar.dataset.signature = signature;
@@ -4104,6 +4221,44 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 					bar.append(el(document, "span", { class: "dshq-db-more", text: "+" + String(pairs.length - DRAFTBAR_LIMIT) }));
 				}
 			}
+			// Reconcile after every card was scanned, so a coordinate that two
+			// composers hold (the main draft and a side thread's, same ref) is only
+			// retracted when the last chip that carries it is gone. A chip that a
+			// card held on the last pass and does not hold now was taken out of the
+			// draft; the card itself is still on screen, so this is a removal and
+			// not a session switch (a card that left the page is dropped below). A
+			// key that appears again — a slow host render, the reader re-adding the
+			// same quote — lifts the retraction it caused.
+			const heldNow = new Set();
+			for (const held of present.values()) {
+				for (const key of held.keys()) heldNow.add(key);
+			}
+			const heldBefore = new Set();
+			for (const was of cardChips.values()) {
+				for (const key of was.keys()) heldBefore.add(key);
+			}
+			for (const held of present.values()) {
+				for (const [key, info] of held) {
+					if (heldBefore.has(key)) continue;
+					restoreChipSource(info);
+				}
+			}
+			for (const [card, was] of cardChips) {
+				if (!open.has(card)) continue;
+				for (const [key, info] of was) {
+					if (heldNow.has(key)) continue;
+					retractChipSource(info);
+				}
+			}
+			for (const [card, held] of present) {
+				if (held.size === 0) cardChips.delete(card);
+				else cardChips.set(card, held);
+			}
+			// A composer card that left the page took its chips with it, but that
+			// is not the reader removing them: forget the ledger without retracting.
+			for (const card of Array.from(cardChips.keys())) {
+				if (!open.has(card)) cardChips.delete(card);
+			}
 			for (const card of Array.from(draftBars.keys())) {
 				if (!seen.has(card)) removeDraftBar(card);
 			}
@@ -4115,6 +4270,7 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 				clearTimeout(draftBarTimer);
 				draftBarTimer = null;
 			}
+			cardChips.clear();
 			for (const card of Array.from(draftBars.keys())) removeDraftBar(card);
 		}
 
@@ -5422,11 +5578,14 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 			// Remember the row this came from before anything can fail, and put the
 			// same coordinate into the sent text as a wire-only ref line: the table
 			// survives this window, the ref survives a reload and an empty table.
+			// The `chip` mark says a chip is what holds this quote in the draft, so
+			// `syncDraftBars` can retract the source mark when the reader takes the
+			// chip back out without sending it.
 			let wireRef = null;
 			if (source !== null) {
 				// The source table keys on the sentence as it was rendered, so the
 				// Markdown marks this plugin added must not be part of the key.
-				const saved = saveSource(plainOf(quoteText), sessionId, source);
+				const saved = saveSource(plainOf(quoteText), sessionId, source, { chip: true });
 				if (saved !== null) {
 					wireRef = { v: 1, s: saved.sessionId, a: saved.attr, k: saved.key, t: saved.turn, n: saved.n };
 					if (ROLE_CODES.has(saved.role)) wireRef.r = saved.role;
@@ -5466,6 +5625,9 @@ box-shadow:0 1px 3px rgba(0,0,0,.25)}
 				focusComposer();
 				return;
 			}
+			// The plain-text form took the quote instead: no chip holds it any more,
+			// so the retraction path must never mistake a later removal for this one.
+			if (wireRef !== null) dropSourceMarks(wireRef, ["chip"]);
 			if (insertPayload(entry, buildPayload(quoteText, trimmed, code, meta), composerText().trim() !== "")) focusComposer();
 			else {
 				noteFailure("insert", "the plain-text fallback failed too");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-client-ui-quote",
-  "version": "0.12.4",
+  "version": "0.12.5-lab.44",
   "description": "Turn any DSH selection into a reviewable quote — comment / add to chat / side chat, source highlights and jump-back, a searchable review list, side threads, revisions, and per-quote reply badges.",
   "icon": "icon.svg",
   "license": "MIT",

package/test/README.md

@@ -1,26 +1,28 @@
 # test
 
-离线回归网。没有测试框架，全部是 Node 脚本；`npm test` 依次跑三套，共 **549 组**断言。
+离线回归网。没有测试框架，全部是 Node 脚本；`npm test` 依次跑四套，共 **686 组**断言。
 
 | 文件 | 组数 | 覆盖 |
 | --- | --- | --- |
 | `check.mjs` | 12 | 清单字段、`exports`、图标、两份 locale 词典、槽位注册、`codec.serialize`、无强制 peer、`files` 发货白名单、截图被根 README 引用。 |
-| `capsule.mjs` | 384 | 输入框 → 发送后链路：线格式、芯片插入、胶囊、悬停卡片、跳回、高亮、草稿聚合条、侧边对话、逐条徽章、diff 引用。 |
-| `panel.mjs` | 153 | 引用清单页：解析、搜索、Markdown/JSON 导出、读取、注册、审阅工作台、本机索引、侧线程回流。 |
+| `capsule.mjs` | 470 | 输入框 → 发送后链路：线格式、芯片插入、胶囊、悬停卡片、跳回、高亮（含草稿坐标不落色、`promoteSource` 转正后才补画、**草稿芯片删掉后标记收回 / 回来再补画**）、草稿聚合条、侧边对话（内置隐藏线程 / fork / better）、逐条徽章、diff 引用。 |
+| `panel.mjs` | 160 | 引用清单页：解析、搜索、Markdown/JSON 导出、读取、注册、审阅工作台、本机索引、侧线程回流。 |
+| `host.mjs` | 44 | 宿主半：隐性上下文种子（继承切点 → 收口回合包着 `session-context` 消息 → descriptor）、切点与 descriptor 顺序、`agents.create` 参数、探针与同源围栏、路由注册与卸载。 |
 | `dom.mjs` | — | 最小 DOM / MutationObserver / Range / `localStorage` 垫片。新用到的 DOM API **先补这里**，否则 `capsule.mjs` 在 Node 里直接挂。 |
-| `capsule.html` | 51 项 | 真浏览器版，`file://` 直接打开；结果写进页面标题与 `#probe-out`。 |
+| `capsule.html` | 51 项 | 真浏览器版，`file://` 直接打开；结果写进页面标题与 `#probe-out`。视口要给足（1600×2000），否则浮层摆放的两条几何断言会因空间不够而失败。 |
 
 ## 命令
 
 ```bash
-npm test                 # check + capsule + panel
+npm test                 # check + capsule + panel + host
 node test/check.mjs      # 只跑清单/契约
 node test/capsule.mjs    # 只跑发送后链路
 node test/panel.mjs      # 只跑清单页
+node test/host.mjs       # 只跑宿主半（隐藏线程创建）
 ```
 
 ## 红线
 
 - 新增行为必须带断言；**不许删断言或放宽期望值换绿**。
-- 若断言数变化，根 README 四处与 CHANGELOG 一处的数字要同步（549 = 12 + 384 + 153）。
+- 若断言数变化，根 README 四处与 CHANGELOG 一处的数字要同步（686 = 12 + 470 + 160 + 44）。
 - 测试跑在 `dom.mjs` 垫片上：先垫 API，再写实现，不要反过来为了过测试而改期望。

package/test/capsule.mjs

@@ -2387,6 +2387,29 @@ try {
 		JSON.stringify([landed.length, String(landed[0]?.ref ?? "").slice(0, 24)])
 	);
 
+	// 3a. 这条坐标要和芯片绑定在一起：删除芯片（没有发送）时，聚合条的回执就是
+	//     靠它把原文上的高亮收回去的（见后面的「原文侧高亮」段）。
+	const chipMarked = [];
+	shells.set("session-chip-mark", {
+		actions: { captureInsertion: () => ({ start: 0, end: 0, draftRev: 3 }) },
+		insertReference(attachment) {
+			chipMarked.push(attachment);
+			return true;
+		}
+	});
+	const markPane = pane("session-chip-mark", "芯片会带走这条坐标");
+	markPane.run.parentNode.setAttribute("data-chat-anchor-key", "row-chip-mark");
+	markPane.run.parentNode.setAttribute("data-chat-turn", "12");
+	selectIn(markPane.run, "芯片会带走这条坐标");
+	barOf().dispatch("click", { target: barOf().querySelector('[data-action="add"]') });
+	const markTable = JSON.parse(globalThis.localStorage.getItem("dsh-client-ui-quote:v2:quote-source") ?? "{}");
+	const markSaved = Object.values(markTable).flat().find((entry) => entry?.key === "row-chip-mark");
+	check(
+		"a quote added to the chat ties its coordinate to the chip",
+		chipMarked.length === 1 && markSaved?.chip === true,
+		JSON.stringify({ inserted: chipMarked.length, saved: markSaved === undefined ? null : { key: markSaved.key, chip: markSaved.chip } })
+	);
+
 	// 3b. A draft that already holds the reader's wording: the quote goes to
 	//     the top and the wording moves to a line of its own below it.
 	const lineCalls = [];
@@ -3100,6 +3123,186 @@ try {
 		JSON.stringify({ draft: reDraft?.draft, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
 	);
 
+	// 主会话「添加到对话」写进草稿的芯片：坐标以 `chip` 记在表里。芯片还在草稿
+	// 里时照常落色；读者点聚合条的 × 或直接退格把它删掉（并没有发送）之后，
+	// 原文上那块高亮必须跟着消失——否则就留下一条无主的黄条。
+	const chipRow = dom.document.createElement("div");
+	chipRow.setAttribute("data-chat-anchor-key", "row-chip");
+	chipRow.setAttribute("data-chat-turn", "8");
+	chipRow.textContent = "前文 加进草稿又后悔的引用 后文";
+	pane.append(chipRow);
+	const chipQuote = "加进草稿又后悔的引用";
+	const chipRef = { v: 1, s: "session-anchor", a: "data-chat-anchor-key", k: "row-chip", t: "8", n: 1 };
+	const chipSaved = testing.saveSource(chipQuote, "session-anchor", { attr: "data-chat-anchor-key", key: "row-chip", turn: "8" }, { chip: true });
+	check(
+		"a coordinate minted by a composer chip carries the chip mark",
+		chipSaved !== null && chipSaved.chip === true,
+		JSON.stringify(chipSaved)
+	);
+	const chipCard = dom.document.createElement("div");
+	chipCard.setAttribute("data-composer-card", "");
+	const chipNode = dom.document.createElement("span");
+	testing.rememberChip(chipQuote, "", "session-anchor", false, { ref: chipRef });
+	chipNode.textContent = testing.chipLabel(chipQuote, "");
+	chipNode.setAttribute("data-dshq-chip", "1");
+	chipCard.append(chipNode);
+	dom.document.body.append(chipCard);
+	const chipBaseline = highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0;
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	check(
+		"a quote held by a draft chip is painted on its source",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === chipBaseline + 1,
+		JSON.stringify({ baseline: chipBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+	chipNode.remove();
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	const chipTable = JSON.parse(globalThis.localStorage.getItem("dsh-client-ui-quote:v2:quote-source") ?? "{}");
+	const chipStoredDraft = Object.values(chipTable).some((list) => Array.isArray(list) && list.some((entry) => entry?.key === "row-chip" && entry?.draft === true));
+	check(
+		"removing the chip without sending drops the source highlight",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === chipBaseline,
+		JSON.stringify({ baseline: chipBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+	check("the retraction is stored, so a reload cannot resurrect the mark", chipStoredDraft, JSON.stringify(chipStoredDraft));
+	// 又把同一句加回草稿（或宿主慢一拍才把它画回来）：高亮应当自己回来。
+	const chipAgain = dom.document.createElement("span");
+	chipAgain.textContent = testing.chipLabel(chipQuote, "");
+	chipAgain.setAttribute("data-dshq-chip", "1");
+	chipCard.append(chipAgain);
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	check(
+		"the chip coming back lifts the retraction",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === chipBaseline + 1,
+		JSON.stringify({ baseline: chipBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+	chipAgain.remove();
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	const chipPromoted = testing.promoteSource(chipRef, chipQuote);
+	testing.paintAnchors();
+	check(
+		"the quote turning up as a capsule paints it again",
+		chipPromoted === true && (highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === chipBaseline + 1,
+		JSON.stringify({ promoted: chipPromoted, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+
+	// 已经作为胶囊发出去过的坐标，再被加进草稿、又删掉：页面上有它的胶囊，
+	// 所以这不是「读者反悔」，标记必须留着。
+	const sentRow = dom.document.createElement("div");
+	sentRow.setAttribute("data-chat-anchor-key", "row-sent-chip");
+	sentRow.setAttribute("data-chat-turn", "9");
+	sentRow.textContent = "前文 已经发出去又被加进草稿的引用 后文";
+	pane.append(sentRow);
+	const sentQuote = "已经发出去又被加进草稿的引用";
+	const sentRef = { v: 1, s: "session-anchor", a: "data-chat-anchor-key", k: "row-sent-chip", t: "9", n: 1 };
+	testing.saveSource(sentQuote, "session-anchor", { attr: "data-chat-anchor-key", key: "row-sent-chip", turn: "9" }, { chip: true });
+	const sentCard = dom.document.createElement("div");
+	sentCard.setAttribute("data-composer-card", "");
+	const sentChip = dom.document.createElement("span");
+	testing.rememberChip(sentQuote, "", "session-anchor", false, { ref: sentRef });
+	sentChip.textContent = testing.chipLabel(sentQuote, "");
+	sentChip.setAttribute("data-dshq-chip", "1");
+	sentCard.append(sentChip);
+	dom.document.body.append(sentCard);
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	const sentBaseline = highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0;
+	const sentCapsule = dom.document.createElement("div");
+	sentCapsule.setAttribute("data-dshq-jump", JSON.stringify(["ref", "session-anchor", "data-chat-anchor-key", "row-sent-chip", "9", 1]));
+	dom.document.body.append(sentCapsule);
+	sentChip.remove();
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	check(
+		"a sent capsule keeps the mark when its draft chip is removed",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === sentBaseline,
+		JSON.stringify({ baseline: sentBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+	sentCapsule.remove();
+	sentCard.remove();
+	testing.syncDraftBars();
+
+	// 整个输入框离开页面（切会话）不是「读者删了芯片」：不收回、也不误删账本。
+	const leaveRow = dom.document.createElement("div");
+	leaveRow.setAttribute("data-chat-anchor-key", "row-leave-chip");
+	leaveRow.setAttribute("data-chat-turn", "10");
+	leaveRow.textContent = "前文 切走会话时还在草稿里的引用 后文";
+	pane.append(leaveRow);
+	const leaveQuote = "切走会话时还在草稿里的引用";
+	const leaveRef = { v: 1, s: "session-anchor", a: "data-chat-anchor-key", k: "row-leave-chip", t: "10", n: 1 };
+	testing.saveSource(leaveQuote, "session-anchor", { attr: "data-chat-anchor-key", key: "row-leave-chip", turn: "10" }, { chip: true });
+	const leaveCard = dom.document.createElement("div");
+	leaveCard.setAttribute("data-composer-card", "");
+	const leaveChip = dom.document.createElement("span");
+	testing.rememberChip(leaveQuote, "", "session-anchor", false, { ref: leaveRef });
+	leaveChip.textContent = testing.chipLabel(leaveQuote, "");
+	leaveChip.setAttribute("data-dshq-chip", "1");
+	leaveCard.append(leaveChip);
+	dom.document.body.append(leaveCard);
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	const leaveBaseline = highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0;
+	leaveCard.remove();
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	check(
+		"a composer that leaves the page does not drop the draft's mark",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === leaveBaseline,
+		JSON.stringify({ baseline: leaveBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+
+	// 同一坐标同时挂在两个草稿里（主会话与侧边线程共用同一个 ref，侧聊草稿也是
+	// 这一句）：删掉其中一颗芯片不代表引用离开了草稿，最后两颗都删掉才收回。
+	const sharedRow = dom.document.createElement("div");
+	sharedRow.setAttribute("data-chat-anchor-key", "row-shared-chip");
+	sharedRow.setAttribute("data-chat-turn", "11");
+	sharedRow.textContent = "前文 两个草稿共享同一个坐标的引用 后文";
+	pane.append(sharedRow);
+	const sharedQuote = "两个草稿共享同一个坐标的引用";
+	const sharedRef = { v: 1, s: "session-anchor", a: "data-chat-anchor-key", k: "row-shared-chip", t: "11", n: 1 };
+	testing.saveSource(sharedQuote, "session-anchor", { attr: "data-chat-anchor-key", key: "row-shared-chip", turn: "11" }, { chip: true });
+	testing.rememberChip(sharedQuote, "", "session-anchor", false, { ref: sharedRef });
+	const sharedLabel = testing.chipLabel(sharedQuote, "");
+	const sharedCardA = dom.document.createElement("div");
+	sharedCardA.setAttribute("data-composer-card", "");
+	const sharedChipA = dom.document.createElement("span");
+	sharedChipA.textContent = sharedLabel;
+	sharedChipA.setAttribute("data-dshq-chip", "1");
+	sharedCardA.append(sharedChipA);
+	dom.document.body.append(sharedCardA);
+	const sharedCardB = dom.document.createElement("div");
+	sharedCardB.setAttribute("data-composer-card", "");
+	const sharedChipB = dom.document.createElement("span");
+	sharedChipB.textContent = sharedLabel;
+	sharedChipB.setAttribute("data-dshq-chip", "1");
+	sharedCardB.append(sharedChipB);
+	dom.document.body.append(sharedCardB);
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	const sharedBaseline = highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0;
+	sharedChipA.remove();
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	check(
+		"one of two chips for one coordinate going away keeps the mark",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === sharedBaseline,
+		JSON.stringify({ baseline: sharedBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+	sharedChipB.remove();
+	testing.syncDraftBars();
+	testing.paintAnchors();
+	check(
+		"the mark goes when the last chip for it is gone",
+		(highlightRegistry.get("dshq-quote")?.ranges?.length ?? 0) === sharedBaseline - 1,
+		JSON.stringify({ baseline: sharedBaseline, ranges: highlightRegistry.get("dshq-quote")?.ranges?.length })
+	);
+	sharedCardA.remove();
+	sharedCardB.remove();
+	testing.syncDraftBars();
+
 	const longQuote = "长".repeat(200);
 	const longRef = { s: "session-anchor", a: "data-chat-anchor-key", k: "row-anchor", t: "5", n: 1 };
 	testing.rememberQuoteText(longRef, longQuote);