[BUG]昨天正常使用完关闭后就无法再次打开

[lwz2233]

npm命令打开harness时出现无法正常加载工作区报错C:\Users\lenovo>npx @deepseek-ai/dsh web
file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-app-boot/lib/index.js:1187
throw new Error(${binName}: ${stage}: ${detail}${stack}, { cause });
^

Error: dsh: plugin tree failed to load: failed to apply loader entry include (cordis:include): failed to apply loader entry workspace (@deepseek-ai/dsh-workspace): corrupt Zstandard session log: first frame is not exactly one header line
Error: corrupt Zstandard session log: first frame is not exactly one header line
at assertZstdHeaderFrame (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:742:86)
at Proxy.readFirstZstdLine (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:1307:5)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Proxy.listArtifacts (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:1078:49)
at async Proxy.list (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:1038:11)
at async [cordis.init] (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-workspace/lib/index.js:324:65)
at async Fiber._reload (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis/lib/index.js:1355:5)
at async Fiber.await (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis/lib/index.js:1399:24)
at async Entry._start (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:528:4)
at async Entry._init (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:517:4)
at boot (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-app-boot/lib/index.js:1187:9)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async runProfile (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh/lib/profile-boot-DG5t9aNs.js:247:14)
at async file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh/lib/bin.js:133:3 {
[cause]: Error: failed to apply loader entry include (cordis:include): failed to apply loader entry workspace (@deepseek-ai/dsh-workspace): corrupt Zstandard session log: first frame is not exactly one header line
at updateError (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:299:9)
at Entry._init (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:519:10)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
[cause]: Error: failed to apply loader entry workspace (@deepseek-ai/dsh-workspace): corrupt Zstandard session log: first frame is not exactly one header line
at updateError (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:299:9)
at Entry._init (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:519:10) {
[cause]: Error: corrupt Zstandard session log: first frame is not exactly one header line
at assertZstdHeaderFrame (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:742:86)
at Proxy.readFirstZstdLine (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:1307:5)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async Proxy.listArtifacts (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:1078:49)
at async Proxy.list (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-session-persistence-jsonl/lib/index.js:1038:11)
at async [cordis.init] (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/dsh-workspace/lib/index.js:324:65)
at async Fiber._reload (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis/lib/index.js:1355:5)
at async Fiber.await (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis/lib/index.js:1399:24)
at async Entry._start (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:528:4)
at async Entry._init (file:///C:/Users/lenovo/AppData/Local/npm-cache/_npx/1e7f6d9597241db0/node_modules/@deepseek-ai/cordis-plugin-loader/lib/index.js:517:4)
}
}
}

Node.js v24.16.0

[denial123789]

This startup stack is the physical-framing branch of Session recovery, not evidence that the launcher or every profile is broken. The outer plugin tree failed to load identifies the workspace loader; the inner corrupt Zstandard session log: first frame is not exactly one header line identifies the persisted artifact boundary.

A safe triage order is:

1. stop every DSH writer;
2. copy and hash the complete Session directory;
3. isolate only the named corrupt Session;
4. restart and verify healthy Sessions return;
5. keep the original bytes for a format-aware repair or upstream report.

Do not delete the whole profile, broadly clear the cache, or recompress the file into one frame: those actions can destroy the comparison and hide unrelated healthy Sessions. The handbook now includes the Windows startup case and the full framing/sequence/identity/read-state matrix here: https://sandbaseai.github.io/deepseek-harness-handbook/session-history-recovery.html

Disclosure: I maintain this independent handbook with SandBase; it is not an official DeepSeek AI project.

[lwz2233]

Thank you very much. After isolating the last two sessions, Harness can run normally.

[xiaoshenming]

隔离坏会话让 Harness 起来，这步是对的。first frame is not exactly one header line 说明至少有一份 session.jsonl.zstd 的物理帧已经不是官方布局（常见于用普通 zstd 整文件重压，或写到一半撕了 header 帧）。

dsh-session-surgeon 可以在 Web 被坏日志卡住时，另开扫 header / inspect，不必先让官方 listArtifacts 物化：

dsh plugin --profile web add "github:xiaoshenming/dsh-session-surgeon#main"

或 CLI：npx --yes github:xiaoshenming/dsh-session-surgeon scan。

• header 帧还能解、后面是 seq gap / torn tail / 缺 message.id → dry-run 再 apply。
• 第一帧已经不是「恰好一行 header」→ 我们拒绝自动修，避免越修越坏。保留你隔离出来的目录，不要删、不要再单帧重压。

不要清整个 profile / npm cache 来「修复」——那会把健康会话一起弄没。