dsh-rewind-plugin 0.6.2 → 0.6.3

package/README.en.md

@@ -12,7 +12,7 @@ A deliberately focused plugin with one job: **rewind to any user message, no mat
 
 - **Rewinding is time-travel** — the target message and everything after it (agent replies, tool calls) are withdrawn from the model context *and* the rendered transcript at once, with no new session and no window switch; the target's text is offered back in the composer so you can edit and re-send it — **truly seamless and convenient by design**.
 - **Lightweight workspace backup** — Claude Code-aligned behavior: tracks files edited by the write-class tools, and external changes to **already-tracked** files are restorable too. Selective tracking, before-write backup, store only on change. One lightweight plugin gives you a **complete** agentic rewind capability.
-- **Privacy-first** — the plugin never deletes or rewrites the session log (append-only) and never actually deletes any of your conversation; file restores stay inside the plugin's own backup directory. Full security model: [SECURITY.md](SECURITY.md).
+- **Privacy-first** — the plugin never deletes or rewrites the session log (append-only) and never actually deletes any of your conversation; backups live in the plugin's own snapshot directory; restores draw only from those backups. Full security model: [SECURITY.md](SECURITY.md).
 - **A complete test system** — unit, probe, and end-to-end host verification, covering compatibility probing, log replay, resume, cross-restart and other scenarios; maintained continuously as the harness evolves to ensure feature stability.
 
 ## Preview
@@ -156,7 +156,7 @@ withdrew should consume the stable, locale-independent helpers exported from
 
 ## Security
 
-This plugin only appends rewind-marker events to the session log; it never deletes or rewrites logged history. Workspace files are written only when you choose "conversation and code"; backups and restores stay under `<dsh home>/rewind-snapshots/`. It never touches your git repository, makes no network requests, and accesses no credentials. Delete `~/.dsh/rewind-snapshots/` to wipe file backups only (chat rewinds are unaffected); the plugin rebuilds automatically. For sessions you've left inactive for a long time, a global auto-cleanup (off by default) can remove their snapshot directory in whole, leaving the active session and the chat log untouched. Full security model: [SECURITY.md](SECURITY.md).
+This plugin only appends rewind-marker events to the session log; it never deletes or rewrites logged history. Workspace files are written only when you choose "conversation and code"; backups are stored under `<dsh home>/rewind-snapshots/`; restores draw only from those backups. It never touches your git repository, makes no network requests, and accesses no credentials. Delete `~/.dsh/rewind-snapshots/` to wipe file backups only (chat rewinds are unaffected); the plugin rebuilds automatically. For sessions you've left inactive for a long time, a global auto-cleanup (off by default) can remove their snapshot directory in whole, leaving the active session and the chat log untouched. Full security model: [SECURITY.md](SECURITY.md).
 
 ## Development
 

package/README.md

@@ -12,7 +12,7 @@ DeepSeek Harness 插件：**一键就地回退对话到任意更早的用户消
 
 - **回退 = 时间回溯**——目标消息及其之后的全部内容（agent 回复、工具调用）同时从**模型上下文**和**渲染对话**中撤回，不新建会话、不切换窗口；目标消息文本会回填输入框，改完可重发。**在原理上就真正无感、便捷**。
 - **轻量工作区备份**——对齐 Claude Code：追踪写类工具编辑过的文件，**已跟踪文件的外部变更也能还原**。局部追踪、写前备份、不变不存。一个轻型插件，即拥有**完备的智能体回退能力**。
-- **信息安全优先**——插件从不删改会话日志（append-only），从不真正删除你的任何对话；文件还原限定在插件自己的备份目录。完整安全模型：[SECURITY.md](SECURITY.md)。
+- **信息安全优先**——插件从不删改会话日志（append-only），从不真正删除你的任何对话；备份存于自己的快照目录；还原只用这些备份。完整安全模型：[SECURITY.md](SECURITY.md)。
 - **完备测试系统**——单元、探针、端到端主机验证，覆盖兼容性探测、日志重放、续接、跨重启等场景；随 harness 升级持续维护，确保功能稳定。
 
 ## 效果预览
@@ -144,7 +144,7 @@ dsh plugin --profile web add dsh-rewind-plugin
 
 ## 安全
 
-本插件只向会话日志追加回退标记事件，从不删除或改写已记录的历史。工作区文件仅在「回退对话和代码」时被改写，备份与还原都限定在 `~/.dsh/rewind-snapshots/` 内。不触碰你的 git 仓库，无网络请求，不访问任何凭据。对**长期不活跃**的会话，另有默认关闭的全局自动清理可整目录移除其快照，不影响活动会话与对话日志。完整安全模型：[SECURITY.md](SECURITY.md)。
+本插件只向会话日志追加回退标记事件，从不删除或改写已记录的历史。工作区文件仅在「回退对话和代码」时被改写，备份存储于 `~/.dsh/rewind-snapshots/`；还原以备份为唯一来源。不触碰你的 git 仓库，无网络请求，不访问任何凭据。对**长期不活跃**的会话，另有默认关闭的全局自动清理可整目录移除其快照，不影响活动会话与对话日志。完整安全模型：[SECURITY.md](SECURITY.md)。
 
 ## 开发
 

package/SECURITY.md

@@ -83,9 +83,8 @@ and is repaired offline (see `docs/compat/troubleshooting.md`).
 
 - **Store root**: `<harness home>/rewind-snapshots/` by default (resolved via
   `resolveDshHome`, so `~/.dsh/...` when `DSH_HOME` is unset); the `snapshotDir`
-  config, then `DSH_REWIND_SNAPSHOT_DIR` env, override it. The store never
-  overlaps the workspace; deleting it only removes file backups and the store
-  rebuilds from scratch.
+  config, then `DSH_REWIND_SNAPSHOT_DIR` env, override it. Deleting it only
+  removes file backups and the store rebuilds from scratch.
 - **Path sanitization**: session ids and call ids are scrubbed to
   `[a-zA-Z0-9._-]` (`safeSessionId` / `safeFileId`) before joining the store
   root; `.` and `..` bare values are replaced — hostile ids cannot traverse
@@ -138,10 +137,18 @@ and is repaired offline (see `docs/compat/troubleshooting.md`).
   same operating-system user: state files are created with the process
   default permissions (no special modes are set — a standard umask applies),
   and the host user remains trusted.
-- It does **not** exclude paths from the store: recording and restore mirror the
-  paths the model's file tools touched, so a sensitive file (e.g. `.env`) the
-  model may read or edit will be backed up and restorable. Keeping one out is
-  a **DSH model-permission** concern (a per-path deny), not a rewind feature.
+- It does **not** exclude paths from the store, and it never oversteps: the
+  plugin only adds backup/restore on top of permissions DSH already holds. Two
+  distinct cases follow:
+  1. **Sensitive / personal-information files** (e.g. a `.env` file, which may
+     sit inside the workspace) the model may read or edit are backed up and
+     restorable.
+  2. **Files outside the session workspace** the model is allowed to touch are
+     likewise backed up and restored.
+  In both cases the plugin introduces no authority of its own — DSH already
+  granted the read/edit; the plugin merely records a before-backup and can
+  restore it. Keeping a path out is a **DSH model-permission** concern (a
+  per-path deny), not a rewind feature.
 - It does **not** touch git (no refs, index, or worktree operations), makes
   **no network requests**, and does **not** access credentials.
 - It does **not** roll back whole-log state: telemetry, search, and `/export`

package/docs/architecture.md

@@ -98,7 +98,7 @@ pruneStale            cross-session auto-cleanup (default off): whole
 
 ## Compatibility strategy
 
-- **Peer ranges as OR-union of DSH rc tuples** (`^0.1.0-rc.6 || ^0.1.1-rc.2`):
+- **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`.

package/docs/compat/audit.md

@@ -11,32 +11,37 @@
 > source reference: the `oss/deepseek-harness` local fork.
 >
 > Version alignment: `peerDependencies` use an OR-union (e.g.
-> `^0.1.0-rc.6 || ^0.1.1-rc.2`) covering each published rc tuple series. npm's
+> `^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`;
-> flow: `scripts/check-dsh-version.mjs`.
+> 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).
 >
-> Client channel (harness `0.1.2-alpha.1`, a **bundled pre-release — NOT published
-> to npm**): the plugin also reads the session chat when a DSH Desktop build ships
-> that version (`latest` on the registry is still `0.1.1-rc.2`; the alpha is only
-> in the bundled `app.asar.unpacked/node_modules/@deepseek-ai/*`). There
-> `uiConversation` exposes the chat as a per-session named `"chat"` view
+> Client channel (harness `0.1.2-alpha.x`; `0.1.2-alpha.2` is published to npm
+> under the `alpha` dist-tag while `latest` stays `0.1.1-rc.2`): the plugin reads
+> the session chat through `uiConversation` whenever the DSH client exposes it.
+> `uiConversation` surfaces the chat as a per-session named `"chat"` view
 > (contributed by `dsh-client-ui-chat` through the `uiSession` slot hook) instead
 > of the session-face `chat` field. `src/client/hidden.ts` (`chatSnapshotOf`) reads
 > the session-face snapshot first (rc.2 path), then the `uiConversation` `"chat"`
-> view (alpha.1 path); both missing degrades to `undefined` (no targets, never a
-> crash). Peers are intentionally **NOT** extended for `0.1.2-alpha.1` because it is
-> not a registry version (see above); the OR-union stays
-> `^0.1.0-rc.6 || ^0.1.1-rc.2` and will gain the `0.1.2` tuple when the harness
-> publishes it. Pinned by `tests/chat-channel.test.ts` (channel precedence + the
-> alpha.1 snapshot shape) and `tests/client-dom.test.ts` (the button-target
-> pairing that consumes the chat). The composer refill is dual-channel the same
-> way: on alpha.1 the withdrawn text is written through the `conversation`
-> service's `input` resolver's `setDraft` (the harness's own Lexical editor),
-> else the rc.2 `<textarea>` / alpha.1 `contenteditable` DOM write (`writeComposer`
-> in `src/client/portals.tsx`); pinned by `tests/client-composer.test.ts`.
+> view (alpha path); both missing degrades to `undefined` (no targets, never a
+> crash). The channel is held via a lazy `ctx.get` (never a declared `inject`), so
+> the plugin keeps the rc.2 type baseline while the OR-union covers the published
+> `0.1.2` tuple: `^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2`. Pinned by
+> `tests/chat-channel.test.ts` (channel precedence + the alpha snapshot shape) and
+> `tests/client-dom.test.ts` (the button-target pairing that consumes the chat).
+> The composer refill is dual-channel the same way: on alpha the withdrawn text is
+> written through the `conversation` service's `input` resolver's `setDraft` (the
+> harness's own Lexical editor), else the rc.2 `<textarea>` / alpha `contenteditable`
+> DOM write (`writeComposer` in `src/client/portals.tsx`); pinned by
+> `tests/client-composer.test.ts`. The session-seat button DOM is dual-channel
+> the same way: the actions (copy/branch) row was located by `[data-time-hover-root]`
+> on ≤ 0.1.1-rc.x and by `[data-actions-reveal]` on 0.1.2-alpha.2
+> (`ACTIONS_ROOT_SELECTOR` / `PENDING_SEAT_SELECTOR` in `src/client/portals.tsx`);
+> pinned by `tests/client-dom.test.ts`.
 
 ## Definition of "fully compatible" (invariants)
 
@@ -60,7 +65,7 @@
 - **session-title / goal fold**: a marker does not disturb `foldSessionTitle` / `foldGoal`.
 - **client ordering**: turn-tail ordering + `step/start` uniqueness hold for tool turns + marker logs.
 - **rewind across a compact checkpoint**: `RewindError('not-on-surface')` refuses cleanly, no crash.
-- **plan-mode**: `hasOpenTurn` pairs only `turn/start`/`turn/end`; a marker produces no `turn/start`, so a rewind during active plan is unaffected (static review confirmed).
+- **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.
 
 ## Known behavior boundaries (deterministic differences, non-crash, documented)
@@ -71,6 +76,7 @@
 - **Session title auto-regeneration**: the title derives from the surface, so an automatically-derived title may change after a rewind.
 - **Files written but uncommitted in a cancelled turn**: a `both` rewind cannot restore them (tool side-effect timing; same as Claude Code).
 - **Attachment files left after a message is shadowed**: attachment storage is not cleaned with the surface (`dsh-attachment-local` not installed, not automatically verified).
+- **Rewind leaves plan mode untouched**: `/plan text` is two independent actions (enter plan mode + steer the message). Rewinding the message undoes only the message — the log-only `plan/mode` state stays active, and the user leaves plan mode with `/plan off`, which still commits after a rewind (the marker creates no open turn). Pin: `verify-host` plan checks (`plan rewind leaves plan mode active`, `/plan off after rewind turns plan mode off`), `tests/hidden.test.ts` `messageTextAt`.
 
 ## Upstream (harness) issues and the plugin's no-compensation stance
 
@@ -161,7 +167,7 @@ new turn at `phase.turn + 1` (`agent.ts:251-255`) **without closing the leftover
 | resume / session-query replay | ✓ | — | ✓ | — | — | — | ✓ | — |
 | tool pipeline (snapshot/restore) | — | — | — | — | — | ✓ | — | ✓ |
 | client ordering | — | — | ✓ | — | — | — | ✓ | — |
-| plan-mode | — | — | — | — | — | — | — | ✓ (static) |
+| plan-mode | ✓ | — | ✓ | — | — | — | — | ✓ (static) |
 
 ✓ = probe passes; — = not applicable. RU-I18N and R-OPENSTEP are upstream issues the plugin
 does not compensate for (see above); G3 is a confirmed-non-defect behavior pinned in

package/docs/release/release.md

@@ -54,18 +54,18 @@ git push origin main --tags   # triggers .github/workflows/publish.yml
 
 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 rc tuple series
-(e.g. `^0.1.0-rc.6 || ^0.1.1-rc.2`), extended as DSH releases new tuples.
+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.
 - **Published-tuple check (optional)**: `node scripts/check-dsh-version.mjs`
-  compares the latest npm version against the tuples the peers cover (exit 0 =
-  nothing to do, exit 1 = update). It reads npm published versions only; a
-  newer-but-unpublished pre-release is a manual pre-release check — see the
-  "Before bumping" step above.
+  compares the `latest` dist-tag version against the tuples 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
+  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.

package/docs/release/release.zh.md

@@ -49,15 +49,16 @@ git push origin main --tags   # 触发 .github/workflows/publish.yml
 
 DSH 仍在 rc 阶段，npm 的 prerelease 匹配规则要求 peer 范围与宿主版本
 **同 `[major, minor, patch]` 元组**才能匹配。因此 peerDependencies 采用
-OR 并集覆盖 DSH 已发布的每个 rc 元组系列（如 `^0.1.0-rc.6 || ^0.1.1-rc.2`），
+OR 并集覆盖 DSH 已发布的每个元组系列（如 `^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2`），
 并随 DSH 发版追加。
 
 - **何时需要更新**：仅当 DSH 发布新元组（`0.1.1 → 0.1.2 → 0.2.x`）时；
   同元组内 rc 滚动（`0.1.1-rc.2 → rc.3`）无需动作。DSH 所有包同版本发布，
   `npm view @deepseek-ai/dsh version` 即权威信号。
-- **已发布元组检查（可选）**：`node scripts/check-dsh-version.mjs` 用 npm 最新版本
-  对比 peer 覆盖的元组（exit 0 无需动作，exit 1 需要）。它**只读 npm 已发布版本**；
-  更新的未发布 pre-release 走**手动发布前检查**——见上文"升版前手动确认"。
+- **已发布元组检查（可选）**：`node scripts/check-dsh-version.mjs` 用 npm `latest`
+  dist-tag 版本对比 peer 覆盖的元组（exit 0 无需动作，exit 1 需要）。它**只读
+  `latest` tag**；发布在其它 tag（如 `alpha`）的 pre-release 走**手动发布前检查**
+  ——见上文"升版前手动确认"。
 - **更新步骤**：给每个 `@deepseek-ai/dsh-*` peer 追加 `|| ^<新元组>-rc.<n>`
   → devDependencies 同步升到最新 → `npm install` → `npm run check` → 发版。
 - **正式版后收敛**：DSH 发布 final 版本后，正式版不受 prerelease 元组规则

package/lib/client.js

@@ -40,6 +40,18 @@ function chatSnapshotOf(face, chatView) {
   if (legacy !== void 0) return legacy;
   return chatView?.getSnapshot() ?? void 0;
 }
+function messageTextAt(chat, seq) {
+  if (chat === void 0) return void 0;
+  for (const key of chat.order) {
+    const node = chat.nodes.get(key);
+    if (node === void 0 || node.kind !== "user" && node.kind !== "steering") continue;
+    const data = node.data;
+    if (data.seq === seq) {
+      return data.content?.map((block) => block.type === "text" && typeof block.text === "string" ? block.text : "").join("");
+    }
+  }
+  return void 0;
+}
 function targetSeqOfArgs(args) {
   if (args === void 0 || args === null) return void 0;
   const match = args.match(/@(\d+)/);
@@ -677,18 +689,6 @@ function retractSpan(steering, targetId) {
 
 // src/client/portals.tsx
 var import_jsx_runtime = require("react/jsx-runtime");
-function userTextAt(chat, seq) {
-  if (chat === void 0) return void 0;
-  for (const key of chat.order) {
-    const node = chat.nodes.get(key);
-    if (node === void 0 || node.kind !== "user") continue;
-    const user = node.data;
-    if (user.seq === seq) {
-      return user.content.map((block) => block.type === "text" && typeof block.text === "string" ? block.text : "").join("");
-    }
-  }
-  return void 0;
-}
 function fillComposerTextarea(text) {
   const textarea = document.querySelector(COMPOSER_TEXTAREA_SELECTOR);
   if (textarea === null) return false;
@@ -750,7 +750,7 @@ async function runRewindAndFill(session, seq, mode, currentSessionId, chatOf, se
     return;
   }
   if (currentSessionId() !== session.sessionId) return;
-  const text = userTextAt(chatOf(session), seq);
+  const text = messageTextAt(chatOf(session), seq);
   if (text === void 0 || text === "") return;
   setComposerText(session.sessionId, text);
 }
@@ -776,8 +776,8 @@ var COMPOSER_TEXTAREA_SELECTOR = "[data-input-scroll] textarea, textarea[data-ph
 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]";
-var PENDING_SEAT_SELECTOR = "[data-pending-steering][data-time-hover-root]";
+var ACTIONS_ROOT_SELECTOR = "[data-time-hover-root], [data-actions-reveal]";
+var PENDING_SEAT_SELECTOR = "[data-pending-steering][data-time-hover-root], [data-pending-steering][data-actions-reveal]";
 function collectTargets(chat, hiddenSeqs) {
   const rows = /* @__PURE__ */ new Map();
   for (const element of document.querySelectorAll(USER_SEAT_SELECTOR)) {

package/lib/index.js

@@ -1,7 +1,7 @@
 // src/index.ts
 import { createAssistantMessage } from "@deepseek-ai/dsh-llm";
 import { unlink } from "node:fs/promises";
-import { settingsNamespace } from "@deepseek-ai/dsh-settings";
+import * as dshSettings from "@deepseek-ai/dsh-settings";
 
 // src/locales.ts
 var en = {
@@ -114,6 +114,12 @@ function translate(lang, key, params = {}) {
   return text;
 }
 
+// src/settings-locale.ts
+function readSettingsSection(provider, ns, brand) {
+  const key = brand?.(ns) ?? ns;
+  return provider.get(key);
+}
+
 // src/rewind.ts
 var RewindError = class extends Error {
   constructor(code, message) {
@@ -1887,7 +1893,11 @@ function apply(ctx, config) {
   const trackedBySession = /* @__PURE__ */ new Map();
   let fsService;
   ctx.inject(["settings"], (settingsCtx) => {
-    const section = settingsCtx.settings.get(settingsNamespace("locale"));
+    const section = readSettingsSection(
+      settingsCtx.settings,
+      "locale",
+      dshSettings.settingsNamespace
+    );
     if (section?.preference === "zh" || section?.preference === "en") {
       activeLocale = section.preference;
     }

package/lib/types/client/hidden.d.ts

@@ -41,6 +41,16 @@ export declare function chatSnapshotOf(face: {
 } | undefined, chatView: {
     getSnapshot(): unknown;
 } | undefined): HiddenChat | undefined;
+/**
+ * The plain text of the human message at `seq` in the chat snapshot, for
+ * filling the composer after a withdraw. Accepts BOTH `user` and `steering`
+ * nodes: a plan-mode (`/plan <text>`) input is delivered through the agent
+ * inbox next-step and claimed, so it renders as `steering`, and its text must
+ * still return to the composer (`portals.tsx` `runRewindAndFill`) — the old
+ * `user`-only read silently left it empty. State absent → undefined; a message
+ * with no text blocks → ''. Same text-blocks join the candidate side uses.
+ */
+export declare function messageTextAt(chat: HiddenChat | undefined, seq: number): string | undefined;
 /**
  * Extract the rewind target seq from a `/rewind` command's structured `args`
  * (e.g. `@5 chat`, `preview @5 both`). Locale-independent — never parses the

package/lib/types/client/portals.d.ts

@@ -80,6 +80,7 @@ export interface SlotsLike {
         readonly sessionId: string;
     }) => ReactNode): () => void;
 }
+/** Join the text blocks of a user message into one plain preview. */
 /**
  * The alpha.1+ session input facade's write face (structural, so the plugin
  * never imports the conversation UI package). `setDraft` replaces the whole

package/lib/types/settings-locale.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Version-neutral settings-namespace reading for the host half.
+ *
+ * DSH rc.2 exposes a `settingsNamespace(value)` brand helper, and `settings.get`
+ * is typed to require a branded `SettingsNamespace`. DSH 0.1.2-alpha.2 removed
+ * that helper (the `SettingsNamespace` *type* remains) and `settings.get`
+ * accepts the raw namespace string. This module collapses both into one runtime
+ * call: on rc.2 the brand is a compile-time marker erased at runtime (so
+ * `settingsNamespace(ns)` returns `ns`), on 0.1.2-alpha.2 the brand helper is
+ * absent and the raw `ns` string is used directly. That is what lets a single
+ * compiled host bundle link and run on both harness generations.
+ *
+ * @module dsh-rewind/settings-locale
+ */
+/** Minimal structural face of the settings provider the host reads from. */
+export interface SettingsProviderLike {
+    /**
+     * Read one registered settings section by namespace. Accepts whatever the
+     * running DSH generation passes: a branded `SettingsNamespace` (rc.2, brand
+     * erased) or the raw namespace string (0.1.2-alpha.2).
+     */
+    get(ns: string): unknown;
+}
+/** The `settingsNamespace(ns)` brand helper, or `undefined` when removed (0.1.2-alpha.2). */
+export type SettingsNamespaceBrand = ((value: string) => string) | undefined;
+/**
+ * Read one settings section keyed by `ns`, tolerant of the settings-namespace
+ * brand across DSH generations. Pass the brand helper when available (the rc.2
+ * path); it is `undefined` on 0.1.2-alpha.2, where the raw `ns` string is used
+ * directly. Never throws: an absent section simply returns `undefined`.
+ */
+export declare function readSettingsSection(provider: SettingsProviderLike, ns: string, brand: SettingsNamespaceBrand): unknown;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-rewind-plugin",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "DSH 插件：真正便捷无感的同窗口内对话回退，从不新建分支；自带轻量工作区备份，可一并还原文件（完整 Claude Code /rewind 语义）。 · DSH plugin: genuinely effortless in-window conversation rewind — never forking a new session; ships a lightweight workspace backup that restores files together with the rewind (full Claude Code /rewind semantics).",
   "keywords": [
     "deepseek-harness",
@@ -72,18 +72,18 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-client-locale": "^0.1.0-rc.6 || ^0.1.1-rc.2",
+    "@deepseek-ai/dsh-client-locale": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
     "@deepseek-ai/dsh-client-runtime": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-commands": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-commands": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-fs": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-home-paths": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-llm": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-sandbox": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-session": "^0.1.0-rc.6 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-settings": "^0.1.0-rc.8 || ^0.1.1-rc.2",
-    "@deepseek-ai/dsh-tools": "^0.1.0-rc.6 || ^0.1.1-rc.2"
+    "@deepseek-ai/dsh-client-ui-commands": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-client-ui-slots": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-commands": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-fs": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-home-paths": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-llm": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-sandbox": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-session": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-settings": "^0.1.0-rc.8 || ^0.1.1-rc.2 || ^0.1.2-alpha.2",
+    "@deepseek-ai/dsh-tools": "^0.1.0-rc.6 || ^0.1.1-rc.2 || ^0.1.2-alpha.2"
   },
   "peerDependenciesMeta": {
     "@deepseek-ai/cordis": {
@@ -142,6 +142,7 @@
     "@deepseek-ai/dsh-goal": "^0.1.1-rc.2",
     "@deepseek-ai/dsh-home-paths": "^0.1.1-rc.2",
     "@deepseek-ai/dsh-llm": "^0.1.1-rc.2",
+    "@deepseek-ai/dsh-plan-mode": "^0.1.1-rc.2",
     "@deepseek-ai/dsh-sandbox": "^0.1.1-rc.2",
     "@deepseek-ai/dsh-session": "^0.1.1-rc.2",
     "@deepseek-ai/dsh-session-projection": "^0.1.1-rc.2",