dsh-chat-manager-wide 1.4.0

package/AGENTS.md

@@ -0,0 +1,127 @@
+> **Fork note.** This is the `dsh-chat-manager-wide` fork. Every command and package spec in this
+> document already points at `dsh-chat-manager-wide@1.4.0`. Do not install it next to the
+> original `dsh-chat-manager` in one profile.
+
+# Agent installation guide
+
+Use this guide when a user explicitly asks an Agent to install, update, verify,
+or remove `dsh-chat-manager-wide` in a selected DeepSeek Harness profile.
+
+## Safety and responsibility boundary
+
+- Confirm the target DSH installation and profile. Use `web` only when it is the user's target.
+- Use the fixed `dsh-chat-manager-wide@1.4.0` package below; never substitute a moving branch or an
+  unreviewed source.
+- Do not print session contents, full profile files, transcript paths, credentials, or other private data.
+- Do not start, stop, or restart DSH without explicit permission.
+- Preserve all sessions, unrelated plugins, and user-owned profile changes.
+- Never delete a session as an installation test unless the user explicitly selects a disposable session
+  and confirms the destructive test.
+- Prefer one durable user installation over disposable copies under `LocalAppData\Temp`. If more than one
+  durable DSH installation remains, ask which installation is the target before changing it.
+
+Permanent deletion is irreversible. The Agent must not claim that this plugin provides secure erasure:
+external attachments, caches, logs, backups, cloud copies, and non-JSONL stores are outside its scope.
+The user is responsible for authority to delete the selected data and for applicable retention or privacy
+requirements. A cancelled confirmation is the safe default and must not send a delete request.
+
+## Fixed package and standard bundle
+
+The `dsh-chat-manager-wide` package is a standard DSH bundle (a fork of `dsh-chat-manager` 1.3.4) with a `dsh.bundle` profile patch. Its exact package spec is:
+
+```text
+dsh-chat-manager-wide@1.4.0
+```
+
+The bundle disables the official workspace row while installed and inserts a uniquely identified native
+workspace row. Removing `dsh-chat-manager-wide` removes that layer, allowing DSH to restore the official
+workspace row. Do not install the tarball under `@deepseek-ai/dsh-client-ui-workspace`; that old aliasing
+approach is not the v1.3.4 contract. The product is shown to users as **DSH Chat Manager**.
+
+## Detect the target DSH
+
+Use read-only filesystem checks to locate the requested target. On Windows:
+
+```powershell
+Get-Command dsh -ErrorAction SilentlyContinue
+Get-Command npx -ErrorAction SilentlyContinue
+```
+
+DSH-Portable exposes the same standard `dsh plugin` contract. Missing system pnpm is normal; do not
+install it globally just for this plugin.
+
+`dsh plugin ... list` is not strictly read-only. Its first invocation may initialize or migrate a Portable
+profile, rebuild dependency links, or update profile package-manager metadata. It is non-destructive to
+session contents, but an Agent must not describe it as a filesystem read-only check. If attribution matters,
+record the selected profile's relevant metadata before invoking it, without printing secrets.
+
+## Install or update
+
+With an existing `dsh` command, run exactly:
+
+```sh
+dsh plugin --profile web add dsh-chat-manager-wide@1.4.0
+```
+
+Use the same `add` command to update or repair. The DSH CLI owns target selection, dependency resolution,
+profile locking, and bundle composition; this plugin does not ship a second Windows installer.
+
+After a successful configuration change, ask for permission before restarting DSH. A successful CLI exit
+alone is not runtime acceptance.
+
+## Acceptance
+
+First verify the selected profile without exposing its contents:
+
+```sh
+dsh plugin --profile web list dsh-chat-manager-wide --depth 0
+```
+
+1. The `dsh-chat-manager-wide` bundle appears exactly once in the requested profile.
+2. Its direct package spec is the fixed `dsh-chat-manager-wide@1.4.0` npm version above.
+3. The profile contains the bundle patch and no duplicate official workspace row from this plugin.
+4. No unrelated dependency, profile patch, or session data was changed by the operation.
+
+With permission to restart DSH, verify the live UI in dark mode:
+
+1. The sidebar header contains an archive action that opens **Archived sessions**.
+2. The archive manager lists archived sessions, filters by name or workspace, and can search archived
+   user/assistant conversation content without exposing another session.
+3. Restoring a disposable archived session returns it to its original workspace position without reloading the page.
+4. The selected session's native actions menu contains **Archive session** and the red **Delete session** action.
+5. Opening Delete shows the target session name and a second confirmation.
+6. Selecting **Cancel** closes the dialog, sends no delete request, and leaves the session visible.
+7. A destructive check is allowed only with a disposable test session explicitly selected by the user.
+8. After confirming that disposable session, verify it disappears in place without reloading the whole DSH page.
+
+For source-checkout UI acceptance, the non-destructive smoke test is:
+
+```sh
+pnpm smoke:ui -- --url http://127.0.0.1:14171 --session "Exact session title"
+```
+
+The title must identify the intended session. The runner must only open the dialog and cancel it; it must
+not send a deletion request or manage the DSH process.
+
+## Uninstall
+
+For a standard profile:
+
+```sh
+dsh plugin --profile web remove dsh-chat-manager-wide
+```
+
+Uninstall removes only this plugin's bundle layer. It must not delete sessions and must not restart DSH
+without permission. After the command, verify that `dsh-chat-manager-wide` is absent and that the
+official workspace row is available again after the next permitted DSH restart.
+
+## Failure handling
+
+Distinguish command discovery, network, HTTP/TLS, package-manager, profile-conflict, version, and
+peer-dependency failures. Do not disable TLS validation, delete a profile, replace unrelated packages,
+or claim success from an exit code alone.
+
+On failure, report the sanitized command error, DSH version, selected profile, requested plugin version,
+what changed, rollback state, and what remains unverified. Do not attempt an irreversible session deletion
+as a recovery step. If the bundle was added but verification failed, stop and obtain permission before any
+further profile change.

package/CHANGELOG.md

@@ -0,0 +1,48 @@
+# Changelog
+
+## 1.4.0
+
+Fork of [`dsh-chat-manager@1.3.4`](https://www.npmjs.com/package/dsh-chat-manager) by WSL043.
+
+### Changed — archived sessions dialog
+
+* The archive manager dialog is now full width (`min(1120px, 100%)`) instead of the shared `Modal`
+  default of 380 px, and it lays out as a master/detail browser:
+  * left pane: search box plus the archived session list; a row is selectable, and every row keeps
+    its Restore / Delete actions;
+  * right pane: the complete current user/assistant transcript of the selected archived session,
+    with role labels, timestamps, internal scrolling, a message count and a "copy conversation"
+    action.
+* The dialog injects its own stylesheet (`#dcm-archive-style`) instead of relying on the workspace
+  client's CSS modules, so the layout survives upstream style drift.
+
+### Added — archived conversation reads
+
+* Host route `POST /plugins/dsh-session-delete/archive-detail`
+  (`readArchivedSessionDetail` in `src/host/archive-manager.mjs`) returns one archived session's
+  transcript. It re-checks archive membership, reads only `user/message` and `assistant/message`
+  events on the `current` surface through `sessionQuery.filterEvents`, and clamps the payload
+  (4000 messages, 40000 characters per message, 4 MiB of text in total).
+* `scripts/build-client-local.mjs` rebuilds `lib/client.js` from the
+  `@deepseek-ai/dsh-client-ui-workspace` client that the local DSH installation serves, for
+  installations without the pinned upstream fixture devDependencies.
+
+### Changed — packaging
+
+* Renamed to `dsh-chat-manager-wide`. The browser module id is now derived from `package.json#name`
+  instead of being hard-coded, so a future rename only touches `package.json` and
+  `cordis.patch.yml` before a rebuild.
+* The composed bundle carries an upstream-attribution header. Upstream's own artifact notice sits
+  ahead of `factory: (require) => {` and was dropped by the bundle extractor, so a published fork
+  shipped without it.
+* Upstream `author` / `repository` / `bugs` / `homepage` metadata was removed so a fork does not
+  advertise upstream's coordinates.
+* `npm run build` keeps the upstream fixture-based build; `npm run build:local` builds from the
+  installed DSH client.
+
+### Limitations
+
+* The transcript contains user and assistant messages only — no tool calls, reasoning blocks or
+  subagent traffic.
+* The custom dialog is only used when the host exposes no official `archived-sessions` settings
+  section; where one exists (DSH-Portable) the plugin still delegates to it.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 WSL043
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/PUBLISH.md

@@ -0,0 +1,167 @@
+# Publishing `dsh-chat-manager-wide`
+
+This directory is a complete, publishable source tree. The working copy you were given was extracted
+from the installed plugin, so `lib/client.js` already contains the fork's UI.
+
+## 0. Before the first publish
+
+1. **Fill in your own package metadata.** `package.json` has no `author`, `repository`, `bugs` or
+   `homepage` on purpose — a fork must not advertise upstream's coordinates. Add yours.
+2. **Rebrand the remaining upstream links in `README.md` and `README.en.md`.** The top badges, the
+   screenshot `raw.githubusercontent.com/WSL043/...` URLs and the issue-form links still point at
+   upstream's repository. The screenshots also still show the old narrow dialog, so replacing them
+   with your own captures is worth doing.
+3. **Publish to npmjs.org, not to your mirror.** `~/.npmrc` on this machine sets
+   `registry=https://registry.npmmirror.com`, which is a read-only mirror — publishing there fails.
+   `package.json` therefore pins `publishConfig.registry` to `https://registry.npmjs.org/`, which npm
+   applies at publish time only; installs keep using the mirror. Log in to the canonical registry
+   explicitly:
+   ```sh
+   npm login --registry https://registry.npmjs.org
+   npm whoami --registry https://registry.npmjs.org
+   ```
+4. **Check the name is free** against that registry:
+   ```sh
+   npm view dsh-chat-manager-wide version --registry https://registry.npmjs.org
+   ```
+   `E404` means the name is available — it was free when this tree was prepared.
+5. **Put it in git:**
+   ```sh
+   git init
+   git add .
+   git commit -m "dsh-chat-manager-wide 1.4.0"
+   git remote add origin <your repository>
+   git push -u origin main
+   ```
+
+**2FA is mandatory for the write.** An account with two-factor authentication that logs in through the
+browser flow (`Logged in on https://registry.npmjs.org/`) can still be refused at publish time:
+
+```text
+npm error code E403
+npm error 403 403 Forbidden - PUT https://registry.npmjs.org/<name> - Two-factor authentication or
+granular access token with bypass 2fa enabled is required to publish packages.
+```
+
+That is the registry asking for a second factor on the write, not a problem with the package. If npm
+does not prompt for a one-time password (as in the run above), the login session token cannot be used to
+publish; pick one of:
+
+* **One-off — pass a fresh code.** `npm publish --otp=<6 digits>` with the code from the authenticator
+  app registered on npmjs.com. Codes expire in about 30 seconds.
+* **Durable — a Granular Access Token with *Bypass 2FA*.** On npmjs.com:
+  *Access Tokens → Generate New Token → Granular Access Token*; enable **Bypass 2FA**, set
+  *Permissions* to **Read and write**, and *Packages* to **All packages** — a package-scoped token
+  cannot be created before the package exists. Then store it against the canonical registry only:
+
+  ```sh
+  npm config set //registry.npmjs.org/:_authToken=npm_xxxxxxxxxxxx
+  npm publish
+  ```
+
+  The token lands in `~/.npmrc` under a registry-scoped key, so the npmmirror `registry` setting keeps
+  serving your installs. Never commit it; if you prefer a per-project file, use a git-ignored `.npmrc`.
+
+## 1. Build the client bundle
+
+Two builds exist; both apply the same `patchWorkspaceClient` patches, so both contain the fork.
+
+```sh
+# A) release build — the same dual-fixture composition upstream ships
+#    (needs the devDependencies: the pinned @deepseek-ai/dsh-client-ui-workspace fixtures)
+pnpm install
+pnpm run build
+
+# B) no install — patch the workspace client of the DSH you already have installed
+node scripts/build-client-local.mjs
+```
+
+Build B is what produced the current `lib/client.js`; it is the fallback when you have no package
+manager or no network. Build A is preferable for a published release because it keeps the older-host
+compatibility that `compatibility.json` documents.
+
+Whatever you run, the browser module id comes from `package.json#name`. Verify it:
+
+```sh
+node -e "const s=require('fs').readFileSync('lib/client.js','utf8');console.log(s.match(/id: \"[^\"]+\"/)[0])"
+# must print: id: "dsh-chat-manager-wide"
+```
+
+## 2. Dry run, then publish
+
+```sh
+npm pack                    # -> dsh-chat-manager-wide-1.4.0.tgz
+tar -tzf dsh-chat-manager-wide-1.4.0.tgz    # inspect the published file list
+npm publish                 # unscoped name; 1.4.0 is a normal release, so no --tag is needed
+```
+
+`1.4.0` carries no prerelease segment, so npm publishes it to `latest` and a bare
+`dsh plugin --profile web add dsh-chat-manager-wide` resolves to it.
+
+When you later iterate with a prerelease version (for example `1.4.1-next.1`), a bare `npm publish`
+fails with "You must specify a tag using --tag when publishing a prerelease version". Use
+`npm publish --tag next` for a channel, or `--tag latest` when a bare install should resolve to it.
+Note that `--tag next` leaves the package without a `latest` tag, so version-less installs fail until
+you publish a normal release.
+
+Check what actually landed:
+
+```sh
+npm view dsh-chat-manager-wide version dist-tags
+```
+
+## 3. Install it
+
+**Always remove the original first.** Both packages disable the official `ui-workspace` row and each
+inserts its own workspace row, and both register the same `/plugins/dsh-session-delete/*` routes.
+Installing them side by side gives you two workspace sidebars.
+
+```sh
+dsh plugin --profile web remove dsh-chat-manager
+
+# from the registry:
+dsh plugin --profile web add dsh-chat-manager-wide@1.4.0
+
+# or from the tarball, to test before publishing (absolute path or ./relative works):
+dsh plugin --profile web add C:\Users\liang\Desktop\dsh-chat-manager-wide\dsh-chat-manager-wide-1.4.0.tgz
+```
+
+Then **restart DSH** — the host half (`src/`) is loaded at boot, so the archive-detail route does not
+exist until then — and refresh the Web UI for the rebuilt client bundle.
+
+Verify the profile without dumping its contents:
+
+```sh
+dsh plugin --profile web list dsh-chat-manager-wide --depth 0
+```
+
+Acceptance in the UI: the sidebar archive action opens a wide dialog with the archived list on the
+left; clicking a row fills the right pane with that session's conversation.
+
+## 4. Update flow
+
+```sh
+# bump the version in package.json, then
+pnpm run build        # or: node scripts/build-client-local.mjs
+npm publish
+dsh plugin --profile web add dsh-chat-manager-wide@<new version>
+```
+
+`add` with the same name updates in place, exactly like upstream's documented repair flow.
+
+## 5. Rollback
+
+```sh
+dsh plugin --profile web remove dsh-chat-manager-wide
+dsh plugin --profile web add dsh-chat-manager@1.3.4
+```
+
+## Licensing
+
+* `LICENSE` is upstream's MIT license (Copyright (c) 2026 WSL043) and is kept unchanged — MIT
+  requires retaining it.
+* `THIRD_PARTY_NOTICES.md` carries both upstream notices: `dsh-chat-manager` and the
+  `@deepseek-ai/dsh-client-ui-workspace` build that every `lib/client.js` is derived from.
+* The composed bundle starts with an attribution header. Upstream's own artifact notice sat ahead of
+  `factory: (require) => {` and was silently dropped by the bundle extractor, so the fork emits its
+  own.

package/README.en.md

@@ -0,0 +1,151 @@
+> **Fork notice.** `dsh-chat-manager-wide` is a modified fork of
+> [dsh-chat-manager](https://www.npmjs.com/package/dsh-chat-manager) 1.3.4 by WSL043 (MIT):
+> the archived-session dialog is full width and archived conversations can be read in place.
+> See [CHANGELOG.md](CHANGELOG.md) for the delta and [PUBLISH.md](PUBLISH.md) for the release flow.
+> Do **not** install this package and the original `dsh-chat-manager` in the same profile; each one
+> inserts its own workspace row.
+>
+> This is the fork you asked for in the previous session.
+
+> Version 1.3.4: When the official archive section and Portable settings navigation are available, the archive button opens the official page; the adjacent search button retains content search and management. Older hosts retain the existing archive dialog.
+
+> [!NOTE]
+> This is an actively maintained, independently removable DSH plugin. It adds archive browsing, conversation-content search, restore, and safe permanent deletion. If this session workflow is not for you, uninstalling the plugin leaves existing sessions untouched.
+
+<div align="center">
+
+# DSH Chat Manager
+
+Package: `dsh-chat-manager-wide` (a fork of `dsh-chat-manager`). [Awesome DSH listing](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/blob/main/data/plugins/WSL043__dsh-chat-manager.yml) · [Image Viewer](https://github.com/WSL043/dsh-image-viewer)
+
+**Manage DeepSeek Harness chat history from the native sidebar: search archives, restore sessions, and delete safely.**
+
+Archive manager · Conversation search · One-click restore · Safe permanent deletion
+
+[![Release](https://img.shields.io/github/v/release/WSL043/dsh-chat-manager?display_name=tag&style=flat-square)](https://github.com/WSL043/dsh-chat-manager/releases/latest)
+[![Checks](https://img.shields.io/github/actions/workflow/status/WSL043/dsh-chat-manager/ci.yml?branch=main&label=checks&style=flat-square)](https://github.com/WSL043/dsh-chat-manager/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/dsh-chat-manager?style=flat-square)](https://www.npmjs.com/package/dsh-chat-manager)
+[![total npm downloads](https://img.shields.io/npm/dt/dsh-chat-manager?style=flat-square&label=total%20downloads)](https://www.npmjs.com/package/dsh-chat-manager)
+[![DSH](https://img.shields.io/badge/DSH-compatible-2f81f7?style=flat-square)](#compatibility)
+[![License](https://img.shields.io/github/license/WSL043/dsh-chat-manager?style=flat-square)](LICENSE)
+[![Stars](https://img.shields.io/github/stars/WSL043/dsh-chat-manager?style=flat-square&label=stars)](https://github.com/WSL043/dsh-chat-manager/stargazers)
+[![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
+
+[中文](README.md) · [Install](#install) · [Use](#use) · [Safety boundary](#safety-boundary)
+
+</div>
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/WSL043/dsh-chat-manager/main/docs/assets/hero.en.png" alt="DeepSeek Harness chat history and archived session manager with search, restore, and safe permanent deletion">
+</p>
+
+| Recover archives | Search conversations | Delete safely |
+| --- | --- | --- |
+| Open the archive manager from the sidebar and restore hidden sessions | Search archived names, workspaces, and user/assistant conversation content | Keep native second confirmation; running work is stopped safely before local records are removed |
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/WSL043/dsh-chat-manager/main/docs/assets/archive-manager.en.png" width="414" alt="Native DeepSeek Harness archived conversation manager with history search, restore, and permanent deletion">
+  <br><sub>Native interface on DeepSeek Harness 0.1.1-rc.2</sub>
+</p>
+
+## Install
+
+### Standard DSH command
+
+```sh
+dsh plugin --profile web add dsh-chat-manager-wide@1.4.0
+```
+
+When the command finishes, save your work and restart DSH once through its normal workflow so the new
+bundle configuration becomes active.
+
+### Agent installation
+
+Use the fixed-version [AGENTS.md](https://raw.githubusercontent.com/WSL043/dsh-chat-manager/v1.3.4/AGENTS.md).
+It defines installation, update, acceptance, uninstall, and safety boundaries. Do not use the `main`
+branch document as an installation contract.
+
+## Use
+
+### Manage archives
+
+1. Select the archive icon in the sidebar header to open **Archived sessions**.
+2. Browse every archive or search by session name, workspace, and user/assistant conversation content.
+3. Select **Restore** to return a session to its original workspace position. To remove it completely,
+   start the permanent-delete confirmation from the same list.
+
+Archive and restore only change DSH's hidden state; they do not delete conversation history. Content search
+is limited to current user and assistant messages inside archived sessions.
+
+### Delete permanently
+
+1. Open the native actions menu beside the target session in the sidebar.
+2. Choose the red **Delete session** action.
+3. Check the session name and select **Delete permanently** in the confirmation dialog, or select
+   **Cancel** to leave it unchanged.
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/WSL043/dsh-chat-manager/main/docs/assets/confirm-delete.en.png" width="414" alt="DeepSeek Harness safe permanent session deletion confirmation dialog">
+  <br><sub>Permanent deletion cannot be undone; the dialog identifies the target session.</sub>
+</p>
+
+Once active, the plugin reuses DSH lifecycle and session-storage capabilities. If work is still running,
+it is stopped and allowed to settle before the target session is deleted. The session list then
+updates in place without reloading the whole DSH page.
+
+## Safety boundary
+
+> [!WARNING]
+> Permanent deletion cannot be undone. Check the session name before confirming and make a separate backup when needed.
+
+The plugin is responsible for validating and removing only the explicitly confirmed session's dedicated
+directory within DSH's default per-session JSONL store and host lifecycle boundary. DSH currently exposes
+no public session-deletion API. The second confirmation is mandatory; cancelling sends no deletion request.
+
+The following are outside the plugin's deletion scope and are not guaranteed to be removed:
+
+- Other sessions, other plugin data, external attachments, caches, indexes, logs, backups, or cloud/sync copies;
+- Non-JSONL storage or hosts without a safe stop capability; these are refused instead of force-deleted;
+- Additional copies created by the operating system, filesystem, host updates, or third-party sync services.
+
+If the operating system refuses cleanup, the plugin reports that deletion could not be confirmed rather
+than misreporting partial completion as success. You are responsible for having authority to delete the
+target data and for meeting applicable retention, audit, and privacy requirements. This is an unofficial
+community plugin, not affiliated with or endorsed by DeepSeek. It is provided under the [MIT License](LICENSE),
+without warranty.
+
+## Compatibility
+
+<!-- dsh-compatibility -->
+Supports the latest DeepSeek Harness release recorded in the package metadata (`0.1.2-rc.1`).
+<!-- /dsh-compatibility -->
+
+Archive browsing, restore, and content search use DSH's workspace registry and session-query capabilities.
+Permanent deletion supports DSH's default per-session JSONL storage. Installing replaces the native workspace
+list with the session-management version; uninstalling restores DSH's original list.
+
+## Update and uninstall
+
+Install the target npm version with the same standard DSH command. For v1.3.4:
+
+```sh
+dsh plugin --profile web add dsh-chat-manager-wide@1.4.0
+```
+
+Uninstall removes only this plugin's bundle layer and never deletes sessions:
+
+```sh
+dsh plugin --profile web remove dsh-chat-manager-wide
+```
+
+DSH-Portable exposes the same standard `dsh plugin` commands. Restart DSH through its normal workflow
+after installing, updating, or uninstalling so the configuration is recomposed.
+
+## Support and license
+
+Use the [bug report form](https://github.com/WSL043/dsh-chat-manager/issues/new?template=bug-report.yml)
+for reproducible problems or the [feature request form](https://github.com/WSL043/dsh-chat-manager/issues/new?template=feature-request.yml)
+for focused improvements. Report security issues privately as described in [SECURITY.md](SECURITY.md).
+
+MIT. See [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md) for the modified upstream client and its license
+notice.

package/README.md

@@ -0,0 +1,139 @@
+> **Fork 说明。** 本包 `dsh-chat-manager-wide` 是 [dsh-chat-manager](https://www.npmjs.com/package/dsh-chat-manager) 1.3.4(WSL043,MIT)的修改版:
+> 加宽了归档会话弹窗,并新增归档对话正文阅读。变更清单见 [CHANGELOG.md](CHANGELOG.md),
+> 发布流程见 [PUBLISH.md](PUBLISH.md)。
+> 同一个 profile 里**不要**同时安装本包与原版 `dsh-chat-manager`,两者会各自插入一个工作区行。
+>
+> 这是你在上一轮会话里优化出来的分支。
+
+> [!NOTE]
+> 1.3.4：有官方归档设置页且 Portable 支持设置导航时，归档入口优先打开官方页面；旁边的搜索入口保留归档内容搜索与管理。旧环境继续使用原归档弹窗。
+>
+> 这是一个持续维护、可独立卸载的 DSH 插件。它补充归档浏览、聊天内容搜索、恢复与安全永久删除；不喜欢这套会话管理方式时，可以直接卸载，现有会话不会因此被删除。
+
+<div align="center">
+
+# DSH Chat Manager · 聊天与会话管理器
+
+**在 DeepSeek Harness 原生侧边栏中搜索、恢复和安全清理会话。**
+
+插件包名：`dsh-chat-manager-wide`(fork 自 `dsh-chat-manager`,后者原名 `dsh-native-session-manager`)。[Awesome DSH 收录](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin/blob/main/data/plugins/WSL043__dsh-chat-manager.yml) · [图片查看器插件](https://github.com/WSL043/dsh-image-viewer)
+
+归档管理 · 聊天记录搜索 · 一键恢复 · 安全永久删除
+
+[![Release](https://img.shields.io/github/v/release/WSL043/dsh-chat-manager?display_name=tag&style=flat-square)](https://github.com/WSL043/dsh-chat-manager/releases/latest)
+[![Checks](https://img.shields.io/github/actions/workflow/status/WSL043/dsh-chat-manager/ci.yml?branch=main&label=checks&style=flat-square)](https://github.com/WSL043/dsh-chat-manager/actions/workflows/ci.yml)
+[![npm](https://img.shields.io/npm/v/dsh-chat-manager?style=flat-square)](https://www.npmjs.com/package/dsh-chat-manager)
+[![npm 总下载量](https://img.shields.io/npm/dt/dsh-chat-manager?style=flat-square&label=%E6%80%BB%E4%B8%8B%E8%BD%BD%E9%87%8F)](https://www.npmjs.com/package/dsh-chat-manager)
+[![DSH](https://img.shields.io/badge/DSH-compatible-2f81f7?style=flat-square)](#兼容性)
+[![License](https://img.shields.io/github/license/WSL043/dsh-chat-manager?style=flat-square)](LICENSE)
+[![Stars](https://img.shields.io/github/stars/WSL043/dsh-chat-manager?style=flat-square&label=stars)](https://github.com/WSL043/dsh-chat-manager/stargazers)
+[![Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com)
+
+[English](README.en.md) · [安装](#安装) · [使用](#使用) · [安全边界](#安全边界)
+
+</div>
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/WSL043/dsh-chat-manager/main/docs/assets/hero.png" alt="DeepSeek Harness 聊天历史与归档会话管理器，支持搜索、恢复和安全永久删除">
+</p>
+
+| 归档可找回 | 聊天可搜索 | 删除更稳妥 |
+| --- | --- | --- |
+| 从侧边栏打开归档管理器，查看并恢复隐藏的会话 | 按会话名、工作区或用户与助手的聊天内容搜索归档 | 原生菜单保留二次确认；运行中的任务先安全停止，再删除本机会话记录 |
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/WSL043/dsh-chat-manager/main/docs/assets/archive-manager.png" width="414" alt="DeepSeek Harness 原生归档会话管理器，支持聊天历史搜索、恢复和永久删除">
+  <br><sub>DeepSeek Harness 0.1.1-rc.2 中的原生界面</sub>
+</p>
+
+## 安装
+
+### DSH 标准命令
+
+```sh
+dsh plugin --profile web add dsh-chat-manager-wide@1.4.0
+```
+
+安装完成后，保存工作并按 DSH 的正常方式重启一次，使新的 bundle 配置生效。
+
+### 交给 Agent
+
+请使用固定版本的 [AGENTS.md](https://raw.githubusercontent.com/WSL043/dsh-chat-manager/v1.3.4/AGENTS.md)，
+其中写明了安装、更新、验收、卸载和安全边界。不要把 `main` 分支文档当作安装依据。
+
+## 使用
+
+### 管理归档
+
+1. 点击侧边栏标题区域的归档图标，打开 **归档会话**。
+2. 直接浏览全部归档，或按会话名、工作区和用户/助手聊天内容搜索。
+3. 点击 **恢复** 让会话回到原来的工作区位置；需要彻底清理时，可从同一列表进入永久删除确认。
+
+归档和恢复只改变 DSH 的隐藏状态，不删除聊天记录。搜索范围仅限已归档会话中的当前用户与助手消息，
+不会把其他会话或插件数据混入结果。
+
+### 永久删除
+
+1. 打开侧边栏中目标会话右侧的原生操作菜单。
+2. 选择红色的 **删除会话**。
+3. 在确认弹窗中核对会话名称并再次确认 **永久删除**；也可以随时点击 **取消**。
+
+<p align="center">
+  <img src="https://raw.githubusercontent.com/WSL043/dsh-chat-manager/main/docs/assets/confirm-delete.png" width="414" alt="DeepSeek Harness 安全永久删除会话的中文二次确认弹窗">
+  <br><sub>永久删除无法撤销，确认弹窗会明确显示目标会话</sub>
+</p>
+
+插件生效后，删除逻辑复用 DSH 的生命周期和会话存储能力。正在运行的任务会先停止并等待
+收敛，然后删除目标会话；成功后只更新会话列表，不重载整个 DSH 页面。
+
+## 安全边界
+
+> [!WARNING]
+> 永久删除无法撤销。点下确认前，请核对会话名称；需要保留的内容请先另行备份。
+
+本插件的责任范围是：在 DSH 默认逐会话 JSONL 存储和宿主生命周期边界内，验证并移除用户明确
+确认的目标会话独占目录。DSH 当前没有公开会话删除 API；二次确认是强制步骤，取消不会发送删除请求。
+
+以下内容不在本插件的删除范围内，也不保证被清理：
+
+- 其他会话、其他插件数据、外部附件、缓存、索引、日志、备份和云端/同步副本；
+- 非 JSONL 存储或宿主没有安全停止能力的会话；这类情况会拒绝强删并报告未完成；
+- 操作系统、文件系统、宿主更新或第三方同步服务造成的额外副本。
+
+如果系统拒绝清理，插件会报告无法确认删除成功，不会把部分完成误报为成功。删除前请确认
+自己有权处理目标数据，并遵守适用的数据留存、审计和隐私要求。本项目是非官方社区插件，
+与 DeepSeek 无隶属或背书关系；按 [MIT 许可证](LICENSE)提供，不附带担保。
+
+## 兼容性
+
+<!-- dsh-compatibility -->
+支持软件包元数据中记录的最新版 DeepSeek Harness（`0.1.5-rc.1`）。
+<!-- /dsh-compatibility -->
+
+归档浏览、恢复和内容搜索使用 DSH 的工作区注册表与会话查询能力；永久删除适用于 DSH 默认的逐会话
+JSONL 存储。安装后替换为带会话管理功能的原生工作区列表；卸载后恢复 DSH 原有列表。
+
+## 更新与卸载
+
+更新时继续用 DSH 标准命令安装目标 npm 版本。v1.3.4 的命令是：
+
+```sh
+dsh plugin --profile web add dsh-chat-manager-wide@1.4.0
+```
+
+卸载只移除这个插件的 bundle 层，不删除任何会话：
+
+```sh
+dsh plugin --profile web remove dsh-chat-manager-wide
+```
+
+DSH-Portable 同样使用标准的 `dsh plugin` 命令。完成安装、更新或卸载后，按 DSH 的正常方式重启，
+使配置重新组合。
+
+## 支持与许可证
+
+可使用[问题反馈表单](https://github.com/WSL043/dsh-chat-manager/issues/new?template=bug-report.yml)
+提交可复现问题，或使用[功能建议表单](https://github.com/WSL043/dsh-chat-manager/issues/new?template=feature-request.yml)
+说明明确需求；安全问题请按 [SECURITY.md](SECURITY.md) 私下报告。
+
+MIT。修改后的上游客户端及其许可说明见 [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md)。

package/README.zh-CN.md

@@ -0,0 +1,5 @@
+# DSH 聊天管理器
+
+简体中文说明已成为仓库首页，请查看 [README.md](README.md)。
+
+The Simplified Chinese README is now the repository default. See [README.md](README.md).