@toddzheng024/dscode-desktop 0.7.36 → 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.36 · **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.36` 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,33 @@ 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.
+
+### Changed
+
+- Upgrade the terminal Harness runtime and vendored TUI dependencies from `0.1.7-alpha.2` to `0.2.0-rc.2`, matching the existing Desktop release target. Keep exact runtime pins and patch-version guards; this does not move to the `0.2.1` alpha channel.
+- Update the live DeepSeek compaction evaluator and its regression fixture for header-based authentication.
+- Upgrade Computer Use to `0.3.3`, whose declared compatibility includes the new Harness. Remove the retired Settings shim so the provider receives native live configuration updates. Restoring execution tools after a saved skill load still requires reloading the skill.
+- Mount the native session controller and its host dependencies so reminders can resolve live and persisted sessions on Harness 0.2. The optional loopback login server also carries authenticated native Connection routes; no browser frontend is mounted.
+- Read `/schedule` from the native reminder catalog instead of historical session events, refresh it while open, and display daily, weekly and cron rules. Storage failures remain visible instead of appearing as an empty list.
+- Pin newly introduced Harness packages, including the shared DeepSeek account service required by clean bundle installations. Isolate patched app-boot, Goal and subagent provider packages in verification runtimes; check Ink patches in memory and use a deterministic clock for the OpenRouter timeout regression.
+- Remove the stale relative source-map directive from the in-memory Ink test fixture, which Node 22.19.0 cannot resolve against a data URL during coverage collection. The shipped Ink runtime is unaffected.
+
+### Added
+
+- Document Atomic Mail as an optional stdio MCP integration with a disabled example entry. Unconfigured or disabled entries add no tools or server instructions to model context; enabling and removing the integration are covered by an offline lifecycle test.
+
 ## [0.7.36] - 2026-10-09
 
 ### Added

package/docs/browser-use.md

@@ -646,7 +646,7 @@ and account settings, browser preview, durable session communication, cross-sess
 memory and opt-in task scheduling together. Ordinary builds remain private;
 the separate [release process](hub-distribution.md#desktop-release-candidate-and-publication)
 qualifies a public candidate for 0.2.0-rc.2. The Desktop preview is published on npm as
-`@toddzheng024/dscode-desktop@0.7.35`. The package does
+`@toddzheng024/dscode-desktop@0.7.38`. The package does
 not yet include all DSCODE Host services. Its experimental
 [native Computer Use adapter](computer-use.md) has passed helper and lifecycle
 checks; window observation, screenshots and input await qualification with

package/docs/email.md

@@ -17,6 +17,79 @@ directory is `~/.dscode/email`; `DSCODE_EMAIL_DIR` overrides it. New directories
 use mode 0700 and messages use 0600. Message content enters session history only
 when selected with Enter. Existing composer drafts and attachments are preserved.
 
+## Atomic Mail via MCP
+
+[Atomic Mail](https://github.com/Atomic-Mail/atomic-mail-agentic) provides a
+separate mailbox for an agent through a local stdio MCP server. This optional
+integration uses DSCODE's existing MCP bridge; it does not populate the built-in
+`/email` inbox or use its `send_email` receipts and contact aliases.
+
+Atomic Mail is absent from the default preset and dependencies. Without a local
+MCP entry, no Atomic Mail process, tool schemas or server instructions load.
+The entry in [the example configuration](https://github.com/qiz029/dscode/blob/main/config/mcp.local.example.yml) is
+disabled, so copying that file alone does not enable it. There is no always-on
+Atomic Mail skill or prompt section.
+
+### Enable the server
+
+For a source checkout or unpacked release, edit `config/mcp.local.yml` in the
+installation directory. For the npm/Hub launcher, edit
+`~/.local/share/dscode-hub/config/mcp.local.yml` (or
+`$DSCODE_HOME/config/mcp.local.yml` when overridden). Create the directory and
+file if needed. Add this row to the existing `insert` list, or use the complete
+patch below for a new file:
+
+```yaml
+- insert:
+    - id: mcp-atomicmail
+      name: '@deepseek-ai/dsh-mcp-client'
+      config:
+        serverName: atomicmail
+        transport: stdio
+        command: npx
+        args: ['--yes', '@atomicmail/mcp@0.3.31']
+        failOnStartupError: true
+```
+
+Node and `npx` must be available; the first enabled launch downloads the pinned
+package from npm. Restart DSCODE, then run `/mcp` and
+`/mcp tools mcp-atomicmail`. A successful connection exposes
+`mcp__atomicmail__register`, `mcp__atomicmail__jmap_request` and
+`mcp__atomicmail__help`, together with the server's own instructions.
+
+### Use and disable the mailbox
+
+Ask the agent to call Atomic Mail's `help` before using the mailbox. Registration
+requires your chosen username and a `watch` preference: `on-demand` reads mail
+when requested; `scheduled` requires a separately configured recurring agent
+task. Enabling the MCP entry does not register an account, send mail or create
+a schedule. Follow the installed server's help for registration and JMAP
+operations; the [upstream MCP guide](https://github.com/Atomic-Mail/atomic-mail-agentic/blob/main/docs/mcp.md)
+describes the service.
+
+Credentials default to `~/.atomicmail`; set `ATOMIC_MAIL_CREDENTIALS_DIR` in
+the row's `config.env` to use a separate absolute directory. Keep credentials
+out of the configuration and version control. Mail arriving through this MCP
+remains external content, and outgoing actions follow the active MCP tool
+permission policy.
+
+With all agents idle, `/mcp disable mcp-atomicmail` removes the connection,
+tools and server prompt contribution for the current process. Set
+`disabled: true` on the row, or remove it, to keep it off after restart.
+Disabling does not erase messages or tool results already in session history;
+start a new session for a conversation without that earlier context. Any
+separately configured schedule must also be disabled separately.
+
+The native bridge was checked with `@atomicmail/mcp@0.3.31` for initialization,
+discovery of all three tools, server instructions and a read-only `help` call
+using an isolated credential directory. An offline MCP fixture checks that
+absent and disabled entries contribute no context, enabling adds tools and
+instructions, and disabling or removing the entry removes both.
+
+This recipe covers the terminal launcher's local stdio integration. Hosted
+OAuth and integration with the built-in inbox are outside its scope. Mailbox
+registration and real mail delivery were not tested.
+
 ## Experimental Desktop inbox
 
 The combined Desktop package adds **Open right sidebar → Email inbox**. It reads

package/docs/hub-distribution.md

@@ -7,7 +7,7 @@
 - `@toddzheng024/dscode-desktop`: the extension for official Harness Desktop, published under the npm `preview` tag. It has its own exact runtime compatibility and Hub listing, and is not part of the terminal Hub profile.
 - Hub profile `dscode`: the exact versions and integrity hashes of the bundle and the DSH runtime.
 
-The complete bundle pins the shared DSH dependencies and the vendored terminal's runtime dependencies explicitly, using the repository lockfile. The terminal's workspace package is compiled into the bundle; its dependencies must still be installed, including `chalk` and `ink`. Do not stack it with another base/TUI bundle in one profile: installing several root bundles in Hub order resolves a wide transitive dependency to the other rc line first. A standalone profile's pnpm hoisted + autoInstallPeers=false is the verified installation path. A direct `npm install` of the bundle hits Computer Use's old peer range; end users install through the launcher.
+The complete bundle pins the shared DSH dependencies and the vendored terminal's runtime dependencies explicitly, using the repository lockfile. The terminal's workspace package is compiled into the bundle; its dependencies must still be installed, including `chalk` and `ink`. Do not stack it with another base/TUI bundle in one profile: installing several root bundles in Hub order resolves a wide transitive dependency to the other rc line first. A standalone profile's pnpm hoisted + autoInstallPeers=false is the verified installation path. Computer Use 0.3.3 declares compatibility with the pinned Harness runtime. End users install through the launcher, which supplies the verified profile layout and installation settings.
 
 ## User
 
@@ -37,7 +37,7 @@ A user who already has dsh-hub installed can apply directly, but must use pnpm 1
 
 Install the official Harness Desktop application with embedded runtime
 0.2.0-rc.2. In **Plugins → Add plugin**, enter
-`@toddzheng024/dscode-desktop@0.7.35`, review and install, then choose
+`@toddzheng024/dscode-desktop@0.7.38`, review and install, then choose
 **Enable now**. Fully quit and reopen Desktop, enable **Show coding view** and
 **Agent presets**, then create a DSCODE session and choose an existing model.
 The Desktop preview is qualified on macOS Apple Silicon. See
@@ -46,7 +46,7 @@ for archive checksums, migration and removal, and [Plugin Hub](plugin-hub.md)
 for the separation between DSCODE and Hub.
 
 Version 0.7.34 fixes the 0.7.33 activation error “4 entries did not activate”
-when Desktop starts without `DSH_HOME`. Update to the current 0.7.35 package and
+when Desktop starts without `DSH_HOME`. Update to the current 0.7.38 package and
 enable it again; exporting a shell variable is unnecessary. Default Desktop
 state uses `~/.dsh`, as resolved by Harness. Publication now verifies installation
 and the affected components with that default environment.

package/docs/plugin-hub.md

@@ -26,7 +26,7 @@ sessions. Their installation handoff delegates to the official plugin manager;
 enabling, configuration and removal stay in **Settings → Plugins**.
 
 Installing or reinstalling 0.7.34 will therefore not remove the bundled Hub.
-Update to `@toddzheng024/dscode-desktop@0.7.35` using the [Desktop installation guide](browser-use.md#install-the-experimental-combined-desktop-package).
+Update to `@toddzheng024/dscode-desktop@0.7.38` using the [Desktop installation guide](browser-use.md#install-the-experimental-combined-desktop-package).
 Fully quit and reopen Desktop after updating; an already running Host may keep
 the old plugin modules loaded.
 

package/docs/releases/0.7.37.md

@@ -0,0 +1,17 @@
+# DSCODE 0.7.37
+
+Status: unpublished candidate. Its workflow was cancelled before publication after the Node 22.19.0 coverage job exposed a test-fixture source-map error. Superseded by [0.7.38](0.7.38.md).
+
+This release upgrades the terminal to Harness 0.2.0-rc.2, restores native reminder integration, and documents optional Atomic Mail MCP support.
+
+- **Aligned runtime:** the terminal and vendored TUI now use Harness `0.2.0-rc.2`, matching the existing Desktop target. All installed Harness packages have exact override pins, including the newly introduced shared account service. Existing DSCODE runtime patches retain their exact-version guards. The DeepSeek compaction evaluator uses the new header-based authentication interface; this release does not move to the `0.2.1` alpha channel.
+- **Native reminders:** the terminal mounts the session controller and its host dependencies so the scheduler can deliver to live sessions and resume persisted sessions while the Host runs. `/schedule` reads the current reminder catalog instead of historical session events, refreshes while open, displays daily, weekly and cron rules, and surfaces read failures. The optional loopback login server also carries authenticated native Connection routes; no browser frontend is mounted. The host services also work with that listener disabled.
+- **Computer Use compatibility:** update to `0.3.3`, whose declared compatibility includes the new Harness, and remove the retired Settings shim so the provider handles native configuration updates. The upstream saved-skill restoration limitation remains: after resuming a session, reload the Computer Use skill if its execution tools are absent. The activation tool remains available.
+- **Optional Atomic Mail:** the [email guide](../email.md) and disabled example MCP row show how to opt in. Unconfigured or disabled rows start no Atomic Mail process and add no tools or server instructions to model context. Disabling or removing a configured row removes its current tools and instructions; it does not erase previous conversation history. This is a separate MCP integration and does not replace the existing email tools.
+- **Reliable verification:** isolated test runtimes now carry the app-boot, Goal and subagent provider packages they exercise. Ink patch tests work in memory and OpenRouter timeout tests use a controlled clock. Fresh installs no longer depend on a previously patched developer tree. Installed-bundle probes include native live and cold-session reminder delivery.
+
+Update with `npm install -g @toddzheng024/dscode@latest`, then run `dscode update` for an existing Hub profile. Fresh installs provision their matching profile on first launch. The Desktop extension remains qualified separately for official Harness 0.2.0-rc.2 on macOS Apple Silicon; its exact release archive is revalidated by the release workflow.
+
+Verification of this change passed a clean `npm ci --ignore-scripts` and `npm run check`: lint, both TypeScript checks, 1,091 unit/component tests, native integration and package checks, and 63 offline evaluation tests. Measured first-party `.mjs` line coverage was 80.37%; the TypeScript terminal is outside that metric. Real Chrome checks passed. The macOS doctor passed preset activation, worktrees, shell persistence, approvals, compaction and session resume; an isolated run with `DSCODE_ACCOUNT_LOGIN=0` also passed live and cold-session reminder delivery. Computer Use helper 0.3.3 passed initialization and its health handshake. Linux arm64 on Node 22.23.3 passed all seven end-to-end stages, including installed bundle execution, failed-upgrade preservation and successful upgrade/rollback. Documentation, lint and tag-version checks are repeated for the version bump, and CI requalifies the exact versioned terminal and Desktop archives before publication.
+
+Real provider inference, live OAuth login, interactive desktop actions and real mail delivery have no automated case in this release. Fixture success establishes runtime and transport behavior, not model quality or those external account flows.

package/docs/releases/0.7.38.md

@@ -0,0 +1,19 @@
+# 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.
+
+- **Aligned runtime:** the terminal and vendored TUI now use Harness `0.2.0-rc.2`, matching the existing Desktop target. All installed Harness packages have exact override pins, including the newly introduced shared account service. Existing DSCODE runtime patches retain their exact-version guards. The DeepSeek compaction evaluator uses the new header-based authentication interface; this release does not move to the `0.2.1` alpha channel.
+- **Native reminders:** the terminal mounts the session controller and its host dependencies so the scheduler can deliver to live sessions and resume persisted sessions while the Host runs. `/schedule` reads the current reminder catalog instead of historical session events, refreshes while open, displays daily, weekly and cron rules, and surfaces read failures. The optional loopback login server also carries authenticated native Connection routes; no browser frontend is mounted. The host services also work with that listener disabled.
+- **Computer Use compatibility:** update to `0.3.3`, whose declared compatibility includes the new Harness, and remove the retired Settings shim so the provider handles native configuration updates. The upstream saved-skill restoration limitation remains: after resuming a session, reload the Computer Use skill if its execution tools are absent. The activation tool remains available.
+- **Optional Atomic Mail:** the [email guide](../email.md) and disabled example MCP row show how to opt in. Unconfigured or disabled rows start no Atomic Mail process and add no tools or server instructions to model context. Disabling or removing a configured row removes its current tools and instructions; it does not erase previous conversation history. This is a separate MCP integration and does not replace the existing email tools.
+- **Reliable verification:** isolated test runtimes now carry the app-boot, Goal and subagent provider packages they exercise. Ink patch tests work in memory and OpenRouter timeout tests use a controlled clock. Fresh installs no longer depend on a previously patched developer tree. Installed-bundle probes include native live and cold-session reminder delivery.
+
+Update with `npm install -g @toddzheng024/dscode@latest`, then run `dscode update` for an existing Hub profile. Fresh installs provision their matching profile on first launch. The Desktop extension remains qualified separately for official Harness 0.2.0-rc.2 on macOS Apple Silicon; its exact release archive is revalidated by the release workflow.
+
+Verification of this change passed a clean `npm ci --ignore-scripts` and `npm run check`: lint, both TypeScript checks, 1,091 unit/component tests, native integration and package checks, and 63 offline evaluation tests. Measured first-party `.mjs` line coverage was 80.37%; the TypeScript terminal is outside that metric. Real Chrome checks passed. The macOS doctor passed preset activation, worktrees, shell persistence, approvals, compaction and session resume; an isolated run with `DSCODE_ACCOUNT_LOGIN=0` also passed live and cold-session reminder delivery. Computer Use helper 0.3.3 passed initialization and its health handshake. Linux arm64 on Node 22.23.3 passed all seven end-to-end stages, including installed bundle execution, failed-upgrade preservation and successful upgrade/rollback. Documentation, lint and tag-version checks are repeated for the version bump, and CI requalifies the exact versioned terminal and Desktop archives before publication.
+
+Real provider inference, live OAuth login, interactive desktop actions and real mail delivery have no automated case in this release. Fixture success establishes runtime and transport behavior, not model quality or those external account flows.

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.36",
+  "version": "0.7.39",
   "private": false,
   "description": "DSCODE for Harness Desktop: coding collaboration, session memory, browser workflows and task management.",
   "license": "MIT",

package/plugins/computer-use/index.mjs

@@ -1,37 +1,7 @@
-/**
- * Computer Use, mounted through DSCODE so a retired settings API still resolves.
- *
- * `@anionex/dsh-computer-use` reads its configuration with `ctx.settings.register`, an API
- * DSH removed in 0.1.7: Settings now projects forms from the profile entry itself, and the
- * missing method made the whole Computer Use bundle fail to activate. The package is
- * pinned at 0.3.2 with no newer release, so this row restores the method — as a read-only
- * view over the composition config, which is where DSCODE configures Computer Use anyway —
- * and then mounts the upstream bundle as its child, which is what makes the order
- * dependable: the shim is installed before the provider's constructor runs.
- *
- * Retire this wrapper when the package reads volatile configuration, and mount
- * `@anionex/dsh-computer-use` directly again.
- *
- * @module dscode-computer-use
- */
-
+/** Mount the compatible upstream provider with DSCODE interaction defaults. */
 import ComputerUseBundle from '@anionex/dsh-computer-use';
 
 export const name = 'dscode-computer-use';
-export const inject = ['settings'];
-
-/** Section handle the 0.3.x provider expects: one read of the composition config, no live writes. */
-function staticSection(base) {
-  return { get: () => base, watch: () => () => {} };
-}
-
 export function apply(ctx, config = {}) {
-  const settings = ctx.settings;
-  // Only ever adds what upstream no longer defines; a Settings service that carries its
-  // own `register` again is left untouched, and the shim is dropped with this row.
-  if (typeof settings.register !== 'function') {
-    settings.register = (_namespace, _schema, options = {}) => staticSection(options.base ?? {});
-    ctx.effect(() => () => { delete settings.register; });
-  }
   ctx.plugin(ComputerUseBundle, config);
 }