@imrascal/dsh-archive
DeepSeek Harness 存档会话管理器：在设置面板中恢复或删除存档会话，并管理回收站。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:imrascal/dsh-archive#9ee5770a0640375519f3e7528db0e6efeedb1efcArchive 以 @imrascal/dsh-archive 发布，当前版本为 0.2.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A DeepSeek Harness (DSH) plugin that manages archived sessions and the trash from the settings panel.
Deletes are reversible: deleting a session moves it to the trash (~/.dsh/trash); only
purge / empty trash are permanent. Live (running) sessions refuse deletion with a clear message.
dsh plugin --profile web add github:imrascal/dsh-archive
Or from a local checkout:
dsh plugin --profile web add file:C:/path/to/dsh-archive
Restart the app after installing (the host half loads at boot), then refresh the page — the section appears under Settings → Archived Sessions.
dsh pluginforwards to pnpm, sopnpmmust be on your PATH.
This feature originally lived as in-box patches across 12 files
(dsh-workspace, dsh-session-persistence-jsonl, dsh-host-apiproxy, dsh-client-runtime,
dsh-client-ui-workspace, ... — reference diffs in patches/). This plugin re-implements
it as a standalone package with a dual-path design:
| Path | When | Behavior |
|---|---|---|
| Native | host/client already carry the archive API | the client calls ctx.workspaces.unarchiveSession / trashList / ... directly — same RPC + store-frame sync as the in-box implementation |
| Fallback | an app update reverted host or client to stock | the host half patches at runtime: adds the trash layer to sessionPersistence and the archive API to workspaceRegistry; the client talks to the plugin's own /dsh-archive/session HTTP route |
So the feature survives app updates: trash data lives in ~/.dsh/trash (data, not code) and the
archive set lives in the workspace registry's persisted state. Whatever the update does to the
packages, the plugin feature-detects at startup and fills in whatever is missing.
dsh/index.js host half: persistence trash layer + registry archive API + /dsh-archive/session route
dsh/client.js browser half: "Archived Sessions" settings section (settings.section slot), no build, react only
cordis.patch.yml bundle mount declaration
patches/ reference diffs for the in-box host patches (the client patches are replaced by this plugin)
scripts/ eval-check.mjs (client factory eval) and host-logic-test.mjs (host backend lifecycle)
If your DSH install already carries the local archive-management patches (as this repo's dev
machine did), the plugin and the in-box patch would register the same archived-sessions section.
To migrate:
node_modules/@deepseek-ai/dsh-client-ui-workspace/lib/client.js to the official
release (drops the embedded ArchivedSessionsSection registration; the host patches may stay —
the plugin detects them and no-ops).To move the host side back to stock as well, back up
~/.dshfirst, reversepatches/, and let this plugin's host half re-add the backend. Trash data and the archive set are unaffected.
~/.dsh/trash/<sessionId>-<timestamp>/, restorable at any time.session-live); the UI explains what to do.0.1.0-rc.5 and later — both the native Web UI (dsh web in a browser) and the
desktop GUI (Electron window), which share the same host services and client bundle./dsh-archive/session.unarchiveSession/deleteSession/ trash*, API-proxy routes, client-runtime methods): every step feature-detects and no-ops; the
client calls the native ctx.workspaces API directly. Service availability is checked per call,
so a service that is provided late (rc.7 gates the registry behind an inject) is picked up
automatically instead of stranding the section on the fallback path.deleteSession is fail-closed: it refuses to run unless the persistence layer is trash-aware,
so the plugin can never drive a stock hard-delete backend (nothing is removed on refusal).@deepseek-ai/cordis 4.x, where reading a
service property off a context (ctx.sessionPersistence) is only allowed when the current fiber
declares it in inject; undeclared reads throw cannot get property "X" without inject. The host
half resolves services through ctx.get(...) and through the patched methods' receiver
(this.ctx, which Cordis shadows to the registry's own fiber) — never through
registry.ctx on a traceable service wrapper, whose ctx property resolves to the caller's
context. On older Cordis 3.x hosts both spellings work; the 0.2.1 path is required on Cordis 4.fs; no platform assumptions).npm install # fetches the @deepseek-ai/cordis devDependency
node scripts/host-logic-test.mjs # host lifecycle: delete → trash → restore → purge → empty → live refusal
node scripts/host-robustness-test.mjs # late service provision + fail-closed delete + route on-demand ensure
node scripts/cordis4-strict-test.mjs # REAL Cordis 4 strict-inject regression (0.2.1: "without inject" fix)
node scripts/eval-check.mjs # client bundle factory eval + apply + slot registration + late-service detection + dual-store resync (0.2.2)
MIT