dsh-archived-chats 1.4.4 → 1.4.6

package/CHANGELOG.md

@@ -4,6 +4,32 @@
 
 Entries describe behavior at each release, not necessarily current behavior. Consult the READMEs and user guides for current usage.
 
+## 1.4.6 — 2026-10-02
+
+### 中文
+
+- 修复会话库同时保留旧版 v3 与当前 v4 日志时，任意旧会话会使所有永久删除、清空回收站及自动回收清理报 `session-location-unavailable` 的问题（#55）。Host 的 `locate()` 返回当前代写入路径，不能据此要求该文件已经存在。
+- 删除安全检查以真实会话独占目录为范围，兼容实际存在的规范代际日志及尚未生成日志的空目录；清单中的已不存在目录不再阻塞删除和中断任务重试。继续拒绝符号链接／junction、非文件日志、目录重叠、不属于会话的路径及不可读清单。
+- 新增混合日志、空／缺失目录和删除安全回归，以及使用官方后端验证单条永久删除、归档直接删除、清空回收站的集成用例。原生 CI 门禁增加到六项；另在隔离目录验证官方 `0.2.0-rc.2` 后端，并在可选 peer 范围中显式加入这个已验证版本。
+
+### English
+
+- Fix `session-location-unavailable` blocking every permanent deletion, Empty Recycle Bin, and automatic recycle purge when the inventory contains a historical v3 log beside current v4 logs (#55). The Host's `locate()` names the current append target, which may not exist yet.
+- Use the actual exclusive session directory as the deletion scope, accepting canonical stored generations and unmaterialized empty directories. Absent inventory directories no longer block deletion or interrupted-purge retries. Keep refusing links/junctions, non-file logs, overlapping directories, non-session-scoped paths, and unreadable inventory.
+- Add mixed-generation, empty/missing-directory, and safety regressions plus an official-backend integration for individual purge, direct archive deletion, and Empty Recycle Bin. The mandatory native CI gate now runs six cases. Also verify the official `0.2.0-rc.2` backend in an isolated fixture and explicitly admit that tested version in the optional peer range.
+
+## 1.4.5 — 2026-09-27
+
+### 中文
+
+- 使用隔离的虚构示例数据重拍八张插件界面截图，替换仍显示 1.3.1 旧界面及已移除快照入口的图片；中英文 README 与插件市场截图清单使用相同文件和顺序。
+- 同步中英文 README、用户指南及架构文档的版本说明，突出当前 `0.1.7-rc.2` Host fixture 与 v4 会话格式验证。本版不改动运行时代码、数据格式或 Host 兼容范围。
+
+### English
+
+- Replace all eight 1.3.1 screenshots, which showed retired snapshot UI, with captures of the current plugin using isolated synthetic example data. Both READMEs and the marketplace screenshot list reference the same files in the same order.
+- Update version notes in both READMEs, user guides, and architecture documents to describe the current `0.1.7-rc.2` Host fixture and v4 session-format verification. Runtime code, data format, and Host compatibility range are unchanged.
+
 ## 1.4.4 — 2026-09-27
 
 ### 中文

package/README.md

@@ -32,7 +32,7 @@ Archive Management gives DeepSeek Harness a place to find chats hidden from the
 
 > The English name is **Archive Management**, and the Chinese name is **归档管理**. The installation package remains `dsh-archived-chats`.
 >
-> This document follows the `main` branch. This guide targets 1.4.4, whose runtime code is unchanged from 1.4.3; package metadata now lists DSH `0.1.7-rc.2` among the verified Hosts. 1.4.3 accepts the v4 session format those Hosts publish. The 1.4.2 export writer no longer carries a dependency that prevents startup on newer Hosts. See the [changelog](CHANGELOG.md) for release history, including 1.4.1's English rename and feedback improvements.
+> This document follows the `main` branch and targets 1.4.6. This release fixes permanent deletion and Recycle Bin cleanup when historical and current session log generations coexist. See the [changelog](CHANGELOG.md) for release history.
 
 ## Quick start
 
@@ -66,6 +66,19 @@ dsh plugin --profile web update dsh-archived-chats
 
 The five views are **Archived**, **Recycle Bin**, **Storage & Retention**, **Origins & Branches**, and **About**. Archiving does not create historical versions; Recycle Bin protection snapshots support recovery, not a browsable version-history library.
 
+## Screenshots
+
+These screenshots show the current interface with synthetic example chats; they contain no private conversations. The [marketplace screenshot list](screenshots.json) uses the same files in the same order.
+
+1. [Archived chats](assets/screenshots/preview-01.png)
+2. [Full-text search](assets/screenshots/preview-02.png)
+3. [Workspace bulk archive](assets/screenshots/preview-03.png)
+4. [Read-only preview](assets/screenshots/preview-04.png)
+5. [Recycle Bin](assets/screenshots/preview-05.png)
+6. [Restore confirmation](assets/screenshots/preview-06.png)
+7. [Storage & Retention](assets/screenshots/preview-07.png)
+8. [Origins & Branches](assets/screenshots/preview-08.png)
+
 The Archived header has **Bulk archive** and **More**. More contains Import backup, Export all, Unarchive all, then Delete all after a separator. The Recycle Bin header directly shows **Restore all** and **Empty Recycle Bin** without a More menu. Recycle rows retain the preview icon and use compact **Restore** and **Delete** text buttons. Workspace and global restoration separately confirm scope, counts, and the Archived destination, skipping pending deletions. Empty Recycle Bin still requires irreversible-action confirmation. The header keeps consistent dimensions across tabs. Workspace actions and global export, unarchive, and deletion ask you to confirm the complete archive scope and chat count.
 
 **About** shows the running version, author, license, guides, project and feedback links, and Check for updates. Opening the page checks public npm version metadata in the background, at most once every 12 hours during a running backend session; failures never block archive management. A newer version adds a **Get update** link beside the title, opening the plugin market without installing or restarting anything. Follow the host's restart guidance when convenient; a browser refresh alone may not load an updated backend. No chat or backup content is sent during update checks.
@@ -121,7 +134,7 @@ The package declares DSH `>=0.1.0-rc.7`; individual features depend on public Ho
 
 Recycle Bin preview still depends on the original session; a missing original may prevent preview even when a protection snapshot can restore it. See [compatibility and limits](docs/USER_GUIDE.md#compatibility-and-limits).
 
-The declared range remains capability-based. Release automation passed Node.js 18 on Ubuntu and Node.js 24 on Ubuntu, macOS, and Windows; the Node.js 24 matrix required the official Host backend integration (5/5) and package checks. The installed 1.4.0 artifact also passed the official native round trip (5/5) against `@deepseek-ai/dsh-session@0.1.5-rc.2`.
+The declared range remains capability-based. Release automation tests Node.js 18 on Ubuntu and Node.js 24 on Ubuntu, macOS, and Windows; the Node.js 24 matrix requires the official `@deepseek-ai/dsh-session@0.1.7-rc.2` Host backend integration (6/6) and package checks, including the v4 session format.
 
 ## Documentation
 
@@ -146,7 +159,7 @@ node scripts/run-native-integration.mjs
 npm pack --dry-run --json
 ```
 
-The suite covers Host and browser behavior, export/import, snapshot fallback recovery, Recycle Bin, retention, search, responsive layout, public types, package contents, and repository hygiene. The native commands install the locked `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture and require all five native round-trip cases to run without skips. All checks use isolated temporary data and never read real sessions.
+The suite covers Host and browser behavior, export/import, snapshot fallback recovery, Recycle Bin, retention, search, responsive layout, public types, package contents, and repository hygiene. The native commands install the locked `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture and require all six native integration cases to run without skips. All checks use isolated temporary data and never read real sessions.
 
 ## Uninstall
 

package/README.zh-CN.md

@@ -30,7 +30,7 @@
 
 > 中文名称为「归档管理」，英文名称为 Archive Management；安装包名始终为 `dsh-archived-chats`。
 >
-> 本文跟随 `main` 分支维护。本文适用于 1.4.4，其运行时代码与 1.4.3 相同；包元数据现将 DSH `0.1.7-rc.2` 列为已验证 Host。1.4.3 接受这些 Host 发出的 v4 会话格式。1.4.2 的导出实现不再携带会导致新版 Host 启动失败的依赖；已安装用户请先升级。版本变更见[更新日志](CHANGELOG.md)，其中包含 1.4.1 的英文名称统一与交互提示优化。
+> 本文跟随 `main` 分支维护，适用于 1.4.6。本版修复旧版与当前版本会话日志混存时，永久删除及回收站清空失败的问题。版本变更见[更新日志](CHANGELOG.md)。
 
 ## 快速开始
 
@@ -64,6 +64,19 @@ dsh plugin --profile web update dsh-archived-chats
 
 五个视图为 **已归档**、**回收站**、**空间与策略**、**来源与分支** 和 **关于**。归档不会创建历史版本；回收站保护快照仅用于恢复，不是可浏览的历史版本库。
 
+## 界面截图
+
+以下截图使用虚构示例聊天展示当前界面，不含私人会话。[插件市场截图清单](screenshots.json)使用相同文件及顺序。
+
+1. [已归档聊天](assets/screenshots/preview-01.png)
+2. [全文搜索](assets/screenshots/preview-02.png)
+3. [工作区批量归档](assets/screenshots/preview-03.png)
+4. [只读预览](assets/screenshots/preview-04.png)
+5. [回收站](assets/screenshots/preview-05.png)
+6. [恢复确认](assets/screenshots/preview-06.png)
+7. [空间与策略](assets/screenshots/preview-07.png)
+8. [来源与分支](assets/screenshots/preview-08.png)
+
 已归档页顶部仅保留 **批量归档** 和 **更多**；「更多」依次提供导入备份、全部导出、全部取消归档，分隔线后为全部删除。回收站顶部直接并列显示 **全部恢复** 和 **清空回收站**，不再设更多菜单；聊天行保留预览图标，使用紧凑的 **恢复** 和 **删除** 文字按钮。工作区恢复和全局恢复分别确认范围、数量及已归档去向，跳过正在永久删除的条目；清空仍须确认不可恢复的后果。各 Tab 顶部保持一致尺寸。工作区操作及全局导出、取消归档、删除均先确认完整归档范围和聊天数量。
 
 「关于」展示当前运行版本、作者、许可证、指南、项目与反馈链接，提供「检查更新」。打开页面时后台查询公开 npm 版本信息，运行期间自动检查间隔至少 12 小时；失败不会阻断归档功能。有新版时标题旁显示「去更新」，打开插件市场，不自动安装或重启。更新后按宿主提示自行安排重启 DSH，仅刷新网页不一定能加载新版后端。
@@ -119,7 +132,7 @@ dsh plugin --profile web update dsh-archived-chats
 
 回收站预览目前仍依赖原会话；原件丢失时，即使保护快照可恢复，也可能无法预览。详见[兼容性与限制](docs/USER_GUIDE.zh-CN.md#兼容性与限制)。
 
-声明的版本范围仍以 Host 公开能力为准。发布自动化已通过 Ubuntu 上的 Node.js 18，以及 Ubuntu、macOS 和 Windows 上的 Node.js 24；Node.js 24 矩阵强制运行官方 Host 后端集成（5/5）与打包检查。已安装的 1.4.0 产物也已在 `@deepseek-ai/dsh-session@0.1.5-rc.2` 上通过官方 native 闭环（5/5）。
+声明的版本范围仍以 Host 公开能力为准。发布自动化在 Ubuntu 上测试 Node.js 18，并在 Ubuntu、macOS 和 Windows 上测试 Node.js 24；Node.js 24 矩阵强制运行基于官方 `@deepseek-ai/dsh-session@0.1.7-rc.2` 的 Host 后端集成（6/6）与打包检查，覆盖 v4 会话格式。
 
 ## 文档
 
@@ -144,7 +157,7 @@ node scripts/run-native-integration.mjs
 npm pack --dry-run --json
 ```
 
-测试覆盖 Host 与浏览器行为、导出导入、快照恢复、回收站、保留策略、全文搜索、响应式布局、公开类型、包内容和仓库卫生。原生集成命令会安装锁定的 `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture，并要求五个原生往返用例全部执行且不能跳过。所有检查只使用隔离临时数据，不读取真实会话。
+测试覆盖 Host 与浏览器行为、导出导入、快照恢复、回收站、保留策略、全文搜索、响应式布局、公开类型、包内容和仓库卫生。原生集成命令会安装锁定的 `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture，并要求六个原生集成用例全部执行且不能跳过。所有检查只使用隔离临时数据，不读取真实会话。
 
 ## 卸载
 

package/docs/ARCHITECTURE.en.md

@@ -2,7 +2,7 @@
 
 English · [中文](ARCHITECTURE.md) · [User guide](USER_GUIDE.md)
 
-This document follows `main`, covering 1.4.4 behavior, whose runtime code is unchanged from 1.4.3 (1.4.3 accepts the v4 session format in the persistence compatibility layer, 1.4.2 switched export ZIP generation to `fflate`); see the [changelog](../CHANGELOG.md) for release history. Runtime code is the authority for interfaces and behavior; user-facing documentation should agree with it.
+This document follows `main` and covers 1.4.6 behavior. This release fixes permanent deletion and Recycle Bin cleanup when historical and current session log generations coexist. See the [changelog](../CHANGELOG.md) for release history. Runtime code is the authority for interfaces and behavior; user-facing documentation should agree with it.
 
 ## Product boundary and modules
 
@@ -159,7 +159,7 @@ Move is missing → trashed; recycle purge is trashed/degraded → purge-pending
 
 Both paths share purge: persist intent → remove and recheck all associated snapshots → physically delete the session → finish registry/metadata cleanup → remove the recycle record last. Physical deletion runs with the caller's lifecycle lock and a pending marker.
 
-Snapshot sweeping uses manifest ownership and the record's named snapshotId to cover corrupted protection data. Unrelated unassignable corruption does not block a session's purge. The log must reside in a directory named for that session ID; shared directories are not purge targets. A missing log or archive index is not proof of completion: durable intent authorizes remaining cleanup.
+Snapshot sweeping uses manifest ownership and the record's named snapshotId to cover corrupted protection data. Unrelated unassignable corruption does not block a session's purge. The log must reside in a directory named for that session ID; shared directories are not purge targets. Safety checks use the actual session directory as the removal scope. If the current-generation log named by `locate()` is absent, inspect canonical generation logs that exist in the directory; empty directories still undergo ancestry and overlap checks. Inventory entries with absent directories are treated as missing and do not block other purges. Links/junctions, non-file logs, overlapping directories, and unreadable inventory still refuse deletion. A missing log or archive index is not proof of completion: durable intent authorizes remaining cleanup.
 
 Failures retain purge-pending. Startup and runtime retries continue these tasks, never restore them to ordinary chats. Archive deletion rejects existing recycle records, protecting the Recycle Bin from archive-wide Delete all. Purging snapshot copies does not promise global attachment cleanup or Host session_projcache eviction; no corresponding safe public eviction API is used.
 
@@ -214,6 +214,6 @@ npm pack --dry-run --json
 git diff --check
 ```
 
-The native commands install the locked `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture and require all five native round-trip cases to run without skips. This is the local equivalent of the mandatory native Host integration gate in CI.
+The native commands install the locked `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture and require all six native integration cases to run without skips. This is the local equivalent of the mandatory native Host integration gate in CI.
 
-The declared DSH `>=0.1.0-rc.7` range remains capability-based. Release automation passed Node.js 18 on Ubuntu and Node.js 24 on Ubuntu, macOS, and Windows; the Node.js 24 matrix required the official Host backend integration (5/5) and package checks. The installed 1.4.0 artifact also passed the official native round trip (5/5) against `@deepseek-ai/dsh-session@0.1.5-rc.2`. Existing screenshots are from v1.3.1 and include retired snapshot UI; they remain historical examples rather than current behavior documentation.
+The declared DSH `>=0.1.0-rc.7` range remains capability-based. Release automation tests Node.js 18 on Ubuntu and Node.js 24 on Ubuntu, macOS, and Windows; the Node.js 24 matrix requires the official `@deepseek-ai/dsh-session@0.1.7-rc.2` Host backend integration (6/6) and package checks, including the v4 session format. The [screenshots](../screenshots.json) show the current interface with synthetic example chats.

package/docs/ARCHITECTURE.md

@@ -2,7 +2,7 @@
 
 [English](ARCHITECTURE.en.md) · 中文 · [用户指南](USER_GUIDE.zh-CN.md)
 
-本文跟随 `main` 分支，功能对应 1.4.4，其运行时代码与 1.4.3 相同（1.4.3 在持久化兼容层接受 v4 会话格式，1.4.2 改用 `fflate` 生成导出 ZIP）；版本变更见[更新日志](../CHANGELOG.md)。运行时代码是接口与行为的依据；用户操作说明与本文应保持一致。
+本文跟随 `main` 分支，功能对应 1.4.6。本版修复旧版与当前版本会话日志混存时，永久删除及回收站清空失败的问题。版本变更见[更新日志](../CHANGELOG.md)。运行时代码是接口与行为的依据；用户操作说明与本文应保持一致。
 
 ## 产品边界与模块
 
@@ -159,7 +159,7 @@ apply 只接受凭据，不接受调用方增补会话 ID。每条执行前在
 
 两条路径共用 purge：持久化删除意图 → 清理该会话的全部关联快照并复查 → 物理删除会话 → 完成注册表与元数据清理 → 最后移除回收记录。物理删除在调用方持有生命周期锁且有待删除标记时执行。
 
-快照清扫使用 manifest 身份归属，并点名记录引用的 snapshotId，以覆盖损坏快照；不相关且无法归属的损坏项不会阻塞该会话删除。会话文件必须位于以自身 ID 命名的独占目录中，共享目录不是合法删除目标。已删除日志或索引不代表任务完成：依靠持久化意图继续清理剩余状态。
+快照清扫使用 manifest 身份归属，并点名记录引用的 snapshotId，以覆盖损坏快照；不相关且无法归属的损坏项不会阻塞该会话删除。会话文件必须位于以自身 ID 命名的独占目录中，共享目录不是合法删除目标。安全检查以真实会话目录为删除范围：`locate()` 返回的当前代日志不存在时，检查目录内实际存在的规范代际日志；空目录仍须通过祖先与目录重叠检查。目录已不存在的清单项视为缺失，不阻断其余删除。符号链接／junction、非文件日志、目录重叠及无法读取的清单仍拒绝删除。已删除日志或索引不代表任务完成：依靠持久化意图继续清理剩余状态。
 
 失败保留 `purge-pending`。启动恢复和运行中的重试继续处理这些任务，不将其恢复为普通聊天。归档删除拒绝已有回收记录，所以归档页全部删除不会波及回收站。删除快照副本不承诺清除 Host 全局附件或 `session_projcache`；插件没有对应的安全公开 eviction API。
 
@@ -214,6 +214,6 @@ npm pack --dry-run --json
 git diff --check
 ```
 
-原生集成命令会安装锁定的 `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture，并要求五个原生往返用例全部执行且不能跳过；这是 CI 强制原生 Host 集成门禁的本地等价检查。
+原生集成命令会安装锁定的 `@deepseek-ai/dsh-session@0.1.7-rc.2` fixture，并要求六个原生集成用例全部执行且不能跳过；这是 CI 强制原生 Host 集成门禁的本地等价检查。
 
-声明的 DSH `>=0.1.0-rc.7` 范围仍以 Host 公开能力为准。发布自动化已通过 Ubuntu 上的 Node.js 18，以及 Ubuntu、macOS 和 Windows 上的 Node.js 24；Node.js 24 矩阵强制运行官方 Host 后端集成（5/5）与打包检查。已安装的 1.4.0 产物也已在 `@deepseek-ai/dsh-session@0.1.5-rc.2` 上通过官方 native 闭环（5/5）。现有截图来自 v1.3.1，含退役快照界面；它们仍是历史示例，不作为当前行为说明。
+声明的 DSH `>=0.1.0-rc.7` 范围仍以 Host 公开能力为准。发布自动化在 Ubuntu 上测试 Node.js 18，并在 Ubuntu、macOS 和 Windows 上测试 Node.js 24；Node.js 24 矩阵强制运行基于官方 `@deepseek-ai/dsh-session@0.1.7-rc.2` 的 Host 后端集成（6/6）与打包检查，覆盖 v4 会话格式。[截图](../screenshots.json)使用虚构示例聊天展示当前界面。

package/docs/USER_GUIDE.md

@@ -2,7 +2,7 @@
 
 English · [简体中文](USER_GUIDE.zh-CN.md) · [Back to README](../README.md)
 
-Archive Management provides a place to browse and manage DSH's archived chats, plus workspace bulk archiving. This document follows the `main` branch. This guide targets 1.4.4, whose runtime code is unchanged from 1.4.3; package metadata now lists DSH `0.1.7-rc.2` among the verified Hosts. 1.4.3 accepts the v4 session format those Hosts publish. The 1.4.2 export writer no longer carries a dependency that prevents startup on newer Hosts. See the [changelog](../CHANGELOG.md) for release history, including 1.4.1's English rename and feedback improvements. For interfaces and data formats, see the [architecture](ARCHITECTURE.en.md).
+Archive Management provides a place to browse and manage DSH's archived chats, plus workspace bulk archiving. This document follows the `main` branch and targets 1.4.6. This release fixes permanent deletion and Recycle Bin cleanup when historical and current session log generations coexist. See the [changelog](../CHANGELOG.md) for release history. For interfaces and data formats, see the [architecture](ARCHITECTURE.en.md).
 
 ## Understand the three locations
 
@@ -198,7 +198,7 @@ Features depend on public Host capabilities, not just a version number:
 - Version 2 protection records require this or a newer plugin. Before downgrading, restore recycled chats you need to retain and back up plugin data.
 - If `trash.json` cannot be read, Archived is marked unverified, the Recycle Bin is unavailable, and archive mutations such as unarchive, tag/note editing, and deletion are refused instead of guessing.
 
-The declared DSH `>=0.1.0-rc.7` range remains capability-based. Release automation passed Node.js 18 on Ubuntu and Node.js 24 on Ubuntu, macOS, and Windows; the Node.js 24 matrix required the official Host backend integration (5/5) and package checks. The installed 1.4.0 artifact also passed the official native round trip (5/5) against `@deepseek-ai/dsh-session@0.1.5-rc.2`.
+The declared DSH `>=0.1.0-rc.7` range remains capability-based. Release automation tests Node.js 18 on Ubuntu and Node.js 24 on Ubuntu, macOS, and Windows; the Node.js 24 matrix requires the official `@deepseek-ai/dsh-session@0.1.7-rc.2` Host backend integration (6/6) and package checks, including the v4 session format.
 
 ## Local data and uninstall
 

package/docs/USER_GUIDE.zh-CN.md

@@ -2,7 +2,7 @@
 
 [English](USER_GUIDE.md) · 简体中文 · [返回 README](../README.zh-CN.md)
 
-归档管理为 DSH 已归档聊天提供查看和管理页面，并扩展按工作区批量归档。本文跟随 `main` 分支维护。本文适用于 1.4.4，其运行时代码与 1.4.3 相同；包元数据现将 DSH `0.1.7-rc.2` 列为已验证 Host。1.4.3 接受这些 Host 发出的 v4 会话格式。1.4.2 的导出实现不再携带会导致新版 Host 启动失败的依赖；已安装用户请先升级。版本变更见[更新日志](../CHANGELOG.md)，其中包含 1.4.1 的英文名称统一与交互提示优化。接口和数据格式见[架构说明](ARCHITECTURE.md)。
+归档管理为 DSH 已归档聊天提供查看和管理页面，并扩展按工作区批量归档。本文跟随 `main` 分支维护，适用于 1.4.6。本版修复旧版与当前版本会话日志混存时，永久删除及回收站清空失败的问题。版本变更见[更新日志](../CHANGELOG.md)，接口和数据格式见[架构说明](ARCHITECTURE.md)。
 
 ## 先理解三个位置
 
@@ -198,7 +198,7 @@ DSH 运行时约每分钟检查，关闭期间暂停，启动恢复完成后补
 - v2 保护快照需要此版或更新的插件读取；回退旧插件前先恢复需要保留的回收聊天，并备份插件数据。
 - 如果 `trash.json` 无法读取，归档列表会标为未经核对，回收站不可用，并拒绝取消归档、编辑标签备注及删除等归档修改，避免猜测状态。
 
-声明的 DSH `>=0.1.0-rc.7` 范围仍表达基于 Host 公开能力的兼容性。发布自动化已通过 Ubuntu 上的 Node.js 18，以及 Ubuntu、macOS 和 Windows 上的 Node.js 24；Node.js 24 矩阵强制运行官方 Host 后端集成（5/5）与打包检查。已安装的 1.4.0 产物也已在 `@deepseek-ai/dsh-session@0.1.5-rc.2` 上通过官方 native 闭环（5/5）。
+声明的 DSH `>=0.1.0-rc.7` 范围仍表达基于 Host 公开能力的兼容性。发布自动化在 Ubuntu 上测试 Node.js 18，并在 Ubuntu、macOS 和 Windows 上测试 Node.js 24；Node.js 24 矩阵强制运行基于官方 `@deepseek-ai/dsh-session@0.1.7-rc.2` 的 Host 后端集成（6/6）与打包检查，覆盖 v4 会话格式。
 
 ## 本地数据与卸载
 

package/lib/deletion-safety.js

@@ -1,5 +1,5 @@
-import { lstat, realpath } from 'node:fs/promises';
-import { basename, dirname, isAbsolute, normalize, parse, relative, sep } from 'node:path';
+import { lstat, readdir, realpath } from 'node:fs/promises';
+import { basename, dirname, isAbsolute, join, normalize, parse, relative, sep } from 'node:path';
 
 function failure(code, message, status) {
   return Object.assign(new Error(message), { code, status });
@@ -24,13 +24,14 @@ function inside(parent, candidate) {
   return offset === '' || (offset !== '..' && !offset.startsWith(`..${sep}`) && !isAbsolute(offset));
 }
 
-async function checkedStat(path, kind) {
+async function checkedStat(path, kind, allowMissing = false) {
   try {
     const stat = await lstat(path);
     if (stat.isSymbolicLink()) throw unsafe(`${kind} uses a symbolic link or junction`);
     return stat;
   } catch (cause) {
     if (cause?.code === 'session-location-unsafe') throw cause;
+    if (allowMissing && cause?.code === 'ENOENT') return null;
     throw unavailable(`${kind} cannot be inspected`);
   }
 }
@@ -47,15 +48,47 @@ async function checkCanonicalDirectoryAncestry(path, checked) {
   }
 }
 
+// Match the Host's committed generation names, with either physical encoding.
+// Temporary files, v0, leading-zero versions and unsafe integers are not logs.
+function isCommittedLog(filename) {
+  const match = /^session(?:\.v([1-9][0-9]*))?\.jsonl(?:\.zstd)?$/u.exec(filename);
+  return match !== null && (match[1] === undefined || Number.isSafeInteger(Number(match[1])));
+}
+
+async function checkLogLocation(path, directory, allowMissing = false) {
+  const stat = await checkedStat(path, 'session location', allowMissing);
+  if (stat === null) return false;
+  if (!stat.isFile()) throw unsafe('session location is not a regular file');
+  let canonicalPath;
+  try { canonicalPath = await realpath(path); }
+  catch { throw unavailable('session location cannot be canonicalized'); }
+  if (!inside(directory, canonicalPath)) throw unsafe('session location escapes its directory');
+  return true;
+}
+
+async function checkSessionLogs(entry) {
+  if (await checkLogLocation(entry.path, entry.realDirectory, true)) return;
+  // locate() names the current append target even for historical-only or
+  // unmaterialized sessions. Inspect committed logs that actually exist;
+  // an empty directory is still the complete recursive-removal scope.
+  let filenames;
+  try { filenames = await readdir(entry.realDirectory); }
+  catch { throw unavailable('session directory cannot be inspected'); }
+  for (const filename of filenames) {
+    if (isCommittedLog(filename)) await checkLogLocation(join(entry.realDirectory, filename), entry.realDirectory);
+  }
+}
+
 /**
  * Resolve the recursively removable directory for one session. The Host's full
- * current inventory is treated as authority: every listed location must be
- * readable, session-scoped, non-linking, and disjoint from the requested tree.
+ * current inventory is treated as authority: every existing directory must be
+ * session-scoped, non-linking, and disjoint from the requested tree. Existing
+ * logs provide additional evidence, but the current generation may not exist.
  * The returned deletion directory is canonical and its complete ancestry has
  * been checked, so a lexical platform alias or higher link is never passed to
  * recursive removal.
- * A missing requested header is a successful restart state, not permission to
- * infer a path from stale registry data.
+ * Missing headers or directories are successful restart states, not permission
+ * to infer a path from stale registry data.
  */
 export async function resolveExclusiveSessionDirectory(persistence, sessionId) {
   if (!safeId(sessionId)) throw unsafe('session id is not a safe directory name');
@@ -95,30 +128,26 @@ export async function resolveExclusiveSessionDirectory(persistence, sessionId) {
     const parent = dirname(entry.directory);
     const storageRoot = dirname(parent);
     if (storageRoot !== parse(storageRoot).root) {
-      const storageRootStat = await checkedStat(storageRoot, 'storage-root ancestor');
-      if (!storageRootStat.isDirectory()) throw unsafe('storage-root ancestor is not a directory');
+      const storageRootStat = await checkedStat(storageRoot, 'storage-root ancestor', true);
+      if (storageRootStat !== null && !storageRootStat.isDirectory()) throw unsafe('storage-root ancestor is not a directory');
     }
-    const parentStat = await checkedStat(parent, 'session-root ancestor');
-    if (!parentStat.isDirectory()) throw unsafe('session-root ancestor is not a directory');
-    const directoryStat = await checkedStat(entry.directory, 'session directory');
+    const parentStat = await checkedStat(parent, 'session-root ancestor', true);
+    if (parentStat !== null && !parentStat.isDirectory()) throw unsafe('session-root ancestor is not a directory');
+    const directoryStat = await checkedStat(entry.directory, 'session directory', true);
+    if (directoryStat === null) continue;
     if (!directoryStat.isDirectory()) throw unsafe('session directory is not a directory');
-    const fileStat = await checkedStat(entry.path, 'session location');
-    if (!fileStat.isFile()) throw unsafe('session location is not a regular file');
     try {
       entry.realDirectory = await realpath(entry.directory);
-      entry.realPath = await realpath(entry.path);
     } catch { throw unavailable('session location cannot be canonicalized'); }
     await checkCanonicalDirectoryAncestry(entry.realDirectory, checkedCanonicalDirectories);
-    if (!inside(entry.realDirectory, entry.realPath)) throw unsafe('session location escapes its directory');
+    await checkSessionLogs(entry);
   }
 
-  const target = entries.find((entry) => entry.id === sessionId);
+  const target = entries.find((entry) => entry.id === sessionId && entry.realDirectory !== undefined);
   if (target === undefined) return { status: 'missing', sessionDirectory: null };
   for (const entry of entries) {
-    if (entry === target) continue;
-    if (inside(target.realDirectory, entry.realPath)
-      || inside(entry.realDirectory, target.realPath)
-      || inside(target.realDirectory, entry.realDirectory)
+    if (entry === target || entry.realDirectory === undefined) continue;
+    if (inside(target.realDirectory, entry.realDirectory)
       || inside(entry.realDirectory, target.realDirectory)) {
       throw unsafe('session locations overlap');
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-archived-chats",
-  "version": "1.4.4",
+  "version": "1.4.6",
   "description": "查看、搜索和恢复已归档会话，支持按工作区批量归档、备份导入导出与回收站管理。",
   "license": "MIT",
   "author": "Ultronen",
@@ -96,7 +96,7 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.1",
-    "@deepseek-ai/dsh-session": ">=0.1.0-rc.7 <0.1.1-0 || >=0.1.1-rc.1 <0.1.2-0 || >=0.1.2-alpha.1 <0.2.0-0 || 0.1.5-rc.2 || 0.1.7-rc.2",
+    "@deepseek-ai/dsh-session": ">=0.1.0-rc.7 <0.1.1-0 || >=0.1.1-rc.1 <0.1.2-0 || >=0.1.2-alpha.1 <0.2.0-0 || 0.1.5-rc.2 || 0.1.7-rc.2 || 0.2.0-rc.2",
     "react": "^18.2.0"
   },
   "peerDependenciesMeta": {