[T-Auto]

What was wrong

DSH product-facing types and lazy scope/profile-host lookups were imported from many OPS modules directly. The plugin avoided load-time value imports, but it did not have one auditable project-owned adapter boundary. Its compatibility declaration also stopped at 0.2.1-rc.2, despite the published 0.2.1-rc.3 and 0.2.1-rc.4 host lines.

The change

• Add the project-owned src/adapter/dsh boundary for DSH type surfaces and runtime host loading.
• Route host-facing type imports through that adapter without changing Cordis registration, prompt, policy, subprocess, PTC, result, UI, worker or cleanup logic.
• Keep dsh-scope lazy and resolve it once at each existing asynchronous adapter seam; no DSH value package is evaluated during plugin module loading.
• Expose the adapter runtime entry as dsh-ops/adapter/dsh for the package's host integration boundary.
• Widen the bounded host range to >=0.2.0-rc.2 <0.2.2-0, covering 0.2.0-rc.2, 0.2.1-rc.2, 0.2.1-rc.3, 0.2.1-rc.4 and 0.2.1, while rejecting 0.2.0-rc.1, 0.2.2-rc.1 and 0.3.0.
• Add a regression test that fails if host imports escape the adapter or scope loading becomes eager.

No @dsh-std protocol support is claimed: the current standard documents provide generic adapter/lifecycle concepts but no normative DSH tool, sandbox, subprocess, PTC or permission protocol for OPS to implement. The product adapter remains project-owned as required by dsh-std.

Validation

node scripts/validate-manifest.mjs
validate-manifest: all 146 checks passed

node test/run.mjs
147 suite(s) passed, 4 skipped

npm run check:size
440 code files checked, all at or under 1000 lines

Focused adapter-boundary, host-metadata, package-source, discovery and native/runtime suites passed.
Native worker: win32-x64, 3,881,472 bytes; staged provenance check passed.
Windows Bash IPC proxies rebuilt and staged; provenance check passed.

The 4 skips are the existing TUI host/native environment skips. The local full run used the staged Windows worker and Bash IPC payload. An isolated DSH 0.2.1-rc.4 host installation was created through the Clash proxy; the real host metadata/composition suite passed 4/4 against its dsh-app-boot compatibility evaluator. rc4 was published less than seven days ago, so no new rc4 dependency was added to this repository; the fixture is outside the repository and is only validation evidence.

Environment

Windows x64, Node 24, Rust 1.97.1, exact source branch from origin/main commit a6e215a; no Desktop profile changes, npm publication, merge or release performed.