DeepSeek Harness · module reference
@deepseek-ai/dsh-client-ui-attachment
Lifecycle of this module across published shells, and the known fix when a plugin requires it.
该模块在各已发布 shell 上的生命周期，以及插件 require 它时的已知修法。
Module history模块历史
@deepseek-ai/dsh-client-ui-attachmentpresent since 0.0.1-rc.5自 0.0.1-rc.5 起Status状态
removed-from-seed 0.1.0-rc.8——但仍是 lazy 图行：bundle 随 combo 批次注册工厂，require 通常仍可解析（非崩溃；时序无硬保证）
Known fix已知修法
Preferred: declare it in dsh.client.external (or inject) — the loader then arrives it before your plugin materializes, turning conditional into certain. To escape timing entirely: bundle it statically (0.0.1-rc.x is still on npm; keep react external to avoid duplicates). Auxiliary features can degrade via try/catch
首选：在 dsh.client.external（或 inject）里声明它——loader 保证先于你的插件到达，条件可解析变确定；要彻底摆脱时序：静态打包进自己的 bundle（npm 上仍有 0.0.1-rc.x，react 保持 external 避免双份）；辅助功能可 try/catch 降级
ysr666/dsh-vision-router — Cautionary tale: we misjudged it as 'crashes on load' — the author reproduced a clean load on three official tags with a real host (resolvable via the graph-row factory, plus its own tapIndex prelude as backstop); closed as a false positive. A lazy graph-row require is NOT a crash —— 反面教材：我们曾把它判成「加载即崩」，作者用三个官方 tag 真实 host 复现正常（图行工厂可解析 + 其自带 tapIndex 前奏兜底），按误报收场。lazy 图行 require ≠ 崩溃https://github.com/ysr666/dsh-vision-router/issues/447