@idoall/dsh-session-colors 0.1.1 → 0.1.3

package/CHANGELOG.md

@@ -8,6 +8,70 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.3] - 2026-09-23
+
+Verified against DeepSeek Harness `0.1.7-alpha.2`. The first fix below is what
+made the previous build fail to load on that release; the other two are a
+declaration correctness fix and a visible behaviour fix.
+
+### Fixed
+
+- **The plugin could not load from a `link:` install on DSH 0.1.7.** From 0.1.7,
+  only a linked plugin's **peer** dependencies resolve from the running
+  installation; a plain dependency is looked up under the plugin's own
+  `node_modules`, which a link install does not populate. `@deepseek-ai/schemastery`
+  was a plain dependency and this repository ships no `node_modules`, so the Host
+  half failed to import and the plugin never loaded. It is a peer now (kept in
+  `devDependencies` for this repository's own tests).
+- **The declared peer range excluded the release it was running on.**
+  `>=0.1.6-0 <0.2.0` does **not** admit `0.1.7-alpha.2` under node-semver's
+  default prerelease rule, so pnpm reports the peer as unmet (the plugin market's
+  discovery check passes `includePrerelease`, which is why it did not surface as
+  an outright incompatibility). The range is now `>=0.1.7-alpha.2 <0.2.0`, with a
+  `dsh.engines.dsh` requirement and `dsh.compatibility.dshReleases` recording
+  `0.1.7-alpha.2`.
+- **Chips no longer stayed behind while rows glided.** DSH 0.1.7 moves sidebar
+  rows with the Web Animations API (`element.animate`), which fires neither
+  `transitionrun` nor `transitionend` and mutates no DOM. The layer only opened
+  its bounded follow window on a transition event, so a collapse, expand or
+  reorder left every chip at the position the glide started from. A row-list
+  mutation and a window resize now re-measure once and enter the same 40-frame
+  follow window; an unrelated body mutation re-measures once but opens no window,
+  so a streaming transcript cannot keep a measuring loop alive.
+
+### Changed
+
+- The Session id is read from the row's own `data-row-key` (`session:<id>`, added
+  in DSH 0.1.7) before falling back to the React fiber, so the common case no
+  longer depends on React internals. The fiber fallback remains for older builds
+  and search-result rows.
+- The client build marker is `host-routes+animated-rows`.
+- The docs-consistency test now evaluates the peer range with the prerelease
+  rule instead of a substring check — the check that let the old, excluding range
+  pass.
+
+### Notes
+
+- `0.1.3` supports DSH `0.1.7-alpha.2` only and declares
+  `>=0.1.7-alpha.2 <0.2.0` as its Host requirement. Installations on an older DSH,
+  including `0.1.6-alpha.2`, should stay on plugin `0.1.2`.
+
+## [0.1.2] - 2026-09-22
+
+### Fixed
+
+- Chips no longer stay at their old coordinates for up to 20 seconds when a
+  workspace is collapsed or expanded. Each mutation option set now gets its own
+  `MutationObserver`: a second `observe()` call on the same target **replaces**
+  the first one's options rather than merging them, so sharing one observer for
+  `childList` and for the `body` class had silently stopped row additions and
+  removals from being watched at all. The chips only moved when the 20-second peer
+  poll happened to re-render the layer.
+
+### Added
+
+- A regression test that fails if two option sets ever share one observer again.
+
 ## [0.1.1] - 2026-09-22
 
 Documentation only — no code change.

package/README.md

@@ -69,12 +69,15 @@ Requirements:
 
 - DeepSeek Harness with a Web profile
 - Node.js 20 or newer
-- **Verified DSH version: `0.1.6-alpha.2`** (see [Compatibility](#compatibility))
+- **Verified DSH version: `0.1.7-alpha.2`** (see [Compatibility](#compatibility))
 
 ```sh
-dsh plugin --profile <profile> add @idoall/dsh-session-colors@0.1.0
+dsh plugin --profile <profile> add @idoall/dsh-session-colors@latest
 ```
 
+The [compatibility table](#compatibility) lists the exact versions, if you need to
+pin one to a specific DSH release.
+
 Working on the plugin itself? Install the directory instead:
 
 ```sh
@@ -114,12 +117,18 @@ stored as HSVA, so alpha round-trips exactly.
 
 ## Compatibility
 
-Current release: plugin **`0.1.1`**, verified against DeepSeek Harness
-**`0.1.6-alpha.2`**.
+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.
 
 | Plugin version | Verified DeepSeek Harness | npm status | What it is |
 | --- | --- | --- | --- |
-| **`0.1.1`** | `0.1.6-alpha.2` | `latest` | Documentation only: the packaged README no longer says "not published", and the market screenshots are declared. No code change. |
+| **`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.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 |
 
 - **Verified DeepSeek Harness** is the exact DSH version this plugin was actually
@@ -127,9 +136,17 @@ Current release: plugin **`0.1.1`**, verified against DeepSeek Harness
   [`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.6-0 <0.2.0` for `dsh-client-ui-layout` and
-  `dsh-client-ui-conversation`: that is the range allowed to **load**, which is
-  not the same as verified.
+- `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.
+- `@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
+  import the Host half.
 - DSH moving faster than this plugin does not break it: chips depend on DSH's row
   DOM (see [Limitations](#limitations)), so a large change to the row structure
   can at worst stop chips from appearing — it cannot block clicking.
@@ -183,7 +200,7 @@ document.querySelector('.dsh-sc-layer').dataset
 // { dshScBuild, dshScStatus, dshScWritable, dshScMarks, dshScError }
 ```
 
-If `dshScBuild` is not `host-routes+drawer-aware`, the device is running a
+If `dshScBuild` is not `host-routes+animated-rows`, the device is running a
 **cached client**: refresh the page (the browser half reloads on a refresh, no DSH
 restart needed). If `dshScStatus` is not `ready`, the store cannot be read — see
 the next item.
@@ -200,9 +217,10 @@ pages, because storage uses its own route. If you see the old "settings
 unavailable" behaviour, check which version is installed.
 
 **Chips are in the wrong place, or gone.**
-The layer finds rows by ARIA role and reads the Session id from the React fiber.
-A large change to DSH's sidebar structure can make it find nothing; chips then
-disappear, but **clicking is unaffected** because the layer is click-through.
+The layer finds rows by ARIA role and reads the Session id from the row's
+`data-row-key` (falling back to React internals). A large change to DSH's sidebar
+structure can make it find nothing; chips then disappear, but **clicking is
+unaffected** because the layer is click-through.
 
 ## Security boundaries
 
@@ -220,8 +238,8 @@ disappear, but **clicking is unaffected** because the layer is click-through.
 ## Limitations
 
 - **The chip depends on DSH's row DOM.** It reads rows by ARIA role and the
-  Session id from React internals. A future DSH release can stop chips from
-  appearing; it cannot break clicking.
+  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.
 - **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
@@ -240,7 +258,7 @@ is not deleted for you; remove it yourself if you do not want it.
 ## Development
 
 ```sh
-npm test        # 34 tests: bundle shape, store, route, cross-device, geometry, docs
+npm test        # 38 tests: bundle shape, store, route, cross-device, geometry, docs
 ```
 
 The browser half is a hand-authored `__ModuleLoader__` bundle, which is the only

package/README.zh.md

@@ -51,12 +51,14 @@
 
 - 带 Web profile 的 DeepSeek Harness
 - Node.js 20 或更新版本
-- **已验证的 DSH 版本：`0.1.6-alpha.2`**（见[兼容性](#兼容性)）
+- **已验证的 DSH 版本：`0.1.7-alpha.2`**（见[兼容性](#兼容性)）
 
 ```sh
-dsh plugin --profile <profile> add @idoall/dsh-session-colors@0.1.0
+dsh plugin --profile <profile> add @idoall/dsh-session-colors@latest
 ```
 
+要按 DSH 版本精确对应，用[兼容性](#兼容性)表里的具体版本号。
+
 要改插件本身就用目录安装：
 
 ```sh
@@ -88,15 +90,20 @@ dsh plugin --profile <profile> add link:/path/to/dsh-session-colors
 
 ## 兼容性
 
-当前版本：插件 **`0.1.1`** 已针对 DeepSeek Harness **`0.1.6-alpha.2`** 验证。
+当前版本：插件 **`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`，低于它的版本未经本轮验证。
 
 | 插件版本 | 已验证的 DeepSeek Harness | npm 发布状态 | 该版本是什么 |
 | --- | --- | --- | --- |
-| **`0.1.1`** | `0.1.6-alpha.2` | `latest` | 仅文档：打包进 npm 的 README 不再写"尚未发布"，并声明了市场截图。无代码改动。 |
+| **`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.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` | 已发布 | 首个版本：会话颜色标记、宿主侧存储、手机抽屉内可见 |
 
 - **已验证的 DeepSeek Harness** 是这个插件**实际跑过**的确切 DSH 版本。这份清单只有一个存放处——[`package.json`](package.json) 的 `dsh.compatibility.dshReleases`——并且有测试保证两个 README 的兼容性段落与它逐字一致、且落在 `peerDependencies` 声明的范围内。未列出的 DSH 版本**不会被宣称为兼容**。
-- `peerDependencies` 声明的范围是 `>=0.1.6-0 <0.2.0`（`dsh-client-ui-layout` 与 `dsh-client-ui-conversation`）：这是**允许加载**的范围，不等于已验证。
+- `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，即使插件实际跑得起来。
+- `@deepseek-ai/schemastery` 声明为 **peer**，不是普通依赖：DSH 0.1.7 只把 link 插件的 **peer** 依赖解析到运行实例，所以用 `link:` 装入本目录时，普通依赖会让宿主半边 import 失败。
 - DSH 升级快于插件时，插件本身不会因此报错：色块依赖 DSH 的行 DOM（见[限制](#限制)），所以 DSH 大改行结构时最坏的结果是**色块不再显示**，不会挡住点击。
 
 ## 跨设备与局域网
@@ -140,7 +147,7 @@ document.querySelector('.dsh-sc-layer').dataset
 // { dshScBuild, dshScStatus, dshScWritable, dshScMarks, dshScError }
 ```
 
-`dshScBuild` 不是 `host-routes+drawer-aware` 就是**客户端缓存**，刷新页面即可（客户端半边刷新即热重载，不需要重启 DSH）。`dshScStatus` 不是 `ready` 则是存储读不到，见下一条。
+`dshScBuild` 不是 `host-routes+animated-rows` 就是**客户端缓存**，刷新页面即可（客户端半边刷新即热重载，不需要重启 DSH）。`dshScStatus` 不是 `ready` 则是存储读不到，见下一条。
 
 **头部控制显示 ⚠。**
 表示读不到存储：`dshScError` 里有原因，`dshScWritable` 说明能不能写。宿主路由未注册（插件没被 profile 加载）或数据目录不可写时会这样。注意**这不是**"这个会话没有颜色"。
@@ -149,7 +156,7 @@ document.querySelector('.dsh-sc-layer').dataset
 从 `0.1.0` 起本插件在局域网/隧道页面与回环页面行为一致（存储走自有路由）。如果你看到的是旧版那种"设置读不到"的表现，先确认装的是哪个版本。
 
 **色块位置不对或消失。**
-色块浮层靠 ARIA role 找会话行、靠 React fiber 取会话 ID。DSH 大改侧栏结构后可能找不到行；此时色块会消失，但**不会影响点击**，因为浮层是点击穿透的。
+色块浮层靠 ARIA role 找会话行、靠行自身的 `data-row-key` 取会话 ID（取不到时回退到 React fiber）。DSH 大改侧栏结构后可能找不到行；此时色块会消失，但**不会影响点击**，因为浮层是点击穿透的。
 
 ## 安全边界
 
@@ -161,7 +168,7 @@ document.querySelector('.dsh-sc-layer').dataset
 
 ## 限制
 
-- **色块依赖 DSH 的行 DOM。** 它靠 ARIA role 找行、靠 React 内部结构取会话 ID。DSH 未来改版可能让色块不再显示；但**不会影响点击**。
+- **色块依赖 DSH 的行 DOM。** 它靠 ARIA role 找行、靠行自身的 `data-row-key` 取会话 ID（回退到 React 内部结构）。DSH 未来改版可能让色块不再显示；但**不会影响点击**。
 - **标记属于单个 DSH 实例。** 它存在某个 profile 的数据目录里，两个独立的 DSH 服务之间不共享。
 - **没有权限模型。** 凡是能访问该 profile 已鉴权路由的人，都能读写标记。
 - **只有颜色。** 没有文字标签、图标或 emoji。
@@ -177,7 +184,7 @@ dsh plugin --profile <profile> remove @idoall/dsh-session-colors
 ## 开发
 
 ```sh
-npm test        # 34 项：bundle 结构、存储、路由、跨设备、几何、文档一致性
+npm test        # 38 项：bundle 结构、存储、路由、跨设备、几何、文档一致性
 ```
 
 浏览器半边是**手写的** `__ModuleLoader__` bundle——这是 DSH 客户端加载器接受的唯一格式。手写是刻意的：**没有构建步骤**，就不会有产物与目标 DSH 版本漂移的问题。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@idoall/dsh-session-colors",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "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",
@@ -20,9 +20,12 @@
   ],
   "dsh": {
     "manifestVersion": 1,
+    "engines": {
+      "dsh": ">=0.1.7-alpha.2 <0.2.0"
+    },
     "compatibility": {
       "dshReleases": {
-        "0.1.6-alpha.2": "compatible"
+        "0.1.7-alpha.2": "compatible"
       }
     },
     "bundle": {
@@ -42,12 +45,10 @@
   "publishConfig": {
     "access": "public"
   },
-  "dependencies": {
-    "@deepseek-ai/schemastery": "^3.18.2"
-  },
   "peerDependencies": {
-    "@deepseek-ai/dsh-client-ui-conversation": ">=0.1.6-0 <0.2.0",
-    "@deepseek-ai/dsh-client-ui-layout": ">=0.1.6-0 <0.2.0",
+    "@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/schemastery": "^3.18.2",
     "react": "^18.2.0"
   },
   "peerDependenciesMeta": {
@@ -58,6 +59,11 @@
       "optional": true
     }
   },
+  "devDependencies": {
+    "@deepseek-ai/cordis": "^4.0.4",
+    "@deepseek-ai/schemastery": "^3.18.2",
+    "react": "^18.3.1"
+  },
   "license": "MIT",
   "engines": {
     "node": ">=20"

package/src/client.js

@@ -15,12 +15,13 @@
  *   `ChipsLayer` and `layerZIndexOf`.
  *
  * There is no Session-row slot, so a chip cannot be rendered inside a row. The
- * layer finds rows by ARIA role and reads each row's Session id from the React
- * fiber the renderer already attached — the only place the id exists, since the
- * row markup carries no id attribute. That coupling is deliberate and is kept
- * harmless: every step is guarded, an unreadable row is skipped, and the layer
- * never accepts pointer events, so a future DSH change can at worst stop the
- * chips from appearing.
+ * layer finds rows by ARIA role and reads each row's Session id from the
+ * `data-row-key` attribute DSH 0.1.7 puts on every row (`session:<id>`),
+ * falling back to the React fiber the renderer attaches — the only source on a
+ * build without that attribute, and still the source for search-result rows.
+ * That coupling is deliberate and is kept harmless: every step is guarded, an
+ * unreadable row is skipped, and the layer never accepts pointer events, so a
+ * future DSH change can at worst stop the chips from appearing.
  *
  * Written as a hand-authored `__ModuleLoader__` bundle (the only format the
  * client loader accepts for a package client half), so it needs no build step.
@@ -46,13 +47,13 @@ window.__ModuleLoader__.load({
 
     const NS = 'sessionColor'
     /**
-     * Build marker. Stored marks are Host-side as of this build, and the chip
-     * layer paints just above the sidebar as of the `drawer-aware` build — the
-     * change that makes a chip visible inside a phone's sidebar drawer. A device
-     * that still shows an older marker is running a cached client and must be
-     * hard-refreshed.
+     * Build marker. Stored marks are Host-side as of the `host-routes` build,
+     * the chip layer paints just above the sidebar as of `drawer-aware`, and as
+     * of `animated-rows` it follows the Web-Animations row gliding DSH 0.1.7
+     * introduced. A device that still shows an older marker is running a cached
+     * client and must be hard-refreshed.
      */
-    const BUILD = 'host-routes+drawer-aware'
+    const BUILD = 'host-routes+animated-rows'
 
     /**
      * This plugin's own Host route. Kept in sync with the Host half's
@@ -429,13 +430,28 @@ window.__ModuleLoader__.load({
 
     //#region row discovery
     /**
-     * Session id of a rendered row, read from the React fiber the renderer
-     * already attached. The row markup deliberately carries no id, so the fiber
-     * is the only exact source; the walk is bounded and every failure returns
-     * undefined, which makes the caller skip that row.
+     * Prefix DSH 0.1.7 uses for a Session row's `data-row-key`. It is the
+     * exact, stable DOM source of a row's Session id; older builds and
+     * search-result rows carry no such attribute.
+     */
+    const SESSION_ROW_KEY = 'session:'
+
+    /**
+     * Session id of a rendered row. The `data-row-key` attribute is read first
+     * because DSH 0.1.7 marks every row with it; the React fiber the renderer
+     * already attached remains the fallback, and the walk is bounded so an
+     * unexpected shape only costs that row its chip.
      * @param node - a Session row element.
      */
     function sessionIdOf(node) {
+      try {
+        const key = node === null || node === undefined || typeof node.getAttribute !== 'function'
+          ? undefined
+          : node.getAttribute('data-row-key')
+        if (typeof key === 'string' && key.startsWith(SESSION_ROW_KEY)) return key.slice(SESSION_ROW_KEY.length)
+      } catch {
+        // An unreadable attribute only sends this row to the fiber fallback.
+      }
       try {
         const key = Object.keys(node).find((name) => name.startsWith('__reactFiber$') || name.startsWith('__reactInternalInstance$'))
         if (key === undefined) return undefined
@@ -603,10 +619,23 @@ window.__ModuleLoader__.load({
           setLayer({ items, clip, zIndex: rows.length === 0 ? 1 : layerZIndexOf(rows[0]) })
         }
         sync()
+        /**
+         * Re-measure now, then keep re-measuring for a bounded window.
+         *
+         * DSH 0.1.7 glides rows with the Web Animations API
+         * (`element.animate`): that fires neither `transitionrun` nor
+         * `transitionend` and mutates no DOM, so the one MutationObserver
+         * callback for a collapse lands on the animation's first frame — every
+         * row still painted at its old coordinates — and nothing would ever
+         * report the movement again. Following each mutation for the same
+         * bounded window as a transition keeps the chips on their rows.
+         */
+        const kick = () => { sync(); follow() }
         // Rows move with their scroll container and re-render on every list
-        // change, so follow both.
+        // change, so follow both. A scroll reports its own frames continuously,
+        // so it needs no follow window of its own.
         document.addEventListener('scroll', sync, true)
-        window.addEventListener('resize', sync)
+        window.addEventListener('resize', kick)
         // A CSS transition moves every row without any scroll, resize or DOM
         // mutation: the phone adapter slides the whole sidebar in with a
         // transform on the drawer while the rows themselves never change. Only
@@ -621,24 +650,53 @@ window.__ModuleLoader__.load({
         }
         document.addEventListener('transitionrun', onTransition, true)
         document.addEventListener('transitionend', onTransition, true)
-        let observer
+        // Each option set needs its OWN observer. A second `observe()` call on
+        // the same target REPLACES the first one's options rather than merging
+        // them (DOM spec), so sharing one observer silently stopped childList
+        // from being watched at all: collapsing a workspace removed its rows
+        // without any re-sync, and the chips sat at their old coordinates until
+        // the peer poll happened to re-render the layer ~20s later.
+        const observers = []
         try {
-          observer = new MutationObserver(sync)
-          observer.observe(document.body, { childList: true, subtree: true })
+          /**
+           * Whether a mutation could have changed the row list, and so started a
+           * row glide. The childList watch is body-wide because rows live deep
+           * inside the sidebar, so a mutation unrelated to the list — a
+           * streaming transcript, a tooltip — re-measures once but must not open
+           * a follow window for every frame it produces.
+           */
+          const rowsChanged = (records) => records.some((record) => {
+            const target = record.target
+            return target !== null && target !== undefined
+              && typeof target.closest === 'function'
+              && target.closest('[role="tree"]') !== null
+          })
+          const onRowsMutation = (records) => { if (rowsChanged(records)) kick(); else sync() }
+          const rowsObserver = new MutationObserver(onRowsMutation)
+          rowsObserver.observe(document.body, { childList: true, subtree: true })
+          observers.push(rowsObserver)
           // The phone adapter opens its drawer by toggling a class on `body`.
           // With transitions disabled the geometry still changes, just without a
           // transition event to follow.
-          observer.observe(document.body, { attributes: true, attributeFilter: ['class'] })
+          const drawerObserver = new MutationObserver(kick)
+          drawerObserver.observe(document.body, { attributes: true, attributeFilter: ['class'] })
+          observers.push(drawerObserver)
+          // A workspace collapse that hides rows instead of removing them
+          // produces no childList mutation, so follow the ARIA state and
+          // `hidden` as well.
+          const stateObserver = new MutationObserver(kick)
+          stateObserver.observe(document.body, { attributes: true, attributeFilter: ['aria-expanded', 'hidden'], subtree: true })
+          observers.push(stateObserver)
         } catch {
-          observer = undefined
+          // Without observers the layer still follows scroll, resize and transitions.
         }
         return () => {
           cancelFrame(frame)
           document.removeEventListener('scroll', sync, true)
-          window.removeEventListener('resize', sync)
+          window.removeEventListener('resize', kick)
           document.removeEventListener('transitionrun', onTransition, true)
           document.removeEventListener('transitionend', onTransition, true)
-          if (observer !== undefined) observer.disconnect()
+          for (const watcher of observers) watcher.disconnect()
         }
       }, [snapshot])