[Bug] 插件 Config 非 Standard Schema 时抛裸 TypeError 无修复指引，建议提供 dsh doctor 诊断命令

[xx-1-a]

一句话说明问题

插件导出非 Standard Schema 的 Config（如普通对象 {}）时，启动直接抛裸 TypeError: Cannot read properties of undefined (reading 'validate')，无任何指向性提示；PM2 模式下表现为无限重启直到 errored，用户无法定位是哪个插件、为什么。

详情

• 复现步骤：

  1. 开发一个自定义插件，export const Config = {}（普通对象，非 Standard Schema）
  2. 通过 dsh plugin add 装入 web profile
  3. dsh web 启动即崩溃：failed to apply loader entry <id> (dsh-path-open): Cannot read properties of undefined (reading 'validate')，堆栈指向 cordis 内部 resolveConfig（runtime.Config["~standard"].validate(config)），完全看不到"你的 Config 写法不对"这类信息
  4. 若经 PM2 托管，表现为 16~151 次静默重启后 errored

• 实际结果：

  • 报错不指向根因：开发者无法从堆栈判断是自己的插件 Config 不符合规范
  • 没有任何"正确写法"指引（官方写法：import z from '@deepseek-ai/schemastery'; export const Config = z.object({...})）
  • 建议：resolveConfig 对非 Standard Schema 的 Config 抛出带插件名 + 文档链接的 ValidationError

• 预期结果：

  • TypeError 替换为可读错误：plugin "xxx": Config must be a Standard Schema (see docs: ...)，并列出插件名与文件位置
  • 附议：提供 dsh doctor 类诊断命令，一键检查所有已装插件的 Config/依赖/服务名冲突

• 环境：Windows 11 Pro / Node.js v24.16.0 / dsh 0.1.0-rc.6

• 备注：插件 Config = {} 时 resolveConfig 在 cordis/lib/index.js:957 崩溃，可稳定复现

[HenryZ838978]

There's one already. pip install deepseek-harness-cli && dsh doctor --node.

P1-reasoner-skip  reasoner skips reasoning stream on trivial prompts (steerable via CoT hint)
P2-bom            plugin manifests carry no UTF-8 BOM (#2798)
P3-serve          dsh web fence: cross-origin data path is rejected (#2573)
P4-spill          subprocess spill directory writable (spillAll no try/catch)
P5-seqgap         session log has no concurrent-writer seq gap (#2571)

Why the "plugin Config throws raw TypeError" case fits. The five probes above are the current v0.3.0 set (2026-08-18); a P6-plugin-schema for exactly your case is the obvious next probe — the pattern (Standard Schema violation → walk ~/.dsh/plugins/**/*.json, report which one fails, print the field path) is a one-file addition to the registry. Happy to take a PR pointer if you have a minimal repro.

Fix today. dsh doctor --node --only P2-bom catches the closest sibling (BOM'd manifests that crash plugin add before Standard Schema ever runs). Full README + timeline: https://github.com/HenryZ838978/deepseek-harness

[HenryZ838978]

Update — the doctor now covers 8 probes and grew for rc.8 → rc.1:

• P1-reasoner-skip · P2-bom · P3-serve · P4-spill · P5-seqgap · P6-subagent-env-scrub · P7-subagent-codex-preflight · P8-multimodal-preflight

At dsh-v0.1.1-rc.1 (2026-08-21): 0 of these 8 fixed since first flagged, per source grep. Vision model deepseek-v4-flash-vision-exp was published this release — first release that ships an image-capable model in the default catalog, which widens the P8 trigger surface (image message + no attachment provider = half-turn commit).

pip install deepseek-harness-cli && dsh doctor --node. Full per-release log: https://github.com/HenryZ838978/deepseek-harness/blob/main/HISTORY.md

[HenryZ838978]

Update — doctor now covers 9 probes as of deepseek-harness-cli 0.3.2 (2026-08-21):

• P1-reasoner-skip · P2-bom · P3-serve · P4-spill · P5-seqgap · P6-subagent-env-scrub · P7-subagent-codex-preflight · P8-multimodal-preflight · P9-files-quota-scope (new for rc.2)

P9 covers the rc.2 Files API path: file-store.ts:reclaimOldestOwned deletes remote /files entries by OWNED_FILE_PREFIX = "dsh-", which is ecosystem-wide, not per-install. Two dsh installs sharing one API key can silently delete each other's file_ids and invalidate prefix cache.

At dsh-v0.1.1-rc.2: 0 of the earlier 8 defects fixed since first flagged. pip install deepseek-harness-cli && dsh doctor --node. Per-release log: https://github.com/HenryZ838978/deepseek-harness/blob/main/HISTORY.md