dsh-rewind-plugin 0.7.5 → 0.9.0-alpha.1

package/docs/release/release.md

@@ -33,45 +33,103 @@ Open `https://www.npmjs.com/package/dsh-rewind-plugin` → package **settings**
 
 ## Subsequent releases (CI, automatic)
 
-```sh
-npm version patch
-git push origin main --tags   # triggers .github/workflows/publish.yml
-```
+The release workflow is **version-driven**: it derives the npm dist-tag from the
+version in `package.json`, independent of branch. A stable version publishes to
+`latest`; a pre-release publishes to the dist-tag named by its pre-release
+identifier (e.g. `0.9.0-alpha.1` → `alpha`, `0.9.0-rc.1` → `rc`). The dist-tag is
+never passed by hand.
+
+The line being released determines the branch and the bump:
+
+| Release | Branch | Bump | dist-tag |
+| --- | --- | --- | --- |
+| Stable patch (current line) | `release/0.8.x` | `npm version patch` | `latest` |
+| Pre-release (next line) | `main` | `npm version prerelease --preid=alpha` | `alpha` |
+| Stable (next line) | `main` | `npm version 0.9.0` | `latest` |
 
+Each release is `git push <branch>` followed by `git push <branch> --tags`.
+
+- The release commit is **`chore: release vX.Y.Z`**; the **lightweight `vX.Y.Z`
+  tag** sits on it. Do **not** create tag/release first with `gh release create
+  <tag>` (it tags the remote `main` head and breaks the tag/version match).
 - **Before bumping, manually confirm there is no newer DSH version the plugin
   has not been verified against** (a pre-release can ship in DSH Desktop
-  without being on npm, e.g. `0.1.2-alpha.1`; see docs/compat/audit.md).
+  without being on npm; see docs/compat/audit.md).
 - The workflow verifies the tag matches `package.json`, runs typecheck + tests +
-  a full build + artifact verification, publishes with `--provenance`
-  (Sigstore), and creates a GitHub Release. It is **idempotent** — an already
-  published version is skipped.
+  a full build + artifact verification, publishes with `--provenance` (Sigstore)
+  to the version-derived dist-tag, and creates a GitHub Release (a pre-release
+  is created as a GitHub pre-release, not `latest`). It is **idempotent** — an
+  already published version is skipped.
 - CI (`.github/workflows/ci.yml`) runs `npm run check` — typecheck + tests +
   build + artifact verification + a `npm pack --dry-run` — on every push / PR
   across both Node engines boundary versions; the tarball layout is guarded by
   `tests/package-layout.test.ts`.
+- The GitHub Release body is auto-created with `--generate-notes` as a
+  **placeholder** (`--latest` / `--prerelease` per version). After the publish
+  run succeeds, overwrite the body by hand in the repo's bilingual style
+  (Chinese first, then English) — never keep the auto text as the final note.
 
-## DSH version alignment (peer range maintenance)
+## DSH version alignment (single peer tuple)
 
 DSH is still in rc; npm's prerelease matching rules require a peer range to
 share the host version's `[major, minor, patch]` tuple. So `peerDependencies`
-uses an OR-union covering every published tuple series
-(e.g. `^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2`), extended as DSH releases new tuples.
-
-- **When to update**: only when DSH releases a new tuple
-  (`0.1.1 → 0.1.2 → 0.2.x`); rc rolling within a tuple (`0.1.1-rc.2 → rc.3`)
-  needs nothing. All `@deepseek-ai/*` packages release together;
-  `npm view @deepseek-ai/dsh version` is the authoritative signal.
-- **Exception — `@deepseek-ai/dsh-client-runtime`**: it never published a
-  `0.1.2-alpha.*` (npm `next` is `0.1.1-rc.2`) and is imported `import type`
-  only, so keep it at `^0.1.0-rc.6 || ^0.1.1-rc.2` (no `0.1.2` member).
+uses one peer tuple per DSH line (e.g. `^0.1.2-rc.1`), replaced (never
+appended) when DSH releases a new tuple.
+
+- **When to update**: only when DSH releases a new tuple (`0.1.2 → 0.1.3 →
+  0.2.x`); rc rolling within a tuple (`0.1.2-rc.1 → rc.2`) needs nothing. All
+  `@deepseek-ai/*` packages release together; `npm view @deepseek-ai/dsh version`
+  is the authoritative signal.
 - **Published-tuple check (optional)**: `node scripts/check-dsh-version.mjs`
-  compares the `latest` dist-tag version against the tuples the peers cover
+  compares the `latest` dist-tag version against the tuple the peers cover
   (exit 0 = nothing to do, exit 1 = update). It reads the `latest` tag only; a
-  pre-release published under another tag (e.g. `alpha`) or bundled without
+  pre-release published under another tag or bundled without
   going to npm is a manual pre-release check — see the "Before bumping" step above.
-- **Update steps**: append `|| ^<new-tuple>-rc.<n>` to every
-  `@deepseek-ai/dsh-*` peer → bump devDependencies to the latest → `npm
-  install` → `npm run check` → release.
+- **Update steps**: replace every `@deepseek-ai/dsh-*` peer's tuple with
+  `^<latest>` → bump devDependencies to the latest → `npm install` →
+  `npm run check` → release.
 - **After DSH goes final**: final releases are not bound by the prerelease
   tuple rule, so the peers can converge to a single stable range (e.g.
   `^0.1.x`); this section can then be deleted.
+
+## Versioned-line release model
+
+**One release targets one DSH version line.** The plugin's own version is
+independent of the host; a release declares its DSH line through the peer
+constraint (a single companion tuple), never through the plugin version.
+
+| Plugin version | DSH line | Role (example) |
+| --- | --- | --- |
+| `0.7.x` | `0.1.1` + `0.1.2` (broad) | frozen / EOL |
+| `0.8.x` | `0.1.2-rc.1` (single) | current line |
+| `0.9.x` | `0.1.3` (single) | following line |
+
+The rows are illustrative — the DSH line a release targets is the peer
+constraint, and its npm dist-tag is derived from the version (see above), so
+this model does not track the plugin's own version number.
+
+**Versioning.** A DSH version-line break is a MAJOR bump (incompatible with the
+prior DSH line). Within a line, MINOR/PATCH remain compatible.
+
+**Branching (trunk-based).** `main` is the single integration and release line
+and is always releasable. The currently-shipped stable is cut into a short-lived
+`release/<version>.x` maintenance branch from its release commit; that branch
+receives backported fixes while `main` advances to the next line. The prior
+(broad-compat) line is frozen as a tag, with no branch.
+
+**dist-tag routing.** The release workflow derives the npm dist-tag from the
+version: a stable version publishes to `latest`; a pre-release publishes to the
+dist-tag named by its pre-release identifier (`0.9.0-alpha.1` → `alpha`,
+`0.9.0-rc.1` → `rc`). A pre-release never occupies `latest`.
+
+**Support window / EOL.** A DSH line is supported within a declared window. By
+default the window runs until the next DSH line ships as `latest`; after that
+the line is EOL, frozen, and receives no further patches. Here `0.8.x`
+(`0.1.2-rc.1`) is supported until `0.9.x` (`0.1.3`) ships as `latest`.
+
+**Bug-fix flow (forward-fix then backport).** A fix affecting multiple supported
+lines is applied on `main` first, then backported to each still-supported
+release branch. A fix specific to one line is applied only on that line.
+
+The single-line model uses one peer tuple per release (see DSH version
+alignment above); the OR-union multi-line practice it replaced is not used.

package/docs/release/release.zh.md

@@ -32,37 +32,84 @@ npm publish --access public
 
 ## 后续发布（CI 自动）
 
-```sh
-npm version patch
-git push origin main --tags   # 触发 .github/workflows/publish.yml
-```
+发布 workflow 为**版本驱动**：npm dist-tag 由 `package.json` 中的版本号决定、与分支无关。
+稳定版发 `latest`；pre-release 发到与其 pre-release 标识符同名的 dist-tag
+（如 `0.9.0-alpha.1` → `alpha`、`0.9.0-rc.1` → `rc`）。dist-tag 无需手传。
+
+按要发布的版本线选择分支与版本步进：
+
+| 发布类型 | 分支 | 版本步进 | dist-tag |
+| --- | --- | --- | --- |
+| 当前线稳定补丁 | `release/0.8.x` | `npm version patch` | `latest` |
+| 下一线 pre-release | `main` | `npm version prerelease --preid=alpha` | `alpha` |
+| 下一线正式版 | `main` | `npm version 0.9.0` | `latest` |
 
-- **升版前手动确认**：确认无插件未针对其验证过的更新 DSH 版本（pre-release 可能只随 Desktop 捆绑、而不发到 npm，如 `0.1.2-alpha.1`；见 docs/compat/audit.md）。
+每次发布为 `git push <分支>`，再 `git push <分支> --tags`。
+
+- 发布提交为 **`chore: release vX.Y.Z`**，**轻量 `vX.Y.Z` tag** 落在该提交上。
+  **不要**用 `gh release create <tag>` 事先建 tag/release（会打到远端 `main`
+  HEAD，导致 tag/版本校验失败）。
+- **升版前手动确认**：确认无插件未针对其验证过的更新 DSH 版本（pre-release
+  可能只随 Desktop 捆绑、而不发到 npm；见 docs/compat/audit.md）。
 - workflow 校验 tag 与 `package.json` 版本一致，跑 typecheck + 测试 + 完整
-  构建 + 产物验证，以 `--provenance`（Sigstore）发布并创建 GitHub Release。
+  构建 + 产物验证，以 `--provenance`（Sigstore）发布到版本推导出的 dist-tag，
+  并创建 GitHub Release（pre-release 会建成 GitHub pre-release，而非 `latest`）。
   **幂等**——已发布的版本会跳过。
 - CI（`.github/workflows/ci.yml`）在每次 push / PR 跑 `npm run check`——
   typecheck + 测试 + 构建 + 产物验证 + `npm pack --dry-run`，且覆盖
   engines 两个边界版本；tarball 布局由 `tests/package-layout.test.ts` 守护。
+- GitHub Release 正文由 workflow 以 `--generate-notes` 自动生成，仅是**占位**
+  （按版本取 `--latest` / `--prerelease`）。发布运行成功后，请用**手写双语**
+  正文（中文在前、英文在后）覆盖——切勿把自动文本当作最终发布说明。
 
-## DSH 版本适配（peer 范围维护）
+## DSH 版本适配（单一 peer 元组）
 
 DSH 仍在 rc 阶段，npm 的 prerelease 匹配规则要求 peer 范围与宿主版本
 **同 `[major, minor, patch]` 元组**才能匹配。因此 peerDependencies 采用
-OR 并集覆盖 DSH 已发布的每个元组系列（如 `^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2`），
-并随 DSH 发版追加。
+**每一条 DSH 线一个 peer 元组**（如 `^0.1.2-rc.1`），DSH 发新元组时**替换**而非追加。
 
-- **何时需要更新**：仅当 DSH 发布新元组（`0.1.1 → 0.1.2 → 0.2.x`）时；
-  同元组内 rc 滚动（`0.1.1-rc.2 → rc.3`）无需动作。DSH 所有包同版本发布，
+- **何时需要更新**：仅当 DSH 发布新元组（`0.1.2 → 0.1.3 → 0.2.x`）时；
+  同元组内 rc 滚动（`0.1.2-rc.1 → rc.2`）无需动作。DSH 所有包同版本发布，
   `npm view @deepseek-ai/dsh version` 即权威信号。
-- **例外 —— `@deepseek-ai/dsh-client-runtime`**：它从未发布 `0.1.2-alpha.*`
-  （npm `next` 为 `0.1.1-rc.2`）且仅被 `import type` 引用，保持
-  `^0.1.0-rc.6 || ^0.1.1-rc.2` 即可（无 `0.1.2` 元组项）。
 - **已发布元组检查（可选）**：`node scripts/check-dsh-version.mjs` 用 npm `latest`
   dist-tag 版本对比 peer 覆盖的元组（exit 0 无需动作，exit 1 需要）。它**只读
-  `latest` tag**；发布在其它 tag（如 `alpha`）的 pre-release 走**手动发布前检查**
+  `latest` tag**；发布在其它 tag 的 pre-release 走**手动发布前检查**
   ——见上文"升版前手动确认"。
-- **更新步骤**：给每个 `@deepseek-ai/dsh-*` peer 追加 `|| ^<新元组>-rc.<n>`
+- **更新步骤**：把每个 `@deepseek-ai/dsh-*` peer 的元组**替换**为 `^<最新版>`
   → devDependencies 同步升到最新 → `npm install` → `npm run check` → 发版。
 - **正式版后收敛**：DSH 发布 final 版本后，正式版不受 prerelease 元组规则
   限制，peer 可收敛为稳定的 `^0.1.x` 单范围，此节即可删除。
+
+## 发布版本线模型
+
+**一个发布对准一条 DSH 版本线。** 插件自身版本号与宿主解耦；某发布所对准的
+DSH 线由 peer 约束（单一 companion 元组）声明，而非插件版本号。
+
+| 插件版本 | DSH 线 | 角色（示例） |
+| --- | --- | --- |
+| `0.7.x` | `0.1.1` + `0.1.2`（广兼容） | 冻结 / EOL |
+| `0.8.x` | `0.1.2-rc.1`（单线） | 当前线 |
+| `0.9.x` | `0.1.3`（单线） | 后续线 |
+
+各行仅为示例——某个发布对准的 DSH 线由 peer 约束声明，其 npm dist-tag 按版本号
+派生（见上文），因此本模型不跟随插件自身版本号变化。
+
+**版本号。** DSH 版本线破坏性变更 ＝ MAJOR 升版（与更早 DSH 线向后不兼容）。
+同一线内 MINOR/PATCH 保持向后兼容。
+
+**分支（主干开发）。** `main` 是唯一集成与发布线，始终可发版。当前已发布
+稳定版从发布提交点切出短命 `release/<版本>.x` 维护分支；该分支承接
+backport 修复，同时 `main` 前进到下一线。更早的（广兼容）线冻结成 tag，无分支。
+
+**dist-tag 路由。** 发布 workflow 按版本号取 npm dist-tag：稳定版发 `latest`；
+pre-release 发到与其 pre-release 标识符同名的 dist-tag（`0.9.0-alpha.1` →
+`alpha`、`0.9.0-rc.1` → `rc`）。pre-release 不占据 `latest`。
+
+**支持窗口 / EOL。** 一条 DSH 线仅在声明的窗口内受支持。默认窗口到下一
+DSH 线作为 `latest` 发布为止；此后该线 EOL、冻结、不再发补丁。此处 `0.8.x`
+（`0.1.2-rc.1`）支持到 `0.9.x`（`0.1.3`）作为 `latest` 发布为止。
+
+**Bug 修复流程（先向前修，再回迁）。** 跨多条支持线的修复，先在 `main` 上
+修复，再回迁到各仍受支持的 release 分支。仅特定线的修复，只在对应线修复。
+
+单线模型每个发布使用单一 peer 元组（见上文「DSH 版本适配」）；其取代的 OR 并集多线做法已不使用。

package/docs/rewind-fix.md

@@ -0,0 +1,80 @@
+# Rewind-marker update guide
+
+> English | [中文](rewind-fix.zh.md)
+
+## Applies to
+
+- **DSH**: `0.1.2-rc.1`
+- **dsh-rewind**: `0.9.0-alpha.1`
+
+## Background
+
+`/rewind` appends a **marker** to the session log, telling DSH "everything from this screen onward is withdrawn". Aged plugin versions used a "ghost step frame" for this; the current version uses a more canonical, functionally-equivalent shape — a content-empty `user/message` that replaces the content after the target (see the [README](../README.en.md), the "How it works" section).
+
+The next DSH line (`v0.1.3`) will reject the old shape, so **sessions rewound by an older plugin may fail to open after an upgrade**. That's why the plugin ships `/dsh-rewind-fix`: it translates those old markers into the new shape and makes the sessions usable again. The new shape is also fully compatible with older DSH versions.
+
+## Warnings
+
+1. **It directly edits the session log** — it rewrites old rewind markers into the new format. The design already handles the common cases safely (**multiple web windows**, **exit / restart**, **switching sessions**, **power loss**): it only touches **closed** sessions, locks and **backs up** each one before writing, **rolls back** on failure, and is **idempotent** (safe to re-run). It changes the marker only — it deletes no conversation content and **loses no information**.
+
+2. **It resets the matching snapshot backups** — the format update renumbers event seqs, so a session that was **updated** has its snapshot backups (the lightweight backups used to **restore files** for "conversation and code") no longer match, and the plugin **clears** them. This only affects **file restore** (those sessions can't use snapshots to restore files); backups start recording fresh. Sessions that weren't updated keep their snapshots.
+
+## Steps
+
+### Step 1 · Confirm your versions
+
+First confirm your DSH and plugin versions are in the "Applies to" range — it's a prerequisite. If either is out of range, the tool may be unavailable or behave differently. You can just ask the AI for your current DSH and dsh-rewind plugin versions and check they're in range.
+
+### Step 2 · Back up manually (optional)
+
+The command rewrites session files and clears some snapshots, so a backup is a good idea. The default data directory is `~/.dsh` (if you've set `$DSH_HOME`, use its value):
+```sh
+cp -r ~/.dsh/sessions          ~/.dsh/sessions.backup
+cp -r ~/.dsh/rewind-snapshots  ~/.dsh/rewind-snapshots.backup
+```
+Or copy them anywhere convenient.
+
+### Step 3 · Start a new session, or pick one that was never rewound
+
+The command only handles **closed** sessions, and it can't run on itself. So:
+- **Start a new session** — ideally send any message first to initialize the window so you can see the command's progress and output.
+- Or pick a session that was **never rewound** (one that needs no update).
+
+Then run the command **in this new session**, and it will update the old sessions that need it.
+
+> ⚠️ Don't run it in a session that itself needs updating and is currently open — the command skips this session, and any other currently-open/in-use session.
+
+### Step 4 · Preview the update scope
+
+Type `/dsh-rewind-fix` in the composer and send it. It only scans, doesn't write — it reports how many sessions were scanned, how many will be updated, how many skipped, and how many failed. Confirm those are what you expect before moving on.
+```
+/dsh-rewind-fix
+```
+
+### Step 5 · Execute
+
+Once you're sure, re-enter the command with `--apply` to actually run it:
+```
+/dsh-rewind-fix --apply
+```
+This really rewrites the session logs and updates the old markers, and **may take a few minutes**. Please let it finish — **don't switch to another session window or close DSH** while it runs: a session you switch to is **safely skipped** (no corruption, but it won't be updated this pass and you'll need to re-run). A session that fails stays as it was, unharmed, and can be updated again later. Sessions that are updated also get their matching **snapshot backups cleared**, so file restore to earlier messages is no longer available for them.
+
+### Step 6 · Restart DSH and preview again (optional)
+
+After the run, restart DSH, then **preview once more**:
+```
+/dsh-rewind-fix
+```
+If it says there are no more sessions to update, the markers are all current and the old sessions will open normally.
+
+### Step 7 · Delete the backup after confirming (optional)
+
+Use it for a while, and once everything works, delete the backup from step 2:
+```sh
+rm -rf ~/.dsh/sessions.backup ~/.dsh/rewind-snapshots.backup
+```
+
+## Notes
+
+- The session logs are still v0 format; when DSH's later `v0 → v1 → v2` migration (in `v0.1.3`) arrives, if you've completed the `rewind` marker update, the markers themselves won't block it.
+- Some sessions may still be blocked by an **unclosed turn** (a turn that was interrupted/cancelled and never wrote `turn/end`). Per the empirical analysis these are widespread and **unrelated to rewind** — they're a DSH-side issue and this tool doesn't handle them. **So updating the markers doesn't guarantee you can upgrade to the next DSH line.**

package/docs/rewind-fix.zh.md

@@ -0,0 +1,80 @@
+# 回退标记更新指南
+
+> [English](rewind-fix.md) | 中文
+
+## 适配
+
+- **DSH**：`0.1.2-rc.1`
+- **dsh-rewind**：`0.9.0-alpha.1`
+
+## 背景
+
+`/rewind` 回退会往会话日志追加一条**标记**，告诉 DSH 从某一屏往后都算「已撤回」。旧版插件用的是「幽灵步骤框架」写法；新版本已换成更规范且功能一致的形态——一条内容为空的 `user/message`，把目标之后的内容整体替换掉（原理见 [README](../README.md) 的「原理」一节）。
+
+新一代 DSH（`v0.1.3`）会拒绝旧写法，所以**用旧版插件回退过的会话，升级后可能打不开**。因此本插件提供了 `/dsh-rewind-fix` 便捷命令，把这些旧标记「翻译」成新格式，让会话重新可用。新格式同样对旧版本 DSH 完全兼容。
+
+## 警告
+
+1. **会直接编辑会话日志** —— 把旧回退标记更新为新格式。设计上对**多个网页窗口、退出重启、切换会话、关机断电**等场景都已做安全处理：只处理**已关闭**的会话，写前加锁+备份、失败自动回滚、可重复运行（**幂等**）；只动标记本身，不删任何对话内容、**无信息丢失**。
+
+2. **会重置对应的快照备份** —— 格式更新会改变事件序号，**被更新过的会话**，其用于「回退对话和代码」时**还原文件**的对应快照备份将不再匹配，因此会被插件**清除**。这只影响**文件还原**，备份会重新开始记录；没被更新的会话快照不变。
+
+## 操作步骤
+
+### 第一步 · 确认版本
+
+先确认你当前的 DSH 与插件版本落在「适配」范围里——这是前提。版本不符时，工具可能不可用或行为不符。你可以直接问 AI「当前的 DSH 与 dsh-rewind 插件版本」，并确认是否在「适配」范围内。
+
+### 第二步 · 手动备份（可选）
+
+命令会改写会话文件、删掉部分快照，稳妥起见先备份一下。默认数据目录是 `~/.dsh`（若你设置了 `$DSH_HOME`，请用它的值）：
+```sh
+cp -r ~/.dsh/sessions          ~/.dsh/sessions.backup
+cp -r ~/.dsh/rewind-snapshots  ~/.dsh/rewind-snapshots.backup
+```
+或者复制到任意合适的位置。
+
+### 第三步 · 新建会话，或选一个从未回退过的会话
+
+命令只处理已关闭的会话，而且不能在自己身上运行——建议你：
+- **新建一个会话**，先随便发一条消息初始化窗口，确保能看到命令执行过程和结果
+- 选择一个**从未回退过**（不需要更新）的会话
+
+然后在**这个新会话窗口里**运行命令，去更新那些需要处理的旧会话。
+
+> ⚠️ 别在「本身就需要更新、且正开着」的会话里运行——命令会跳过本会话，以及任何正被打开/使用的会话。
+
+### 第四步 · 预览更新范围
+
+在编辑区域输入 `/dsh-rewind-fix` 并发送。它只扫描、不写盘，会告诉你：扫描了几个会话、其中几个将被更新、几个跳过、几个失败。确认是你预期的那几项，再进下一步。
+```
+/dsh-rewind-fix
+```
+
+### 第五步 · 执行
+
+确认无误后，重新输入命令并加 `--apply` 真正执行：
+```
+/dsh-rewind-fix --apply
+```
+这一步会真的改动会话日志、把旧标记更新成新格式，**可能需要几分钟**。请耐心等它跑完，**不要中途切换会话窗口**或关闭 DSH——被切到的会话会被**安全地跳过**（不损坏，但这次不会更新，需重新执行）。更新失败的会话保持原状态不变、无破坏，可重新进行更新。被更新的会话会同时**清掉对应的文件快照备份**，更早消息回退时文件还原不可用。
+
+### 第六步 · 重启 DSH，再预览确认（可选）
+
+执行完后重启一下 DSH，然后**再跑一次预览**：
+```
+/dsh-rewind-fix
+```
+如果提示已经没有待更新的会话，说明标记已全部更新到位，旧会话就能正常打开了。
+
+### 第七步 · 确认正常后删除备份（可选）
+
+继续使用一段时间，确认一切功能正常后，删掉第二步拷贝的备份即可：
+```sh
+rm -rf ~/.dsh/sessions.backup ~/.dsh/rewind-snapshots.backup
+```
+
+## 补充说明
+
+- 当前会话日志仍为 v0 格式；DSH 后续（`v0.1.3`）的 `v0 → v1 → v2` 迁移到来时，如果你完成了 `rewind` 标记更新，标记本身就不会阻断它。
+- 个别会话还可能因**未闭合的 turn**（某次回合被打断/取消、没写 `turn/end`）等问题而卡住迁移——根据实测分析，这些问题普遍存在，**与 rewind 无关**，属 DSH 侧自身问题，本工具不处理。**所以更新完标记并不保证一定能升到下一 DSH 线。**

package/lib/client.js

@@ -35,16 +35,12 @@ __export(index_exports, {
 module.exports = __toCommonJS(index_exports);
 
 // src/client/hidden.ts
-function resolveChatWatch(resolveView, resolveFace, sessionId, cb) {
+function resolveChatWatch(resolveView, sessionId, cb) {
   const view = resolveView(sessionId);
-  if (view?.subscribe !== void 0) return view.subscribe(cb);
-  const face = resolveFace(sessionId);
-  return face?.subscribe(cb) ?? (() => {
+  return view?.subscribe?.(cb) ?? (() => {
   });
 }
-function chatSnapshotOf(face, chatView) {
-  const legacy = face?.getSnapshot().chat;
-  if (legacy !== void 0) return legacy;
+function chatSnapshotOf(chatView) {
   return chatView?.getSnapshot() ?? void 0;
 }
 function messageTextAt(chat, seq) {
@@ -328,16 +324,12 @@ var STYLE = `
 }
 
 /* ---- Snapshot-cleanup settings card (mirrors the harness PluginCard look) ---- */
-/* Dual-channel note: the harness card corner/border drifted across versions \u2014
-   0.1.1-rc.2 uses border-radius 12px + 1px solid border-l2, while 0.1.2-rc.1
-   uses 16px + 0.5px border-l4 (and adds corner-shape: round). We intentionally
-   keep the 0.1.1-rc.2 values here for now; if the 0.1.2-rc.1 look is wanted,
-   switch these on the host version like the other dual-channel surfaces (see the
-   host-version probe in src/client/index.ts). */
+/* Standardized on the 0.1.2 harness card look (border-radius 16px + 0.5px
+   border-l4, 0.5px internal separators). */
 .dsh-rewind-cleanup-card {
   list-style: none;
-  border: 1px solid var(--dsw-alias-border-l2);
-  border-radius: 12px;
+  border: 0.5px solid var(--dsw-alias-border-l4);
+  border-radius: 16px;
   background: var(--dsw-alias-bg-layer-3);
   transition: border-color .16s, background .16s;
 }
@@ -405,7 +397,7 @@ var STYLE = `
   color: var(--dsw-alias-label-secondary);
 }
 .dsh-rewind-cleanup-body {
-  border-top: 1px solid var(--dsw-alias-border-l2);
+  border-top: 0.5px solid var(--dsw-alias-border-l2);
   margin: 0 16px;
   padding: 4px 0 8px;
 }
@@ -427,7 +419,7 @@ var STYLE = `
   padding: 12px 0;
 }
 .dsh-rewind-cleanup-field + .dsh-rewind-cleanup-field {
-  border-top: 1px solid var(--dsw-alias-border-l2);
+  border-top: 0.5px solid var(--dsw-alias-border-l2);
 }
 .dsh-rewind-cleanup-head {
   display: flex;
@@ -648,7 +640,7 @@ function waitForCommand(session, chatOf, match, timeoutMs = 8e3, watch) {
         settle({ kind: node.outcome.kind, text: node.outcome.text });
       }
     };
-    const unsubscribe = (watch ?? ((cb) => session.subscribe(cb)))(check);
+    const unsubscribe = watch(check);
     const timer = setTimeout(() => settle(null), timeoutMs);
     check();
   });
@@ -988,15 +980,6 @@ var rewindLog = {
 
 // src/client/portals.tsx
 var import_jsx_runtime = require("react/jsx-runtime");
-function fillComposerTextarea(text) {
-  const textarea = document.querySelector(COMPOSER_TEXTAREA_SELECTOR);
-  if (textarea === null) return false;
-  const setter = Object.getOwnPropertyDescriptor(HTMLTextAreaElement.prototype, "value")?.set;
-  setter?.call(textarea, text);
-  textarea.dispatchEvent(new Event("input", { bubbles: true }));
-  textarea.focus();
-  return true;
-}
 function fillComposerEditable(text) {
   const editable = document.querySelector(COMPOSER_EDITABLE_SELECTOR);
   if (editable === null) return false;
@@ -1020,7 +1003,6 @@ function fillComposerEditable(text) {
   return true;
 }
 function fillComposer(text) {
-  if (fillComposerTextarea(text)) return true;
   return fillComposerEditable(text);
 }
 function writeComposer(text, facade) {
@@ -1089,7 +1071,7 @@ async function runRewindAndFill(session, seq, mode, currentSessionId, chatOf, wa
   }
 }
 function composerSurface() {
-  return document.querySelector(COMPOSER_TEXTAREA_SELECTOR) ?? document.querySelector(COMPOSER_EDITABLE_SELECTOR);
+  return document.querySelector(COMPOSER_EDITABLE_SELECTOR);
 }
 function showHint(text) {
   const surface = composerSurface();
@@ -1106,16 +1088,11 @@ function showHint(text) {
   }
   window.setTimeout(() => hint.remove(), 3200);
 }
-var COMPOSER_TEXTAREA_SELECTOR = "[data-input-scroll] textarea, textarea[data-phase]";
 var COMPOSER_EDITABLE_SELECTOR = "[data-composer-input]";
 var USER_SEAT_SELECTOR = '[data-chat-flow-kind="user"][data-chat-anchor-key], [data-chat-flow-kind="steering"][data-chat-anchor-key]';
 var CHAT_SEAT_SELECTOR = "[data-chat-anchor-key]";
-var ACTIONS_ROOT_SELECTOR = "[data-time-hover-root], [data-actions-reveal]";
 var PENDING_SEAT_SELECTOR = "[data-pending-steering]";
 function actionsContainerOf(row) {
-  const root = row?.matches(ACTIONS_ROOT_SELECTOR) ? row : row?.querySelector(ACTIONS_ROOT_SELECTOR);
-  const actions = root?.lastElementChild;
-  if (actions instanceof HTMLElement && actions.querySelector("button") !== null) return actions;
   const buttons = Array.from(row?.querySelectorAll("button") ?? []);
   const lastButton = buttons.filter((button) => !button.classList.contains(CLASS.button)).at(-1);
   const structural = lastButton?.parentElement;
@@ -1306,7 +1283,6 @@ function RewindButton({ target, sessionId, sessionOf, chatOf, watchChat, current
 function composerText() {
   const surface = composerSurface();
   if (surface === null) return "";
-  if (surface instanceof HTMLTextAreaElement) return surface.value;
   return surface.textContent ?? "";
 }
 async function retractPending(session, itemId, text, setComposerText) {
@@ -1357,8 +1333,8 @@ function createRewindBridge(deps) {
 }
 
 // src/client/build-info.ts
-var PLUGIN_VERSION = true ? "0.7.5" : "dev";
-var BUILD_HASH = true ? "25e8b3ca" : "dev";
+var PLUGIN_VERSION = true ? "0.9.0-alpha.1" : "dev";
+var BUILD_HASH = true ? "ca24fc4e" : "dev";
 
 // src/client/locales.ts
 var zh = {
@@ -1616,7 +1592,6 @@ var name = "dsh-rewind";
 var inject = ["slots", "sessions", "locale", "commandUi"];
 var NS2 = "rewind";
 var HEADER_ACTIONS_SLOT = "conversation.session.header.actions";
-var COMPOSER_TEXTAREA_SELECTOR2 = "[data-input-scroll] textarea, textarea[data-phase]";
 var COMPOSER_EDITABLE_SELECTOR2 = "[data-composer-input]";
 function apply(ctx) {
   rewindLog.info("boot", `loaded v${PLUGIN_VERSION} (build ${BUILD_HASH})`);
@@ -1636,7 +1611,7 @@ function apply(ctx) {
       if (session === void 0) return void 0;
       try {
         const view = uiConversation()?.binding(session.sessionId).target(CHAT_VIEW);
-        return chatSnapshotOf(session, view);
+        return chatSnapshotOf(view);
       } catch {
         return void 0;
       }
@@ -1667,7 +1642,6 @@ function apply(ctx) {
           return void 0;
         }
       },
-      (id) => sessionOf(id),
       sessionId,
       cb
     );
@@ -1777,7 +1751,7 @@ function apply(ctx) {
     for (const name2 of ["rewind", "undo"]) {
       yield commandUi.decorate({ name: name2, ...rewindPopupSpec });
     }
-    const composerSurface2 = () => document.querySelector(COMPOSER_TEXTAREA_SELECTOR2) ?? document.querySelector(COMPOSER_EDITABLE_SELECTOR2);
+    const composerSurface2 = () => document.querySelector(COMPOSER_EDITABLE_SELECTOR2);
     yield () => {
       style.remove();
     };