dsh-rewind-plugin 0.15.0-beta.2 → 0.15.1

package/README.md

@@ -187,7 +187,7 @@ node scripts/verify-host.mjs   # 端到端验证构建产物
 npm version patch && git push origin <branch> --tags
 ```
 
-一次性 npm 侧配置与完整流程：见 [docs/release/release.zh.md](docs/release/release.zh.md)。
+一次性 npm 侧配置与完整流程：见 [docs/release/release.md](docs/release/release.md)。
 
 ## 许可
 

package/lib/client.js

@@ -1320,7 +1320,7 @@ function createRewindBridge(deps) {
 }
 
 // src/client/build-info.ts
-var PLUGIN_VERSION = true ? "0.15.0-beta.2" : "dev";
+var PLUGIN_VERSION = true ? "0.15.1" : "dev";
 var PLUGIN_PACKAGE = "dsh-rewind-plugin";
 var BUILD_HASH = true ? "0582c3a6" : "dev";
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-rewind-plugin",
-  "version": "0.15.0-beta.2",
+  "version": "0.15.1",
   "description": "In-window conversation rewind with workspace file restore · 同窗口内对话回退并可还原工作区文件",
   "icon": "./assets/icon.svg",
   "keywords": [
@@ -43,11 +43,9 @@
     "README.md",
     "README.en.md",
     "SECURITY.md",
-    "CONTRIBUTING.md",
-    "docs",
-    "assets",
     "LICENSE",
-    "locale/*.json"
+    "locale/*.json",
+    "assets/icon.svg"
   ],
   "dsh": {
     "bundle": {
@@ -145,41 +143,41 @@
   "devDependencies": {
     "@deepseek-ai/cordis": "4.0.3",
     "@deepseek-ai/cosmokit": "1.8.4",
-    "@deepseek-ai/dsh-agent": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-api-session-controller": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-attachment": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-connection": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-locale": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-store": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-commands": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-conversation": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-input-trigger": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-plugin-manager": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-primitives": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-session": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-settings": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-client-ui-slots": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-command-compact": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-commands": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-compaction": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-compaction-basic": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-compaction-image-offload": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-fs": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-goal": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-home-paths": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-llm": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-plan-mode": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-sandbox": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-scope": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-session": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-session-projection": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-session-stats": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-session-title": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-settings": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-token-meter": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-tools": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-typert-protocol": "0.2.0-rc.2",
-    "@deepseek-ai/dsh-user-questions": "0.2.0-rc.2",
+    "@deepseek-ai/dsh-agent": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-api-session-controller": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-attachment": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-connection": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-locale": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-store": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-commands": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-input-trigger": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-plugin-manager": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-primitives": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-session": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-settings": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-client-ui-slots": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-command-compact": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-commands": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-compaction": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-compaction-basic": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-compaction-image-offload": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-fs": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-goal": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-home-paths": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-llm": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-plan-mode": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-sandbox": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-scope": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-session": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-session-projection": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-session-stats": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-session-title": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-settings": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-token-meter": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-tools": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-typert-protocol": "0.2.1-alpha.1",
+    "@deepseek-ai/dsh-user-questions": "0.2.1-alpha.1",
     "@deepseek-ai/schemastery": "3.18.4",
     "@types/node": "^24.0.0",
     "@types/react": "^18.3.31",

package/CONTRIBUTING.md

@@ -1,73 +0,0 @@
-# Contributing
-
-Thanks for considering a contribution to dsh-rewind. This file is short on
-purpose: the authoritative spec for how the repo works is `AGENTS.md` (read it
-first), and the docs live under `docs/` with an index in `docs/README.md`.
-
-## Project principles
-
-- **Focused on purpose** — one thing: in-window rewind to any earlier user
-  message, never forking a session.
-- **Security first** — session logs are append-only; file restores draw only from
-  the plugin's own backup directory. See `SECURITY.md`.
-- **Minimal** — avoid over-abstraction; keep the plugin light and maintainable.
-
-## Prerequisites
-
-- Node `^22.19.0 || >=24.0.0` (see `engines` in `package.json`), npm.
-
-## Setup and commands
-
-```sh
-npm install            # devDeps from the npm registry
-npm run build          # esbuild → lib/ (host ESM + client closure + types)
-npm run check          # one-shot full gate: typecheck + test + build + verify:host + pack --dry-run
-npm run typecheck      # tsc --noEmit (host / client / client-test)
-npm test               # vitest: unit + compatibility suites
-npm run verify:host    # end-to-end host verification (full check suite)
-```
-
-`prepare` runs the build, so `npm pack` / `npm publish` always carry a fresh
-`lib/` and `LICENSE`.
-
-## Before you open a PR
-
-- **Every change must pass** `npm run check`.
-- Commit messages use conventional commits with **English** subjects
-  (`feat` / `fix` / `docs` / `test` / `refactor` / `chore` / …). Code comments
-  are written in English.
-- Keep `rewind.ts` pure and `snapshot.ts` host-independent — if a change needs
-  I/O or harness types in the planning layer, that is a design smell.
-
-## Documentation rules
-
-- New/changed behavior that is durable (formats, contracts, compatibility
-  findings) must update the relevant doc in the same PR:
-  - **`docs/format.md`** — any change to the on-disk format (bump version,
-    migrate, or move the state root; no silent re-interpretation).
-  - **`docs/contract/client-contract.md`** — any change to the meaning of
-    `@<seq>` / `sourceEventSeq` / `data-dsh-rewind-hidden`; breaking a listed
-    stability tier is a minor/major version bump.
-  - **`docs/compat/audit.md`** — new compatibility findings (it is the single
-    source of truth; other docs link to it instead of restating).
-  - **`SECURITY.md`** — any change to the security model (trust boundary,
-    mutation gates, containment, crash handling).
-- Bilingual docs use the `.md` / `.zh.md` file split; keep the two mirrors in
-  sync.
-
-## Testing expectations
-
-- Pure planning (`rewind.ts`, `hidden.ts`) → unit tests in `tests/`.
-- Store behavior (`snapshot.ts`) → `tests/snapshot.test.ts` plus the focused
-  suites (`snapshot-bytes`, `snapshot-mode`, `downgrade-safety`,
-  `parent-guard`), and crash-safety scenarios in `tests/crash-safety.test.ts`
-  via the test-only `crash` seam (`RestoreRunOptions.crash`).
-- Harness interaction → the compatibility suites
-  (`compat-invariants` / `compat-interop` / `compat-gaps`) and
-  `scripts/verify-host.mjs`.
-
-## Releasing
-
-Releases are CI-driven via GitHub Actions Trusted Publishing (OIDC, no stored
-token): push a `v<version>` tag and CI publishes with Sigstore provenance. Full
-details: `docs/release/release.md`.

package/docs/README.md

@@ -1,33 +0,0 @@
-# Docs
-
-Documentation lives under `docs/`, organized by concern. Everything here is
-maintainer-facing unless the purpose column says otherwise. This file is the
-index/navigation entry point.
-
-## Index
-
-| Path | Purpose | Audience |
-| --- | --- | --- |
-| `architecture.md` | Module layering, rewind/checkpoint pipelines, compatibility strategy, roadmap | maintainers |
-| `format.md` | Durable on-disk format spec (checkpoint entries + restore journals) | maintainers |
-| `harness-reference.md` | DeepSeek Harness interface reference + plugin source layout | maintainers |
-| `snapshot-auto-cleanup.md` | Global snapshot auto-cleanup policy and command (`.zh` mirror) | users / maintainers |
-| `rewind-fix.md` | Historical guide for the removed `/dsh-rewind-fix` (`.zh` mirror) | users / maintainers |
-| `contract/client-contract.md` | Rewind visibility contract for third-party DOM plugins (`.zh` mirror) | integrators |
-| `compat/audit.md` | Compatibility audit: verified surfaces, recorded findings, probe matrix | maintainers |
-| `compat/tracking-boundary.md` | Which files a rewind restores: the tracking boundary (`.zh` mirror) | users / maintainers |
-| `compat/diagnostics.md` | Browser diagnostics (anomaly alerts; verbose switch gates the startup identity line) (`.zh` mirror) | users / maintainers |
-| `release/release.md` | Release workflow & DSH peer-version alignment (`.zh` mirror) | maintainers |
-
-Repo-root docs outside `docs/`: `SECURITY.md` (security model) and
-`CONTRIBUTING.md` (contribution guide).
-
-## Conventions
-
-- Bilingual docs use the `.md` / `.zh.md` file split (e.g. `contract/client-contract.md`
-  + `contract/client-contract.zh.md`); the root pair is the exception — `README.md` is
-  Chinese, `README.en.md` English.
-- `compat/audit.md` is the single source of truth for compatibility conclusions;
-  other docs link to it instead of restating them.
-- Cross-links are relative so the whole `docs/` directory stays relocatable — and it
-  ships intact in the npm tarball via the `docs` entry in `files` (`package.json`).

package/docs/architecture.md

@@ -1,145 +0,0 @@
-# Architecture
-
-How dsh-rewind is built: module layering, the rewind pipeline, the checkpoint
-pipeline, the compatibility strategy, and the roadmap. The module map lives in
-`AGENTS.md`; this document adds the wiring between the modules. The durable
-on-disk format is specified separately in
-`docs/format.md`, the security model in `SECURITY.md`.
-
-## Purpose
-
-One thing: rewind a conversation **in place** to any earlier user message —
-never forking a session or switching windows — with an optional Claude-Code-
-style workspace file restore (`both` mode). No network, no git operations, no
-credentials access.
-
-## Module layering
-
-The module map is the one in `AGENTS.md` (`Layout at a glance`); this document
-adds the wiring between the modules and does not repeat it.
-
-Two dependency rules keep the design testable:
-
-1. **`rewind.ts` is pure** — no I/O, no `Session` dependency; everything
-   derives from the event log + ordered surface, so the whole planning layer
-   is unit-testable without a host.
-2. **`snapshot.ts` is host-independent** — it talks to the disk through plain
-   `node:fs` plus injected seams (`DiskProbe`, `DeleteFile`, a test-only
-   `crash` hook), so the store is testable without the harness.
-
-The client never reads the DOM to derive rewind state; it consumes the host's
-machine channels (see [Compatibility strategy](#compatibility-strategy)).
-
-## Rewind pipeline
-
-```
-↶ button / /rewind @<seq> both
-  → handleRewind: parseRewindTarget + planRewind (target must be a
-    user/message currently on the surface)
-  → agent.cancel({ keepInbox: true }) if running; waitForAgentIdle
-  → dropPendingSteering (next-step inbox only; queued messages untouched)
-  → append the rewind marker = a user/message with surfaceOp
-    { op: 'replace', startSeq, endSeq } over every surface node after the
-    target (+ sourceEventSeqs = shadowed seqs)          [a single event]
-  → if mode 'both': store.restoreAfter(targetSeq) + syncRestoreObservations
-  → result text carries machine tokens (impact=<n>, restore:/delete: lines)
-  → client: hides withdrawn rows (data-dsh-rewind-hidden), refills composer
-    with the target message's text
-```
-
-Key invariants:
-
-- **The log is append-only.** The marker is the *only* mutation: it cuts the
-  model-visible surface, never the raw history (search/export still see it).
-- **The marker content is a constant `(empty message)` placeholder.** It carries
-  the dsh-rewind plugin source and is a `user/message`, the only surface type
-  that can cite the shadowed seqs (`sourceEventSeqs`) — `assistant/message` can
-  no longer carry them (v2). It derives to itself, so it stays as a present
-  user turn at the surface tail. The content is provider-independent and never
-  empty: the session log is immutable but the model serving a session may
-  change later, and a strict OpenAI-compatible gateway rejects an empty user
-  message (HTTP 400, Issue #21).
-- **No ghost step frame is needed**: the token-meter step machine ignores
-  `user/message`, and the session invariant imposes no open-turn requirement
-  on it, so the marker is appended while idle, outside any turn, as one event.
-- **Restore is reconciled against the live disk** (`planRestore`), so repeated
-  rewinds are idempotent and a rewind whose target state already matches is a
-  no-op. A path whose directory no longer resolves to its commit-time location
-  is skipped and reported, never written through (see `SECURITY.md`).
-
-### Marker format history
-
-The rewind marker is written as form C (a `user/message` with a
-`surfaceOp.replace` over the shadowed range, `sourceEventSeqs`, and the
-constant `(empty message)` content). Earlier
-plugin versions wrote shapes a newer harness no longer accepts:
-
-- **form A** — a bare `assistant/message(turn=N, step=0)` with no frame.
-- **form B** — a ghost turn frame: `[step/start][assistant/message][step/end]`
-  inside a closed turn.
-
-A/B became unreadable once v2 reserved surface `replace` to a node that cites
-`sourceEventSeqs` (`assistant/message` can no longer carry them). The
-`/dsh-rewind-fix` command rewrote form A/B in closed sessions to form C so a
-newer harness accepts the log — it was a **temporary migration tool** (kept on
-the `0.9.x` line) and is **removed in the `0.10.x` line**.
-
-## Checkpoint pipeline (Claude Code before-backup model)
-
-```
-tools/execute        captureBefore: for write / edit, stage a raw byte copy of
-                     the file's BEFORE state into the store's .pending/
-                     (node:fs copyFile, never through a string);
-                     subagent sessions are NOT tracked and get no rewind
-                     surface at all (Claude Code alignment — the Harness
-                     refuses generic Session RPCs for a subagent-owned
-                     identity, so /rewind cannot execute there).
-tools/post-execute   commitEntry: anchor = latest user/message seq; skip
-                     failed calls; publish the staged bytes as the entry's
-                     sidecar and write the metadata beside them — including
-                     where the directory resolved (`realpath`), the location
-                     pin a restore re-checks.
-session/event        user/message boundary: reconcileTracked re-reads every
-  (user/message)     tracked file and records a new before-backup for any
-                     whose disk state changed since last seen — external
-                     edits/deletions enter the record this way.
-prune                keeps the newest 100 anchor groups per session, storing
-                     identical before-content as in-place links that are
-                     materialized before their group is dropped, never dropping
-                     a group a non-terminal restore journal still references,
-                     and recycles terminal restore journals.
-pruneStale            cross-session auto-cleanup (default off): whole
-                     long-inactive session dirs past the cutoff are removed;
-                     the active session is never targeted (a subagent's tool
-                     result never triggers the sweep — it owns no dir and would
-                     claim that exemption).
-```
-
-## Compatibility strategy
-
-- **Peer ranges as one tuple per DSH line**: 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) and `package.json` is
-  the only place the current tuple is written down; `scripts/check-dsh-version.mjs`
-  flags when a new tuple arrives. See `docs/release/release.md`.
-- **Test-driven investigation**: `tests/compat-invariants.test.ts` /
-  `compat-interop.test.ts` / `compat-gaps.test.ts` probe harness behavior and pin findings in
-  `docs/compat/audit.md`; `scripts/verify-host.mjs` runs a real end-to-end
-  rewind + `/compact` chain (the full check suite).
-- **Stable machine channels for third parties**: `dsh-rewind-plugin/client`
-  exports the pure hidden-span computation; withdrawn rows carry
-  `data-dsh-rewind-hidden`; both are semver-protected
-  (`docs/contract/client-contract.md`). DOM coupling is minimized to a small
-  set of marked rows plus a structurally-typed slot registration.
-
-## Roadmap
-
-Ideas under consideration, not commitments:
-
-- **Multi-process identity/lock**: the current in-flight guard is
-  per-process; a cross-process exclusive lock (like the change-ledger
-  competitors) would cover multiple host processes on one worktree.
-- **Locale expansion**: client/host copy is zh/en today; the copy layer
-  (`src/locales.ts`, `src/client/locales.ts`) is already keyed for more.
-- **Composer re-send polish**: the target text is already refilled after a
-  rewind; a first-class "edit and re-send" affordance is a small extension.

package/docs/compat/audit.md

@@ -1,170 +0,0 @@
-# Compatibility audit (compat-audit)
-
-> Method: **the tests are the audit**. The probes in `tests/compat-invariants.test.ts`,
-> `tests/compat-interop.test.ts`, `tests/compat-gaps.test.ts`,
-> `tests/compat-tool-updates.test.ts` and
-> `scripts/verify-host.mjs` drive the plugin's real execution paths through the DSH
-> subsystems' **real consumer paths** (real `@deepseek-ai/*` packages) and assert
-> compatibility invariants. A probe failure is a finding; it enters the
-> fix/pin/record loop.
->
-> Targeted version: npm `@deepseek-ai/*@0.2.0-rc.2` (the peers declare the matching range).
-> Source reference: the upstream [github.com/deepseek-ai/deepseek-harness](https://github.com/deepseek-ai/deepseek-harness).
->
-> Version alignment: one peer tuple per DSH line, declaring only what was verified — the
-> model, the update steps, and the `check-dsh-version.mjs` signal live in
-> `docs/release/release.md`. The floor moved when a release changed interfaces inside the
-> tuple: `0.1.6-alpha.2` removed the client session-ownership and queue-mirror APIs, and
-> `0.1.7-alpha.1` moved the session writer to format v4 (producer-owned message sources,
-> tool-role results, `developer/message`) and replaced the settings namespace registry with
-> each entry's volatile `Config`, so the peer floor and both plugin seams moved with them.
-> The plugin targets a single DSH version line; compatibility with earlier lines is not kept.
-
-### Single channel
-
-The plugin targets one DSH channel. Each seam below reads the targeted
-version's shape only (no `Session.events` / `<textarea>` / face-`chat`
-legacy branch).
-
-| Seam | Implementation at the targeted version |
-| --- | --- |
-| Host session log | `session.snapshotEvents()` |
-| Client chat snapshot | `uiConversation` `chat` view (`chatSnapshotOf`) |
-| Client composer refill | `conversation.input.setDraft` facade |
-| Client settings card | entry form via `ctx.configForms.get(entryId)` (`plugins.bundle.config`) |
-| Client seat-button DOM | structural locate of the copy-`<button>` container (`actionsContainerOf`) |
-
-## Definition of "fully compatible" (invariants)
-
-| Invariant | Meaning | Probe location |
-|---|---|---|
-| I1 log replayability | A rewound log passes token-meter replay and `Session.create` (the resume-preflight validation) without throwing | `compat-invariants` I1, `verify-host` 12/13 |
-| I2 surface consistency | After a cut, the surface has no duplicate nodes, every node exists in the log, the withdrawn target never returns to the surface, and `deriveMessages()` is legal | `compat-invariants` I2 |
-| I3 step/turn structure | Client turn-tail ordering, unique `step/start` (real turns), no ghost turns; the `user/message` rewind marker adds no step frame | `compat-invariants` I3, `helpers.assertTurnTailOrdering` |
-| I4 fold-service safety | stats / title / goal / projection fold a marker-bearing log without throwing, with predictable values | `compat-invariants` I4 |
-| I5 compact interop | A tool-call orphaned by a cancelled turn is pair-balanced once shadowed by a rewind; a rewind across a compaction checkpoint is explicitly refused; a rewind-then-compact transaction stays legal | `compat-interop` I5, `verify-host` 12/14 |
-| I6 tool pipeline | before-snapshot capture/commit/restore is correct (existing `snapshot.test.ts` + `verify-host` 4–8) for the tracked tools `write` / `edit` — `str_replace_editor` is an optional DSH package that stopped being a default tool in DSH 0.1.3, so it is not tracked; cancellation timing never hangs | `verify-host` 4–9 |
-| I7 client ordering | A log carrying tool turns and rewind markers (a single `user/message` replace) satisfies the client builder ordering | `compat-interop` I7 |
-| I8 runtime safety | `rewind`/`compact` combinations never leave a dangling step/turn frame | `verify-host` 13 |
-| I9 tool-update projection | `0.1.7-rc.2` folds mid-conversation tool additions from the whole log while a rewind cuts only the surface: after a withdrawal no `tool-addition`/`tool-removal` block reaches the provider and the current declarations stay complete | `compat-tool-updates` I9 |
-
-## Verified-compatible surfaces (probes pass)
-
-- **compaction transactions**: `toolPairingBalancedBefore/After` stays balanced after a marker cut; the real `/compact` command (`command-compact` + `compaction-basic`, stub summarizer) can land `compaction/start…end` on top of a rewind marker and stay replayable; `/compact` is a legal no-op on a small surface.
-- **tool-update history (`0.1.7-rc.2`)**: `Session.toolHistory()` folds the full append-only log, so a withdrawn `tool-addition` stays recorded after a rewind; `projectToolUpdates` drops every update whose message left the request and falls back to the complete current declarations. Pin: `tests/compat-tool-updates.test.ts` (on-surface projection, then the post-rewind fallback).
-- **session-stats**: the `user/message` marker adds no step (the step count stays at the real turns' steps), no phantom turn.
-- **session-title / goal fold**: a marker does not disturb `foldSessionTitle` / `foldGoal`.
-- **plan-mode**: the marker is a turn-less `user/message` (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 (`0.1.7-alpha.1`)**: the card declares `configForms` as a module-level inject (the web profile always composes `ui-settings`), stages through the harness's own `SettingsFormModel` + `SettingsForm`, and registers into `plugins.bundle.config` keyed by the bundle package name; it reads that shared per-entry form's snapshot and writes through its revision-fenced `mutate`, disposing the model's subscription with the fiber. The host half declares the bundle's page policy (`configure({ auto: false }, ctx.fiber)` inside a `ctx.inject(['settings'])` child, per the dsh-settings README), opting the entry out of a client-built schema page. Pins: `verify:host` (`the bundle declares its own config page`), `tests/client-settings-card.test.ts` (staged plan, refusal, subscription release), `tests/client-lifecycle.test.ts`.
-- **client session ownership (`0.1.6-alpha.2`)**: `SessionListState.current` / `currentAddress` are gone; main-view ownership is read from the row's `retainedBy.mainView` label — what `ui-workspace` retains the open session with. Pin: `tests/client-refill.test.ts`.
-- **client pending input (`0.1.6-alpha.2`)**: `SessionSnapshot.queue` and the host `queue-mirror` are gone; pending steering rows come from the session's own `inbox` projection, and only USER-sourced `next-step` rows are retractable (the removed mapping was `source.kind === 'user' ? 'steering' : 'context'`). The rendered bubble also stays the client's own submission echo until the durable node arrives (`ChatView.pendingInputs` merges the Host occurrence into that echo by `rpcId`; `QueueDock` mirrors only `next-turn`), so the occurrence lands with NO DOM mutation — the portal refresh therefore follows the `inbox` face's own `subscribe` beside the DOM observer. An attachment-bearing row is identified by its message-attachment block (`data-message-attachments`) and matched by block count, not by rendered text (the block renders a file name or an image's loading label, which no inbox row reproduces); a missing attribute degrades to "no button". Pins: `tests/pending.test.ts`, `tests/client-retract.test.ts`, `tests/client-portal-refresh.test.ts`, `tests/client-dom.test.ts`.
-- **client settings slot (`0.1.6-alpha.2`)**: `settings.plugin.item` is gone; the configuration form registers into `plugins.bundle.config`, keyed by the bundle package name. Pin: `tests/client-contract.test.ts`.
-- **`agent/created` lifecycle guard**: the session-format reconcile runs on the alpha line's `agent/created` (fire-and-forget); pin: `verify-host` 4e dispatches it.
-- **marker vs `/compact`**: the checkpoint shape is unchanged on this line — a `user/message` replace (`surfaceOp {replace, startSeq, endSeq}` + `sourceEventSeqs`); `assistant/message` still cannot carry `sourceEventSeqs`.
-- **`image/offload` projection**: the alpha line's first `SessionMessageProjection` changes derived content without touching surface node membership; candidate listing and target resolution tolerate it. Pin: `tests/image-offload-projection.test.ts`.
-- **session-cwd**: the fs tools no longer canonicalize a parent-traversing cwd, so `src/session-cwd.ts` returns `header.cwd` verbatim. Pin: `tests/session-cwd.test.ts`.
-- **startup admission (`0.1.7-rc.1`)**: the gate reads the manifest's own `@deepseek-ai/dsh-*` peers and requires each to satisfy the runtime with `includePrerelease`; it runs for a profile bundle and again for every row its patch inserts, and a denial skips the bundle or disables the row. This plugin's declarations all satisfy the targeted version above, so it is admitted with no exemption — a skipped bundle on a later line is a peer mismatch, not a load failure.
-
-## Known behavior boundaries (deterministic differences, non-crash, documented)
-
-- **session-stats / session-telemetry fold the full log**: post-rewind stats do **not** rewind — `turns`/`steps`/`llmMs` still include withdrawn content; the `user/message` marker is folded as a present user turn (it adds no step). This is the intended "fold the full log" semantics, pinned by probe.
-- **token-meter usage anchor stays stable** (G3): the `user/message` marker carries no usage, but because it is not an `assistant/message`, the baseline anchor does not drop to a heuristic estimate — it stays `usage` across a rewind. Pinned by `compat-gaps` G3.
-- **marker content is the constant `(empty message)` placeholder**: never empty, because the session log is immutable but the model serving a session may change later — a strict OpenAI-compatible gateway rejects an empty user message (HTTP 400, Issue #21). The marker is a small visible user turn in derived history. Pin: `verify-host` (`marker is a user/message with the dsh-rewind producer source and the (empty message) placeholder`).
-- **marker shape (v4)**: the replace `surfaceOp` is `{ op: 'replace', startSeq, endSeq }` (renamed from `start`/`end` in session-format v3); the dsh-rewind source is the single producer-owned kind `{ kind: 'dsh-rewind' }`, declared by merging `MessageSourceMap` (v4 removed the catch-all `plugin` kind and rejects it on write). Two older shapes stay readable, because a stored marker is immutable: the released v3 wrapper `{ kind: 'plugin', plugin: 'dsh-rewind' }`, and the `plugin:dsh-rewind` form the v3→v4 conversion gives a producer its rename table does not know. The `user/message` + `sourceEventSeqs` shape and the `(empty message)` content are unchanged.
-- **Withdrawn content stays searchable/exportable**: session-query full-text and `/export` read the raw log; a rewind cuts only the surface, so withdrawn messages remain (declared in the README).
-- **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`.
-- **Bundle card metadata is declared by the plugin, not by the manager (`0.1.7-alpha.1`)**: the manager still titles a bundle with `shortName(pkg.name)` and its raw `package.json` description when nothing else is declared, but it now reads plugin-owned resources first — `locale/<lang>.json` (`meta.title`/`meta.description`) through the package exports map, and an `icon` file relative to the manifest. This plugin declares both, so its card shows an icon and copy that follows the active language; only the fallback description remains mixed-language. Pin: `tests/package-layout.test.ts` (icon path/media/size and both dictionaries).
-- **Synchronous Session history reads are deprecated** on this line (`snapshotEvents` / `eventAt` / `ownEvents`): existing calls may remain, new calls are prohibited. The plugin keeps its existing reads (turn anchor + candidate listing); the migration path is a `ctx.sessionProjections` projection unit or the async paged history read this line has not shipped yet — not a plugin-side index.
-- **A peer version range is never enforced at runtime**, and a physical copy nearer than the host still wins (upstream profile-resolution lookup order: "a peer version range is not an additional resolver filter"; "a nearer physical candidate wins"). So the `@deepseek-ai/schemastery` peer floor *is* the availability guarantee for `.volatile()` (#40): a plugin directory or linked checkout left holding an older copy (e.g. the pre-3.18.2 devDependency) shadows the host's 3.18.4 and fails the top-level `Config` evaluation before the plugin loads. Floor pinned at `^3.18.4`.
-
-## Upstream (harness) issues and the plugin's no-compensation stance
-
-The plugin treats these as harness-side defects it does not compensate for. Each entry records
-the harness issue, its current status, and the plugin's stance, so a future maintainer does not
-"fix the wrong direction."
-
-### RU-I18N (resolved on the 0.1.7 line): host command copy follows the user's language
-
-> **Status**: the `locale` settings section is gone — the locale host half only calls
-> `settings.configure({ auto: false })`, and the preference lives in the `locale` entry's own
-> Config. The plugin reads that value through the settings service's descriptor read
-> (`readHostLocale` in `src/index.ts` calls `settings.describe({ redactSecrets: true })`, the
-> route the settings UI and the client's own locale runtime take) at mount — which is what the
-> once-registered command descriptions carry — and again before each command renders, so the
-> output follows a language switch without a remount. The read is best-effort: a missing
-> method, a missing entry, or a throwing read stays on the neutral English default.
->
-> **Client-side command-description i18n is still first-party-only**: DSH localizes host
-> command descriptions through the client `locale` binding (`ui-commands`), but the
-> description keys come from a **closed allowlist** (`HOST_FACES`: compact, export, feedback,
-> goal, permission, plan). A command outside that set — every third-party plugin — is passed
-> through verbatim, and no host command *output* is localized by the harness for anyone. This
-> plugin's host dictionary is what carries both, in the language read above.
->
-> **Plugin stance**: no compensation; the seam is the descriptor read above. The wrong direction
-> is the earlier one — reading `settings.get('locale').preference` once inside an
-> `ctx.inject(['settings'])` callback and assuming cordis ordered the locale section before it
-> (it does not; the descriptors were baked in the English default, defect #28).
-
-### R-OPENSTEP (rewind part resolved): an unclosed `step` in the log breaks token-meter replay
-
-> **Status**: resolved upstream — DSH auto-closes crash-left step/turn/tool boundaries at load
-> (`interruptedTurnClosers`, consumed by the agent-loop's `resumeWith` cold read). A leftover
-> unclosed step can still come from a third-party plugin appending `step/start` through the public
-> `Session.append`, or from a hand-edited log; when it does, replay rejects later step activity, so
-> `/compact` fails and automatic compaction silently stays disabled. Rewind's part: the marker is a
-> `user/message` and appends no `step/start`, so the rewind amplifier is closed.
->
-> **Plugin stance**: no guard. A `hasOpenStep` + `planRewind` pre-refusal was implemented and
-> misjudged on **real session logs** (normal rewinds refused, GUI verification broken), so it was
-> reverted — do not re-attempt a plugin-side pre-refusal. The fix direction is upstream (token-meter
-> recovery for unclosed steps), and the residual risk is accepted: that log is already abnormal.
-
-### R-PROMPTCARD (resolved on the 0.1.7 line): the repeated `System prompt` card is filtered out of chat
-
-> **Status**: `isVisibleChatNode`
-> (`packages/client/ui-chat/src/client/contract/chat-visibility.ts`) drops `system-prompt`
-> nodes — and the `permission` command — from the visible chat rows before the row is built,
-> so a rewind on this line adds no prompt row at all; the durable events and the trajectory
-> inspection keep them. #22, #31 and the (now removed) repeated `System prompt` card known issue
-> no longer reproduce.
->
-> **Plugin stance**: still no compensation. The DOM row-hiding seam (`hiddenSeqsOf`) covers
-> withdrawn messages, where hiding is essential, not cosmetic.
-
-### R-PANELKEYS: the panel keyboard stays the plugin's own
-
-> **Situation**: on Web, Escape, Tab, the four arrows, and Enter without Alt are
-> platform-reserved. The predicate is exported (`bindingIssue` from
-> `@deepseek-ai/dsh-client-shortcuts/protocol`), but a reserved binding is still refused, so
-> neither a plugin nor a user may bind them. `Menu`
-> is the dropdown primitive, while the harness's command-option panel (`ui-commands`'
-> popupSelect) renders `MenuSurface` plus its own controller with `role="listbox"`/
-> `role="option"`. `ui-commands`' `settle()` also calls `focusComposer()` unconditionally
-> after `await onSelect(...)`; its only early return requires replacing the popup binding,
-> which needs the internal `segment` that business code cannot reach.
->
-> **Decision**: the mode-selection and retract panels keep their own capture-phase
-> Escape/↑/↓ handling — focus-independent, the shape the official command panel uses — and
-> keep `role="dialog"`. The plugin neither renders `Menu` nor compensates the composer focus
-> restore. Capture ownership is pinned by `tests/client-popover.test.ts`; the ghost-row walk
-> exclusion is **not** pinned, and on the typed `/rewind` path Enter still needs a row to hold
-> focus after the shell's focus restore.
-
-## Uncovered boundaries (need an additional e2e layer; non-blocking)
-
-- Real LLM streaming and auto title generation (L2 stubbed).
-- Real SQLite index lifetime (`dsh-session-query-sqlite` not installed; native deps).
-- Actual browser rendering replay (the client contract's logic layer is covered by `client-contract.test.ts`).
-- Real JSONL persistence round-trip (`dsh-session-persistence-jsonl` depends on native `koffi`; the round-trip validates the harness's own zstd/JSON codec, the plugin is not party to it, not worth the cost, not installed).
-- `session-reference`'s `SessionReferenceResolver.prepare` needs a full session-query service; its data base (current-surface projection) is already covered by the G1 probe (`foldSurface`).
-- telemetry pipeline (`dsh-session-telemetry-otel`) and the attachment provider (`dsh-attachment-local`).
-- Running workflow/jobs cancelled by a rewind: the tool contract requires observing `exec.signal` and settling (`packages/core/tools/src/index.ts`); a rewind triggers the harness's standard cancel, not plugin-specific — statically confirmed, real workflows untested.
-
-Statuses and stances for the named findings live in the sections above; G1 (surface classification
-via `foldSurface`), G2 (projection checkpoint) and G3 (the confirmed-non-defect usage anchor on
-token-meter) all pass in `compat-gaps.test.ts`.