@toddzheng024/dscode-desktop 0.7.33 → 0.7.35

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.33 · **Harness runtime:** 0.2.0-rc.2
+**Version:** 0.7.35 · **Harness runtime:** 0.2.0-rc.2
 
 Preview release candidate; publication is a separate step.
 
@@ -37,8 +37,9 @@ desktop_dsh='/Applications/DeepSeek Harness.app/Contents/Resources/runtime/cli/b
 "$desktop_dsh" plugin --profile desktop add /absolute/path/to/dscode-desktop.tgz --ignore-scripts
 ```
 
-Restart Desktop, select the **DSCODE** preset, select a workspace, and configure
-the model under **Settings → DSCODE models** or **DSCODE accounts**.
+Fully quit and reopen Desktop. In **Settings → General**, enable **Show coding view**; enable **Agent presets** in Plugins if disabled. Create a new session and select **DSCODE** and a workspace. Use an existing model from the normal model picker.
+
+**Settings → DSCODE** contains setup, Models, Accounts and Schedules at the same level. Models and Accounts add optional providers; they are not required for existing Desktop accounts. **Plugins → DSCODE · Community** opens the same page. The package activation notice explains the required restart.
 
 Installation through the official **Plugins → Add plugin** interface was checked
 on macOS Desktop 0.2.0-rc.2. Public npm installation instructions accompany a
@@ -47,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.33` in **Plugins → Add plugin**,
+`@toddzheng024/dscode-desktop@0.7.35` 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.
@@ -81,9 +82,9 @@ configuration and the user patch. Keep a backup before migrating your own state.
 - Durable session messaging, source-backed memory and opt-in scheduling.
 - Email inbox, IMAP/Gmail setup and explicit message-to-session delivery.
 - Independent code review, optional automatic permission review and diagnostics.
-- Plugin Hub search, categories and details, read-only conversation discovery,
-  and reviewed installation through the official plugin manager. Enable and
-  configure installed plugins in **Settings → Plugins**; see `docs/plugin-hub.md`.
+
+Plugin Hub is not bundled: this package does not add its settings page, catalog
+connection or discovery tools. See `docs/plugin-hub.md` for version boundaries.
 
 Use the bundled guides under `docs/` for individual settings and boundaries.
 The terminal's state directory may differ from Desktop's; sharing credentials

package/cordis.patch.yml

@@ -42,14 +42,14 @@
 - insert:
     - id: dscode-credentials
       name: "@toddzheng024/dscode-desktop/credentials"
+      config:
+        desktop: true
     - id: dscode-desktop-workspace
       name: "@toddzheng024/dscode-desktop/workspace"
     - id: dscode-custom
       name: "@toddzheng024/dscode-desktop/custom"
     - id: dscode-desktop
       name: "@toddzheng024/dscode-desktop"
-    - id: dscode-hub
-      name: "@toddzheng024/dscode-desktop/hub"
     - id: dscode-openrouter
       name: "@toddzheng024/dscode-desktop/openrouter"
       config:
@@ -92,8 +92,6 @@
           cursorVisualization: visible
     - id: dscode-desktop-triggers
       name: "@toddzheng024/dscode-desktop/triggers"
-    - id: dscode-browser
-      name: "@toddzheng024/dscode-desktop/browser"
     - id: dscode-auto-review
       name: "@toddzheng024/dscode-desktop/auto-review"
 
@@ -431,3 +429,6 @@
 
           - id: present
             name: '@deepseek-ai/dsh-tool-present'
+
+          - id: dscode-browser
+            name: '@toddzheng024/dscode-desktop/browser'

package/docs/CHANGELOG.md

@@ -6,7 +6,24 @@ Per-release notes live in [`docs/releases/`](releases/); the entries below summa
 
 <!-- Add upcoming changes under Unreleased. -->
 
-## [Unreleased]
+## [0.7.35] - 2026-10-08
+
+- Promote the verified Desktop package to both `preview` and `latest` so default installations receive this fix instead of 0.7.33. Promotion requires a matching public-install receipt.
+
+- Scope Desktop browser tools, skill and command to DSCODE sessions. Standard sessions no longer inherit the DSCODE browser entry; TUI Browser Use keeps its existing integration.
+- Group setup, Models, Accounts and Schedules under one DSCODE settings page, using Harness theme tokens and compact controls. Add a community-labeled Plugins item and an activation notice with full-restart and preset-selection instructions.
+- Prefer existing native Desktop credentials and save new Desktop keys to the native store. Terminal credentials remain a legacy fallback; explicit removal clears both copies. Existing Desktop models do not require a separate DSCODE login.
+
+- Remove bundled Plugin Hub functionality from the Desktop package: no Hub settings page, catalog endpoint, conversation discovery tools, source files or Hub-specific runtime dependencies. DSCODE's catalog listing and release synchronization remain available; this does not publish a standalone Hub Desktop plugin. Already published 0.7.34 packages retain their previous contents; update to 0.7.35 to remove the integration.
+- Update the Desktop demo and browser guide to distinguish DSCODE's integration features from official Harness Browser Use, and replace bundled-Hub qualification with checks that the package and running Host contain no Hub integration.
+
+## [0.7.34] - 2026-10-08
+
+- Fix Desktop activation without an exported `DSH_HOME`: workspace discovery, email, scheduling and automatic review now resolve the native Harness home, including the default `~/.dsh`, blank overrides and supported tilde paths.
+- Keep browser state, memory, session communication/cards, delegation, review baselines, provider caches, diagnostics and usage records under that same resolved home. The terminal launcher continues to map its `DSCODE_HOME` into `DSH_HOME`; explicit memory and audit directories remain supported. Credentials and mail retain their existing account-store locations. This change does not move previously misplaced state automatically.
+- Public Desktop installation qualification now runs with `DSH_HOME` absent and requires all four affected components to activate. The native Host and signed macOS lifecycle verifiers also support this default-home scenario.
+- The demo guide separates DSCODE's workflow from the Hub's discovery contribution and adds a Desktop walkthrough draft with setup, reset and qualification boundaries. The existing terminal recording instructions remain available. Release-note links also work when read on GitHub Releases or as downloaded Markdown.
+- Desktop Hub publication retries the npm propagation window where the exact version is visible but the Hub still reports `package_not_found` or an older index. Retries are bounded; policy/credential failures and integrity mismatches still stop publication.
 
 ## [0.7.33] - 2026-10-08
 

package/docs/browser-use.md

@@ -5,6 +5,27 @@ DevTools MCP. Chrome starts only when you use `/browser start` or the agent call
 `browser_start`. No MCP configuration or separate npm installation is needed.
 Google Chrome is required for browser tasks; ordinary coding does not need it.
 
+## Relationship to official Harness Browser Use
+
+Official Harness already provides a [Browser Use framework and experimental
+providers](https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/browser-use/README.md),
+including Chrome DevTools MCP, Playwright MCP and Stagehand. Basic page browsing,
+clicking, typing, screenshots and developer inspection are not unique DSCODE
+features. Backend and Session lifecycle plumbing overlap with upstream work.
+
+DSCODE adds its own per-origin access and separate Developer grants, screenshot
+point annotations delivered to the conversation, and explicit login handoff and
+resume controls. The sections below describe their behavior and limits. These
+are DSCODE integration features; this guide does not claim that every upstream
+provider lacks equivalent capabilities.
+
+The official [Browser sidebar](https://github.com/deepseek-ai/deepseek-harness/blob/master/packages/client/ui-sidebar-browser/README.md)
+embeds a web view and does not itself register model tools. DSCODE's Browser
+preview captures an external Chrome connection. It does not drive that embedded
+web view, share its login state automatically, or present a live browser stream.
+Persistent profiles, Chrome attachment and experimental extension/WebMCP support
+are additional DSCODE connection choices, not evidence of better task quality.
+
 ## Start a task
 
 From this checkout, run `npm start`, then ask:
@@ -52,8 +73,9 @@ running. A new start gets fresh page IDs; interrupted actions are never replayed
 | `/browser use extension` | Experimental: share selected existing Chrome tabs through the DSCODE extension, without enabling a browser-wide remote-debugging port. |
 
 Stop all session browsers before changing defaults. These settings persist in
-`browser/config.json` under `DSH_HOME` (or `DSCODE_HOME`, falling back to
-`~/.dscode`). They apply to future starts. The agent cannot change browser mode
+`browser/config.json` under the native Harness home: a nonblank `DSH_HOME`,
+otherwise `~/.dsh`. The terminal launcher maps `DSCODE_HOME` into `DSH_HOME`.
+They apply to future starts. The agent cannot change browser mode
 through a tool. Dedicated profiles are separate from personal Chrome profiles;
 log in directly in the visible window when needed. The agent should keep that
 tab and hand control to you for login or 2FA, then inspect the same page again.
@@ -623,8 +645,8 @@ The source checkout can also package the DSCODE agent preset, custom-model
 and account settings, browser preview, durable session communication, cross-session
 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. Public npm distribution is still
-pending. The package does
+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
 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
@@ -632,9 +654,9 @@ macOS Accessibility permission.
 Choose this package or the browser-only bundle; enabling both duplicates their
 browser services.
 
-The current candidate's package name is `@toddzheng024/dscode-desktop`. It also
-includes [Plugin Hub](plugin-hub.md) for community discovery and installation
-through the official manager. The earlier private
+The Desktop plugin's package name is `@toddzheng024/dscode-desktop`. Version 0.7.35
+removes bundled [Plugin Hub](plugin-hub.md) functionality; older 0.7.33 and 0.7.34
+packages still include it. The earlier private
 `@toddzheng024/dscode-desktop-preset-probe` must be removed before installing
 this package; both register the same DSCODE components. Back up your Desktop
 state first. A separate macOS Desktop 0.2.0-rc.2 migration check preserved
@@ -716,20 +738,15 @@ desktop_package='/absolute/path/printed-by-pack-command.tgz'
 "$desktop_dsh" plugin --profile desktop add "$desktop_package" --ignore-scripts
 ```
 
-Reopen Desktop, choose **DSCODE** for a new session, and configure a model under
-**Settings → DSCODE models**, or connect a supported account under
-**Settings → DSCODE accounts**. Browser preview is available in the right sidebar.
-**Settings → DSCODE schedules** manages tasks for an open DSCODE session and
-explicitly enables or stops delivery. Its launch preference is saved; Desktop
-must remain open to deliver tasks. See [Desktop scheduling](triggers.md#experimental-desktop-scheduling)
-for restart, removal and permission behavior, and current qualification limits.
-
-The account page saves or removes the shared OpenRouter API key. Changes also
-affect terminal sessions and native routes reading that same credential file;
-environment-owned keys remain read-only. The saved key is never returned to the
-form. Choose **DSCODE OpenRouter** in the model picker for DSCODE reasoning
-controls, including Ultra on supported models. The native OpenRouter route
-remains available separately.
+Fully quit and reopen Desktop after installing or updating. In **Settings → General**, enable **Show coding view** and enable **Agent presets** in Plugins if disabled. Create a new session with **DSCODE**; existing sessions keep their original preset. Choose a model from the normal picker to reuse an existing Desktop account.
+
+In 0.7.35 and later, **Settings → DSCODE** groups Get started, Models, Accounts and Schedules as peer entries and follows the host's light/dark theme. **Plugins → DSCODE · Community** opens the same setup page. Models and Accounts are optional additions. Published 0.7.34 still has separate settings pages.
+
+Browser tools, the browser skill and `/browser` are mounted only in DSCODE sessions. Standard sessions retain their existing tools, and the DSCODE preview explains the preset boundary instead of starting a browser there. TUI Browser Use remains enabled through its existing composition. The Desktop package still supplies shared credential and subagent compatibility services; this scope change does not remove those Host adapters.
+
+**Settings → DSCODE → Schedules** manages tasks for an open DSCODE session and explicitly enables or stops delivery. Its launch preference is saved; Desktop must remain open to deliver tasks. See [Desktop scheduling](triggers.md#experimental-desktop-scheduling) for restart, removal and permission behavior, and current qualification limits.
+
+Desktop credentials now prefer the existing native store and save new keys there. Existing terminal keys remain a fallback when no native key is present; saving a Desktop key does not replace the terminal key. Explicit key removal clears both copies to prevent a legacy key from becoming active again. Environment-owned keys remain read-only, and the saved key is never returned to the form. Choose **DSCODE OpenRouter** for DSCODE reasoning controls, including Ultra on supported models. The native OpenRouter route remains available separately.
 
 For Grok, run `grok login` in a terminal and refresh the account status. DSCODE
 reads `~/.grok/auth.json` without changing or refreshing its tokens. For OpenCode

package/docs/custom-providers.md

@@ -36,7 +36,7 @@ editor and discovering models again does not replace it with a server-reported
 output limit. Models whose output budget has never been edited can still adopt
 the server's reported value.
 
-In Desktop's **Settings → DSCODE models**, **Discover models** immediately merges the returned models into the draft. Existing models keep their order, thinking mode and image-input choice; new models are appended. Reported limits refresh unless you have edited that value, including an output budget you deliberately left blank. Models absent from the response remain in the draft. Choose **Save provider** to persist the changes.
+In Desktop's **Settings → DSCODE → Models**, **Discover models** immediately merges the returned models into the draft. Existing models keep their order, thinking mode and image-input choice; new models are appended. Reported limits refresh unless you have edited that value, including an output budget you deliberately left blank. Models absent from the response remain in the draft. Choose **Save provider** to persist the changes.
 
 Thinking defaults to the server's behavior. Identified oMLX models also offer Off/On in the editor and Off/On in `/effort` (the stored effort IDs are `off` and `high`). Other custom APIs do not receive guessed reasoning parameters. Native Responses reasoning items and Anthropic thinking signatures are retained for replay to the same service, model and protocol.
 
@@ -44,7 +44,7 @@ Thinking defaults to the server's behavior. Identified oMLX models also offer Of
 
 In the model editor, set **Input → Text and images** only when that model and endpoint support image input. Existing configurations and newly discovered models default to **Text only**; DSCODE does not infer vision support from a model name. Discovery preserves your explicit choice. Changing the base URL, API format or model ID resets the editor's image choice to **Text only**, so enable it again for the new deployment.
 
-In the [experimental Desktop package](browser-use.md#install-the-experimental-combined-desktop-package), open **Settings → DSCODE models**, select the saved provider, enable the model's **Accepts images** checkbox and choose **Save provider**. Select that saved model in the session's model picker. The same explicit capability setting and request-image limits apply in both interfaces. The settings test checks text, streaming and tools; it does not test image understanding.
+In the [experimental Desktop package](browser-use.md#install-the-experimental-combined-desktop-package), open **Settings → DSCODE → Models**, select the saved provider, enable the model's **Accepts images** checkbox and choose **Save provider**. Select that saved model in the session's model picker. The same explicit capability setting and request-image limits apply in both interfaces. The settings test checks text, streaming and tools; it does not test image understanding.
 
 All three protocols can send user images, browser annotation screenshots and images returned by tools. DSCODE reads their durable attachments and sends image bytes to the configured API: Chat Completions uses `image_url` data URLs, Responses uses `input_image`, and Anthropic Messages uses base64 `image` blocks. Tool screenshots follow their tool result as user image content. Enabling this option does not add vision capability to a text-only server.
 
@@ -64,7 +64,7 @@ Automatic review follows its configured model route. When that route is Custom,
 
 ## Persistence
 
-Service and model configuration lives in `~/.dscode/providers.yaml`; keys use the existing owner-only `~/.dscode/credentials.yaml` store. Provider records contain no key values. Each service receives a stable `custom-…` ID and a derived `DSCODE_CUSTOM_CUSTOM_…_API_KEY` credential reference. An environment variable with that exact reference takes precedence over the saved key, following the existing credential-store rules.
+Service and model configuration lives in `~/.dscode/providers.yaml`; terminal keys use the existing owner-only `~/.dscode/credentials.yaml` store. In Desktop 0.7.35 and later, existing native credentials take precedence and new keys are saved to the native Harness store (`~/.dsh/.credentials.yaml` by default). Old DSCODE keys remain a fallback; explicit removal clears both copies to avoid reactivating a legacy key. Provider records contain no key values. Each service receives a stable `custom-…` ID and a derived `DSCODE_CUSTOM_CUSTOM_…_API_KEY` credential reference. An environment variable with that exact reference takes precedence over the saved key, following the existing credential-store rules.
 
 Configuration is shared across projects and installed versions, written atomically, and reloaded by other running Hosts. Stale editors cannot overwrite newer configuration. Renaming a service preserves its ID, so persisted sessions continue to resolve it. Removing a provider removes its route and writable stored credential; it does not reroute existing sessions or delete their history. An environment-supplied key remains in the environment. If it masks a stored key, clear the environment override before removing the provider to remove that stored key too.
 

package/docs/demo.md

@@ -1,15 +1,81 @@
-# The 90-second demo
+# Demo guide
 
-Most coding agents work alone. This script shows the three things DSCODE does
-instead — sessions that can see each other, an independent reviewer for code and
-for approvals, and side questions that never disturb the main conversation — in
-an order a stranger can follow.
+## Desktop feature summary
+
+The 0.7.35 Desktop preview installs into official Harness Desktop.
+Its qualified target is macOS Apple Silicon with runtime **0.2.0-rc.2**.
+This version removes bundled Hub functionality. Demonstrate DSCODE on its own
+and state which version is being shown.
+
+| Area | What the user gains | Boundary |
+| --- | --- | --- |
+| DSCODE coding workflow | A DSCODE preset with custom model/account settings, session communication, memory, usage and delegation views | Terminal-only panels retain their terminal UI; model behavior depends on the configured provider. |
+| DSCODE browser integration | Per-site and Developer permissions, screenshot preview and point annotations delivered to the conversation, manual login handoff | Official Harness already has Browser Use. DSCODE connects external Chrome; it does not enhance or share login state with the official embedded browser. |
+| DSCODE optional services | Email inbox integration and scheduled work | Account configuration and explicit opt-in are required. Desktop must stay open for scheduled delivery. |
+
+Hub community discovery belongs in a separate product demo. The removal does
+not deliver a standalone Hub Desktop package. See [Plugin Hub](plugin-hub.md)
+for the behavior of earlier published versions.
+
+## Five-minute Desktop walkthrough draft
+
+Allow separate time for downloads and account setup. This complete timed
+walkthrough has not been rehearsed with a live model.
+
+### Prepare
+
+1. Use a disposable Desktop profile and scratch workspace. For the published
+   demo, install `@toddzheng024/dscode-desktop@0.7.35` through **Plugins → Add
+   plugin**, then choose **Enable now**. Fully quit and reopen Desktop after
+   updating. Hub is separate from this package. For local development builds,
+   follow the [installation guide](browser-use.md#install-the-experimental-combined-desktop-package)
+   and identify the checkout being demonstrated.
+2. Select the **DSCODE** preset when creating the session. Harness 0.2.0-rc.2
+   gates the preset picker behind **Show coding view**; ensure that option and
+   the Agent presets UI are enabled before recording. A Standard session does
+   not acquire the complete DSCODE preset just because the package is installed.
+3. Configure a model in private, confirm one short response and install Chrome.
+   For annotations, choose a model that accepts images. Do not record API keys,
+   account login or personal workspace contents.
+4. Rehearse one small coding task and the browser annotation with that model.
+   Keep the matching release page or local-build information ready. A local
+   build must not be presented as the published 0.7.35 archive.
+
+### Walkthrough
+
+| Approximate time | Action | Point to explain |
+| --- | --- | --- |
+| 0:00–0:30 | Show the enabled DSCODE plugin and a DSCODE session. | Existing DSH Desktop users can add the coding workflow through a plugin. |
+| 0:30–2:00 | Run the rehearsed small coding task in the scratch workspace. | Show actual changes and verification; model quality is not established by the installation checks. |
+| 2:00–4:00 | Ask the agent to open https://example.com. Grant that origin if requested. In **Browser preview**, refresh, select a point, enter “Summarize the text at this point” and choose **Send annotation**. | Basic browsing overlaps official Browser Use. The demonstrated DSCODE additions are the permission controls and screenshot/point handoff into the conversation. |
+| 4:00–4:30 | Open the session usage view; show the delegation view only if the task actually delegated. | Views reflect the current DSCODE session and available records. |
+| 4:30–5:00 | Show the matching install specification and release notes, or label the local build. | Published availability and an unreleased change are distinct states. |
+
+### Rehearsal and reset
+
+- Reopen Desktop after a package update. Confirm both plugin activation and a
+  working new DSCODE session before starting the recording.
+- Refresh the screenshot and select a new point after navigation or expiry.
+  Image understanding needs an image-capable model. Describe text-only delivery
+  as text-only.
+- Stop the session browser between rehearsals. Its Chrome profile and login
+  state are separate from the official embedded browser.
+- Keep standalone DMG delivery, Hub integration, coordinated update/changelog
+  UI, Profile rollback and native Computer Use permission qualification out of
+  this demo's claims. See [Browser use](browser-use.md) and the
+  [0.7.35 release notes](releases/0.7.35.md) for published behavior and limits.
+
+## The 90-second terminal demo
+
+The terminal script shows sessions that can see each other, an independent
+reviewer for code and approvals, and side questions that leave the main
+conversation's context unchanged.
 
 The recording lands in `assets/demo.gif`; put that image directly under the
-README tagline. Every command below is real, so the demo is reproducible: the
-only unpredictable part is the model's own wording.
+README tagline. Rehearse the commands below with the selected model before
+recording: response quality and timing are not established by this script.
 
-## Record it
+### Record it
 
 ```sh
 brew install asciinema agg
@@ -39,12 +105,12 @@ Before you hit record:
   or full home paths). Any interface language works; the captions below are
   English.
 
-## Shot list
+### Shot list
 
 | Time | Screen | Do this | Say this (captions) |
 |---|---|---|---|
 | 0:00–0:06 | Shell in the scratch repo | `dscode` | "A coding agent in your terminal — macOS, local, one pinned harness." |
-| 0:06–0:22 | TUI, main session | Type `Add a bounds check to parse() in parser.ts and run the tests.` | "It reads the file, edits it, runs the tests." |
+| 0:06–0:22 | TUI, main session | Type `Trim whitespace and ignore empty fields in parse() in parser.ts. Add and run tests.` | "It reads the file, edits it, runs the tests." |
 | 0:22–0:36 | Same terminal | `/btw why would the first turn have a cold cache?` — leave the main turn running | "A side question runs in its own read-only child session. The answer never enters the main conversation." |
 | 0:36–0:56 | Second terminal | `dscode sessions` then `dscode send <the other session id> --steer "review the change in parser.ts and reply with what you would change"` | "Two sessions on one machine can find each other, hand work over and answer." |
 | 0:56–1:06 | Back in the first terminal | Show the reply arriving (`/mailbox`, or the agent's `read_session`/`send_session` tools if you asked it to hand the review over itself) | "The answer comes back as a message, not as a new task." |
@@ -60,7 +126,7 @@ Two beats worth keeping if you have the seconds:
 - `/agents` at the end: the `/btw` child session is a real, read-only session,
   not a hidden prompt.
 
-## Reproduce it without recording
+### Reproduce it without recording
 
 ```sh
 npm i -g @toddzheng024/dscode

package/docs/hub-distribution.md

@@ -33,6 +33,24 @@ The default state directory is `~/.local/share/dscode-hub`, overridable with `DS
 
 A user who already has dsh-hub installed can apply directly, but must use pnpm 10.15.1, set a dedicated `DSH_HOME` and `DSH_AGENTS_HOME`, and set `npm_config_ignore_scripts=true` on the install command. The launcher is recommended because it unifies those conditions.
 
+### Desktop users
+
+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
+**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
+[Desktop installation](browser-use.md#install-the-experimental-combined-desktop-package)
+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
+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.
+
 ## Release checklist
 
 Cutting a release from this repository, in order. The rule that matters most: **the git tag must equal `v<package.json version>`, and that version must not already be on npm from a different build.**
@@ -118,8 +136,8 @@ node scripts/verify-desktop-registry.mjs .research/desktop-release-runtime --loc
 `prepare:desktop` provisions exact direct dependencies with install scripts
 disabled; it refuses to overwrite an unrelated project. `release:desktop`
 builds a public candidate only for Harness 0.2.0-rc.2, then unpacks those exact
-bytes for Host startup/restart, browser, annotation, isolation and authenticated
-Hub RPC checks. The source runtime is checked for unintended changes. The
+bytes for Host startup/restart, browser, annotation and isolation checks, plus
+checks that Hub files, UI, tools and endpoint are absent. The source runtime is checked for unintended changes. The
 local install rehearsal additionally resolves dependencies in a new native
 Harness profile and boots the installed package; it does not establish public
 npm availability or drive the Electron UI.
@@ -137,15 +155,24 @@ npm run publish:desktop -- credentials
 npm run publish:desktop -- npm
 npm run publish:desktop -- hub
 npm run publish:desktop -- verify
+npm run publish:desktop -- promote
 ```
 
 Each phase checks the archive and receipt again. The npm phase publishes with
 `--tag preview`; an existing version is reusable only with identical integrity.
 The Hub phase syncs the package and requires the exact version, integrity and
-Desktop compatibility to resolve. The final phase downloads public bytes,
+Desktop compatibility to resolve. A newly published package can appear on
+the npm version endpoint before the Hub can fetch its package index. In this
+post-publication phase, `package_not_found` and an index missing the exact
+version retry up to 40 times, 15 seconds apart. Other rejections and credential
+errors stop immediately; the final integrity and compatibility checks still
+apply. The final phase downloads public bytes,
 checks their SHA-256, and installs the exact npm version into a new native
-Harness profile before booting it and checking the preset and Hub RPC. The
-result is saved as `artifacts/local/desktop-public-install.json`. No model
+Harness profile before booting it and checking the preset and absence of bundled Hub tools and endpoint. The
+result is saved as `artifacts/local/desktop-public-install.json`. The `promote`
+phase requires this public receipt to match the candidate, then updates npm
+`latest` to the same version as `preview`. Both entry points serve the current
+qualified preview; the Desktop support boundary remains unchanged. No model
 account is used, and no real-model quality claim follows from these probes.
 
 The existing npm token must permit the new Desktop package. Successful `whoami`
@@ -153,7 +180,7 @@ proves authentication only; the first publish establishes write permission.
 Desktop publication does not replace the terminal profile, create a DMG, or
 implement an automatic Desktop updater. GitHub Release attaches the Desktop
 archive, checksum and instructions alongside the terminal assets. Follow the
-[Plugin Hub guide](plugin-hub.md) for discovery and official management.
+[Plugin Hub guide](plugin-hub.md) for the separation from DSCODE and earlier-version behavior.
 
 ### Login-free publishing (local machine)
 

package/docs/memory.md

@@ -59,7 +59,7 @@ renderer interaction with the slash commands.
 
 A SQLite lease coordinates multiple processes and the background holds a heartbeat; a source session under recovery, an expired lease and a clear operation all stop an old result from committing. The consolidation model has no shell, MCP, file-write or delegation tools, and file paths are determined by the plugin.
 
-Directory resolution order: plugin `root` → `DSCODE_MEMORY_HOME` → `$DSCODE_HOME/memories` → `$DSH_HOME/memories` → `~/.local/share/dscode-hub/memories`. A source launch normally uses the project's `.runtime/memories`, and an npm launch uses the launcher's state directory. To share memory between installations, set the same `DSCODE_MEMORY_HOME` explicitly.
+Directory resolution order: plugin `root` → `DSCODE_MEMORY_HOME` → the native Harness home plus `memories`. Harness resolves a nonblank `DSH_HOME` (including supported tilde paths), otherwise `~/.dsh`. A source launch normally sets the project's `.runtime` as that home; the npm launcher maps its `DSCODE_HOME` into `DSH_HOME`. To share memory between installations, set the same `DSCODE_MEMORY_HOME` explicitly. Version 0.7.34 does not automatically move memory left in an earlier fallback directory.
 
 ```text
 memories/

package/docs/plugin-hub.md

@@ -1,68 +1,35 @@
-# Plugin Hub in Harness Desktop
+# DSCODE and Plugin Hub
 
-The DSCODE Desktop candidate includes **Settings → Plugin Hub**, backed by
-[DSH Plugin Hub](https://dshpluginhub.ai). It uses the same public catalog as
-the Hub website and CLI. No Hub login is required to browse.
+DSCODE and [DSH Plugin Hub](https://dshpluginhub.ai) are separate products.
+Installing DSCODE should not also install a Hub browsing interface.
 
-## Find and inspect plugins
+## Version 0.7.35 and later
 
-Enter a package name or describe a capability, optionally choose a category,
-and select **Search**. **Load more plugins** continues the current search.
-Open **View details** to read the description, repository, license, weekly
-downloads, publisher indicators, reported security checks and declared
-compatibility. The website link opens the corresponding Hub listing.
+The Desktop build no longer includes the Hub settings page, Host endpoint,
+`plugin_hub_search` or `plugin_hub_info` tools, Hub source files or Hub-specific
+runtime dependencies. DSCODE sessions do not require the community catalog to
+start or use coding and browser features.
 
-Publisher verification and a passing scan do not guarantee safety. Missing,
-failed and incomplete scans remain visible. Compatibility declarations come
-from the catalog; the official installer also checks the actual package.
+The package retains its catalog listing metadata so people can discover DSCODE
+through Hub. Release-time catalog synchronization and the terminal launcher's
+existing Hub distribution mechanism remain in place. Neither adds the Desktop
+Hub interface to a user's DSCODE installation.
 
-In a DSCODE conversation, ask the agent to find a plugin. The read-only
-`plugin_hub_search` and `plugin_hub_info` tools use the same catalog and Desktop
-compatibility checks. These tools do not install plugins, change the Profile
-or expose account credentials. Catalog descriptions are third-party data.
-The native Standard preset does not receive these tools.
+Hub discovery is available on the separate website. This change does not publish
+a standalone Hub Desktop plugin or move Hub into the official Plugins page.
 
-## Install and enable
+## Published versions 0.7.33 and 0.7.34
 
-1. Open the package details and choose **Review installation**.
-2. Review the exact npm package, version and registry returned by the official
-   plugin manager, alongside the Hub's scan and compatibility information.
-3. Choose **Confirm installation**. The official manager downloads the package
-   and dependencies. **Cancel installation** requests cancellation through that
-   manager; the displayed outcome determines whether it completed in time.
-4. Select **Manage installed plugin**, then enable and configure it in the
-   official **Settings → Plugins** page.
+These releases still contain **Settings → Plugin Hub**, catalog search and
+categories, package details, and the two read-only discovery tools in DSCODE
+sessions. Their installation handoff delegates to the official plugin manager;
+enabling, configuration and removal stay in **Settings → Plugins**.
 
-Installation leaves the plugin disabled. Enabling third-party plugins runs
-their code in the Host. Build-script approvals, enable/disable, configuration
-and removal remain with the official plugin manager. When it reports a failure,
-cancellation, override or restart requirement, the Hub preserves that outcome.
-It does not report every completed package command as successful activation.
+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).
+Fully quit and reopen Desktop after updating; an already running Host may keep
+the old plugin modules loaded.
 
-An installation preview expires after five minutes. Reopen the preview if it
-expires. Closing and reopening the Hub page recovers the latest operation while
-the same Host remains running. After a Host restart, check **Plugins** before
-retrying; the Hub's operation history is not persisted.
-
-## Current boundaries
-
-- The first integration installs the catalog's latest exact npm version. It
-  checks DSH and Node ranges, platform, interface support, withdrawal and
-  deprecation. Git/tarball-only entries remain discoverable but are not installed
-  through this integration.
-- Already available bundles link to official management. This page does not
-  replace them, select older versions, check for updates or roll back a Profile.
-- Searches cover the community catalog, including packages for other Harness
-  interfaces. Details explain when a package does not fit this Desktop.
-- The DSCODE terminal package and Desktop package are separate entries. A
-  terminal-only package is not made Desktop-compatible by appearing in search.
-- Search queries and package lookups go to `api.dshpluginhub.ai`. Provider keys,
-  conversation text, workspace files and local credentials are not sent by this
-  catalog client. The agent may include task terms in a query you ask it to make.
-- This guide describes the source candidate. Public Desktop npm distribution is still
-  being qualified. Official Add plugin installation, Hub installation with
-  handoff to official management, and migration from the legacy probe name
-  have passed on macOS Desktop 0.2.0-rc.2.
-
-See [Desktop candidate installation](browser-use.md#install-the-experimental-combined-desktop-package)
-and [distribution](hub-distribution.md) for package setup and release status.
+Historical Hub installation and UI verification applies to those earlier
+versions. It does not establish availability of a separate Hub Desktop package.
+See [distribution](hub-distribution.md) for release gates.

package/docs/releases/0.7.33.md

@@ -1,12 +1,12 @@
 # DSCODE 0.7.33
 
-This release candidate packages DSCODE for official Harness Desktop, adds community plugin discovery through our Plugin Hub, and establishes a separate Desktop publication path alongside the terminal release.
+This release packages DSCODE for official Harness Desktop, adds community plugin discovery through our Plugin Hub, and establishes a separate Desktop publication path alongside the terminal release.
 
 - **Formal Desktop plugin:** `@toddzheng024/dscode-desktop` has an icon, English/Chinese display metadata, package-specific instructions and an exact Harness peer version. It adds coding, browser preview, collaboration, memory, email and opt-in scheduling to the official application. The qualified target is macOS Apple Silicon with Harness runtime `0.2.0-rc.2`. Other runtime candidates remain private. A standalone application, DMG and automatic Desktop updates are deferred.
 - **Plugin Hub:** native Settings and read-only conversation tools share the Hub API and schema. Search, categories, numbered pagination and details expose compatibility and reported security information. Installation requires an exact npm version, official inspection and explicit confirmation. New plugins remain disabled, and the UI opens official management for enabling, configuration and removal. Git-only entries remain visible without installation; Hub Profile application and rollback are outside this integration. A reported scan result is not a guarantee about plugin behavior.
 - **Installation and migration:** official Add plugin accepts the archive, followed by Enable now. Users of the earlier private probe remove its old package name before installing the formal package, because both register the same components. The migration check verifies preserved sessions, credentials, configuration and user patches; keep a backup for your own state. Ordinary same-name replacement, incompatible-update refusal, removal and reinstallation have separate lifecycle checks.
 - **Reproducible distribution steps:** an independent Desktop runtime builds a public candidate, then the exact archive is unpacked and exercised through native Host startup/restart and browser probes. Publication verifies its checksums, version, compatibility and qualification receipt, publishes with the npm `preview` tag, synchronizes the Hub and checks the served public bytes. GitHub assets include the archive, checksum, installation README and release notes. Public availability is established by successful publication and registry verification, not by a local build.
-- **Browser and model workflows:** this version includes the browser and custom-provider work accumulated since 0.7.32. Browser access uses site and Developer grants, document-bound WebMCP discovery, explicit handoff and retained tabs. Desktop previews keep annotation drafts across navigation and permission changes while rejecting expired or replaced documents. Custom services support Chat Completions, Responses and Anthropic Messages, optional images, manual model limits and cancellable discovery/tests. The detailed fixes and boundaries are recorded in the [changelog](../CHANGELOG.md).
+- **Browser and model workflows:** this version includes the browser and custom-provider work accumulated since 0.7.32. Browser access uses site and Developer grants, document-bound WebMCP discovery, explicit handoff and retained tabs. Desktop previews keep annotation drafts across navigation and permission changes while rejecting expired or replaced documents. Custom services support Chat Completions, Responses and Anthropic Messages, optional images, manual model limits and cancellable discovery/tests. The detailed fixes and boundaries are recorded in the [changelog](https://github.com/qiz029/dscode/blob/main/docs/CHANGELOG.md).
 
 Verification: `npm run check` passed on the release implementation (1,067
 unit/component cases, 79.99% full-source line coverage, both TypeScript checks,
@@ -23,8 +23,15 @@ The official macOS application separately installed and enabled the private
 formal archive, and its Hub installed `dsh-theme-plugin@0.3.3` disabled and
 opened official management. A native lifecycle check migrated the old probe
 name and preserved state. Those rendered GUI/migration observations used the
-private 0.7.32 candidate. Public npm publication and the post-publication
-installation check remain pending; the retained local receipts do not prove
-that users can already download this version from the registry.
+private 0.7.32 candidate. The launcher, terminal bundle and Desktop plugin were subsequently published
+to npm at 0.7.33, and the Hub lists both the terminal profile and Desktop plugin.
+The final release run passed 1,068 unit/component cases at 79.98% coverage and
+all other maintained gates. Public Desktop installation, the installed Host
+and Hub RPC passed in CI. A separate fresh public terminal installation passed
+startup configuration, terminal imports and Hub doctor. The GitHub Desktop
+archive and checksum match the qualified npm bytes. The first two publication
+attempts encountered npm propagation delay; rerunning the same verified
+artifacts completed publication without changing versions or bytes. Detailed
+receipts and boundaries are recorded in [Verification](https://github.com/qiz029/dscode/blob/main/docs/verification.md).
 
 Unverified paths: real-model task quality, native Computer Use screenshot/input with macOS Accessibility permission, other OS/architecture/runtime combinations, and third-party plugin behavior after enabling. General remote HTTP MCP retains separate runtime compatibility/security work. Scripted model fixtures and browser probes do not establish live model quality. Demo preparation is deferred until distribution is ready.

package/docs/releases/0.7.34.md

@@ -0,0 +1,24 @@
+# DSCODE 0.7.34
+
+This release fixes Desktop plugin activation during a normal application launch without an exported `DSH_HOME`.
+
+- **Default Desktop home:** workspace discovery, email, scheduling and automatic permission review previously refused to activate unless `DSH_HOME` was explicitly set. They now use the same native home resolver as Harness: a nonblank override, including supported tilde paths, or `~/.dsh`. Users seeing “4 entries did not activate” in 0.7.33 can install `@toddzheng024/dscode-desktop@0.7.34` and enable it again. No shell environment setup is required.
+- **Consistent local state:** browser permissions/configuration, memory, session cards and messaging, delegation, review baselines, provider caches, diagnostics and usage resolve that same home. Explicit memory/audit directories remain supported, and the terminal launcher still translates `DSCODE_HOME` into its native Harness home. Shared account credentials and mail keep their existing locations. Old fallback data is not migrated automatically.
+- **Installation qualification:** public installation now deliberately omits `DSH_HOME` and checks workspace, email, scheduling and automatic-review activation. A package cannot pass the publication gate using only an explicitly configured home. Native Host and signed macOS lifecycle verifiers also accept a default-home scenario. The earlier 0.7.33 checks set `DSH_HOME`, which concealed this activation failure.
+- **Distribution maintenance:** this release includes bounded retries for npm-to-Hub propagation and the Desktop/Hub demo guide added after 0.7.33. Versioned release notes, checksums, compatibility and installation instructions continue to ship with the package.
+
+Verification: the default-home native Host reproduced the original activation
+failure before the fix and passed startup/restart after it. The signed macOS
+application passed installation, upgrade, incompatible-update refusal, removal
+and reinstallation with `DSH_HOME` absent, including state preservation and
+browser checks. `npm run check` passed 1,073 unit/component cases at 80.17%
+full-source line coverage, both TypeScript checks, native integration, package
+checks and 63 eval cases. Eight focused home-resolution/release-gate tests also
+passed. The exact Desktop candidate passed native Host startup/restart and
+browser qualification. Installation receipts and public release status are
+recorded in the [verification record](https://github.com/qiz029/dscode/blob/main/docs/verification.md).
+
+The Desktop target remains macOS Apple Silicon with Harness runtime 0.2.0-rc.2.
+Live-model task quality, native Computer Use Accessibility qualification and
+other platform/runtime combinations are not established by these checks. This
+release does not provide a standalone DMG or migrate old fallback data.