@michengai/dsh-archive-manager 1.1.6 → 1.1.8

package/CHANGELOG.md

@@ -4,6 +4,25 @@
 
 Published release notes are retained below; new versions are added without removing earlier entries.
 
+## 1.1.8 - 2026-10-23
+
+- Added primary sidebar navigation entry and dedicated workspace panel: users can now access Archive Manager directly from the first-level sidebar, opening a 960px centered workspace view. The entry can be toggled on or off at any time via the `sidebarEntry` switch in plugin configuration (`plugins.bundle.config` slot).
+- Added toggleable online updates and host-level security locking: added an `onlineUpdate` switch in plugin configuration. Disabling it immediately hides the "Check for updates" button and version badge in the header, and rejects update requests at the endpoint level. Environments requiring security compliance or curated catalog distribution can enforce `updater: false` (or `onlineUpdate: false`) in Cordis patch configuration to disable the updater at startup and lock the UI toggle.
+- Added baseURI dynamic endpoint resolution for reverse proxies: API requests now resolve against document `baseURI` to preserve path prefixes when DSH is hosted under a reverse proxy or subdirectory, preventing 404 errors on update and settings routes.
+- Unified the online feedback button icon to use the host's native `IconEditOutlineRegular`.
+
+## 1.1.7 - 2026-10-22
+
+- Fixed session titles or blank-session visibility changing after disabling Archive Manager (#71). The plugin no longer replaces the official projection-cache table; ordinary cache reads and writes remain host-owned.
+- On activation, hand historical plugin checkpoints back to the official cache after checking session identity. Keep newer same-version official projections and official rows with different projection versions. Failed handoffs can retry on later activation; source cache files are retained.
+- Archive and restore now use the official workspace APIs. Archiving an unknown session reports the official error instead of being skipped, and restore no longer reattaches a session that the workspace no longer lists. The plugin no longer blocks the official workspace update from dropping a member that has no path index.
+- Preserve restore wrappers and validation installed before Archive Manager is enabled, and restore the original method and property descriptor on disable.
+- Batch archive and restore share one serial loop. When one session gets an official error, the list or confirmation card keeps that reason and the rest continue. Successful items are not repeated. Batch delete still uses the official scoped call.
+- Batch results no longer show a permanent zero for unprocessed items. The retry count is the failed items, so the organizer summary matches the retry button.
+- Keep only the tombstones and in-flight write barrier needed for permanent deletion. Disabling removes those guards without closing the official cache service. The barrier tracks only tasks that entered through the guards; official cache writes started before activation cannot be reliably drained and may leave an orphan cache row after disabling in an exceptional interleaving. Closing this gap requires host-side write-drain support.
+- Session repair parses individual Zstandard frames using an explicit boundary scanner, ensuring reliable single-frame header extraction and verification across Node 24.22+ and earlier versions.
+- Upgrade note: users who disabled an older version must activate the fixed version at least once to hand off old records. Keys rejected by the official backend, such as IDs containing colons, remain in the legacy domain and return to native host behavior instead of receiving a replacement cache.
+
 ## 1.1.6 - 2026-10-19
 
 - Fixed the "Archive all conversations" action appearing in a single session's action menu. The workspace menu context is now recorded only from workspace rows and cleared by session rows, other rows, or empty areas, so a stale workspace binding can no longer leak into a session menu.

package/CHANGELOG.zh-CN.md

@@ -4,6 +4,25 @@
 
 以下发布说明会持续保留；新增版本时不再删除较早记录。
 
+## 1.1.8 - 2026-10-23
+
+- 新增主侧边栏直接导航入口与工作区主面板：支持在主界面一级侧边栏展示归档管理器图标入口，点击可直接切换至专属工作区主面板（960px 居中版心与独立滚动容器）；可在插件详情页（`plugins.bundle.config` 槽位）随时开启或关闭 `sidebarEntry` 开关。
+- 新增在线更新控制开关与宿主安全锁定：详情页新增「在线更新」原生开关，关闭后即时隐藏标题区「检查更新」按钮与版本提示徽标，并阻断更新请求；支持面向精选索引或企业合规环境在 Cordis 配置文件中声明 `updater: false`（或 `onlineUpdate: false`）硬锁定，启动时强制禁用且界面开关自动置灰。
+- 支持反向代理与带路径前缀部署：前端 API 请求统一基于页面 `baseURI` 解析动态基准地址，完美适配反向代理路径前缀与二级目录部署，避免反代环境下更新与设置接口 404。
+- 设置页标题栏的在线反馈按钮统一对齐宿主原生 `IconEditOutlineRegular` 图标。
+
+## 1.1.7 - 2026-10-22
+
+- 修复停用归档插件后会话标题或空白会话显示异常的问题（#71）：插件不再替换官方投影缓存表，日常读写始终由宿主负责。
+- 启用修复版时，将历史插件缓存按会话身份核验后交接至官方缓存；保留官方更新的同版本投影，不覆盖不同投影版本，失败可在后续启用时重试，旧缓存原文件不删除。
+- 归档和恢复改走官方工作区接口。未知会话归档会按官方结果报错，不再静默跳过；恢复不再把已不在工作区记账里的会话按目录挂回去。官方改工作区时丢掉没有路径索引的成员，插件不再拦截。
+- 恢复会话保留启用归档插件前已有的包装和校验，停用后还原原方法及属性描述符。
+- 批量归档和恢复共用同一条串行循环。某一条遇到官方报错时，列表或确认卡片留下这条原因，并继续处理后面的会话；已成功的不会重做。批量删除仍走官方一次作用域接口。
+- 批量结果不再显示恒为零的「未处理」。失败项用重试数量表示，整理面板的计数与重试按钮一致。
+- 保留永久删除所需的墓碑和在途写入屏障，停用只撤回这些守护，不关闭官方缓存服务。屏障仅跟踪经过守护入口的任务；启用前已启动的官方缓存写入无法被可靠排空，极端时序下停用后仍可能留下孤儿缓存行，该缺口需要宿主提供写入排空能力。
+- 会话修复使用显式帧边界扫描解析单帧 Zstandard 数据，确保在 Node 24.22+ 及更早版本下均能可靠提取首帧头部并完成工件校验。
+- 升级说明：曾停用旧版的用户需要至少启用一次修复版以完成交接。官方后端不接受的缓存 key（如含冒号的 ID）保留在旧域，恢复宿主原生行为，不再额外接管。
+
 ## 1.1.6 - 2026-10-19
 
 - 修复单条会话的操作菜单错误出现「归档全部会话」的问题：工作区菜单上下文现在只从工作区行记录，点击会话行、其他行或空白区域会立即清空，避免复用上一次的工作区绑定。

package/README.md

@@ -95,6 +95,39 @@ dsh plugin --profile web add @michengai/dsh-archive-manager@latest --registry=ht
 
 Restart DSH Web, then hard-refresh your browser with `Ctrl+Shift+R`. Open **Settings → Archived sessions** to get started.
 
+- **Reverse proxy deployment**: Supports hosting DSH behind prefix-stripping reverse proxies (e.g. `/app/dsh/`). API and update endpoints automatically resolve against the page base URI (`document.baseURI`), preventing 404 errors caused by lost prefix segments.
+
+## Plugin Configuration & Toggles
+
+The plugin follows standard DSH bundle configuration conventions. Options are located at:
+> **Sidebar → Plugins → Click `@michengai/dsh-archive-manager`** (the host's `plugins.bundle.config` slot).
+
+Two native switches are available. Their values are persisted in `archive-manager/settings.json` under your local configuration directory and survive restarts; they are not two equivalent Cordis YAML options. `sidebarEntry` is managed through this UI, while `onlineUpdate` is also subject to the host lock described below:
+
+### 1. Sidebar Entry (`sidebarEntry`)
+- **Default**: Disabled (`false`)
+- **Description**: Displays a persistent **Archived sessions** navigation icon in the host's left primary sidebar.
+- **Effect**:
+  - When enabled, clicking the sidebar icon opens the Archive Manager directly in the primary workspace with a **960px centered container** (matching host plugin manager conventions). This eliminates vertical scrolling constraints in narrow settings dialogs;
+  - When disabled, unregisters the sidebar entry cleanly (and resets active panel gracefully if currently viewing the panel, preventing blank views);
+  - The standard **Settings → Archived sessions** view remains active either way, and state is synchronized live across both entry points.
+
+### 2. Online Updates (`onlineUpdate` / `updater`)
+- **Default**: Enabled (`true`)
+- **Description**: Controls whether the plugin checks for and installs updates from npm.
+- **Effect**:
+  - **Dynamic UI Sync**: Disabling the toggle hides the **Check for updates** button and version badge in the header immediately without requiring a full page reload;
+  - **Endpoint Guard**: When disabled, the update API route returns `HTTP 403` for all check and install requests, preventing unreviewed updates;
+  - **Host / Platform Lock**: For curated plugin indexes (such as VibeDev) or restricted enterprise environments, this can be locked directly via Cordis configuration (bundle patch) without needing UI interaction:
+    ```yaml
+    - insert:
+        - id: ui-workspace-archive-manager
+          name: '@michengai/dsh-archive-manager'
+          config:
+            updater: false # or onlineUpdate: false
+    ```
+    Once configured, the updater is disabled at startup, the update action stays hidden, and the online-update switch is disabled. The host lock takes precedence over the user's choice in settings.json and cannot be lifted through the UI. Removing the host lock restores the saved user preference.
+
 ## Usage
 
 | Goal | Action |
@@ -125,7 +158,7 @@ Compact project groups can be collapsed. Stars and restore/archive icons appear
 
 - Use the star on either tab and the **Favorites only** dropdown to find important chats. Favorites persist on the host across archive, restore, and browser changes. Reopen management to see changes made in other pages. Unknown or unreadable sessions retain their stored favorite IDs; cleanup requires confirmed artifact absence.
 - On Unarchived, enter 1–36,500 whole idle days and preview candidates under the current filters. Deselect individual candidates before confirmation. Favorites, the current chat, running sessions (including subagents), and pending interactions are protected; sessions without a valid activity time are excluded.
-- Archive rechecks favorites and activity. Batch archive, restore, and delete report successful, skipped, failed, and remaining items; the first failure stops the batch. Retry only the remainder. Delete retries still require confirmation.
+- Archive rechecks favorites and activity. Batch archive, restore, and delete report progress plus successful, skipped, and failed counts. A failure does not stop the rest; retry only the failed items. Delete retries still require confirmation.
 - **Undo this archive** restores sessions archived by the current batch, including successful retries. It is available only while the current management page remains open; refreshing or closing clears it. Permanent deletion cannot be undone.
 - Favorites can still be archived manually. Protection applies to idle cleanup only. There is no scheduled or automatic background cleanup.
 
@@ -161,6 +194,12 @@ dsh --profile web --dump-config
 
 The configuration should include `ui-workspace-archive-manager` and must not disable official `workspace` or `session-projection-cache`. A leftover `archive-manager-host` override can be removed. On current DSH hosts the official `ui-settings-unarchive-sessions` entry is gone, so this plugin no longer disables it (doing so only warned that the patch entry was missing). If your profile's `cordis.patch.yml` still disables `workspace`, `session-projection-cache`, or `ui-workspace`, remove those overrides and restart.
 
+### Does disabling the fixed version lose session titles?
+
+The fixed version no longer takes over the official projection-cache table. On activation it checks session identity and hands compatible historical plugin checkpoints back to the official cache, retaining the original cache files. **If you disabled an older version, activate the fixed version at least once to perform this handoff**; replacing the package while it stays disabled cannot run the migration.
+
+Failed handoffs can retry on later activation. Keys rejected by the official backend, such as session IDs containing colons, remain in the old plugin domain rather than being forced into the official cache. Those sessions return to native host cache behavior; their conversation logs are not deleted. See the [changelog](CHANGELOG.md) for details.
+
 ### How is archiving different from deletion?
 
 Archiving puts a conversation away so you can restore it later. **Permanent deletion cannot be undone** and may also remove that session's attachments. It does not delete your project working directory. Deletion requires confirmation.

package/README.ru.md

@@ -125,7 +125,7 @@ dsh plugin --profile web add @michengai/dsh-archive-manager@latest --registry=ht
 
 - Используйте звезду на любой вкладке и выпадающий список **Только избранное**, чтобы найти важные чаты. Избранное сохраняется на хосте при архивировании, восстановлении и смене браузера. Переоткройте управление, чтобы увидеть изменения, сделанные на других страницах. Неизвестные или нечитаемые сессии сохраняют свои сохранённые ID избранного; очистка требует подтверждённого отсутствия артефакта.
 - На вкладке **Незаархивированные** введите 1–36 500 целых дней в поле **Дни простоя** и просмотрите кандидатов при текущих фильтрах. Снимите отдельных кандидатов перед подтверждением. Избранное, текущий чат, запущенные сессии (включая субагентов) и ожидающие взаимодействия защищены; сессии без корректного времени активности исключаются.
-- Архив повторно проверяет избранное и активность. Пакетное архивирование, восстановление и удаление сообщают об успешных, пропущенных, неудачных и оставшихся элементах; первый сбой останавливает пакет. Повторяйте только оставшиеся элементы. Повторное удаление всё равно требует подтверждения.
+- Архив повторно проверяет избранное и активность. Пакетное архивирование, восстановление и удаление показывают ход и число успешных, пропущенных и неудачных элементов. Ошибка одной записи не останавливает остальные; повтор затрагивает только неудачные. Повторное удаление всё равно требует подтверждения.
 - **Отменить эту архивацию** восстанавливает сессии, архивированные текущим пакетом, включая успешные повторы. Доступно, пока открыта текущая страница управления; обновление или закрытие очищает его. Постоянное удаление отменить нельзя.
 - Избранное всё ещё можно архивировать вручную. Защита относится только к очистке неактивных. Плановой или автоматической фоновой очистки нет.
 
@@ -161,6 +161,12 @@ dsh --profile web --dump-config
 
 В конфигурации должен присутствовать `ui-workspace-archive-manager`, и он не должен отключать официальные `workspace` или `session-projection-cache`. Оставшийся override `archive-manager-host` можно удалить. В текущих хостах DSH официальной записи `ui-settings-unarchive-sessions` уже нет, поэтому плагин больше её не отключает (иначе dump-config предупреждает, что запись патча не найдена). Если `cordis.patch.yml` вашего профиля всё ещё отключает `workspace`, `session-projection-cache` или `ui-workspace`, удалите эти override и перезапустите.
 
+### Сохраняются ли названия после отключения исправленной версии?
+
+Исправленная версия больше не заменяет официальную таблицу кэша проекций. При включении она проверяет идентичность сессии и переносит совместимые старые записи плагина в официальный кэш, сохраняя исходные файлы. **Если старая версия была отключена, исправленную версию нужно включить хотя бы один раз для переноса**; замена пакета в отключённом состоянии не запускает миграцию.
+
+Неудачный перенос можно повторить при следующем включении. Ключи, которые официальный backend не принимает (например, ID с двоеточием), остаются в старом домене плагина. Для этих сессий восстанавливается штатное поведение кэша хоста; журналы разговоров не удаляются. Подробности — в [журнале изменений](CHANGELOG.md).
+
 ### Чем архивирование отличается от удаления?
 
 Архивирование убирает беседу, чтобы позже её можно было восстановить. **Постоянное удаление отменить нельзя** и оно может также удалить вложения этой сессии. Оно не удаляет рабочую директорию вашего проекта. Удаление требует подтверждения.

package/README.zh-CN.md

@@ -99,6 +99,39 @@ dsh plugin --profile web add @michengai/dsh-archive-manager@latest --registry=ht
 
 安装后重启 DSH Web，并按 `Ctrl+Shift+R` 硬刷新浏览器。打开「设置 → 归档会话」即可使用。
 
+- **反向代理部署**：支持将 DSH 部署在带路径前缀的反向代理后面（如 `/app/dsh/`），插件 API 与更新检查端点统一自动按页面基址（`document.baseURI`）相对解析，避免丢失代理路径前缀导致 404。
+
+## 插件配置与可选开关
+
+插件遵循 DSH 官方扩展配置规范，配置项位于：
+> **主界面侧边栏「插件」→ 点击 `@michengai/dsh-archive-manager` 详情页**（对应宿主 `plugins.bundle.config` 槽位）。
+
+此处提供两个原生扁平行开关。界面开关值保存在本地配置 `archive-manager/settings.json` 中，重启后保留；它们不是两个等价的 Cordis YAML 配置项。`sidebarEntry` 只通过此界面管理，`onlineUpdate` 另受下述宿主锁定规则约束：
+
+### 1. 侧边栏入口 (`sidebarEntry`)
+- **默认状态**：关闭（`false`）
+- **功能说明**：在宿主左侧主导航栏增加常驻的 **「归档会话」** 图标入口。
+- **生效效果**：
+  - 开启后，在侧边栏点击即可直达归档中心，并在主工作区以 **960px 居中版心**（对齐官方插件管理规范）展开完整大面板，彻底告别在设置弹窗狭窄视口内滚动的局限；
+  - 关闭后安全注销侧栏槽位（若当前正停留在归档大面板，会自动安全切回默认视图，防止悬空和白屏）；
+  - 无论是否开启侧栏入口，DSH 原有的「设置 → 归档会话」入口始终保留，两处界面数据与操作 100% 实时同步。
+
+### 2. 在线更新 (`onlineUpdate` / `updater`)
+- **默认状态**：开启（`true`）
+- **功能说明**：控制是否允许在线检查并安装归档管理器的新版本。
+- **生效效果**：
+  - **界面联动**：关闭开关后，归档管理面板标题旁的「检查更新」按钮与版本提示徽标将即时隐藏，无需刷新页面；开启后自动恢复展示；
+  - **接口安全拦截**：关闭后，服务端的更新路由对任何版本检查和安装请求均返回 `HTTP 403` 禁用状态，彻底杜绝在插件内安装未审核版本；
+  - **宿主/平台级锁定**：面向精选插件索引（如 VibeDev）或企业安全合规环境，支持直接在 Cordis 配置文件（bundle patch）中声明，无需进入界面手动配置：
+    ```yaml
+    - insert:
+        - id: ui-workspace-archive-manager
+          name: '@michengai/dsh-archive-manager'
+          config:
+            updater: false # 或 onlineUpdate: false
+    ```
+    配置生效后，更新器在启动时即被禁用，更新入口隐藏，详情页在线更新开关置灰。宿主锁定优先于本地配置中的用户选择，界面不能解除锁定；宿主移除锁定后，重新按已保存的用户选择生效。
+
 ## 使用
 
 | 你想做什么 | 操作 |
@@ -125,7 +158,7 @@ dsh plugin --profile web add @michengai/dsh-archive-manager@latest --registry=ht
 
 - 在已归档或未归档会话行右侧点击星标，通过收藏下拉菜单中的「只看收藏」找回重要会话。收藏保存在宿主数据中，归档、恢复或更换浏览器不会清除；其他页面修改的收藏可在重新打开管理页后读取。
 - 在「未归档」设置 1～36500 的整数闲置天数，结合当前项目、搜索、日期和收藏筛选，点击「预览闲置归档」。确认清单允许逐条取消，默认排除收藏、当前打开、正在执行（含子代理）以及等待交互的会话；缺少有效最后活动时间的会话不参与。
-- 归档前再次检查收藏和活动状态。批量归档、恢复、删除显示进度与成功／跳过／失败／未处理数量；首个失败后停止，支持只重试剩余项。删除重试仍需确认。
+- 归档前再次检查收藏和活动状态。批量归档、恢复、删除显示进度与成功、跳过、失败数量；某一条失败后继续处理后续，只重试失败项。删除重试仍需确认。
 - 「撤回本次归档」只恢复最近一批实际归档成功的会话，包括该批重试成功的部分。仅在本次打开管理页期间有效，关闭页面或刷新会清除记录；不会撤回原有归档，也不能恢复永久删除的会话。
 - 收藏会话仍可手动归档；收藏保护只针对闲置整理。没有定时自动归档，不会在后台自行整理。
 
@@ -165,6 +198,12 @@ dsh --profile web --dump-config
 
 配置中应包含 `ui-workspace-archive-manager`，且不应再禁用官方 `workspace` 或 `session-projection-cache`。若还留着 `archive-manager-host` 的禁用覆盖，可以删掉。当前 DSH 宿主已无官方 `ui-settings-unarchive-sessions` 入口，本插件不再对其 disable（否则 dump-config 会告警条目不存在）。若 profile 的 `cordis.patch.yml` 仍禁用 `workspace`、`session-projection-cache` 或 `ui-workspace`，请移除这些覆盖，再重启。
 
+### 从旧版升级后，停用时标题还会丢吗？
+
+修复版不再接管官方投影缓存表。启用时会核验历史插件缓存对应的会话身份，并将可接受的记录交接给官方缓存；旧缓存文件保留，不会自动删除。**之前已停用旧版的用户，需要至少启用一次修复版完成交接**，不能只在禁用状态下替换安装包。
+
+交接失败可在后续启用时重试。官方后端不接受的 key（例如含冒号的会话 ID）不会强行迁入，仍保留在旧插件域；这些会话恢复宿主原生缓存行为，不代表其聊天日志被删除。完整边界见[更新日志](CHANGELOG.zh-CN.md)。
+
 ### 归档和删除有什么区别？
 
 归档只是收起会话，可以恢复。**永久删除无法撤销**，并可能一并清理该会话的附件；不会删除你的项目工作目录。删除前会要求确认。

package/lib/api-base.js

@@ -0,0 +1,32 @@
+function pageBaseHref() {
+  const doc = globalThis.document;
+  if (typeof doc === "undefined" || doc === null) return void 0;
+  const raw = doc.baseURI;
+  if (typeof raw !== "string" || raw === "") return void 0;
+  try {
+    const url = new URL(raw);
+    const lastSlash = url.pathname.lastIndexOf("/");
+    const lastSegment = url.pathname.slice(lastSlash + 1);
+    if (/\.(html?|php|aspx?|jsp)$/i.test(lastSegment)) {
+      url.pathname = url.pathname.slice(0, lastSlash + 1);
+    } else if (!url.pathname.endsWith("/")) {
+      url.pathname += "/";
+    }
+    return url.href;
+  } catch {
+    return void 0;
+  }
+}
+function resolveApiUrl(path) {
+  if (typeof path !== "string" || path.charAt(0) !== "/" || path.charAt(1) === "/") return path;
+  const base = pageBaseHref();
+  if (base === void 0) return path;
+  try {
+    return new URL(path.slice(1), base).href;
+  } catch {
+    return path;
+  }
+}
+export {
+  resolveApiUrl
+};

package/lib/archive-organizer.js

@@ -46,18 +46,15 @@ function idleArchiveCandidate(session, { days, now = Date.now(), favorites = /*
 }
 async function runSessionBatch(ids, operate, { onProgress, refresh } = {}) {
   const requested = [...new Set(ids.map(checkedId))];
-  const result = { requested, succeeded: [], skipped: [], failures: [], unprocessed: [], remaining: [], refreshError: null };
+  const result = { requested, succeeded: [], skipped: [], failures: [], remaining: [], refreshError: null };
   const report = () => onProgress?.({ total: requested.length, done: result.succeeded.length + result.skipped.length + result.failures.length, succeeded: result.succeeded.length, skipped: result.skipped.length, failed: result.failures.length });
   report();
-  for (const [index, id] of requested.entries()) {
+  for (const id of requested) {
     try {
       (await operate(id) ? result.succeeded : result.skipped).push(id);
     } catch (error) {
       result.failures.push({ sessionId: id, message: error instanceof Error ? error.message : String(error) });
-      result.unprocessed = requested.slice(index + 1);
-      result.remaining = requested.slice(index);
-      report();
-      break;
+      result.remaining.push(id);
     }
     report();
   }