@oksure/dsh-client-ui-mobile-comfort
dsh Web 客户端的触控设备体验修复：抑制点击生成的工具提示残影，并消除控件的双击缩放歧义。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:oksure/dsh-mobile-comfort#353bd01375a6cf021a2d5fd8796793d6ad518eeeClient Ui Mobile Comfort 以 @oksure/dsh-client-ui-mobile-comfort 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
点击下方 Badge 复制 Markdown，粘贴到 README 即可。
验证 package.json 声明的 GitHub 仓库，即可管理这个公开页面。认领后，Hub 会优先安排当前版本的安全扫描，并在通过后公开展示结果。
认领这个 Plugin →Touch-device comfort fixes for the DeepSeek Harness web client, packaged as an out-of-tree dsh bundle plugin.
On phone and tablet browsers the dsh web UI shows two touch-specific problems:
mouseenter/focus, which mounts a tooltip; when the tapped control then moves (sidebar collapse animation), no trailing mouseleave ever fires on touch browsers, so the bubble lingers indefinitely. Reproduced on WebKit: the tooltip stays visible 3+ seconds after every tap with no pointer anywhere near. This sheet hides [role="tooltip"] under (hover: none) and (pointer: coarse) — tooltips are a hover affordance, and coarse pointers get none.touch-action rules, so on iOS Safari rapid second taps zoom the page instead of clicking (and first clicks carry the legacy delay). The sheet sets touch-action: manipulation on interactive elements, leaving pinch zoom untouched.Desktop pointers are unaffected: both rules key off input modality (touch-action) or pointer class (hover/pointer media features).
dsh plugin --profile web add file:/path/to/dsh-mobile-comfort
Then restart the profile (dsh web). Verify by loading the UI on a phone: tapping the sidebar toggle must not leave a tooltip behind.
lib/client.js — browser half: injects one stylesheet for the lifetime of the plugin fiber (ctx.effect, HMR-safe disposer).lib/index.js — host half: no-op (browser-only plugin).cordis.patch.yml — bundle patch inserting the ui-mobile-comfort row.The root causes live in @deepseek-ai/dsh-client-ui-primitives (Tooltip.tsx: onFocus shows immediately and only disabled handles the no-mouseleave case) and in the absence of any touch-action policy. A full diagnosis with engine-level event traces is in docs/mobile-touch-report.md; it is written up to be posted to the upstream Discussions as well.
MIT