Resumed Failed For Session...preset standard failed to mount; Stopped Working

[elibroftw]

Apparently this is because of dsh plugin add. I tried to get dsh to add a dsh-web-search-exa plugin. Seems like things broke after restarting.

[xiaoshenming]

dsh plugin add 之后会话打不开，常见不是 preset 本身坏了，而是磁盘上的 session.jsonl.zstd 被某次写入弄脏（seq gap、未知事件类型、或 user/message 缺 id），重启后官方从磁盘恢复就整份拒读。

dsh-session-surgeon 可以先看文件健康，不走官方 history 物化：

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

重启 dsh web，左侧「会话医生」选中那条：

• health 是 seq-gap-* / torn / message-missing-id：默认 dry-run 预览，确认后再 apply（先 .bak.<utc>）。缺 id 只补 id，不丢内容。
• health 是 unknown-type：插件写了官方不认识的事件。我们不会给别人的自定义事件补 ignorable，也不会删行。这时先卸掉那个插件，或把会话目录移出 ~/.dsh/sessions 再开新会话。
• 「preset standard failed to mount」本身是配置/插件挂载问题，修文件救不回 preset。但把坏日志移走或修好之后，Web 往往能重新起来。

把 inspect 输出的 health / issues 贴过来（不要上传整份会话文件）。

[elibroftw]

I had to rename profiles dir to profiles-bak.
Plugins/Cordis patching does not work. How are we supposed to "modify the harness" if plugins themselves bricks the harness.

[xiaoshenming]

Renaming profiles to profiles-bak getting the host up again usually means a plugin failed to mount (Cordis include / preset), not that the session file itself is unreadable.

Two different failures get mixed together here:

1. preset standard failed to mount / plugin tree crash on startup — disable the plugin you just added (you already did this by moving profiles). Surgeon cannot repair a broken plugin.
2. After a plugin did write to a session, restart then history unavailable / seq gap / missing message.id / unknown event type — that is a disk artifact. Inspect first:

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

If health is unknown-type, we still will not stamp ignorable on someone else's event (and as of 0.1.2-alpha.1 that envelope field is gone anyway). Move that one session dir out of ~/.dsh/sessions and open a new chat.

If you paste inspect health / issues (not the raw log), we can tell which of the two you still have.

[denial123789]

I added a two-path triage for this report to an independent recovery guide: https://github.com/sandbaseai/deepseek-harness-handbook/blob/main/docs/en/troubleshooting/invalid-overlay-boot-failure.md

It separates preset ... failed to mount (profile composition) from history unavailable / seq or unsupported-event errors (Session persistence), and warns against renaming the whole profiles directory before preserving hashes and the implicated layer.