zn-dk/dsh-session-repair
Session log diagnosis and security repair: raw zstd/JSONL artifact verification, deterministic repair of empty tool-call ID chains, single-slot pre-repair backup and recovery, audit records; Web "session physical examination" panel + read-only diagnostic tool dsh_session_repair; npm dsh-session-repair 0.5.3
dsh-session-repair is a Web plugin for session diagnosis and safe repair: it verifies raw zstd/JSONL session artifacts and classifies health into severity levels — healthy, warning (settled history with unclosed structures — readable, no writable repair offered), repairable (deterministically fixable issues such as empty tool-call ID chains) and blocked (hard conflicts like ID collisions, zstd damage or session mismatch that cannot be auto-fixed). Before any repair it creates trusted checkpoints and pre-repair backups, then applies deterministic fixes — for example the 'identity-loss' family where a gateway emitted an empty id/name on a tool-call delta and every later load throws 'message must have tool source'.
Install
dsh plugin --profile web add dsh-session-repairnpm dsh-session-repair 0.6.2 verified 2026-09-03 (repository field → github.com/Zn-Dk/dsh-session-repair; README EN primary with 中文 edition). Install from npm (recommended): dsh plugin --profile web add dsh-session-repair; from GitHub: dsh plugin --profile web add github:Zn-Dk/dsh-session-repair. Restart dsh web after install and refresh http://127.0.0.1:3080.
Compatibility
DSH Web profile; session logs stored as raw zstd/JSONL artifacts; repair targets the identity-loss failure family (upstream discussion #4365).
Details
- Repo: zn-dk/dsh-session-repair
- Category: Web UI Enhancements
- Stars: 3
- Version: npm dsh-session-repair 0.6.2
- Last push: 2026-08-31
- First seen: 2026-08-22
Recent updates
0.6.2 current on npm (verified 2026-09-03).
FAQ
- When would I need this?
- When a session refuses to load — e.g. after the DeepSeek gateway emitted an empty id/name on a tool-call delta, poisoning persisted history so every load throws 'message must have tool source'.
- Is repair destructive?
- No — diagnostics come first, then trusted checkpoints and pre-repair backups are created before any deterministic fix is applied.
- What do the severity levels mean?
- healthy (no issues), warning (readable but unclosed structures — no writable repair offered), repairable (deterministic fixes exist, e.g. empty tool-call ID chains), blocked (hard conflicts that cannot be auto-fixed, e.g. zstd damage).
Alternatives
dream12347/dsh-session-manager · zimixvx/dsh-archive-manager