dsh-doctor

One-command health check for DeepSeek Harness local environments. A zero-dependency implementation of the community-requested "dsh doctor" idea (official Discussions #1719).

Usage

npx github:ciceroyang/dsh-doctor
node doctor.mjs --json                    # checks array
node doctor.mjs --json --envelope         # dsh-doctor/v1 envelope (community contract)
node doctor.mjs --profile <dir>           # target a specific DSH_HOME/directory

Community contract (dsh-doctor/v1)

Aligned with the zoahdev and moonquake2004 implementations (official discussion #1719):

• envelope: { schema, generatedAt, profile, exitCode, summary{pass,warn,fail}, ok, checks:[{name,status,detail}] }
• status literals: pass / warn / fail / skip (r5; the ok literal is retired, the top-level boolean stays ok)
• exit codes: 0 all-pass / 1 any warn / 2 any fail (CLI entry point only, see #1719 r4/r5)
• check-name vocabulary (v1.1 draft, see #1719): node / pnpm / dsh / ds_home / profiles / sessions / log_health / dedupe / port — this implementation already uses the core names
• the node threshold aligns with the repo-declared engines (^22.19.0 || >=24.0.0, root package.json); #2259 asks to propagate it into the published manifests
• vocabulary r5 compatible — drafted by @ciceroyang (this repo), reviewed by @sjh9714 (dsh-win32) and @moonquake2004
• the full frozen spec lives at docs/contract-v1.md (English) / docs/contract-v1.zh.md (中文)

Checks

• node version (>=18 usable; >=22.15 required for historical session-log reading)
• pnpm presence (dsh plugin depends on it)
• dsh on PATH
• DSH_HOME / settings.yaml existence and writability (with sudo-ownership hint)
• profile manifest integrity (per-profile bundle counts, corrupt ones flagged)
• session log count (multi-frame zstd health)
• built-in zstd availability
• port 3080 availability
• duplicate critical packages (multiple dsh-tools/dsh-skill/cordis copies = tool-scheduling crash risk, #1849)
• session-log health sampling (multi-frame zstd frame scan + full decode — the differentiating check)

Every check reports ok / warn / fail with an actionable fix.

Quick answers doctor encodes

• pnpm not found on PATH → npm i -g pnpm (mirror for restricted networks)
• "cannot save confirmation state" toast → settings.yaml not writable, fix ownership
• plugin tree failed to load → locate the entry via --dump-config, verify with a manual node import
• historical sessions unreadable → Node < 22.15 has no built-in zstd

References

• Proposal: official Discussions #1719
• Field guide with real pitfalls: https://github.com/ciceroyang/dsh-report-studio/blob/main/docs/tutorial-zh.md