# Harness 0.2.0-rc.2 adaptation

Plugin 0.2.0 targets official Harness tag `dsh-v0.2.0-rc.2`, commit `639ed015397290b3745d163aafe02ffee4aa3f84`, for distribution under npm `latest`. This follows the plugin 0.2.0-alpha.1 preview tested against master `21638c56315ae6a2b552d6091945d3144c9af32e`. Plugin and host versions are independent: Harness still labels its release RC.

The earlier preview rejects this host because its exact peer declarations and runtime guard do not include 0.2.0-rc.2. This release adds that exact host, makes it recommended, and updates the official DSH dependency cohort. It retains the independent `sandbox-auto` identity, workspace-write + ask baseline, producer-owned message sources, append-only legacy identity migration and delegated authority protections. An unlisted future host, including a subsequent final 0.2.0 release, is not automatically admitted.

The consumed permission-presets, approval, tool pipeline, Session, system-prompt, subagent core and LLM source trees are unchanged across the two revisions. Related shell changes add deletion-path guidance and tolerate padded PowerShell completion lines. Those changes do not alter the plugin's consumed call or event contracts. Source equality alone does not establish runtime compatibility; `validation/0.2.0/source-contracts.json` records the comparison separately from execution results.

This release's runtime acceptance scope is the official, exact npm Harness 0.2.0-rc.2 package cohort through the `dsh --profile headless` product entry on macOS arm64, using the existing `/tmp` workspace. The release process requires the same immutable plugin tarball for the product-entry fixture, real DeepSeek API checks, three-process persistence checks and publication. Recorded results, artifact identity and dependency evidence in `release-candidate.json` and `validation/0.2.0` determine which checks passed; neither this document nor a compatibility declaration substitutes for those results. Persistence checks cover native V4 logs carrying the old Auto identity, including subagent lineage, and do not establish V3-to-V4 artifact-format migration compatibility. Historical hosts remain declared and are checked by the product-entry CI matrix; they are not all covered by the local new-host run.

At the user's explicit request, this release does not repeat Desktop installation or browser UI acceptance. The user has already installed the official application. The checks above must not be described as a test of the 0.2.0-rc.2 Desktop installer, Electron application, plugin-manager UI or Windows sandbox. Earlier preview Desktop evidence remains historical and is not relabeled as evidence for this release.

The documented installation routes are the application plugin manager with `@nanmicoder/dsh-auto-mode` (npm latest), the exact spec `@nanmicoder/dsh-auto-mode@0.2.0`, or `https://github.com/NanmiCoder/dsh-auto-mode`. Registry web pages are not install specs. Documenting these routes does not claim that a Desktop UI installation was exercised in this release run.