bug: /api/host.describe 未正确暴露 version 而是被硬编码为 0.0.1

[weinibuliu]

https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/host/apiproxy/src/api-proxy.ts#L2923-L2939

// ...
    host: {
      describe(request) {
        // TODO: version should read apps/cli's package.json; placeholder for now.
        const selection = defaults.defaultModelSelection()
        return Promise.resolve(ok(request, {
          version: '0.0.1', // <- NOTE: 这里被硬编码为 0.0.1
          // Same source as session.create's fallback: the UI's default project
          // must match where an unspecified-cwd session actually lands.
          cwd: defaults.cwd,
          // Read live for the same reason: this is what the NEXT session will
          // start from, so a saved default has to be what it reports.
          provider: selection.provider,
          model: selection.model,
          attachedSessions: ctx.agents.list().length,
          canOpenPath: canOpenPaths(),
        }))
      },
// ...

[Electricitysheep]

host.describe 把 version 硬编码 0.0.1——客户端如果靠它判断版本会误导，小 bug 但该修。

希望官方下个 rc 带上，这个影响 API 消费者（如桌面壳/远程端）的版本检测。

[gengwg]

Also can we put this version somewhere in the web UI? Currently there is no /api/version endpoint.

[zoahdev]

Confirmed against current main HEAD 99f6f02 (rc.7, 2026-08-17) — the bug is real and the contract already says what it should be.

Implementation: packages/host/apiproxy/src/api-proxy.ts:2863-2868 — host.describe(request) returns version: '0.0.1' with an explicit // TODO: version should read apps/cli's package.json; placeholder for now.

Contract: packages/host/apiproxy/src/api/host.ts:39 documents version = the host app's (apps/cli) package.json version, so the hardcode contradicts the documented contract. api/host.schema.ts:15 declares version: z.string() — no semver validation, so nothing catches the placeholder at the boundary.

Current reality: apps/cli/package.json is 0.1.0-rc.7, so every API consumer (desktop shells, remote ends, health checks) that keys on host.describe.version sees 0.0.1 and silently misdetects. As you said: small, but real, and cheap to fix.

Suggested minimal fix (matching the contract):

• Source the version once at boot from apps/cli's package.json (or an env/global injected at build, e.g. process.env.DSH_VERSION with a fallback), and use it in describe().
• Add a unit test that pins describe().version !== '0.0.1' (and equals the package version), so the placeholder can't regress silently.

For @gengwg's request (version in web UI): once describe reports the real version, a UI surface is just a consumer — e.g. the settings/about pane can call the existing host.describe RPC (no new /api/version endpoint needed). If you want it before that, the same boot constant can be exposed on the existing health/debug surface. Worth one issue either way so it doesn't get lost.