DeepSeek Harness · failure diagnosis
“cannot resolve” — the async twin of the dsh module-table miss
client-modules: cannot resolve "…"
The async import() twin of “missed the module table”: the specifier is not a seed word, not materialized, and not a row in the boot graph.
这是「missed the module table」的异步 import() 版本：specifier 不是 seed 词、未物化、也不在 boot graph 里。
Why it happens根因
Same root causes as the synchronous miss — a module the shell does not provide, reached through an async import().
与同步缺失同一根因——shell 不提供的模块，通过异步 import() 触达。
How to fix it怎么修
Same fix as “missed the module table”: npx dsh-why names the module and its history.
与「missed the module table」同一修法：npx dsh-why 定位模块与它的版本历史。
Related errors相关报错
client-modules: require("…") missed the module table— another way a plugin fails to loadclient-modules: bundle script … failed to load— another way a plugin fails to loadFailed to load plugins— another way a plugin fails to loadDeepSeek API request to https://api.deepseek.com failed— dsh starts fine, but a run dies
client-modules: require("…") missed the module table—— 插件加载失败的另一种形态client-modules: bundle script … failed to load—— 插件加载失败的另一种形态Failed to load plugins—— 插件加载失败的另一种形态DeepSeek API request to https://api.deepseek.com failed—— dsh 起得来，但某次 run 挂了
FAQ常见问题
Is “cannot resolve” the same as “missed the module table”?
Yes — it is the async import() variant of the same resolution failure.
「cannot resolve」和「missed the module table」一样吗？
一样——是同一个解析失败的异步 import() 变体。