[Bug] 0.1.2-rc.1 (next): client-modules "build-time externals drift" breaks session/workspace controllers ("loader fibers failed")

[shenhuanageshei]

Environment

• @deepseek-ai/dsh 0.1.2-rc.1 (next channel; latest is still 0.1.1-rc.2)
• Platform: Windows (portable deployment), Node v24

Symptom

After upgrading to 0.1.2-rc.1, the web UI fails to boot:

Failed to load plugins
@deepseek-ai/dsh-api-session-controller
@deepseek-ai/dsh-api-workspace-controller
loader fibers failed

Root cause

The client bundles for dsh-api-session-controller and dsh-api-workspace-controller carry a runtime require("@deepseek-ai/dsh-client-store") (and @deepseek-ai/dsh-client-ui-primitives), but those two packages are neither a platform seed word nor a registered client entry:

• dsh-client-store has no dsh.client declaration and no exports["./client"] (only exports["."] -> lib/index.js), so it is never composed as a manifest entry.
• The front-end loader then throws the canonical error in dsh-client-modules/lib/client.js:

client-modules: require("...") missed the module table — not a platform seed word,
not a materialized module, and no registered package factory
(a build-time externals drift, or a dynamic dependency that did not arrive)

i.e. the build externalized dsh-client-store but did not ship it as an independent client bundle (unlike @deepseek-ai/cordis, which is seeded as a platform word).

Impact

The whole plugin tree fails to load on the web front end, making 0.1.2-rc.1 unusable in the browser. (Server-side loader entries load fine; this is front-end client-modules only.)

Repro

1. Install @deepseek-ai/dsh@0.1.2-rc.1 (next).
2. Start dsh web, open the UI.
3. Observe the loader failure above.

Additional note

0.1.2-rc.1 also introduces token auth (?token=... -> signed cookie); see discussion #5519 for the PWA/iOS side effect.

Workaround: stay on latest (0.1.1-rc.2), which does not have these controller/client packages.

[rayfalling]

similar problem
Error: dsh: plugin tree failed to load: dsh: 5 entries did not activate
@deepseek-ai/dsh-session-checkpoint-policy: pending (waiting for service: sessionPersistence)
@deepseek-ai/dsh-message-feedback: pending (waiting for service: sessionPersistence)
@deepseek-ai/dsh-workspace: pending (waiting for service: sessionPersistence)
@deepseek-ai/dsh-api-session-controller: pending (waiting for service: workspaceRegistry)
@deepseek-ai/dsh-api-workspace-controller: pending (waiting for service: workspaceRegistry)

[aoaoms]

Failed to load plugins
failed to import loader entry 35d9b241 (@deepseek-ai/dsh-session-log-export): client-modules: require("@deepseek-ai/dsh-client-runtime/client") missed the module table — not a platform seed word, not a materialized module, and no registered package factory (a build-time externals drift, or a dynamic dependency that did not arrive)

[aoaoms]

I manually disabled this plugin in cordis.patch.yml , and then it worked.

我手动在cordis.patch.yml 文件里添加了一个禁用配置后，可以正常进入dsh啦。

禁用有问题的会话日志导出插件

• id: session-log-download
  name: '@deepseek-ai/dsh-session-log-export'
  disabled: true