dsh-session-migration-repair
修复当前构建版本拒绝迁移的旧版 DSH 会话日志（格式 v0）：扫描缺陷、备份、就地修复，并根据真实迁移链进行离线验证。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:zzdhsxk/dsh-session-migration-repair#82e63bd5a10d2cde5ba8f47ccc100ac36cd5534eSession Migration Repair 以 dsh-session-migration-repair 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Repair legacy (format v0) DSH session logs that the current build refuses to migrate: scan → back up → fix → verify offline against the host's own migration chain → write.
English | 中文
Since DSH 0.1.5 a stored session is migrated through v0 → v1 → v2 → v3 on open, and every step is validated strictly. Fields that older builds wrote empty are rejected by the migration chain, surfacing as "history unavailable" for that session. This tool fixes exactly those logs.
Four deterministic defect classes, all auto-repairable:
| Error | Root cause | Fix |
|---|---|---|
released tool-call-chunks row N id and optional name must be strings | streamed tool-call chunk rows carry an empty id (only the first row used to have it) | recover the real id/name from the assistant/chunk tool-call-delta of the same turn|step|index |
assistant/message N message content[k] name must be a non-empty string | tool-call block name is empty (often after an earlier repair tool rewrote the chain) | recover the tool name from the same step's delta |
format v2 assistant/message ... invalid message content kind "tool-call": user/message 0 content[0] id must be a non-empty string | the block-end tool-call block inside assistant/chunk has an empty id (the outer message is misleading) | fill it from the delta as well |
tool/call ... does not match one advertised tool call | tool/call.arguments no longer equals the advertised block's arguments | align both sides, preferring the side free of replacement characters (U+FFFD) |
As a DSH plugin (registers one model-callable tool plus a bundled skill):
dsh plugin --profile web add dsh-session-migration-repair # from npm
dsh plugin --profile web add github:<owner>/dsh-session-migration-repair # from GitHub
# restart dsh web and reload the page
Or use the CLI standalone — zero dependencies, Node ≥ 22.15 (Node 20's node:zlib has no zstd API):
node bin/cli.mjs --help
dsh-session-migration-repair list # list sessions (generation + quarantined files)
dsh-session-migration-repair scan <session-id|path> # read-only diagnosis
dsh-session-migration-repair validate <session-id|path># run the full migration chain offline
dsh-session-migration-repair fix <session-id|path> --yes # backup → repair → verify → write
Options: --dry-run, --no-fix-arguments, --dsh-home <dir>, --dsh-root <dir>, --json.
$DSH_HOME/session-migration-repair/backups/<timestamp>/ and an audit line is appended to audit/repair-log.jsonl.lib/core/zstd.mjs): walks physical frame boundaries (frame and block headers only), decompresses frame by frame and decodes UTF-8 once — concatenating per-chunk decodes corrupts multi-byte characters that straddle a boundary.assistant/chunk tool-call-delta carrying the real id and tool name, so every empty field can be recovered.sessionFormatCatalog.createRestore(); this tool drives it, so the verdict matches what the server would do — no restart-and-click loops..corrupt-* quarantined backups) can be repaired; a session directory removed with rm -rf is unrecoverable.fix refuse to write.node --test test/*.test.mjs # unit tests
DSH_REAL_V0_LOG=/path/to/defective.jsonl.zstd node --test test/*.test.mjs # regression on a real log
MIT