dsh-rewind-plugin 0.7.4 → 0.8.0-alpha.1

package/README.en.md

@@ -156,7 +156,8 @@ withdrew should consume the stable, locale-independent helpers exported from
 2. **Lightweight file rewind has a cost** — in specific cases not all changes can be rewound. Consistent with Claude Code. See: [File-rewind tracking boundary](docs/compat/tracking-boundary.md).
 3. **Rewinds from `≤ v0.2.4`** — sessions rewound with these versions may **fail to load history** after more conversation. Install a v0.3.3-or-earlier release and use its bundled repair tool ([docs/compat/troubleshooting.md](docs/compat/troubleshooting.md)).
 4. **Rewinds from `≤ v0.3.3`** — compaction (`/compact`) is unavailable for those sessions. Newer versions are compatible; for affected old sessions, start a new session.
-5. **The turn-rail shows rewound turns** — the right-side rail added in DSH `v0.1.2-alpha.1` keeps ticks for withdrawn messages: clicking does not jump and hovering shows the withdrawn text. Only a display difference; no functional impact.
+5. **The turn-rail shows rewound turns** — the right-side rail added in DSH `v0.1.2` keeps ticks for withdrawn messages, and hovering shows the withdrawn text. Only a display difference; no functional impact.
+6. **The system prompt is re-displayed after a rewind** — in DSH `v0.1.2`, rewinding and resending a message shows the "System prompt" component again, just like `/compact`. Only a display difference; no functional impact.
 
 > [!NOTE]
 > Browser diagnostics are available; see [Browser diagnostics](docs/compat/diagnostics.md).

package/README.md

@@ -143,7 +143,8 @@ dsh plugin --profile web add dsh-rewind-plugin
 2. **轻量文件回退存在代价**——特定情况可能无法回退所有修改。行为与 Claude Code 一致。详见：[文件回退的追踪边界](docs/compat/tracking-boundary.zh.md)。
 3. **v0.2.4 及更早版本**回退过的会话，继续对话后可能加载历史失败。可安装 v0.3.3 及之前版本的随附修复工具处理（[完整步骤](docs/compat/troubleshooting.zh.md)）。
 4. **v0.3.3 及更早版本**回退过的会话，压缩对话（compact）不可用。新版本已兼容；受影响的旧会话建议新建会话。
-5. **导轨显示已回退轮次**——DSH `v0.1.2-alpha.1` 新增的右侧导轨，会为已撤回消息保留刻度：点击不跳转、悬浮显示已撤回正文。仅显示差异，无功能影响。
+5. **导轨显示已回退轮次**——DSH `v0.1.2` 新增右侧导轨，为已撤回消息保留刻度，悬浮显示已撤回正文。仅显示差异，无功能影响。
+6. **回退重显系统提示词**——DSH `v0.1.2` 回退重发消息时，与 `/compact` 一样重显“系统提示词”组件。仅显示差异，无功能影响。
 
 > [!NOTE]
 > 本插件提供浏览器端诊断输出；详见 [浏览器诊断](docs/compat/diagnostics.zh.md)。

package/docs/architecture.md

@@ -98,10 +98,11 @@ pruneStale            cross-session auto-cleanup (default off): whole
 
 ## Compatibility strategy
 
-- **Peer ranges as OR-union of DSH version tuples** (`^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2`):
-  npm's prerelease rules require the peer range to share the host's
-  `[major, minor, patch]` tuple; `scripts/check-dsh-version.mjs` detects when
-  a new tuple requires appending. See `docs/release/release.md`.
+- **Peer ranges as one tuple per DSH line** (`^0.1.2-rc.1`): npm's prerelease
+  rules require the peer range to share the host's `[major, minor, patch]`
+  tuple, so a new DSH tuple replaces the peer tuple (the single-line model);
+  `scripts/check-dsh-version.mjs` flags when a new tuple arrives. See
+  `docs/release/release.md`.
 - **Test-driven investigation**: `tests/compat-invariants.ts` /
   `compat-interop` / `compat-gaps` probe harness behavior and pin findings in
   `docs/compat/audit.md`; `scripts/verify-host.mjs` runs a real end-to-end

package/docs/compat/audit.md

@@ -7,36 +7,33 @@
 > compatibility invariants. A probe failure is a finding; it enters the
 > fix/pin/record loop.
 >
-> Targeted version: npm `@deepseek-ai/*@0.1.1-rc.2` (matches `package-lock.json`);
-> source reference: the `oss/deepseek-harness` local fork.
+> Targeted version: npm `@deepseek-ai/*@0.1.2-rc.1` (matches `package-lock.json`).
+> Source reference: the upstream [github.com/deepseek-ai/deepseek-harness](https://github.com/deepseek-ai/deepseek-harness).
 >
-> Version alignment: `peerDependencies` use an OR-union (e.g.
-> `^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2`) covering each published tuple series. npm's
-> prerelease matching rules require a candidate to share the range comparator's
-> `[major, minor, patch]` tuple, so each new tuple series (e.g. a future
-> `0.1.2-rc.x`, `0.2.x`) requires appending a union member; rc rolling within a
-> tuple (`0.1.1-rc.2 → rc.3`) is a no-op. Signal: `npm view @deepseek-ai/dsh version`;
+> Version alignment: `peerDependencies` use one tuple per DSH line
+> (e.g. `^0.1.2-rc.1`). npm's prerelease matching rules require a candidate to
+> share the range comparator's `[major, minor, patch]` tuple, so a new DSH tuple
+> replaces the peer tuple (single-line model); any prerelease within the SAME
+> tuple is a no-op. Signal: `npm view @deepseek-ai/dsh version`;
 > flow: `scripts/check-dsh-version.mjs` (it reads the `latest` dist-tag only; a
-> `-alpha` prerelease published under another tag, e.g. `0.1.2-alpha.2` under
-> `alpha`, is a manual pre-release check).
+> prerelease published under another tag is a manual pre-release check).
 >
-> `0.1.2-alpha.1` was never published to npm, so the peer OR-union is declared only from `0.1.2-alpha.2`; the plugin code still supports the `alpha.1`+ client.
->
-> `0.1.2-alpha.2` … `0.1.2-alpha.5` verified-compatible. Built/tested on the rc.2
-> baseline (the `latest` dist-tag); the same published build also drives the alpha
-> line, and `alpha.2`/`alpha.3`/`alpha.4`/`alpha.5` share the `0.1.2` tuple, so the
-> single `^0.1.2-alpha.2` peer member covers all four. `rc.2` (`latest`) remains the
-> primary baseline; five versions verified: rc.2, alpha.2, alpha.3, alpha.4, alpha.5.
-
-### Channeled seams (version × channel)
-
-| Seam | rc.2 (`0.1.1-rc.2`) | alpha.2 / alpha.3 | alpha.4 / alpha.5 |
-| --- | --- | --- | --- |
-| Host session log (`eventsOf`) | `Session.events` | `Session.events` | `session.snapshotEvents()` |
-| Client chat snapshot (`chatSnapshotOf`) | session-face `chat` field | `uiConversation` `chat` view | `uiConversation` `chat` view |
-| Client composer refill (`writeComposer`) | `<textarea>` DOM write | `conversation.input.setDraft` | `conversation.input.setDraft` |
-| Client settings card | nested `ctx.inject(['settingsScope'])` | nested `ctx.inject(['settingsScope'])` | nested `ctx.inject(['settingsScope'])` |
-| Client seat-button DOM (`actionsContainerOf`) | `[data-time-hover-root]` | `[data-actions-reveal]` | structural locate of the copy-`<button>` container |
+> The plugin targets a single DSH version line (`0.1.2-rc.1`); compatibility
+> with earlier lines is not kept.
+
+### Single channel (`0.1.2-rc.1`)
+
+The plugin targets one DSH channel. Each seam below reads the 0.1.2-rc.1 shape
+only (no `Session.events` / `[data-time-hover-root]` / `<textarea>` / face-`chat`
+legacy branch).
+
+| Seam | 0.1.2-rc.1 implementation |
+| --- | --- |
+| Host session log | `session.snapshotEvents()` |
+| Client chat snapshot | `uiConversation` `chat` view (`chatSnapshotOf`) |
+| Client composer refill | `conversation.input.setDraft` facade |
+| Client settings card | nested `ctx.inject(['settingsScope'])` |
+| Client seat-button DOM | structural locate of the copy-`<button>` container (`actionsContainerOf`) |
 
 ## Definition of "fully compatible" (invariants)
 
@@ -62,7 +59,7 @@
 - **rewind across a compact checkpoint**: `RewindError('not-on-surface')` refuses cleanly, no crash.
 - **plan-mode**: a marker reuses the last started turn (no phantom turn); a rewind never touches the log-only `plan/mode` state (plan mode stays active; the user leaves it with `/plan off`) and the log stays replayable (`compat-invariants` I1/I3 marker + `plan/mode` probe, `verify-host`).
 - **agent-loop cancellation**: `finally` guarantees step/turn closure; the rewind force-stop path leaves no dangling frame.
-- **settings-card cross-version reach**: the Snapshot cleanup card must be registered through a **nested** `ctx.inject(['settingsScope'], …)` — naming `settingsScope` in the module-level inject unmounts the whole client plugin on rc.2 (card and rewind button disappear). It uses only the rc.2↔alpha-common scope subset (`getSnapshot().value` + `set`), never the alpha-only `mutate`.
+- **settings-card registration**: the Snapshot cleanup card must be registered through a **nested** `ctx.inject(['settingsScope'], …)` — naming `settingsScope` in the module-level inject would keep the whole client plugin unmounted on a host without that service (card and rewind button would disappear). It reads `getSnapshot().value` + `set`, never the `mutate` write API.
 
 ## Known behavior boundaries (deterministic differences, non-crash, documented)
 
@@ -81,7 +78,7 @@ The plugin treats these as harness-side defects it does not compensate for. Each
 ### RU-I18N: host-side locale preference is not reliably readable at command registration (harness-side structural timing defect; plugin reads once, never retries)
 
 - **Root cause (harness-side)**: the plugin resolves `activeLocale` in an
-  `ctx.inject(['settings'])` callback that reads `settings.get(settingsNamespace('locale')).preference`
+  `ctx.inject(['settings'])` callback that reads `settings.get('locale').preference`
   **once, with no retry** (`src/index.ts`). `dsh-client-locale`'s host half
   registers that `locale` settings section **through its own `ctx.inject(['settings'])`**
   (`packages/client/locale/src/index.ts`). Both callbacks wait only on `settings` and are

package/docs/contract/client-contract.md

@@ -21,7 +21,7 @@ the plugin itself uses (it never reads the DOM or host copy):
 ```ts
 import { hiddenSeqsOf, type HiddenChat } from 'dsh-rewind-plugin/client'
 
-const chat = session.getSnapshot().chat // rc.2 source; 0.1.2-alpha.1+ uses the uiConversation "chat" view
+const chat = uiConversation.binding(sessionId).target('chat')?.getSnapshot() // the 0.1.2-rc.1 "chat" view
 const hidden = hiddenSeqsOf(chat as HiddenChat) // Set<number> of anchor seqs
 ```
 

package/docs/contract/client-contract.zh.md

@@ -20,7 +20,7 @@
 ```ts
 import { hiddenSeqsOf, type HiddenChat } from 'dsh-rewind-plugin/client'
 
-const chat = session.getSnapshot().chat // rc.2 来源；0.1.2-alpha.1+ 用 uiConversation "chat" 视图
+const chat = uiConversation.binding(sessionId).target('chat')?.getSnapshot() // 0.1.2-rc.1 的 "chat" 视图
 const hidden = hiddenSeqsOf(chat as HiddenChat) // 被隐藏的 anchor seq 集合
 ```
 

package/docs/harness-reference.md

@@ -1,8 +1,7 @@
 # DeepSeek Harness interface reference
 
 > Maintainer doc: the harness subsystems this plugin depends on, and the key
-> source files behind each interface. Local fork (if present):
-> `<workspace>/oss/deepseek-harness/` — official repo:
+> source files behind each interface. Official repo:
 > [github.com/deepseek-ai/deepseek-harness](https://github.com/deepseek-ai/deepseek-harness)
 
 ## Subsystem docs (`docs/subsystems/`)
@@ -40,8 +39,8 @@ Also under `docs/` at the repo root: `persistence-catalog.md` (full
 | `tools/pre-execute` / `execute` / `post-execute` | [packages/core/tools/src/index.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/core/tools/src/index.ts) |
 | Client DOM anchors (`data-chat-flow-kind` / `data-chat-anchor-key`) | [packages/client/ui-conversation/src/client/chat/ChatNodeSeat.tsx](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/ui-conversation/src/client/chat/ChatNodeSeat.tsx) |
 | User bubble rendering | [packages/client/ui-conversation/src/client/chat/MessageItem.tsx](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/ui-conversation/src/client/chat/MessageItem.tsx) |
-| Client `SessionFace` (`command` / `cancel`) | [packages/client/runtime/src/client/contract/session.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/runtime/src/client/contract/session.ts) |
-| Client `PendingWait` (`respond`) | [packages/client/runtime/src/client/sessions/pending.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/runtime/src/client/sessions/pending.ts) |
+| Client `SessionFace` (`command` / `cancel`) | [packages/api/session-controller/src/client/contract/session.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/api/session-controller/src/client/contract/session.ts) |
+| Client pending interaction (SessionPendingInteraction) | [packages/client/ui-session/src/client/index.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/ui-session/src/client/index.ts) |
 
 ## Plugin source layout
 

package/docs/release/release.md

@@ -33,45 +33,101 @@ 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 tag is the **lightweight `npm version` tag** (on the `chore: release …`
+  commit). Push it as-is — **do not** create the tag or the release beforehand
+  with `gh release create <tag>`: that tags the remote's current `main` head, so
+  an unpushed version bump leaves the tag on the wrong commit and the
+  tag/version match check fails.
 - **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 | Notes |
+| --- | --- | --- |
+| `0.7.x` | `0.1.1` + `0.1.2` (broad) | frozen / EOL |
+| `0.8.x` | `0.1.2-rc.1` (single) | current stable |
+| `0.9.x` | `0.1.3` (single) | next line |
+
+**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,82 @@ 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`。
+
+- tag 即 `npm version` 生成的**轻量 tag**（落在 `chore: release …` 提交上）。
+  直接原样 push 即可——**不要**用 `gh release create <tag>` 事先建 tag 或
+  release：它会给远端当前 `main` 的 HEAD 打 tag，若版本 bump 尚未 push，tag
+  就会落在错误提交上，导致 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 版本线破坏性变更 ＝ 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/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
-   rc.2 uses border-radius 12px + 1px solid border-l2, while alpha uses 16px +
-   0.5px border-l4 (and adds corner-shape: round). We intentionally keep the
-   rc.2 values here for now; if the alpha 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,18 +1088,14 @@ 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 copy = row?.querySelector("button");
-  const structural = copy?.parentElement;
+  const buttons = Array.from(row?.querySelectorAll("button") ?? []);
+  const lastButton = buttons.filter((button) => !button.classList.contains(CLASS.button)).at(-1);
+  const structural = lastButton?.parentElement;
   if (structural instanceof HTMLElement && structural.querySelector("button") !== null) return structural;
   return void 0;
 }
@@ -1305,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) {
@@ -1356,8 +1333,8 @@ function createRewindBridge(deps) {
 }
 
 // src/client/build-info.ts
-var PLUGIN_VERSION = true ? "0.7.4" : "dev";
-var BUILD_HASH = true ? "73e01232" : "dev";
+var PLUGIN_VERSION = true ? "0.8.0-alpha.1" : "dev";
+var BUILD_HASH = true ? "ca24fc4e" : "dev";
 
 // src/client/locales.ts
 var zh = {
@@ -1615,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})`);
@@ -1635,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;
       }
@@ -1666,7 +1642,6 @@ function apply(ctx) {
           return void 0;
         }
       },
-      (id) => sessionOf(id),
       sessionId,
       cb
     );
@@ -1776,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();
     };