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

package/SECURITY.md

@@ -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/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.2` (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
@@ -16,8 +16,11 @@
 > 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 — unless it changes interfaces inside the tuple: `0.1.6-alpha.2`
-> removed the client session-ownership and queue-mirror APIs, so the peer floor
-> moved to it. Signal: `npm view @deepseek-ai/dsh dist-tags`;
+> 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).
 >
@@ -35,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)
@@ -62,10 +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`.
@@ -76,14 +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 not localizable (`0.1.6-alpha.2`)**: the manager titles a bundle with `shortName(pkg.name)` (`dsh-rewind-plugin` → `rewind-plugin`) and shows the raw `package.json` description; only its private `BUILTIN_COPY` (three official bundles) is translated, and `DshManifest` carries no title/description field. Its rows section renders for every bundle, official included. Only the description is the plugin's to set; nothing is compensated.
+- **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.
 
@@ -91,39 +95,36 @@ 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_FACES` — 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_FACES`: compact, export, feedback, goal,
   permission, plan). A command outside that set — every third-party plugin — is passed through
   verbatim, never translated (`builtinRowFace` 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.
+  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
 
@@ -161,6 +162,34 @@ new turn at `phase.turn + 1` (`agent.ts:277-283`) **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).
@@ -186,7 +215,8 @@ new turn at `phase.turn + 1` (`agent.ts:277-283`) **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/contract/client-contract.md

@@ -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/format.md

@@ -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/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` 帮你管理这些快照——既可以回收旧会话占用的磁盘，也可以清空**当前**会话、让它从"现在"重新开始记录回退历史。