@idoall/dsh-session-colors 0.1.5 → 0.1.6

package/CHANGELOG.md

@@ -8,6 +8,49 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.6] - 2026-09-28
+
+Verified against DeepSeek Harness `0.2.0-rc.1` (the latest release candidate) as
+well as `0.1.7-rc.2`, `0.1.7-rc.1` and `0.1.7-alpha.2`. No code change: every
+contract this plugin depends on is unchanged between `0.1.7-rc.2` and
+`0.2.0-rc.1`, and this release confirms the same code on the new RC and records
+it.
+
+### Changed
+
+- The `peerDependencies` and `dsh.engines.dsh` ranges change from
+  `>=0.1.7-alpha.2 <0.2.0` to
+  `>=0.1.7-alpha.2 <0.2.0-0 || 0.2.0-rc.1 || >=0.2.0 <0.3.0`. The old upper
+  bound admitted `0.2.0-rc.1` only through node-semver's prerelease ordering; on
+  the `0.2.0` **final** release the compatibility precheck would have disabled
+  the plugin row at boot. Under node-semver's prerelease rule a prerelease is
+  admitted only when a comparator names its exact `major.minor.patch`, so the
+  new range has three alternatives: the verified `0.1.7` line, exactly
+  `0.2.0-rc.1` (an untested `0.2.0-rc.2` stays out), and the stable `0.2.0`
+  line up to `<0.3.0`.
+- `dsh.compatibility.dshReleases` now records `0.2.0-rc.1` alongside
+  `0.1.7-rc.2`, `0.1.7-rc.1` and `0.1.7-alpha.2`; both READMEs state all four
+  versions.
+
+### Notes
+
+- Contracts verified unchanged between `0.1.7-rc.2` and `0.2.0-rc.1`: the
+  client-modules loader and the slot registration API differ only in package
+  version numbers; the compatibility precheck
+  (`evaluatePluginCompatibility` and its callers) is byte-identical; the
+  sidebar row keeps `data-row-key="session:<id>"`, `role="treeitem"` and
+  `aria-selected`; `conversation.session.header.utilities` is still a
+  session-scoped list; `shell.overlay` is still declared by `ui-layout`; the
+  `slots`/`locale`/`layout` service faces and the `react@^18.2.0` baseline are
+  unchanged.
+- Verified on the running `0.2.0-rc.1` web-profile instance with the published
+  `0.1.5`: the client half loads and prints its diagnostic line, the Host half's
+  `GET /plugins/dsh-session-colors/marks` answers `200`, the header control
+  renders, and DSH does not disable the plugin row.
+- `0.1.6` supports DSH `0.2.0-rc.1`, `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`.
+
 ## [0.1.5] - 2026-09-25
 
 Verified against DeepSeek Harness `0.1.7-rc.2` (the latest release candidate) as

package/README.md

@@ -23,7 +23,7 @@
   <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).
+> **✅ Supports DSH `0.2.0-rc.1` — the latest `0.2.0` release candidate.** Verified on the running release candidate as well as on `0.1.7-rc.2`, `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
@@ -71,8 +71,8 @@ Requirements:
 
 - DeepSeek Harness with a Web profile
 - Node.js 20 or newer
-- **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`
+- **Verified DSH version: `0.2.0-rc.1`** (the latest release candidate),
+  `0.1.7-rc.2`, `0.1.7-rc.1` and `0.1.7-alpha.2` — plugin `0.1.6`
   (see [Compatibility](#compatibility))
 
 ```sh
@@ -121,26 +121,35 @@ stored as HSVA, so alpha round-trips exactly.
 
 ## Compatibility
 
-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`**.
+Current release: plugin **`0.1.6`** is verified against DeepSeek Harness
+**`0.2.0-rc.1`** — the latest `0.2.0` release candidate — as well as against
+**`0.1.7-rc.2`**, **`0.1.7-rc.1`** and **`0.1.7-alpha.2`**.
 
 | Plugin version | Verified DeepSeek Harness | npm status | What it is |
 | --- | --- | --- | --- |
-| **`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.6`** | **`0.2.0-rc.1`** (latest RC), `0.1.7-rc.2`, `0.1.7-rc.1`, `0.1.7-alpha.2` | `latest` | Verifies the same code on DSH `0.2.0-rc.1` and rewrites the declared load range so the plugin survives the `0.2.0` final release. No code change over `0.1.5`; upgrading needs no migration. |
+| `0.1.5` | `0.1.7-rc.2` (latest 0.1.7 RC), `0.1.7-rc.1`, `0.1.7-alpha.2` | published | 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` supports DSH `0.2.0-rc.1`, the latest release candidate.** Between
+`0.1.7-rc.2` and `0.2.0-rc.1` every contract this plugin depends on is
+unchanged — the client-modules loader and the slot registration API differ only
+in their package version numbers, the compatibility precheck that evaluates
+`peerDependencies` is byte-identical, the sidebar row keeps its
+`data-row-key`/`role`/`aria-selected` markup, `conversation.session.header.utilities`
+is still a session-scoped list, and `shell.overlay` still renders the same layer
+— so **`0.1.6` confirms the same code runs unchanged on the new RC and records
+it.** The range changes because the old `<0.2.0` upper bound admitted
+`0.2.0-rc.1` only through prerelease ordering: on the `0.2.0` **final** release
+the plugin row would have been disabled at boot. Under node-semver's prerelease
+rule each tuple must be named, so the range now has three alternatives — the
+verified `0.1.7` line, exactly `0.2.0-rc.1`, and the `0.2.0` stable line up to
+`<0.3.0`.
+**Upgrading from `0.1.5` 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.
 
@@ -149,17 +158,19 @@ auto-declared compatible.
   [`package.json`](package.json) — and a test keeps both READMEs' compatibility
   sections word-for-word with it and inside the range `peerDependencies`
   declares. A DSH version that is not listed is **never claimed as compatible**.
-- `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 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`.
+- `peerDependencies` declare `>=0.1.7-alpha.2 <0.2.0-0 || 0.2.0-rc.1 || >=0.2.0 <0.3.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 three
+  alternatives are deliberate: a prerelease is admitted only when a comparator
+  names its exact `major.minor.patch`, so the `0.1.7` line needs its own
+  comparator, `0.2.0-rc.1` is pinned exactly (an untested `0.2.0-rc.2` stays
+  out), and the stable `0.2.0` line is admitted so the plugin survives the
+  final release. The lower bound names the alpha on purpose: a range like
+  `>=0.1.6-0 <0.2.0` admits none of the verified versions.
+- DSH evaluates those peers at boot and **disables** a plugin row whose range is
+  not satisfied, so a correct range is load-bearing rather than cosmetic. The
+  evaluation code is identical in `0.1.7-rc.1`, `0.1.7-rc.2` and `0.2.0-rc.1`.
 - 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

package/README.zh.md

@@ -23,7 +23,7 @@
   <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 `0.2.0-rc.1` —— 最新的 `0.2.0` 候选版本（RC）。** 已在运行中的该 RC 实例上实测通过，同时也兼容 `0.1.7-rc.2`、`0.1.7-rc.1` 与 `0.1.7-alpha.2`；详见[兼容性](#兼容性)。
 
 > DSH Session Colors 是 DeepSeek Harness 社区插件。它不修改 DSH 核心，也不改写任何会话或工作区数据：一个标记只是"会话 ID → 一个颜色"。
 
@@ -53,7 +53,7 @@
 
 - 带 Web profile 的 DeepSeek Harness
 - Node.js 20 或更新版本
-- **已验证的 DSH 版本：`0.1.7-rc.2`**（最新候选版）、`0.1.7-rc.1` 与 `0.1.7-alpha.2`——插件 `0.1.5`（见[兼容性](#兼容性)）
+- **已验证的 DSH 版本：`0.2.0-rc.1`**（最新候选版）、`0.1.7-rc.2`、`0.1.7-rc.1` 与 `0.1.7-alpha.2`——插件 `0.1.6`（见[兼容性](#兼容性)）
 
 ```sh
 dsh plugin --profile <profile> add @idoall/dsh-session-colors@latest
@@ -92,22 +92,24 @@ dsh plugin --profile <profile> add link:/path/to/dsh-session-colors
 
 ## 兼容性
 
-当前版本：插件 **`0.1.5`** 已针对 DeepSeek Harness **`0.1.7-rc.2`**（最新的 `0.1.7` 候选版本）验证，同时也兼容 **`0.1.7-rc.1`** 与 **`0.1.7-alpha.2`**。
+当前版本：插件 **`0.1.6`** 已针对 DeepSeek Harness **`0.2.0-rc.1`**（最新的 `0.2.0` 候选版本）验证，同时也兼容 **`0.1.7-rc.2`**、**`0.1.7-rc.1`** 与 **`0.1.7-alpha.2`**。
 
 | 插件版本 | 已验证的 DeepSeek Harness | npm 发布状态 | 该版本是什么 |
 | --- | --- | --- | --- |
-| **`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.6`** | **`0.2.0-rc.1`**（最新 RC）、`0.1.7-rc.2`、`0.1.7-rc.1`、`0.1.7-alpha.2` | `latest` | 在 DSH `0.2.0-rc.1` 上实测同一份代码，并重写声明范围使插件能在 `0.2.0` 正式版上继续加载。代码与 `0.1.5` 相同，升级无需迁移。 |
+| `0.1.5` | `0.1.7-rc.2`（最新 0.1.7 RC）、`0.1.7-rc.1`、`0.1.7-alpha.2` | 已发布 | 确认同一份代码在第二个候选版本上原样可用并加以声明。代码与 `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 版本不会被自动宣称为兼容。
+**`0.1.6` 支持 DSH `0.2.0-rc.1`，即最新的候选版本（RC）。** `0.1.7-rc.2 → 0.2.0-rc.1` 之间，本插件依赖的契约全部没有变化——client-modules 加载器与 slot 注册 API 只差包版本号，评估 `peerDependencies` 的兼容性预检逐字节相同，侧栏行仍带 `data-row-key`/`role`/`aria-selected`，`conversation.session.header.utilities` 仍是 session 作用域的 list 座位，`shell.overlay` 仍渲染同一层——所以 **`0.1.6` 确认同一份代码在新 RC 上原样可用，并把它记入声明。** 范围这次要改，是因为旧的 `<0.2.0` 上界只是靠预发布排序才接纳了 `0.2.0-rc.1`：到了 `0.2.0` **正式版**，插件行会在启动时被直接禁用。而按 node-semver 的预发布规则，每个元组都得有比较符明确写出，所以范围写成三个分支——已验证的 `0.1.7` 线、精确的 `0.2.0-rc.1`、以及到 `<0.3.0` 为止的 `0.2.0` 正式版线。
+**从 `0.1.5` 升级无需任何迁移。** 仍在更旧的 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` 把同一范围声明为宿主要求：这是**允许加载**的范围，不等于已验证。该范围**同时接纳** `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` 中完全相同。
+- `peerDependencies` 声明的范围是 `>=0.1.7-alpha.2 <0.2.0-0 || 0.2.0-rc.1 || >=0.2.0 <0.3.0`（`dsh-client-ui-layout` 与 `dsh-client-ui-conversation`），`dsh.engines.dsh` 把同一范围声明为宿主要求：这是**允许加载**的范围，不等于已验证。三个分支是刻意写的：按 node-semver 的预发布规则，预发布只有在某个比较符写出同一个 `major.minor.patch` 时才被接纳——所以 `0.1.7` 线要自己的比较符，`0.2.0-rc.1` 精确钉死（没人测过的 `0.2.0-rc.2` 进不来），`0.2.0` 正式版线放开是为了插件能在正式版上继续加载。下界特意写成这个 alpha：`>=0.1.6-0 <0.2.0` 这样的范围一个已验证版本都不接纳。
+- DSH 会在启动时校验这些 peer，范围不满足就**直接禁用该插件行**，所以范围写对已经不只是"声明问题"；这段判定代码在 `0.1.7-rc.1`、`0.1.7-rc.2` 与 `0.2.0-rc.1` 中完全相同。
 - 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 大改行结构时最坏的结果是**色块不再显示**，不会挡住点击。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@idoall/dsh-session-colors",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "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",
@@ -21,10 +21,11 @@
   "dsh": {
     "manifestVersion": 1,
     "engines": {
-      "dsh": ">=0.1.7-alpha.2 <0.2.0"
+      "dsh": ">=0.1.7-alpha.2 <0.2.0-0 || 0.2.0-rc.1 || >=0.2.0 <0.3.0"
     },
     "compatibility": {
       "dshReleases": {
+        "0.2.0-rc.1": "compatible",
         "0.1.7-rc.2": "compatible",
         "0.1.7-rc.1": "compatible",
         "0.1.7-alpha.2": "compatible"
@@ -48,8 +49,8 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.7-alpha.2 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.7-alpha.2 <0.2.0",
+    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.7-alpha.2 <0.2.0-0 || 0.2.0-rc.1 || >=0.2.0 <0.3.0",
+    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.7-alpha.2 <0.2.0-0 || 0.2.0-rc.1 || >=0.2.0 <0.3.0",
     "@deepseek-ai/schemastery": "^3.18.2",
     "react": "^18.2.0"
   },