[Bug] DSH Desktop 2.0.4: desktop profile 无法启动 Renderer boot failed for 1 plugin(s)（@nanmicoder/dsh-agent-teams 依赖已移除的 conversationEvents 服务）

[imrascal]

Environment: DSH Desktop v2.0.4 (win32, Electron 43, node v24.18.1), Windows 11, desktop profile. Failing plugin: @nanmicoder/dsh-agent-teams@0.1.14 (npm). Bundled client packages (@deepseek-ai/dsh-web-app, @deepseek-ai/dsh-client-ui-conversation, ...) are all 0.1.2-alpha.1 (desktop-private build, not published to npm).

Steps to reproduce

1. Upgrade DSH Desktop from 2.0.3 to 2.0.4.
2. Launch DSH Desktop with the desktop profile.
3. Startup fails; the app never shows the main window.

Actual result

Log (%APPDATA%\DSH Desktop\logs\dsh-2026-08-29.log, reproduced across many runs):

dsh-plugin-desktop: renderer boot failed (plugins: @nanmicoder/dsh-agent-teams): The client Loader did not provide an error message.
RendererStartupFailure: Renderer boot failed for 1 plugin(s)
    at start (file:///C:/Applications/DSH%20Desktop/resources/app.asar/lib/main.js:5070:49)

• The whole desktop profile refuses to start (RendererStartupFailure).
• The error names the plugin but hides the cause ("The client Loader did not provide an error message.").
• Removing @nanmicoder/dsh-agent-teams restores startup.

Root cause

Two layers stack:

1. DSH Desktop 2.0.4's bundled client (0.1.2-alpha.1) removed the conversationEvents service and replaced it with uiConversation:

   • Upstream commit c7d8e32aece2dbf6328c4bbed34bdf6d5934b56f (refactor(conversation): separate Conversation, Chat, and Trajectory owners)
   • New registration entry point: ctx.uiConversation.events.register(def) (UiConversation Service in @deepseek-ai/dsh-client-ui-conversation src/client/conversation/assembly.ts / event-registry.ts)
   • Full-tree search of the 2.0.4 install: conversationEvents has 0 hits; npm 0.1.1-rc.2 (2.0.3 era) still contains it — confirmed introduced by 2.0.4.

2. agent-teams 0.1.14's client entry still declares and uses the old service (lib/client/index.js):

   export const inject = ['conversationEvents', 'slots', 'sessions', 'locale', 'modelDirectories'];
   // apply():
   ctx.conversationEvents.register(agentTeamsCardDefinition);

3. Cordis 4 strict-injection semantics: when an injected service is missing, the fiber parks in a waiting state — it does not activate and does not throw (fiber.await() resolves normally). The renderer boot report then flags the entry as inactive (fiber.state !== ACTIVE(2)), reports {status:"failed", plugins:["@nanmicoder/dsh-agent-teams"]} with no error, and the main process prints "The client Loader did not provide an error message." and throws RendererStartupFailure.

Suggestions

• Plugin side: @nanmicoder/dsh-agent-teams should switch to uiConversation (upstream PR NanmiCoder/dsh-agent-teams#93 fixes it; unmerged/unreleased).
• Desktop side (focus of this report):
  1. Missing error detail: the desktop build should surface the plugin's real failure reason (compare the web profile's pending (waiting for service: conversationEvents)); "did not provide an error message" is undiagnosable.
  2. Error isolation: a single incompatible third-party bundle should not block the whole desktop profile from starting (see deepseek-harness#4175 — a recoverable-startup PoC already exists).
  3. Breaking-change notice: removing conversationEvents in 0.1.2-alpha.1 is breaking; the desktop upgrade path should detect incompatible profile bundles and offer actionable guidance.

Related

• Same root cause reported on the web side: deepseek-ai/deepseek-harness#2118, #4175
• agent-teams: #91, #92, #93

Workaround

Remove @nanmicoder/dsh-agent-teams from ~/.dsh/profiles/desktop/package.json dependencies and the dsh.profile.bundles list, then pnpm install; or wait for the plugin 0.1.15 (includes #93).