@idoall/dsh-session-colors 0.1.3 → 0.1.5

package/CHANGELOG.md

@@ -8,6 +8,59 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.5] - 2026-09-25
+
+Verified against DeepSeek Harness `0.1.7-rc.2` (the latest release candidate) as
+well as `0.1.7-rc.1` and `0.1.7-alpha.2`. No code change: every contract this
+plugin depends on is unchanged between `rc.1` and `rc.2`, and this release
+confirms the same code on the second RC and records it.
+
+### Added
+
+- `dsh.compatibility.dshReleases` now records `0.1.7-rc.2` alongside
+  `0.1.7-rc.1` and `0.1.7-alpha.2`; both READMEs state all three versions.
+- The design record documents the one substantive addition in `rc.2` — the
+  Session-row seats `sidebar.session.row.leading` and `sidebar.session.row.hover`
+  — and why the chip deliberately stays on its own click-through layer instead of
+  moving into that seat: the leading seat shares the status dot's 16px cell and is
+  mounted only while a row is idle, so a chip placed there would disappear for
+  running, waiting and archived Sessions.
+
+### Notes
+
+- The peer and `dsh.engines.dsh` ranges stay `>=0.1.7-alpha.2 <0.2.0`. Under
+  node-semver's prerelease rule that range already admits `0.1.7-rc.2` (a
+  comparator names the same `major.minor.patch`), so it was deliberately **not**
+  widened for the second RC — widening would admit versions nobody tested.
+- `0.1.5` supports DSH `0.1.7-rc.2`, `0.1.7-rc.1` and `0.1.7-alpha.2`.
+  Installations on an older DSH, including `0.1.6-alpha.2`, should stay on plugin
+  `0.1.2`.
+- The duplicated `@deepseek-ai/schemastery` peer bullet in the English README was
+  removed; the Chinese README already carried it once.
+
+## [0.1.4] - 2026-09-23
+
+Verified against DeepSeek Harness `0.1.7-rc.1` (the latest release candidate) as
+well as `0.1.7-alpha.2`. No code change: `0.1.3` already absorbed the `0.1.7`
+changes, and this release confirms the same code on the RC and records it.
+
+### Added
+
+- `dsh.compatibility.dshReleases` now records `0.1.7-rc.1` alongside
+  `0.1.7-alpha.2`; both READMEs state both versions.
+- The design record documents the new `0.1.7-rc.1` behaviour that makes the peer
+  range load-bearing: boot evaluates `@deepseek-ai/dsh*` peers and **disables** a
+  plugin row whose range the running version does not satisfy.
+
+### Notes
+
+- The peer and `dsh.engines.dsh` ranges stay `>=0.1.7-alpha.2 <0.2.0`. Under
+  node-semver's prerelease rule that range already admits `0.1.7-rc.1` (a
+  comparator names the same `major.minor.patch`), so it was deliberately **not**
+  widened for the RC — widening would admit versions nobody tested.
+- `0.1.4` supports DSH `0.1.7-rc.1` and `0.1.7-alpha.2`. Installations on an
+  older DSH, including `0.1.6-alpha.2`, should stay on plugin `0.1.2`.
+
 ## [0.1.3] - 2026-09-23
 
 Verified against DeepSeek Harness `0.1.7-alpha.2`. The first fix below is what

package/README.md

@@ -23,6 +23,8 @@
   <a href="#development">Development</a>
 </p>
 
+> **✅ Supports DSH `0.1.7-rc.2` — the latest `0.1.7` release candidate.** Verified on the running release candidate as well as on `0.1.7-rc.1` and `0.1.7-alpha.2`; see [Compatibility](#compatibility).
+
 > DSH Session Colors is a DeepSeek Harness community plugin. It does not modify
 > DSH core and does not rewrite any Session or Workspace data: a mark is only
 > "Session id → one colour".
@@ -69,7 +71,9 @@ Requirements:
 
 - DeepSeek Harness with a Web profile
 - Node.js 20 or newer
-- **Verified DSH version: `0.1.7-alpha.2`** (see [Compatibility](#compatibility))
+- **Verified DSH version: `0.1.7-rc.2`** (the latest release candidate),
+  `0.1.7-rc.1` and `0.1.7-alpha.2` — plugin `0.1.5`
+  (see [Compatibility](#compatibility))
 
 ```sh
 dsh plugin --profile <profile> add @idoall/dsh-session-colors@latest
@@ -117,20 +121,29 @@ stored as HSVA, so alpha round-trips exactly.
 
 ## Compatibility
 
-Current release: plugin **`0.1.3`**, verified against DeepSeek Harness
-**`0.1.7-alpha.2`**.
-
-**`0.1.3` supports DSH `0.1.7-alpha.2` only.** On an older DSH — including
-`0.1.6-alpha.2` — keep plugin **`0.1.2`**: `0.1.3` declares its Host requirement
-as `>=0.1.7-alpha.2 <0.2.0` and is not verified below it.
+Current release: plugin **`0.1.5`** is verified against DeepSeek Harness
+**`0.1.7-rc.2`** — the latest `0.1.7` release candidate — as well as against
+**`0.1.7-rc.1`** and **`0.1.7-alpha.2`**.
 
 | Plugin version | Verified DeepSeek Harness | npm status | What it is |
 | --- | --- | --- | --- |
-| **`0.1.3`** | `0.1.7-alpha.2` | `latest` | Adapts to DSH 0.1.7: the Session id now comes from the row's own `data-row-key` (fiber fallback kept), and chips follow the Web-Animations row gliding `0.1.7` introduced. The Host dependency is declared the way `0.1.7` resolves a linked plugin, and the peer range admits the release. |
+| **`0.1.5`** | **`0.1.7-rc.2`** (latest RC), `0.1.7-rc.1`, `0.1.7-alpha.2` | `latest` | Confirms the same code runs unchanged on the second release candidate and declares it. No code change over `0.1.4`; upgrading needs no migration. |
+| `0.1.4` | `0.1.7-rc.1` (RC), `0.1.7-alpha.2` | published | Confirms the `0.1.7` adaptation runs unchanged on the first release candidate and declares it. No code change over `0.1.3`. |
+| `0.1.3` | `0.1.7-alpha.2` | published | Adapts to DSH 0.1.7: the Session id comes from the row's own `data-row-key` (fiber fallback kept), chips follow the Web-Animations row gliding `0.1.7` introduced, and the Host dependency is declared the way `0.1.7` resolves a linked plugin. |
 | `0.1.2` | `0.1.6-alpha.2` | published | Fixes chips staying at their old coordinates for ~20s when a workspace is collapsed or expanded: a second `MutationObserver.observe()` on the same target had silently replaced the `childList` watch. |
 | `0.1.1` | `0.1.6-alpha.2` | published | Documentation only: the packaged README no longer says "not published", and the market screenshots are declared. |
 | `0.1.0` | `0.1.6-alpha.2` | published | First release: Session colour marks, Host-side storage, visible inside a phone's sidebar drawer |
 
+**`0.1.5` supports DSH `0.1.7-rc.2`, the latest release candidate.** Between
+`rc.1` and `rc.2` every contract this plugin depends on is unchanged — the
+client-modules loader and the slot registration API are byte-identical, the
+sidebar row keeps its `data-row-key`/`role`/`aria-selected` markup and its exact
+geometry, and `shell.overlay` still renders the same layer — so **`0.1.5`
+confirms the same code runs unchanged on the second RC and records it.**
+**Upgrading from `0.1.4` needs no migration.** On an older DSH — including
+`0.1.6-alpha.2` — keep plugin **`0.1.2`**. Newer DSH releases are not
+auto-declared compatible.
+
 - **Verified DeepSeek Harness** is the exact DSH version this plugin was actually
   run against. That list has one home — `dsh.compatibility.dshReleases` in
   [`package.json`](package.json) — and a test keeps both READMEs' compatibility
@@ -139,10 +152,21 @@ as `>=0.1.7-alpha.2 <0.2.0` and is not verified below it.
 - `peerDependencies` declares `>=0.1.7-alpha.2 <0.2.0` for `dsh-client-ui-layout`
   and `dsh-client-ui-conversation`, and `dsh.engines.dsh` declares the same range
   as the Host requirement: that is the range allowed to **load**, which is not the
-  same as verified. The lower bound names the alpha on purpose — under
-  node-semver's default prerelease rule a range like `>=0.1.6-0 <0.2.0` does
-  **not** admit `0.1.7-alpha.2`, so pnpm reports the peer as unmet even though the
-  plugin runs.
+  same as verified. The range admits **all three** of `0.1.7-alpha.2`,
+  `0.1.7-rc.1` and `0.1.7-rc.2` (a prerelease is admitted when some comparator
+  names the same `major.minor.patch`), so it was deliberately **not** widened for
+  the RCs — doing so would admit versions nobody tested. The lower bound names the
+  alpha on purpose: a range like `>=0.1.6-0 <0.2.0` admits none of them.
+- DSH 0.1.7 evaluates those peers at boot and **disables** a plugin row whose
+  range is not satisfied, so a correct range is now load-bearing rather than
+  cosmetic. The evaluation code is identical in `rc.1` and `rc.2`.
+- DSH 0.1.7-rc.2 added a real Session-row seat,
+  `sidebar.session.row.leading` — a 16px cell before the title. The chip
+  deliberately **stays on its own click-through layer**: that seat shares its cell
+  with the status dot and is mounted **only while the row is idle** (a running,
+  waiting or archived row renders no occupant), so a chip placed there would
+  vanish exactly when it is most useful. See
+  [Limitations](#limitations) and the design record.
 - `@deepseek-ai/schemastery` is a **peer**, not a plain dependency: DSH 0.1.7
   resolves only a linked plugin's peer dependencies from the running
   installation, so a `link:` install of this directory would otherwise fail to
@@ -240,6 +264,12 @@ unaffected** because the layer is click-through.
 - **The chip depends on DSH's row DOM.** It reads rows by ARIA role and the
   Session id from the row's `data-row-key`, falling back to React internals. A
   future DSH release can stop chips from appearing; it cannot break clicking.
+- **The chip is not a row occupant.** DSH 0.1.7-rc.2 declares a real
+  `sidebar.session.row.leading` seat in the row's status-dot cell, and this plugin
+  deliberately does **not** use it: that seat is mounted only while a row is idle,
+  so a chip placed there would disappear for running, waiting and archived
+  Sessions. The chip stays on its own click-through layer, which keeps it visible
+  in every state and never covers the dot.
 - **Marks are per DSH instance.** They live in one profile's data directory, so
   two independent DSH servers do not share them.
 - **No permission model.** Anyone who can reach the Host's authenticated routes

package/README.zh.md

@@ -23,6 +23,8 @@
   <a href="#开发">开发</a>
 </p>
 
+> **✅ 已支持 DSH `0.1.7-rc.2` —— 最新的 `0.1.7` 候选版本（RC）。** 已在运行中的该 RC 实例上实测通过，同时也兼容 `0.1.7-rc.1` 与 `0.1.7-alpha.2`；详见[兼容性](#兼容性)。
+
 > DSH Session Colors 是 DeepSeek Harness 社区插件。它不修改 DSH 核心，也不改写任何会话或工作区数据：一个标记只是"会话 ID → 一个颜色"。
 
 工作分散在多个工作区里，而工作区列表就是一堵长得差不多的标题墙。任务跑完之后，刚才那条会话就很难再找回来——状态点已经回到空闲，标题也只是二十个里的一个。**自己选的颜色，是让一行变得好认的最省事办法。**
@@ -51,7 +53,7 @@
 
 - 带 Web profile 的 DeepSeek Harness
 - Node.js 20 或更新版本
-- **已验证的 DSH 版本：`0.1.7-alpha.2`**（见[兼容性](#兼容性)）
+- **已验证的 DSH 版本：`0.1.7-rc.2`**（最新候选版）、`0.1.7-rc.1` 与 `0.1.7-alpha.2`——插件 `0.1.5`（见[兼容性](#兼容性)）
 
 ```sh
 dsh plugin --profile <profile> add @idoall/dsh-session-colors@latest
@@ -90,19 +92,23 @@ dsh plugin --profile <profile> add link:/path/to/dsh-session-colors
 
 ## 兼容性
 
-当前版本：插件 **`0.1.3`** 已针对 DeepSeek Harness **`0.1.7-alpha.2`** 验证。
-
-**`0.1.3` 只支持 DSH `0.1.7-alpha.2`。** 更旧的 DSH（包括 `0.1.6-alpha.2`）请继续用插件 **`0.1.2`**：`0.1.3` 声明的宿主要求是 `>=0.1.7-alpha.2 <0.2.0`，低于它的版本未经本轮验证。
+当前版本：插件 **`0.1.5`** 已针对 DeepSeek Harness **`0.1.7-rc.2`**（最新的 `0.1.7` 候选版本）验证，同时也兼容 **`0.1.7-rc.1`** 与 **`0.1.7-alpha.2`**。
 
 | 插件版本 | 已验证的 DeepSeek Harness | npm 发布状态 | 该版本是什么 |
 | --- | --- | --- | --- |
-| **`0.1.3`** | `0.1.7-alpha.2` | `latest` | 适配 DSH 0.1.7：会话 id 改从行自身的 `data-row-key` 读取（保留 fiber 回退），色块跟随 0.1.7 引入的 Web Animations 行滑动；宿主依赖按 0.1.7 对 link 插件的解析方式声明，peer 范围也真正覆盖该版本。 |
+| **`0.1.5`** | **`0.1.7-rc.2`**（最新 RC）、`0.1.7-rc.1`、`0.1.7-alpha.2` | `latest` | 确认同一份代码在第二个候选版本上原样可用并加以声明。代码与 `0.1.4` 相同，升级无需迁移。 |
+| `0.1.4` | `0.1.7-rc.1`（RC）、`0.1.7-alpha.2` | 已发布 | 确认 `0.1.7` 适配在首个候选版本上原样可用并加以声明。代码与 `0.1.3` 相同。 |
+| `0.1.3` | `0.1.7-alpha.2` | 已发布 | 适配 DSH 0.1.7：会话 id 改从行自身的 `data-row-key` 读取（保留 fiber 回退），色块跟随 0.1.7 引入的 Web Animations 行滑动；宿主依赖按 0.1.7 对 link 插件的解析方式声明。 |
 | `0.1.2` | `0.1.6-alpha.2` | 已发布 | 修掉折叠/展开工作区后色块停在旧位置约 20 秒：同一个 target 上第二次 `MutationObserver.observe()` 把 `childList` 监听顶掉了。 |
 | `0.1.1` | `0.1.6-alpha.2` | 已发布 | 仅文档：打包进 npm 的 README 不再写"尚未发布"，并声明了市场截图。 |
 | `0.1.0` | `0.1.6-alpha.2` | 已发布 | 首个版本：会话颜色标记、宿主侧存储、手机抽屉内可见 |
 
+**`0.1.5` 支持 DSH `0.1.7-rc.2`，即最新的候选版本（RC）。** `rc.1 → rc.2` 之间，本插件依赖的契约全部没有变化——client-modules 加载器与 slot 注册 API 逐字节相同，侧栏行仍带 `data-row-key`/`role`/`aria-selected` 且几何尺寸完全一致，`shell.overlay` 仍渲染同一层——所以 **`0.1.5` 确认同一份代码在第二个 RC 上原样可用，并把它记入声明。从 `0.1.4` 升级无需任何迁移。** 仍在更旧的 DSH（含 `0.1.6-alpha.2`）上时，请继续用插件 **`0.1.2`**。更高的 DSH 版本不会被自动宣称为兼容。
+
 - **已验证的 DeepSeek Harness** 是这个插件**实际跑过**的确切 DSH 版本。这份清单只有一个存放处——[`package.json`](package.json) 的 `dsh.compatibility.dshReleases`——并且有测试保证两个 README 的兼容性段落与它逐字一致、且落在 `peerDependencies` 声明的范围内。未列出的 DSH 版本**不会被宣称为兼容**。
-- `peerDependencies` 声明的范围是 `>=0.1.7-alpha.2 <0.2.0`（`dsh-client-ui-layout` 与 `dsh-client-ui-conversation`），`dsh.engines.dsh` 把同一范围声明为宿主要求：这是**允许加载**的范围，不等于已验证。下界特意写成 alpha 版本——按 node-semver 的默认预发布规则，`>=0.1.6-0 <0.2.0` 这样的范围**并不包含** `0.1.7-alpha.2`，pnpm 会把 peer 报成 unmet，即使插件实际跑得起来。
+- `peerDependencies` 声明的范围是 `>=0.1.7-alpha.2 <0.2.0`（`dsh-client-ui-layout` 与 `dsh-client-ui-conversation`），`dsh.engines.dsh` 把同一范围声明为宿主要求：这是**允许加载**的范围，不等于已验证。该范围**同时接纳** `0.1.7-alpha.2`、`0.1.7-rc.1` 与 `0.1.7-rc.2`（只要范围里有比较符写了同一个 `major.minor.patch`，该版本的预发布就会被接纳），所以**刻意不为 RC 放宽**——放宽只会顺带接纳没人测过的版本。下界特意写成这个 alpha：`>=0.1.6-0 <0.2.0` 这样的范围一个都不接纳。
+- DSH 0.1.7 会在启动时校验这些 peer，范围不满足就**直接禁用该插件行**，所以范围写对已经不只是"声明问题"；这段判定代码在 `rc.1` 与 `rc.2` 中完全相同。
+- DSH 0.1.7-rc.2 新增了一个真正的会话行座位 `sidebar.session.row.leading`（标题前那格 16px）。色块**刻意仍留在自己的点击穿透浮层上**：该座位与状态点共用同一格，且**只在行处于空闲时**才挂载（运行中、等待中、已归档的行都不渲染占位），把色块放进去反而会在最需要它的时候消失。详见[限制](#限制)与设计记录。
 - `@deepseek-ai/schemastery` 声明为 **peer**，不是普通依赖：DSH 0.1.7 只把 link 插件的 **peer** 依赖解析到运行实例，所以用 `link:` 装入本目录时，普通依赖会让宿主半边 import 失败。
 - DSH 升级快于插件时，插件本身不会因此报错：色块依赖 DSH 的行 DOM（见[限制](#限制)），所以 DSH 大改行结构时最坏的结果是**色块不再显示**，不会挡住点击。
 
@@ -169,6 +175,7 @@ document.querySelector('.dsh-sc-layer').dataset
 ## 限制
 
 - **色块依赖 DSH 的行 DOM。** 它靠 ARIA role 找行、靠行自身的 `data-row-key` 取会话 ID（回退到 React 内部结构）。DSH 未来改版可能让色块不再显示；但**不会影响点击**。
+- **色块不是行内占位元素。** DSH 0.1.7-rc.2 声明了真正的行座位 `sidebar.session.row.leading`（就落在状态点那一格），本插件**刻意不使用**它：该座位只在行空闲时挂载，色块放进去会在运行中、等待中与已归档的会话上消失。色块因此留在自己的点击穿透浮层上——任何状态下都可见，也永远不盖住状态点。
 - **标记属于单个 DSH 实例。** 它存在某个 profile 的数据目录里，两个独立的 DSH 服务之间不共享。
 - **没有权限模型。** 凡是能访问该 profile 已鉴权路由的人，都能读写标记。
 - **只有颜色。** 没有文字标签、图标或 emoji。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@idoall/dsh-session-colors",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "type": "module",
   "description": "DSH web plugin: give any Session a colour mark, shown as a chip in the sidebar and picked from the conversation header. Marks are stored on the Host, so a colour chosen on one device is visible on every other one — including over LAN and tunnels.",
   "main": "./src/index.js",
@@ -25,6 +25,8 @@
     },
     "compatibility": {
       "dshReleases": {
+        "0.1.7-rc.2": "compatible",
+        "0.1.7-rc.1": "compatible",
         "0.1.7-alpha.2": "compatible"
       }
     },