dsh-rewind-plugin 0.13.0-alpha.1 → 0.14.0-alpha.1

package/CONTRIBUTING.md

@@ -8,7 +8,7 @@ first), and the docs live under `docs/` with an index in `docs/README.md`.
 
 - **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 stay inside
+- **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.
 

package/SECURITY.md

@@ -90,7 +90,7 @@ transcript.
 
 ## Filesystem containment
 
-- **Store root**: `<harness home>/rewind-snapshots/` by default (resolved via
+- **Store root**: `<dsh 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. Deleting it only
   removes file backups and the store rebuilds from scratch.
@@ -128,9 +128,9 @@ transcript.
   bounded by the cap plus the number of unresolved journals (the exact cap is
   pinned in `docs/format.md`). Across sessions, the opt-in `pruneStale` sweep
   removes whole **long-inactive** session directories (measured by the newest
-  member being idle past `maxAgeDays`); it uses `lstat` (no symlink following),
-  skips dot-prefixed temp files, and never targets the active session
-  (`keepActiveId`).
+  member being idle past the configured `autoCleanupMaxAgeDays`); it uses
+  `lstat` (no symlink following), skips dot-prefixed temp files, and never
+  targets the active session (`keepActiveId`).
 
 ## Crash safety
 

package/assets/icon.svg

@@ -0,0 +1,24 @@
+<svg width="36" height="36" viewBox="0 0 36 36" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <!-- Layout follows the terminal card glyph (packages/client/ui-sidebar-terminal):
+       a rounded tile inset from the canvas (28/36 here, 22/28 there) with a
+       white round-capped prompt. The fill follows the Subagent plugin artwork
+       (packages/client/ui-primitives/src/plugin-artwork.tsx), whose blue square
+       carries the same vertical light-to-dark gradient: #69B9FF at the top,
+       #324DE2 at the bottom.
+       The rewind mark is the in-app back-arrow (src/client/styles.ts, 16-unit
+       grid) scaled 1.4x. Its ink box including the 0.75 stroke reaches
+       (1.75,1.75)-(14.25,12.75) on that grid, so the translate lands its centre
+       on the tile centre (18,18), and the ink spans 62.5% of the tile width —
+       the terminal glyph's own ratio. -->
+  <rect x="4" y="4" width="28" height="28" rx="8" fill="url(#rewind_blue)" />
+  <g transform="translate(6.8 7.85) scale(1.4)" stroke="#FFFFFF" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round">
+    <path d="M6.5 2.5 2.5 6.5l4 4" />
+    <path d="M2.5 6.5h7a4 4 0 0 1 4 4v1.5" />
+  </g>
+  <defs>
+    <linearGradient id="rewind_blue" x1="18" y1="4" x2="18" y2="32" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#69B9FF" />
+      <stop offset="1" stop-color="#324DE2" />
+    </linearGradient>
+  </defs>
+</svg>

package/docs/README.md

@@ -12,7 +12,7 @@ index/navigation entry point.
 | `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` | Migrate old rewind markers (A/B→C) with `/dsh-rewind-fix` (`.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 |

package/docs/architecture.md

@@ -134,13 +134,13 @@ pruneStale            cross-session auto-cleanup (default off): whole
 
 ## Compatibility strategy
 
-- **Peer ranges as one tuple per DSH line** (`^0.1.2-rc.1`): npm's prerelease
+- **Peer ranges as one tuple per DSH line** (`^0.1.6-alpha.2`): 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
+- **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`

package/docs/compat/audit.md

@@ -7,7 +7,7 @@
 > compatibility invariants. A probe failure is a finding; it enters the
 > fix/pin/record loop.
 >
-> Targeted version: npm `@deepseek-ai/*@0.1.6-alpha.1` (the range the peers and `dsh.engines.dsh` declare).
+> Targeted version: npm `@deepseek-ai/*@0.1.7-alpha.1` (the range the peers and `dsh.engines.dsh` declare).
 > Source reference: the upstream [github.com/deepseek-ai/deepseek-harness](https://github.com/deepseek-ai/deepseek-harness).
 >
 > Version alignment: `peerDependencies` use one tuple per DSH line
@@ -15,7 +15,12 @@
 > share the range comparator's `[major, minor, patch]` tuple, so a new DSH tuple
 > replaces the peer tuple (single-line model). The range is conservative — it
 > declares only what was verified, so a release already inside it changes
-> nothing. Signal: `npm view @deepseek-ai/dsh dist-tags`;
+> nothing — unless it changes 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. Signal: `npm view @deepseek-ai/dsh dist-tags`;
 > flow: `scripts/check-dsh-version.mjs` (it reads the `latest` dist-tag only; a
 > prerelease published under another tag is a manual pre-release check).
 >
@@ -33,7 +38,7 @@ legacy branch).
 | 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 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)
@@ -45,9 +50,9 @@ legacy branch).
 | 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–8, 15 |
+| 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` 15 |
+| I8 runtime safety | `rewind`/`compact` combinations never leave a dangling step/turn frame | `verify-host` 13 |
 
 ## Verified-compatible surfaces (probes pass)
 
@@ -60,7 +65,11 @@ legacy branch).
 - **rewind across a compact checkpoint**: `RewindError('not-on-surface')` refuses cleanly, no crash.
 - **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 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.
+- **settings-card registration (`0.1.7-alpha.1`)**: `settingsScope` is gone with the namespace registry. 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 the entry's form snapshot and writes through its revision-fenced `mutate`, and disposes the model's subscription with the fiber.
+- **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'`). Pins: `tests/pending.test.ts`, `tests/client-retract.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`.
+- **client settings form (`0.1.7-alpha.1`)**: the same release retired the `settingsScope` bind (namespace registry) in favour of the shared per-entry form; the card now reads that form's snapshot and stages edits through `mutate`. Pin: `tests/client-settings-card.test.ts` (staged plan, refusal, and the fiber releasing the model's subscription), `tests/client-lifecycle.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`.
@@ -71,13 +80,14 @@ legacy branch).
 
 - **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 plugin source and the (empty message) placeholder`).
-- **marker shape (v3)**: the replace `surfaceOp` is `{ op: 'replace', startSeq, endSeq }` (renamed from `start`/`end` in session-format v3); the dsh-rewind source is the plain CLOSED third-party plugin shape `{ kind: 'plugin', plugin: 'dsh-rewind' }` (no private field — the released-format source validator rejects any member outside `kind`/`plugin` + the context-injection `form`/`sections`/`summary`, and a plugin extends the source map by adding a `kind`, not fields); the `user/message` + `sourceEventSeqs` shape and the `(empty message)` content are unchanged.
+- **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. Not migrated in this release.
 
@@ -85,46 +95,43 @@ legacy branch).
 
 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: host-side locale preference is not reliably readable at command registration (harness-side structural timing defect; plugin reads once, never retries)
+### RU-I18N (resolved on the 0.1.7 line): host command copy follows the user's language
 
-- **Root cause (harness-side)**: the plugin resolves `activeLocale` in an
-  `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'])`**
+- **History (0.1.2–0.1.6 lines)**: the plugin resolved `activeLocale` in an
+  `ctx.inject(['settings'])` callback that read `settings.get('locale').preference`
+  **once, with no retry** (`src/index.ts`), while `dsh-client-locale`'s host half registered that
+  `locale` settings section through its own `ctx.inject(['settings'])`
   (`packages/client/locale/src/index.ts`). Both callbacks wait only on `settings` and are
-  independent of each other, so cordis makes **no ordering guarantee** between the
-  section registration and the plugin's read.
-- **Observed failure**: a probe confirmed that when the plugin's read runs, `settings.get('locale')`
-  returns `undefined` (the section is not yet registered), so `activeLocale` stays at the
-  default `'en'` and — because the read is one-shot — is never corrected. The result is that
-  **all host-side `t()` output (runtime messages and command descriptions alike) renders in
-  English**, regardless of the user's language preference.
-- **Not a user-config problem**: `settings.yaml` correctly carries `locale.preference: zh`;
-  reading it directly works. The defect is purely the host-side read racing the section
-  registration.
-- **Plugin stance**: no compensation. The plugin does not add a lazy re-read, a retry loop, or a
-  post-locale description re-registration as a workaround, because the guarantee belongs to the
-  harness (make the locale preference available before plugin registration, or support per-locale
-  command descriptions). The plugin's `t()` design is retained; localized host output is treated
-  as an upstream capability to be restored when the harness provides it. (This is still not a
-  plugin deviation: the client localizes only the six first-party descriptions in
-  `HOST_DESCRIPTION_KEYS` — compact, export, feedback, goal, permission, plan — while every
-  third-party description, this plugin's included, passes through verbatim.)
-- **Client-side command-description i18n is first-party-only**: DSH also localizes host command
+  independent of each other, so cordis made **no ordering guarantee** between the section
+  registration and the plugin's read. The plugin's own command descriptors were registered
+  **synchronously** in the same `apply`, i.e. before that microtask ran, so their `description`
+  strings were baked in the neutral English default — the defect reported as #28 — while the
+  runtime output, evaluated later at command execution from the then-updated `activeLocale`, did
+  follow the stored preference. A preference changed *after* the mount reached the output only on
+  the next mount, because the read was one-shot.
+- **Resolution (0.1.7)**: the section is gone — the locale host half now only calls
+  `settings.configure({ auto: false })`, and the preference lives in the `locale` entry's own
+  Config. The plugin reads that same 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 descriptors keep the mount-time language until
+  the plugin remounts). 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_DESCRIPTION_KEYS`: compact, export, feedback, goal,
+  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, never translated (`hostDescription` only rewrites a description that equals the
-  first-party English copy). So the plugin's own `/rewind` command description can never ride this
-  channel either; it is authored in the host's tongue (English by default), same as the host
-  runtime copy above.
+  verbatim, never translated (`builtinRowFace` only rewrites a description that equals the
+  first-party English copy), 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.
 
 ### R-OPENSTEP (rewind part resolved): an unclosed `step` in the log breaks token-meter replay; the rewind no longer compounds it
 
 > **Root cause (harness-side)**: an unclosed step left by a crash makes token-meter replay
 > reject any later step activity. DSH `0.1.1-rc.2` now auto-closes crash-left step/turn/tool
 > boundaries at load via `interruptedTurnClosers` (`dsh-session`, consumed by
-> `session-persistence/src/coordinator.ts`) — **the crash path is fixed**.
+> `packages/core/agent-loop/src/index.ts:907`) — **the crash path is fixed**.
 >
 > **Plugin guard (attempted and reverted)**: a `hasOpenStep` + `planRewind` pre-refusal was
 > implemented (`open-step`) but misjudged on **real session logs** (normal rewinds refused, GUI
@@ -135,19 +142,19 @@ The plugin treats these as harness-side defects it does not compensate for. Each
 
 #### Concrete `step/start` trigger paths (source-confirmed)
 
-The tree has exactly **one** `append('step/start')` producer: `packages/core/agent-loop/src/agent.ts:279`
+The tree has exactly **one** `append('step/start')` producer: `packages/core/agent-loop/src/agent.ts:303`
 (no other producer inside the official packages; `session/end-seed` etc. only truncate torn writes,
 not logically-unclosed steps).
 
 | # | Trigger path | Plausibility | Basis |
 |---|---|---|---|
-| P1 | **Abnormal process termination**: `step/start` is batched to disk (write-behind, `maxDelayMs` per batch) → the step is mid-execution (LLM stream/tool, seconds to minutes) → SIGKILL / OOM-kill / power loss / WSL hard-close → `step/end` (in `finally`, only runs while the process is alive) is never persisted | **Most realistic** | `agent.ts:292` finally; write-behind batching; torn-write fix truncates only a half-written line |
+| P1 | **Abnormal process termination**: `step/start` is batched to disk (write-behind, `maxDelayMs` per batch) → the step is mid-execution (LLM stream/tool, seconds to minutes) → SIGKILL / OOM-kill / power loss / WSL hard-close → `step/end` (in `finally`, only runs while the process is alive) is never persisted | **Most realistic** | `agent.ts:313` finally; write-behind batching; torn-write fix truncates only a half-written line |
 | P2 | **Third-party plugin bug**: only the official agent-loop produces one, but external plugins may `session.append('step/start', …)` and never close it | possible | public `Session.append` |
 | P3 | **Manual session-file editing**: edit `~/.dsh/…/session.jsonl[.zstd]` (zstd needs decompress/recompress; plaintext config edits directly) | possible but laborious | `persistence-jsonl/format.ts` (`JsonlCompression = 'zstd' \| 'none'`) |
-| P4 | **append itself failing**: `append('step/end')` in `finally` throws (payload is plain numbers, nearly impossible) | theoretical | `agent.ts:292` |
+| P4 | **append itself failing**: `append('step/end')` in `finally` throws (payload is plain numbers, nearly impossible) | theoretical | `agent.ts:313` |
 
 **Amplifier (rewind is not the only trigger)**: after a crash resume, agent-loop `turn()` opens a
-new turn at `phase.turn + 1` (`agent.ts:251-255`) **without closing the leftover step** — so
+new turn at `phase.turn + 1` (`agent.ts:277-283`) **without closing the leftover step** — so
 "continue the conversation" (a new `step/start`) trips the same token-meter check. Scope:
 
 - **The conversation itself is unaffected** (the request path does not call `tokenMeter.measure`; only compaction-basic does tree-wide).
@@ -155,6 +162,34 @@ new turn at `phase.turn + 1` (`agent.ts:251-255`) **without closing the leftover
 - **Automatic compaction silently stays disabled** (the `agent/pre-step` hook catches and warns; the conversation continues).
 - **rewind's role (resolved)**: the v2 `user/message` rewind marker appends no `step/start`, so a rewind no longer introduces the first trip-wire and the R-OPENSTEP rewind amplifier is closed. The harness-side root cause (an unclosed step after a crash, tripped by continuing the conversation) remains.
 
+### R-PROMPTCARD (resolved on the 0.1.7 line): the repeated `System prompt` card is filtered out of chat
+
+> **History (0.1.2–0.1.6 lines)**: Chat rendered a collapsed `System prompt`
+> card at every request-series start. Any surface mutation bumps `contentGeneration` (a positional
+> `replace` — rewind, `/compact` — or a `SessionMessageProjection`, e.g. image offload), so the next
+> request logs `request/header { reason: 'series' }`; a process restart logs `'resume'`. The client
+> shows the card for every reason except `'change'`. The effective prompt is unchanged — only the
+> card repeats. Triggers beyond rewind: `/compact`, restart/resume, projections, explicit
+> `startsSeries`.
+>
+> **Upstream decision (deliberate, twice)**: `6ad01cbd8d` suppressed the repeat on `resume` (note
+> `2026-09-03-resume-headers-do-not-repeat-system-prompts.md`, rejecting the card as a "lifecycle
+> marker" that "incorrectly implies another prompt injection"); three days later `77b6b10c21`
+> restored it — a resume/series header starts a visible request series. Locked by the `ui-chat` test
+> `repeats an unchanged system prompt after a surface rewrite…`.
+>
+> **Resolution (0.1.7)**: upstream stopped rendering the card in chat at all. `isVisibleChatNode`
+> (`packages/client/ui-chat/src/client/contract/chat-visibility.ts`, added by `b6f99fad55`
+> "feat(ui-chat): filter system prompts and permission commands") drops `system-prompt` nodes — and
+> the `permission` command — from the visible chat rows, while the durable events and the trajectory
+> inspection keep them. The `showsPrompt` computation is unchanged and no longer matters: the node is
+> filtered before the row is built, so a rewind on this line adds no prompt row at all. #22, #31 and
+> README known issue #4 no longer reproduce.
+>
+> **Plugin stance**: still no compensation. The DOM row-hiding seam (`hiddenSeqsOf`) covers withdrawn
+> messages, where hiding is essential, not cosmetic; nothing was added for the card, and the
+> display-layer workup above stays valid history.
+
 ## Uncovered boundaries (need an additional e2e layer; non-blocking)
 
 - Real LLM streaming and auto title generation (L2 stubbed).
@@ -180,7 +215,8 @@ new turn at `phase.turn + 1` (`agent.ts:251-255`) **without closing the leftover
 | client ordering | — | — | ✓ | — | — | — | ✓ | — |
 | 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
+✓ = probe passes; — = not applicable. RU-I18N and R-PROMPTCARD are resolved on the 0.1.7 line (see
+above); R-OPENSTEP is an upstream issue the
+plugin does not compensate for (see above); G3 is a confirmed-non-defect behavior pinned in
 `compat-gaps.test.ts` (G1 surface classification via `foldSurface` and G2 projection checkpoint
 both pass).

package/docs/compat/diagnostics.md

@@ -35,6 +35,7 @@ console filter:
 | `refill` | The composer refill after a rewind (command/wait/refill throws, a rejected or unmatched command, an outcome that never settles) |
 | `preview` | The `/rewind preview` impact probe behind the mode popover (command rejected/unmatched/threw, an outcome that never settles) |
 | `portals` | Per-message button mount issues (e.g. no session binding) |
+| `retract` | The pending-steering retract path (the remove lost the race, or the remove threw) |
 | `settings` | The snapshot-cleanup settings card |
 | `hiding` | **Reserved** — no active alert at present. If a future row-hiding diagnostic is added, it belongs in this region. |
 

package/docs/compat/diagnostics.zh.md

@@ -25,6 +25,7 @@
 | `refill` | 回退后的输入框回填（命令/等待/回填抛出异常、命令被拒绝或未匹配、等待的结果始终未落定） |
 | `preview` | 模式气泡背后的 `/rewind preview` 影响探测（命令被拒绝/未匹配/抛出异常、等待的结果始终未落定） |
 | `portals` | 每条消息按钮的挂载问题（如无会话绑定） |
+| `retract` | 插话撤回路径（remove 竞争失败，或 remove 抛错） |
 | `settings` | 快照清理设置卡片 |
 | `hiding` | **保留区**——当前无活跃告警。若未来新增行隐藏诊断，应归属此区域。 |
 

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 = uiConversation.binding(sessionId).target('chat')?.getSnapshot() // the 0.1.2-rc.1 "chat" view
+const chat = uiConversation.binding(sessionId).target('chat')?.getSnapshot() // the `uiConversation` "chat" view
 const hidden = hiddenSeqsOf(chat as HiddenChat) // Set<number> of anchor seqs
 ```
 
@@ -35,7 +35,9 @@ dsh-chat-timeline#6).
 ## DOM attribute
 
 Each withdrawn row carries `data-dsh-rewind-hidden="true"` while hidden,
-removed on un-hide. Contract:
+removed on un-hide. The same attribute also lands on a step/process GROUP shell
+— the view container around a turn's process rows, which is not itself a message
+— when every member it holds is withdrawn. Contract:
 
 - The **attribute name** is stable; treat the value as opaque.
 - It is **observational only** — rewind hides via `style.display`; the

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

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

package/docs/format.md

@@ -7,7 +7,7 @@ and this spec disagree, the code wins and this spec is a bug.
 
 ## State root
 
-The store root defaults to `<harness home>/rewind-snapshots/` — the dsh data
+The store root defaults to `<dsh home>/rewind-snapshots/` — the dsh data
 directory (`~/.dsh/rewind-snapshots/` when `DSH_HOME` is unset) — overridable in
 order by the `snapshotDir` plugin config, then the `DSH_REWIND_SNAPSHOT_DIR`
 environment variable. It is a sibling of the workspace, never a subtree of it.
@@ -46,7 +46,7 @@ Deleting the root only removes file backups; the store rebuilds from scratch.
 - `store` is the session's store-format marker (a decimal version, written
   atomically); a missing marker means the released v1 string format. `format` is
   the DSH **session**-format marker the snapshots were anchored under (see
-  `docs/snapshot-auto-cleanup.md`) — the two are independent.
+  `SECURITY.md`) — the two are independent.
 
 ## Checkpoint entry
 
@@ -261,10 +261,11 @@ migration tool. Old-format data is never silently re-interpreted.
 
 ## Cleanup policy persistence
 
-The snapshot auto-cleanup policy (the `enabled` switch and the `maxAgeDays`
-idle cutoff) is no longer a file: it lives in the **dsh-settings document** under
-the `dsh-rewind-snapshot-cleanup` namespace (validated by a schemastery schema;
-defaults are the `base` layer). The policy was previously persisted in a legacy
-`<dsh home>/snapshot-cleanup.json` file; that file store and its one-time
-startup migration have been removed. The last-sweep clock stays in its own
-`<dsh home>/snapshot-cleanup-last-sweep.json` state file, which is unchanged.
+The snapshot auto-cleanup policy (the `autoCleanupEnabled` switch and the
+`autoCleanupMaxAgeDays` idle cutoff) is no longer a file: it is this plugin
+entry's own live configuration (both fields declared `.volatile()`, validated by
+the entry's schemastery `Config` schema, defaults on the schema). The policy was
+previously persisted in a legacy `<dsh home>/snapshot-cleanup.json` file; that
+file store and its one-time startup migration have been removed. The last-sweep
+clock stays in its own `<dsh home>/snapshot-cleanup-last-sweep.json` state file,
+which is unchanged.

package/docs/harness-reference.md

@@ -37,8 +37,8 @@ Also under `docs/` at the repo root: `persistence-catalog.md` (full
 | `CommandDefinition`, `CommandInvocation` | [packages/interaction/commands/src/index.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/interaction/commands/src/index.ts) |
 | `Agent` (`status` / `session`) | [packages/core/agent/src/runtime-types.ts](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/core/agent/src/runtime-types.ts) |
 | `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 DOM anchors (`data-chat-flow-kind` / `data-chat-anchor-key`) | [packages/client/ui-chat/src/client/chat/ChatNodeSeat.tsx](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/ui-chat/src/client/chat/ChatNodeSeat.tsx) |
+| User bubble rendering | [packages/client/ui-chat/src/client/chat/MessageItem.tsx](https://github.com/deepseek-ai/deepseek-harness/blob/main/packages/client/ui-chat/src/client/chat/MessageItem.tsx) |
 | 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) |
 
@@ -61,7 +61,9 @@ src/client/index.ts     client plugin: /rewind command decoration + per-message
 src/client/popover.ts   mode-selection popover (both-mode impact confirm)
 src/client/hidden.ts    withdrawn-span computation (hiddenSeqsOf), pure
 src/client/candidates.ts  rewind candidate listing (rewindCandidatesOf), pure
-src/client/pending.ts   pending-steering bubble ↔ queue-mirror matching, pure
+src/client/pending.ts   pending-steering bubble ↔ inbox next-step (user-sourced) matching, pure
+src/client/portals.tsx  per-user-message ↶ button portals (React bridge into the actions row)
+src/client/settings-card.tsx  snapshot-cleanup form on the bundle page (plugins.bundle.config)
 src/client/locales.ts   zh / en copy (LocaleNamespaceMap)
 src/client/styles.ts    injected styles (dsh design tokens)
 src/client/build-info.ts  client build identity (__DSH_REWIND_VERSION__ / __DSH_REWIND_BUILD__)
@@ -70,6 +72,7 @@ scripts/build.mjs       esbuild: lib/index.js (host ESM) + lib/client.js (loader
 scripts/check-dsh-version.mjs  DSH peer-tuple check (latest dist-tag vs peers)
 scripts/update-badge.mjs       regenerate the tests badge (CI only)
 scripts/verify-host.mjs end-to-end host verification (full check suite)
+scripts/session-decode.mjs / session-encode.mjs  `.jsonl.zstd` codec (test fixtures)
 tests/                  vitest suites (rewind / snapshot / hidden / session-cwd / integration)
 docs/                   maintainer docs: contract/, compat/, release/ subdirectories
 assets/screenshots/     UI screenshots

package/docs/release/release.md

@@ -43,9 +43,9 @@ 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` |
+| Stable patch (current line) | `release/<line>.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` |
+| Stable (next line) | `main` | `npm version <next>` | `latest` |
 
 Each release is `git push <branch>` followed by `git push <branch> --tags`.
 
@@ -79,7 +79,9 @@ outside it.
 
 - **When to update**: when the verified range changes — a new DSH tuple, or a
   deliberate narrowing (e.g. dropping the internal `alpha` series); a release
-  already inside the range changes nothing. All `@deepseek-ai/*` packages
+  already inside the range changes nothing **unless it changes interfaces inside
+  the tuple** (`0.1.6-alpha.2` removed the client session-ownership and
+  queue-mirror APIs, so the floor moved with it). All `@deepseek-ai/*` packages
   release together; `npm view @deepseek-ai/dsh dist-tags` is the signal.
 - **Published-tuple check (optional)**: `node scripts/check-dsh-version.mjs`
   compares the `latest` dist-tag version against the tuple the peers cover
@@ -93,11 +95,10 @@ outside it.
   `^0.1.x`); this section can then be deleted.
 - **Declared minimum (`dsh.engines.dsh`)**: alongside the peer tuple, each
   release declares the DSH runtime floor under `dsh.engines.dsh` (e.g.
-  `>=0.1.2-rc.1`), consumed by the plugin-manager update guard. Bump it in
+  `>=0.1.2-rc.1`). Nothing reads it on the current line yet, so it is a
+  forward-looking declaration rather than an enforced guard. Bump it in
   the same release that changes the peer range; never leave code raised while
-  the declared floor stays behind. Only the `>=X.Y.Z[-pre]` form is
-  supported (`^`/`~`/multi-range are treated as "cannot verify" and
-  fail closed).
+  the declared floor stays behind. Only the `>=X.Y.Z[-pre]` form is used.
 
 ## Versioned-line release model
 
@@ -131,8 +132,7 @@ dist-tag named by its pre-release identifier (`0.9.0-alpha.1` → `alpha`,
 
 **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`.
+the line is EOL, frozen, and receives no further patches.
 
 **Bug-fix flow (forward-fix then backport).** A fix affecting multiple supported
 lines is applied on `main` first, then backported to each still-supported

package/docs/release/release.zh.md

@@ -40,9 +40,9 @@ npm publish --access public
 
 | 发布类型 | 分支 | 版本步进 | dist-tag |
 | --- | --- | --- | --- |
-| 当前线稳定补丁 | `release/0.8.x` | `npm version patch` | `latest` |
+| 当前线稳定补丁 | `release/<line>.x` | `npm version patch` | `latest` |
 | 下一线 pre-release | `main` | `npm version prerelease --preid=alpha` | `alpha` |
-| 下一线正式版 | `main` | `npm version 0.9.0` | `latest` |
+| 下一线正式版 | `main` | `npm version <next>` | `latest` |
 
 每次发布为 `git push <分支>`，再 `git push <分支> --tags`。
 
@@ -69,8 +69,10 @@ DSH 仍在 rc 阶段，npm 的 prerelease 匹配规则要求 peer 范围与宿
 **每一条 DSH 线一个 peer 元组**（如 `^0.1.2-rc.1`）；范围是保守的，只声明实际验证过的内容。
 
 - **何时需要更新**：**已验证范围**变化时——DSH 发新元组，或主动收窄（例如不再
-  声明内测的 DSH `alpha` 系列）；落在已声明范围内的发布不改变任何东西。DSH 所有包
-  同版本发布；信号是 `npm view @deepseek-ai/dsh dist-tags`。
+  声明内测的 DSH `alpha` 系列）；落在已声明范围内的发布不改变任何东西，**除非它在
+  同一元组内改变了接口**（`0.1.6-alpha.2` 删除了客户端会话所有权与 queue 镜像
+  API，下限随之移动）。DSH 所有包同版本发布；信号是
+  `npm view @deepseek-ai/dsh dist-tags`。
 - **已发布元组检查（可选）**：`node scripts/check-dsh-version.mjs` 用 npm `latest`
   dist-tag 版本对比 peer 覆盖的元组（exit 0 无需动作，exit 1 需要）。它**只读
   `latest` tag**；发布在其它 tag 的 pre-release 走**手动发布前检查**
@@ -80,10 +82,9 @@ DSH 仍在 rc 阶段，npm 的 prerelease 匹配规则要求 peer 范围与宿
 - **正式版后收敛**：DSH 发布 final 版本后，正式版不受 prerelease 元组规则
   限制，peer 可收敛为稳定的 `^0.1.x` 单范围，此节即可删除。
 - **声明的最低运行时（`dsh.engines.dsh`）**：与 peer 元组一起，每个发布在
-  `dsh.engines.dsh` 声明 DSH 运行时下限（如 `>=0.1.2-rc.1`），供插件管理器
-  更新守卫读取。**与 peer 范围持平的同一发布里一并 bump**；不可只升代码、
-  声明下限停留在旧值。仅支持 `>=X.Y.Z[-pre]` 形式（`^`/`~`/多范围会被视为
-  「无法校验」而 fail-closed）。
+  `dsh.engines.dsh` 声明 DSH 运行时下限（如 `>=0.1.2-rc.1`）。当前线上还没有
+  任何读取方，因此它只是前置声明、尚未被强制执行。**与 peer 范围持平的同一发布里
+  一并 bump**；不可只升代码、声明下限停留在旧值。仅使用 `>=X.Y.Z[-pre]` 形式。
 
 ## 发布版本线模型
 
@@ -111,8 +112,7 @@ pre-release 发到与其 pre-release 标识符同名的 dist-tag（`0.9.0-alpha.
 `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` 发布为止。
+DSH 线作为 `latest` 发布为止；此后该线 EOL、冻结、不再发补丁。
 
 **Bug 修复流程（先向前修，再回迁）。** 跨多条支持线的修复，先在 `main` 上
 修复，再回迁到各仍受支持的 release 分支。仅特定线的修复，只在对应线修复。

package/docs/rewind-fix.md

@@ -18,7 +18,7 @@ The plugin is prepared in two parts, both shipped in the new version:
 
 1. **New rewind markers use the new shape** (forward) — this is a **correct, low-risk**, long-term change aligned with the official `/compact` design (see the [README](../README.en.md), the "How it works" section), and the new shape is fully compatible with **both old and new** DSH.
 
-2. **The `/dsh-rewind-fix` command** (backward) — for **already-existing** old sessions, the plugin ships a convenient update command that translates those old markers into the new shape so the sessions are usable again.
+2. **The `/dsh-rewind-fix` command** (backward) — for **already-existing** old sessions, the plugin shipped an update command (removed in plugin `0.10.x`) that translated those old markers into the new shape so the sessions were usable again.
 
 This document covers mainly the **update command**.
 

package/docs/rewind-fix.zh.md

@@ -18,7 +18,7 @@
 
 1. **新产生的 rewind 标记换成新格式**（向前）——这一步是**正确、低风险**的长期改动（对标官方 `/compact` 设计，见 [README](../README.md)「原理」一节），新格式对**新旧版本** DSH 均完全兼容。
 
-2. **提供 `/dsh-rewind-fix` 命令**（向后）——对于**已经存在**的旧会话，本插件提供便捷更新命令，把旧标记「翻译」成新格式，让会话重新可用。
+2. **提供 `/dsh-rewind-fix` 命令**（向后）——对于**已经存在**的旧会话，本插件曾提供便捷更新命令（已在插件 `0.10.x` 移除），把旧标记「翻译」成新格式，让会话重新可用。
 
 本文档主要讲解**更新命令**的使用方法。
 

package/docs/snapshot-auto-cleanup.md

@@ -1,5 +1,7 @@
 # Snapshot cleanup
 
+<!-- docs-scope: applies to DSH <= 0.1.6, where the policy is a dsh-settings document namespace. DSH 0.1.7 stores it as the plugin entry's own live configuration; the 0.1.7 seam is recorded in docs/compat/audit.md and docs/format.md. -->
+
 The plugin saves a backup of each file before it's edited, so you can rewind your
 code to an earlier point. These backups are called **snapshots**, and they're
 grouped by message and stored per session.

package/docs/snapshot-auto-cleanup.zh.md

@@ -1,5 +1,7 @@
 # 快照清理
 
+<!-- docs-scope: 适用于 DSH <= 0.1.6，此时策略存放在 dsh-settings 文档的命名空间；DSH 0.1.7 起改为本插件条目自身的实时配置，0.1.7 的接缝记录在 docs/compat/audit.md 与 docs/format.md。 -->
+
 插件会在每次修改文件前保存一份备份，方便你把代码回退到之前的状态。这些备份叫**快照**，按消息分组、按会话存放。
 
 `/snapshot-auto-cleanup` 帮你管理这些快照——既可以回收旧会话占用的磁盘，也可以清空**当前**会话、让它从"现在"重新开始记录回退历史。