@toddzheng024/dscode-desktop 0.7.38 → 0.7.39

package/README.md

@@ -3,7 +3,7 @@
 DSCODE adds a coding preset, browser workflows, cross-session collaboration,
 memory and task management to the official DeepSeek Harness Desktop application.
 
-**Version:** 0.7.38 · **Harness runtime:** 0.2.0-rc.2
+**Version:** 0.7.39 · **Harness runtime:** 0.2.0-rc.2
 
 Preview release candidate; publication is a separate step.
 
@@ -48,7 +48,7 @@ public release; a candidate build alone does not publish a package.
 ## Install a published version
 
 After this version is available on npm, enter
-`@toddzheng024/dscode-desktop@0.7.38` in **Plugins → Add plugin**,
+`@toddzheng024/dscode-desktop@0.7.39` in **Plugins → Add plugin**,
 review the installation, install, then choose **Enable now**. Using the exact
 version keeps the installation tied to these instructions and compatibility
 requirements. The `preview` tag tracks the current Desktop preview release.

package/docs/CHANGELOG.md

@@ -6,6 +6,15 @@ Per-release notes live in [`docs/releases/`](releases/); the entries below summa
 
 <!-- Add upcoming changes under Unreleased. -->
 
+## [0.7.39] - 2026-10-10
+
+### Fixed
+
+- Load the native DeepSeek API-key and Account plugins from the terminal bundle, with both importing its patched shared adapter. Harness 0.2 split the adapter library from its plugin entry points; the 0.7.38 bundle incorrectly mounted the library as a plugin, leaving the API-key route unavailable. Preserve existing provider settings row IDs.
+- Require installed-bundle local diagnostics to have no plugin activation failures, and verify both native DeepSeek provider registrations and model resolution before any fixture adapter is introduced. These checks make provider startup part of the release gate without sending model requests.
+
+Version 0.7.38 reached npm and Hub before this fault was found in a fresh public install; its remaining release workflow was cancelled. Upgrade to 0.7.39.
+
 ## [0.7.38] - 2026-10-10
 
 The 0.7.37 candidate was cancelled before publication after its Node 22.19.0 coverage check failed. This release includes that upgrade and the test-fixture fix below.

package/docs/releases/0.7.38.md

@@ -1,5 +1,7 @@
 # DSCODE 0.7.38
 
+Status: superseded by 0.7.39. This version reached npm and Hub, but a fresh public install exposed a broken DeepSeek provider entry point and the remaining release workflow was cancelled. Use 0.7.39 or later.
+
 This release upgrades the terminal to Harness 0.2.0-rc.2, restores native reminder integration, and documents optional Atomic Mail MCP support.
 
 The 0.7.37 candidate was cancelled before npm or Hub publication when its Node 22.19.0 coverage check failed. This version retains the upgrade and removes a stale source-map reference from the in-memory Ink test fixture. The failure was reproduced locally on Node 22.19.0; all 1,091 unit/component tests and coverage checks passed on that exact runtime after the fix. The original tag remains unchanged.

package/docs/releases/0.7.39.md

@@ -0,0 +1,11 @@
+# DSCODE 0.7.39
+
+This release repairs DeepSeek provider startup in the published terminal bundle and retains the Harness 0.2.0-rc.2 upgrade, native reminders, Computer Use 0.3.3 and optional Atomic Mail integration from 0.7.38.
+
+- **Working DeepSeek entries:** Harness 0.2 separates its shared adapter library from the API-key and Account plugins. The bundle now ships both native plugin entries and points them at its patched adapter, retaining DSCODE effort policies. Existing API-key and Account settings row IDs remain unchanged. This fixes the `invalid plugin` activation error and missing API-key provider seen in a fresh 0.7.38 installation.
+- **Installed provider verification:** the release gate now boots the installed launcher's local doctor and rejects plugin activation failures. The real Harness probe checks that both `deepseek-official` and `deepseek-account` register and resolve model information before it adds its offline fixture adapter. Fixture agent success can no longer hide this missing provider.
+- **Publication boundary:** 0.7.38 reached npm and Hub before the public installation check found this problem; its remaining workflow was cancelled. The existing version and tag are retained. Install 0.7.39 instead.
+
+Update the launcher with `npm install -g @toddzheng024/dscode@latest`, then run `dscode update` for an existing Hub profile. The Desktop extension remains qualified separately for official Harness 0.2.0-rc.2 on macOS Apple Silicon.
+
+Verification passed `npm run check`: lint, both TypeScript checks, 1,091 unit/component tests, native integration, package checks and 63 offline evaluations; measured first-party `.mjs` coverage was 80.35%. The exact candidate also passed `verify:hub` in a clean temporary workspace: native locked installation, installed local diagnostics, both DeepSeek provider registrations and model resolution, ACP, agent execution, session messaging, cards, memory, failed-upgrade preservation and successful upgrade/rollback. Running that verification directly from the developer checkout was blocked by its local `.env` bootstrap setting; no local credentials were copied to the clean workspace. Documentation and tag-version checks passed before tagging. Real provider inference, live OAuth login, interactive desktop actions and real mail delivery have no automated case. Computer Use retains the upstream saved-skill restoration limitation documented in [0.7.38](0.7.38.md).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@toddzheng024/dscode-desktop",
-  "version": "0.7.38",
+  "version": "0.7.39",
   "private": false,
   "description": "DSCODE for Harness Desktop: coding collaboration, session memory, browser workflows and task management.",
   "license": "MIT",