dsh-memoir 0.7.0 → 0.7.1

package/README.en.md

@@ -12,7 +12,7 @@
 No embeddings, vector database, or cloud memory service. The npm package has zero bundled runtime dependencies; DSH peers are supplied by the host.
 
 > [!IMPORTANT]
-> `dsh-memoir@0.7.0` is a compatibility-only release for DSH **0.1.5-rc.1**, with no new features. It requires `>=0.1.5-rc.1 <0.1.6-0`; upgrade DSH first. Keep `dsh-memoir@0.6.2` on DSH 0.1.2, or `0.5.6` on DSH 0.1.1-rc.2.
+> `dsh-memoir@0.7.1` fixes lost session snapshots after restart or RAM eviction (#10), supporting DSH **0.1.5-rc.1 / rc.2**. It requires `>=0.1.5-rc.1 <0.1.6-0`; check your host first. Keep `0.6.2` on DSH 0.1.2, or `0.5.6` on DSH 0.1.1-rc.2; those older lines do not include this fix.
 
 ```bash
 npm install --global @deepseek-ai/dsh@0.1.5-rc.1
@@ -57,7 +57,16 @@ Complete history and Hot Memory are separate layers:
 
 - **Full Memory** retains every record for the GUI, human review, Markdown projection, and ranked retrieval.
 - **Hot Memory** selects only budgeted actions, lessons, and recent state; the full `PROJECT_MEMORY.md` is never injected.
-- **Session Snapshot** freezes injected text within a session. New writes are immediately readable by tools and the GUI, while automatic injection refreshes in the next new session.
+- **Session Snapshot** durably freezes injected text per session and restores it after restart or RAM eviction. New writes remain immediately readable by tools and the GUI; automatic injection refreshes in the next new session. Recovery failures explicitly report degraded persistence.
+
+### Snapshot recovery and cleanup (0.7.1)
+
+- Default directory: `$DSH_HOME/dsh-memoir.json.snapshots/`, or `<storePath>.snapshots/` with a custom store. Records are partitioned by data-source/settings hash, language, and session hash. They load on demand without scanning the whole directory at startup.
+- `sessionSnapshotMax` bounds RAM only. Disk records have no automatic TTL and survive shrinking, uninstalling, or clearing RAM. Include them in backups. To reclaim disk, stop the relevant DSH processes, back up first, and manually remove records you no longer need to resume. Access after removal establishes a new baseline.
+- Languages use separate namespaces; switching back restores the original baseline for that language. Budget changes affect new baselines only. Forks/new session IDs do not inherit the parent's frozen record.
+- Old sessions whose snapshots were lost before upgrading establish a baseline from current memory once. Memoir does not guess or slice original text out of historical system prompts. Corrupt, inaccessible, or locked records remain unchanged; fallback freezes only in the current process, with diagnostics and a log warning.
+- Text is capped at 256 KiB and each record at 2 MiB; exceeding either reports the same degradation. New POSIX directories/files use 0700/0600; Windows access remains governed by directory ACLs. Snapshot files contain memory text and are user data.
+- This fix prevents rebuilding recoverable snapshots; it cannot guarantee provider KV-cache retention or hit rates.
 
 ## Agent tools and memory lifecycle
 
@@ -79,7 +88,7 @@ Similar-memory governance starts with BM25 candidates, then combines title simil
 
 v0.6.2 diagnostics show the latest decision and process-local counters. Turns calling `memoir_record` or `memoir_update` skip reminders; submitting a reminder does not confirm persistence. Agent disposal clears gate state, with a fallback cap of 1024 recently active agents (eviction also forgets their turn watermark and cooldown). Manual recording remains available when automatic distillation is disabled.
 
-The validated baseline is DSH `0.1.5-rc.1` (npm has not published an unsuffixed 0.1.5). BM25 is lexical retrieval and does not guarantee cross-language semantic matches without shared terms. Distillation guidance does not replace fact checking.
+DSH `0.1.5-rc.1` and the newest rc.2 are supported (pre-release verification: npm `next` is rc.2, while `latest` remains rc.1). BM25 is lexical retrieval and does not guarantee cross-language semantic matches without shared terms. Distillation guidance does not replace fact checking.
 
 Automatic distillation is an observable agent turn-end reminder, not silent background scraping of every chat. The default `1 / 0 / 1` means every eligible worked turn, no extra cooldown, and at least one tool call.
 
@@ -117,6 +126,8 @@ Installing into a DSH-alpha `web` profile registers a native Memory Conversation
 <details>
 <summary>More GUI screenshots</summary>
 
+![v0.7.1 durable snapshot diagnostics on DSH rc.2](https://raw.githubusercontent.com/Qinling-Melon-Farmers/dsh-memoir/v0.7.1/picture/v0.7.1-snapshot-persistence-zh.png)
+
 ![v0.7.0 native memory settings on DSH 0.1.5-rc.1](https://raw.githubusercontent.com/Qinling-Melon-Farmers/dsh-memoir/v0.7.0/picture/v0.7.0-dsh015-settings-zh.png)
 
 ![v0.6.2 automatic distillation lifecycle diagnostics](https://raw.githubusercontent.com/Qinling-Melon-Farmers/dsh-memoir/v0.6.2/picture/v0.6.2-distill-diagnostics-zh.png)
@@ -139,12 +150,12 @@ Installing into a DSH-alpha `web` profile registers a native Memory Conversation
 
 | Channel | DSH baseline | Installation | Status |
 | --- | --- | --- | --- |
-| npm `latest` (`0.7.0`) | `>=0.1.5-rc.1 <0.1.6-0` | `dsh plugin --profile web add dsh-memoir@latest` | Compatibility release validated on 0.1.5-rc.1 |
+| npm `latest` (`0.7.1`) | `>=0.1.5-rc.1 <0.1.6-0` | `dsh plugin --profile web add dsh-memoir@latest` | Snapshot recovery fix; rc.1 / rc.2 validated |
 | pinned npm `0.6.2` | `>=0.1.2-alpha.2 <0.1.3` | `dsh plugin --profile web add dsh-memoir@0.6.2` | Legacy 0.1.2 line |
 | pinned npm `0.5.6` | `0.1.1-rc.2` | `dsh plugin --profile web add dsh-memoir@0.5.6` | rc2 compatibility line |
-| GitHub `main` (`0.7.0`) | `>=0.1.5-rc.1 <0.1.6-0` | source clone + `link:` | Development and debugging |
+| GitHub `main` (`0.7.1`) | `>=0.1.5-rc.1 <0.1.6-0` | source clone + `link:` | Development and debugging |
 
-Node.js `^22.19.0 || >=24.0.0` is required. 0.7.0 keeps the native `conversation.view` / `settings.section` slots and `snapshotEvents()`. DSH 0.1.5 uses Session log V3, independent of Memoir store v4 / settings v3. Back up DSH_HOME before upgrading DSH; migrated sessions are not guaranteed readable by older hosts. This Memoir release neither migrates nor resets memory and retains frozen session snapshots without enabling new dynamic-prompt behavior.
+Node.js `^22.19.0 || >=24.0.0` is required. 0.7.1 keeps the native `conversation.view` / `settings.section` slots and `snapshotEvents()`. DSH 0.1.5 uses Session log V3, independent of Memoir store v4 / settings v3. Back up DSH_HOME before upgrading DSH; migrated sessions are not guaranteed readable by older hosts. This Memoir release neither migrates nor resets memory and retains frozen session snapshots without enabling new dynamic-prompt behavior.
 
 <details>
 <summary>Install from source</summary>
@@ -196,7 +207,7 @@ Every field below can be set in the memoir `config` row in `cordis.patch.yml`. E
 | `hotMemoryMaxTokens` | `1200` | hard ceiling that no session exceeds |
 | `readDefaultLimit` | `8` | default `memoir_read` result count |
 | `readMaxLimit` | `30` | live upper bound per recall |
-| `sessionSnapshotMax` | `128` | frozen session-snapshot LRU capacity |
+| `sessionSnapshotMax` | `128` | resident LRU capacity; durable records are not deleted |
 | `queryCacheSize` | `128` | BM25 query LRU capacity |
 
 Shrinking a cache evicts the oldest entries immediately. Existing frozen sessions are not rewritten after budget changes, preserving prompt-prefix stability. “Restore startup configuration” removes Web overrides and returns to profile startup values.
@@ -213,7 +224,7 @@ v0.5.6 benchmark (Node 24.19, 900/1200-token budget; full data in [`bench/report
 
 Numbers vary by machine and corpus. The important properties are that injection remains bounded and the cache-hit path is independent of total memory size.
 
-0.7.0 passes 193 tests and type checking, retaining all existing regressions and adding an official DSH Session V3 object test for provenance, distillation, tool writes, and frozen injection. An isolated DSH 0.1.5-rc.1 profile passes Web Settings, bilingual diagnostics, and API checks. Historical alpha/rc validation is recorded in the changelog and does not imply 0.7.0 can be installed on older hosts.
+0.7.1 has 202 tests: 201 pass on Windows with one POSIX permission test skipped; all pass on Linux. Coverage includes actual process restart, same-session concurrent creation, LRU, empty baselines, forks, language isolation, corruption and permission errors, plus existing BM25/Hot Memory/tool regressions. DSH rc.1 and the newest rc.2 are validated. Prefix equality in tests is not a guarantee of actual billing savings.
 
 ## FAQ
 
@@ -242,6 +253,6 @@ pnpm test
 npm run bench
 ```
 
-Read [CONTRIBUTING.md](./CONTRIBUTING.md) before submitting changes. See [CHANGELOG.md](./CHANGELOG.md) for version history. Formal packages are published by the tag workflow through npm OIDC. The current npm release is [v0.7.0](https://github.com/Qinling-Melon-Farmers/dsh-memoir/releases/tag/v0.7.0), and `main` is synchronized with it.
+Read [CONTRIBUTING.md](./CONTRIBUTING.md) before submitting changes. See [CHANGELOG.md](./CHANGELOG.md) for version history. Formal packages are published by the tag workflow through npm OIDC. The current npm release is [v0.7.1](https://github.com/Qinling-Melon-Farmers/dsh-memoir/releases/tag/v0.7.1), and `main` is synchronized with it.
 
 Apache-2.0

package/README.md

@@ -11,7 +11,7 @@
 无需 embedding、向量数据库或云端记忆服务；npm 包零捆绑运行时依赖，DSH peer 由宿主提供。
 
 > [!IMPORTANT]
-> `dsh-memoir@0.7.0` 是 DSH **0.1.5-rc.1** 的兼容性发布，不增加新功能。要求 `>=0.1.5-rc.1 <0.1.6-0`；请先升级 DSH。旧 DSH 0.1.2 用户固定使用 `dsh-memoir@0.6.2`，0.1.1-rc.2 用户固定使用 `0.5.6`。
+> `dsh-memoir@0.7.1` 修复重启和内存淘汰后旧会话快照丢失（#10），支持 DSH **0.1.5-rc.1 / rc.2**。要求 `>=0.1.5-rc.1 <0.1.6-0`；请先核对宿主版本。旧 DSH 0.1.2 用户固定使用 `0.6.2`，0.1.1-rc.2 用户固定使用 `0.5.6`；这些旧版未包含本次修复。
 
 ```bash
 npm install --global @deepseek-ai/dsh@0.1.5-rc.1
@@ -56,7 +56,16 @@ memoir_record / memoir_update
 
 - **Full Memory** 保留全部记录，用于 GUI、人工审阅、Markdown 投影和排序检索。
 - **Hot Memory** 只选择预算内的 actions、lessons 与 recent state；不会把整个 `PROJECT_MEMORY.md` 塞进 prompt。
-- **Session Snapshot** 在会话内冻结注入文本。新写入立即可被工具和 GUI 读取，但自动注入从下一个新会话开始更新。
+- **Session Snapshot** 按会话持久化冻结注入文本，重启恢复与内存淘汰后仍复用原文。新写入立即可被工具和 GUI 读取，但自动注入从下一个新会话开始更新；恢复失败会显式报告降级。
+
+### 快照恢复与清理（0.7.1）
+
+- 默认目录：`$DSH_HOME/dsh-memoir.json.snapshots/`；自定义 storePath 时为 `<storePath>.snapshots/`。记录按数据源/设置文件的哈希、语言和会话哈希分开保存；按需读取，不在启动时加载全部文件。
+- `sessionSnapshotMax` 只限制内存 LRU。磁盘记录无自动 TTL，不随缩容、卸载或清理内存删除；备份记忆时请一起备份该目录。需要回收磁盘时先停止相关 DSH 进程并备份，再人工删除确定不再恢复的记录。删除后再次访问会建立新基线。
+- 语言切换使用独立快照空间；切回原语言会复用其旧基线。预算修改仅影响新基线；fork/新 session id 不借用父会话快照。
+- 升级前已丢失快照的旧会话，首次使用新版只能按当前记忆建立一次新基线；不从历史 system prompt 猜测截取原文。读取损坏、权限或锁失败时保留原文件，回退到进程内冻结；诊断页和日志会提示重启稳定性降级。
+- 单条文本上限 256 KiB，记录上限 2 MiB；超限走同样的可诊断降级。POSIX 新目录/记录使用 0700/0600，Windows 权限仍由目录 ACL 管理。记录含记忆文本，应视为用户数据。
+- 本修复消除可恢复快照的重复重建，不能保证提供商仍保留 KV cache 或保证命中率。
 
 ## Agent 工具与记忆生命周期
 
@@ -78,7 +87,7 @@ memoir_record / memoir_update
 
 v0.6.2 的诊断页显示最近触发或跳过原因及本次进程计数。已经调用 `memoir_record` 或 `memoir_update` 的回合不再提醒；提交提醒不代表写入已完成。Agent 销毁会清理门控状态，最多保留 1024 个最近活动 Agent（淘汰后不再保留其回合水位和冷却）。关闭自动蒸馏后仍可手动记录。
 
-当前验证基线为 DSH `0.1.5-rc.1`（npm 尚无不带后缀的 0.1.5）。BM25 是词项召回，不能保证无共同词项的跨语言语义匹配；提炼质量提示也不能替代事实核验。
+当前支持 DSH `0.1.5-rc.1` 与最新 rc.2（发布前核验：npm `next` 为 rc.2、`latest` 仍为 rc.1）。BM25 是词项召回，不能保证无共同词项的跨语言语义匹配；提炼质量提示也不能替代事实核验。
 
 自动蒸馏是可观察的 Agent 收尾提醒，不是后台静默抓取聊天内容。默认 `1 / 0 / 1` 表示：每个有效 worked turn、无额外冷却、至少一次工具调用即可提醒。
 
@@ -116,6 +125,8 @@ v0.6.2 的诊断页显示最近触发或跳过原因及本次进程计数。已
 <details>
 <summary>查看更多 GUI 截图</summary>
 
+![v0.7.1 在 DSH rc.2 中的快照持久化诊断](https://raw.githubusercontent.com/Qinling-Melon-Farmers/dsh-memoir/v0.7.1/picture/v0.7.1-snapshot-persistence-zh.png)
+
 ![v0.7.0 在 DSH 0.1.5-rc.1 中的原生记忆设置](https://raw.githubusercontent.com/Qinling-Melon-Farmers/dsh-memoir/v0.7.0/picture/v0.7.0-dsh015-settings-zh.png)
 
 ![v0.6.2 自动蒸馏生命周期诊断](https://raw.githubusercontent.com/Qinling-Melon-Farmers/dsh-memoir/v0.6.2/picture/v0.6.2-distill-diagnostics-zh.png)
@@ -138,12 +149,12 @@ v0.6.2 的诊断页显示最近触发或跳过原因及本次进程计数。已
 
 | 渠道 | DSH 基线 | 安装方式 | 状态 |
 | --- | --- | --- | --- |
-| npm `latest`（`0.7.0`） | `>=0.1.5-rc.1 <0.1.6-0` | `dsh plugin --profile web add dsh-memoir@latest` | 当前兼容性发布；验证基线 0.1.5-rc.1 |
+| npm `latest`（`0.7.1`） | `>=0.1.5-rc.1 <0.1.6-0` | `dsh plugin --profile web add dsh-memoir@latest` | 快照恢复修复；已验证 rc.1 / rc.2 |
 | npm 固定版 `0.6.2` | `>=0.1.2-alpha.2 <0.1.3` | `dsh plugin --profile web add dsh-memoir@0.6.2` | 旧 0.1.2 兼容线 |
 | npm 固定版 `0.5.6` | `0.1.1-rc.2` | `dsh plugin --profile web add dsh-memoir@0.5.6` | rc2 兼容线 |
-| GitHub `main`（`0.7.0`） | `>=0.1.5-rc.1 <0.1.6-0` | 源码 clone + `link:` | 开发和调试使用 |
+| GitHub `main`（`0.7.1`） | `>=0.1.5-rc.1 <0.1.6-0` | 源码 clone + `link:` | 开发和调试使用 |
 
-需要 Node.js `^22.19.0 || >=24.0.0`。0.7.0 继续使用原生 `conversation.view` / `settings.section` 与 `snapshotEvents()`。DSH 0.1.5 的会话日志升级至 V3；其迁移与 Memoir 的 store v4 / settings v3 是独立格式。升级 DSH 前备份 DSH_HOME，迁移后的 DSH 会话不能承诺被旧宿主读取。Memoir 本次不迁移或清空记忆，也不启用新动态提示词行为；既有会话快照语义保持不变。
+需要 Node.js `^22.19.0 || >=24.0.0`。0.7.1 继续使用原生 `conversation.view` / `settings.section` 与 `snapshotEvents()`。DSH 0.1.5 的会话日志升级至 V3；其迁移与 Memoir 的 store v4 / settings v3 是独立格式。升级 DSH 前备份 DSH_HOME，迁移后的 DSH 会话不能承诺被旧宿主读取。Memoir 本次不迁移或清空记忆，也不启用新动态提示词行为；既有会话快照语义保持不变。
 
 <details>
 <summary>从源码安装</summary>
@@ -195,7 +206,7 @@ dsh plugin --profile web add "link:/absolute/path/dsh-memoir"
 | `hotMemoryMaxTokens` | `1200` | 任何会话都不能超过的硬上限 |
 | `readDefaultLimit` | `8` | `memoir_read` 默认结果数 |
 | `readMaxLimit` | `30` | 单次召回实时上限 |
-| `sessionSnapshotMax` | `128` | 会话冻结快照 LRU 容量 |
+| `sessionSnapshotMax` | `128` | 内存快照 LRU 容量，不删除磁盘快照 |
 | `queryCacheSize` | `128` | BM25 查询 LRU 容量 |
 
 缩小缓存容量会立即淘汰最旧项；已冻结会话不会因预算修改而重写，以维持 prompt 前缀稳定。“恢复启动配置”会删除 Web 覆盖并回到 profile 的启动值。
@@ -212,7 +223,7 @@ v0.5.6 基准（Node 24.19，900/1200 token；完整数据见 [`bench/report.md`
 
 基准值取决于机器和语料；它证明的重点是注入预算保持有界、缓存命中路径与记忆总量解耦。
 
-0.7.0 的 193 项测试与类型检查通过，保留全部既有回归，并新增使用官方 DSH Session V3 对象的来源、蒸馏、工具写入与冻结注入测试。隔离 DSH 0.1.5-rc.1 的 Web 设置、双语诊断与 API 回归通过。旧版 alpha/rc 的历史验证见各版本更新日志；不据此宣称 0.7.0 可安装在旧宿主。
+0.7.1 含 202 项测试：Windows 201 项通过、1 项 POSIX 权限测试跳过；Linux 全部通过。覆盖实际跨进程快照恢复、同会话并发写入、LRU、空基线、fork、语言隔离、损坏与权限失败，以及原有 BM25/Hot Memory/工具回归。已核验 DSH rc.1 和最新 rc.2；没有把测试前缀一致性等同于实际账单节省保证。
 
 ## 常见问题
 
@@ -241,6 +252,6 @@ pnpm test
 npm run bench
 ```
 
-提交前请阅读 [CONTRIBUTING.md](./CONTRIBUTING.md)。版本变化见 [CHANGELOG.md](./CHANGELOG.md)，正式包由 tag 工作流通过 npm OIDC 发布。当前 npm 正式版是 [v0.7.0](https://github.com/Qinling-Melon-Farmers/dsh-memoir/releases/tag/v0.7.0)，`main` 与该版本同步。
+提交前请阅读 [CONTRIBUTING.md](./CONTRIBUTING.md)。版本变化见 [CHANGELOG.md](./CHANGELOG.md)，正式包由 tag 工作流通过 npm OIDC 发布。当前 npm 正式版是 [v0.7.1](https://github.com/Qinling-Melon-Farmers/dsh-memoir/releases/tag/v0.7.1)，`main` 与该版本同步。
 
 Apache-2.0

package/lib/client.js

@@ -157,6 +157,18 @@ var MemoirApi = class {
 // src/client/i18n.ts
 var dictionaries = {
   zh: {
+    "snapshot.disk": "\u4F1A\u8BDD\u5FEB\u7167\u6301\u4E45\u5316",
+    "snapshot.restored": "\u4ECE\u78C1\u76D8\u6062\u590D",
+    "snapshot.created": "\u5EFA\u7ACB\u65B0\u57FA\u7EBF",
+    "snapshot.failures": "\u6301\u4E45\u5316\u5931\u8D25",
+    "snapshot.last": "\u6700\u8FD1\u78C1\u76D8\u64CD\u4F5C",
+    "snapshot.idle": "\u5C1A\u672A\u8BFB\u53D6",
+    "snapshot.volatile": "\u964D\u7EA7\u4E3A\u8FDB\u7A0B\u5185\u5FEB\u7167",
+    "snapshot.degraded": "\u65E0\u6CD5\u4FDD\u8BC1\u91CD\u542F\u540E\u524D\u7F00\u4E00\u81F4\uFF1B\u8BF7\u68C0\u67E5\u5FEB\u7167\u5B58\u50A8",
+    "snapshot.invalid-record": "\u683C\u5F0F\u6216\u6821\u9A8C\u4E0D\u7B26\uFF0C\u539F\u6587\u4EF6\u5DF2\u4FDD\u7559",
+    "snapshot.record-too-large": "\u8D85\u51FA\u5FEB\u7167\u5927\u5C0F\u4E0A\u9650",
+    "snapshot.unavailable": "\u8BFB\u5199\u4E0D\u53EF\u7528\u6216\u9501\u8D85\u65F6",
+    "snapshot.retention": "LRU \u4EC5\u9650\u5236\u5185\u5B58\uFF1B\u78C1\u76D8\u5FEB\u7167\u65E0\u81EA\u52A8\u8FC7\u671F\u3002\u65E7\u4F1A\u8BDD\u9996\u6B21\u5347\u7EA7\u53EF\u80FD\u5EFA\u7ACB\u4E00\u6B21\u65B0\u57FA\u7EBF\uFF1B\u4E0D\u4FDD\u8BC1\u670D\u52A1\u7AEF\u7F13\u5B58\u547D\u4E2D\u3002",
     "distill.title": "\u81EA\u52A8\u84B8\u998F\u751F\u547D\u5468\u671F",
     "distill.worked": "\u7D2F\u8BA1\u6709\u6548\u5DE5\u4F5C\u56DE\u5408",
     "distill.agents": "\u8DDF\u8E2A Agent",
@@ -335,6 +347,18 @@ var dictionaries = {
     "settings.saveFailed": "\u8BBE\u7F6E\u4FDD\u5B58\u5931\u8D25"
   },
   en: {
+    "snapshot.disk": "Durable session snapshots",
+    "snapshot.restored": "Restored from disk",
+    "snapshot.created": "New baselines",
+    "snapshot.failures": "Persistence failures",
+    "snapshot.last": "Last disk operation",
+    "snapshot.idle": "Not read yet",
+    "snapshot.volatile": "Process-local fallback",
+    "snapshot.degraded": "Prefix stability across restart is not guaranteed; check snapshot storage",
+    "snapshot.invalid-record": "Invalid format or hash; original file preserved",
+    "snapshot.record-too-large": "Snapshot size limit exceeded",
+    "snapshot.unavailable": "Storage unavailable or lock timeout",
+    "snapshot.retention": "LRU bounds RAM only; disk snapshots do not auto-expire. Older sessions may establish a new baseline once after upgrade. Server-side cache hits are not guaranteed.",
     "distill.title": "Automatic distillation lifecycle",
     "distill.worked": "Eligible worked turns",
     "distill.agents": "Tracked agents",
@@ -1497,6 +1521,34 @@ ${projectSignature}`;
             "/",
             diag.snapshotMax
           ] }),
+          diag.snapshotPersistence ? /* @__PURE__ */ (0, import_jsx_runtime.jsxs)("div", { "data-dsh-part": "snapshot-persistence", children: [
+            /* @__PURE__ */ (0, import_jsx_runtime.jsx)("h4", { children: t("snapshot.disk") }),
+            /* @__PURE__ */ (0, import_jsx_runtime.jsxs)("div", { children: [
+              t("snapshot.restored"),
+              ": ",
+              diag.snapshotPersistence.restored,
+              " \xB7 ",
+              t("snapshot.created"),
+              ": ",
+              diag.snapshotPersistence.created,
+              " \xB7 ",
+              t("snapshot.failures"),
+              ": ",
+              diag.snapshotPersistence.failures
+            ] }),
+            /* @__PURE__ */ (0, import_jsx_runtime.jsxs)("div", { children: [
+              t("snapshot.last"),
+              ": ",
+              t(`snapshot.${diag.snapshotPersistence.lastStatus}`)
+            ] }),
+            diag.snapshotPersistence.lastError ? /* @__PURE__ */ (0, import_jsx_runtime.jsxs)("div", { role: "status", children: [
+              t("snapshot.degraded"),
+              " (",
+              t(`snapshot.${diag.snapshotPersistence.lastError}`),
+              ")"
+            ] }) : null,
+            /* @__PURE__ */ (0, import_jsx_runtime.jsx)("div", { children: t("snapshot.retention") })
+          ] }) : null,
           /* @__PURE__ */ (0, import_jsx_runtime.jsxs)("div", { children: [
             t("diag.cache"),
             ": ",