[Bug] 0.2.1-rc.2 desktop: workspaceController unavailable — cannot add workspace (storage-domain disabled)

[yutowrz]

Environment

• Product: DeepSeek Harness desktop (Windows x64), installed at D:\dsh
• Affected version: 0.2.1-rc.2 (nightly)
• Working version: 0.2.0-rc.2
• OS: Windows 11 10.0.26200
• Profile: ~/.dsh/profiles/desktop

Symptom

Clicking Add workspace -> selecting a folder -> confirming fails with:

workspace create failed: gateway/service-unavailable:
typert gateway: workspace/create: active Service "workspaceController" is unavailable

The rest of the UI loads fine; only workspace creation is broken.

Root cause

@deepseek-ai/dsh-api-workspace-controller@0.2.1-rc.2 declares a required peer dependency on @deepseek-ai/dsh-storage-domain@0.2.1-rc.2:

"peerDependencies": {
  "@deepseek-ai/dsh-api-gateway": "0.2.1-rc.2",
  "@deepseek-ai/dsh-client-connection": "0.2.1-rc.2",
  "@deepseek-ai/dsh-host-directory-picker": "0.2.1-rc.2",
  "@deepseek-ai/dsh-session": "0.2.1-rc.2",
  "@deepseek-ai/dsh-storage-domain": "0.2.1-rc.2",
  "@deepseek-ai/dsh-typert-protocol": "0.2.1-rc.2",
  "@deepseek-ai/dsh-workspace": "0.2.1-rc.2"
}

But the generated desktop config ~/.dsh/profiles/desktop/cordis.yml disables it:

- id: storage-domain
  name: '@deepseek-ai/dsh-storage-domain'
  disabled: true
  config:
    backend: json

-> dependency never satisfied -> dsh-api-workspace-controller is not activated -> the Typert gateway has no workspaceController service -> workspace/create returns service-unavailable (503).

Why this is a regression

In 0.2.0-rc.2 the same entry has no disabled key (enabled), and adding workspaces works. @deepseek-ai/dsh-base/cordis.patch.yml also declares storage-domain without disabled: true, so the disable is injected by a desktop/profile layer that was not updated for the new controller dependency.

Also observed (possibly related)

A web-boot crash log:

Error: web boot: 78 entries did not activate
... could not load "@deepseek-ai/dsh-api-gateway":
  plugins/??@deepseek-ai/dsh-api-gateway/client.js,...

Workaround

Roll back to 0.2.0-rc.2 - workspace creation works again.

Not a fix (tested)

Adding - id: storage-domain + disabled: false to cordis.patch.yml does not help; cordis.yml is regenerated on boot and the bundle's disabled: true wins.

Suggested fix

1. Do not disable storage-domain in the desktop profile on 0.2.1-rc.2, or
2. Make workspace-controller tolerate a missing storage-domain (optional injection + fallback to storage-json), or
3. Update the desktop bundle's patch layer to match the new controller's dependencies.

Happy to provide the full config files / logs if useful.