dsh-creator-mode-plus 0.3.8

package/AGENTS.md

@@ -0,0 +1,40 @@
+# Creator Mode+ repository orders
+
+This repository contains only the DSH-side fixed bridge and its user preset. DSHX outside the Host is the supervisor. Official DeepSeek Harness runtime source outranks this repository when contracts disagree.
+
+Read [docs/bridge-contract.md](docs/bridge-contract.md) and [docs/dshx-v0.7-alignment.md](docs/dshx-v0.7-alignment.md) before changing tool arguments, lifecycle behavior, compatibility ranges, installation, migration, or Harness-update guidance.
+
+## Change gates
+
+- Keep the model-facing surface to the ten named tools, including `dshx_hot_reload` and the session-bound `dshx_browser_open`. Every argument must remain schema-bounded and independently allowlisted in `src/runner.js`. Test the exact argv behind all ten tools; a registration-only test is insufficient.
+- `dshx_hot_reload` accepts only a claimed plugin id. Derive Host/profile/port and session provenance inside the bridge. Require checked same-PID replacement and disposal evidence; it grants no shell, arbitrary path, or process-control authority. Module replacement never proves feature behavior.
+- Require the complete stable DSHX `>=0.7.8 <0.8.0` contract, not only a matching version string. Atomic same-Home Host discovery/attach, identity-bound start/restart/update gates, isolated verification Home, Creator, watched-plugin removal, external safe profile-bundle removal, proactive Guardian integrity quarantine, RC2 boot-manifest activation, managed-shell, Harness Update Assistant, and their knowledge contracts must be present before the bridge or installer mutates anything.
+- Preserve bridge-v2 provenance: session id comes from `exec.agent.id`, not model input. Claim one plugin per session before any named operation; different plugins may run concurrently, while the same plugin fails closed for a second owner.
+- Preserve workspace provenance: scaffold destination comes from `exec.agent.session.header.cwd`, never model input. If the Harness plugin path is outside that workspace, DSHX owns the atomic source-plus-symlink transaction.
+- Preserve automatic session-start Guardian arm, agent-dispose claim release, adopted-launcher lifetime tracking, exact-session recovery steering, and incident acknowledgement. Never register or wrap Host signal handlers.
+- Keep Host start, stop, restart, arbitrary shell, arbitrary argv, paths, profile selection, and ports outside model input.
+- Treat App, direct CLI, and dshx as launchers for one long-lived Web Host per `DSH_HOME`. Duplicate/unknown Host visibility fails closed; isolated verification must never be retained.
+- Keep Harness `update prepare`, `verify`, `apply`, and `rollback` outside the Creator session. DSHX v0.7 permits only read-only `update plan` from a managed shell; this does not become a bridge update tool.
+- Preserve the ordered `activate-new-client` DSHX operation; profile linking and resolution happen before watched-patch mutation.
+- Preserve the `dshx_remove_plugin` order: quarantine/remove the watched Host row, prove same-PID absence, use the official profile remover while the dependency exists, prove dependency/link absence, and detach only target-verified plugin-owned symlinks. Partial attempts resume from durable quarantine without rerunning package removal for an already-absent dependency. Preserve source and never expose recursive source deletion.
+- Keep boot-captured bundle removal outside the ten-tool bridge. Creator Mode+ may hand it to external `dshx plugin remove`, but must never expose that command through the managed shell or reinterpret it as `dshx_remove_plugin` watched-row success.
+- Keep the preset-scoped bash guard narrow: block claimed plugin-root, Harness-link, and active-profile teardown while allowing ordinary file/component cleanup inside a plugin. Guardian must independently quarantine a claimed watched row when its profile link disappears.
+- Keep Host recovery outside DSH and bounded to one restart plus a crash-loop fuse. Official client-Loader recovery must remain same-origin, Host-stamped, uniquely attributed, quarantined before reload, and separate from arbitrary render/visual/function failures. Never expose internal `creator watch/release/disarm/client-failure/recovery` argv as model inputs.
+- Treat preset generations as concurrent. Any process-global route or resource must use a Host-scoped lease shared across independently loaded module generations, and must have a regression test that mounts two generations before either is disposed.
+- A managed upgrade that does not change `agent.cordis.yml` bytes must preserve that file's exact filesystem stamp. Do not retrigger preset generation for skill, metadata, or bundled-asset-only changes.
+- Route structured outcomes by scope. A checked server with only module-HMR evidence pending returns HOT_RELOAD_READY and its next fixed action. Browser-adapter failures block browser verification, not independent activation. Real source, ownership, authentication and Host-identity failures block their dependent operation.
+- Edit only this package and user-owned presets. Never patch Harness core or shipped presets.
+- Retain source, Host, client-manifest, page-load, and visual evidence internally. User-facing updates state plugin completion, verified features and remaining work; expose operational details only for a user question or required user action.
+
+## Release gate
+
+Run `npm run check`, `DSHX_HARNESS=<absolute-checkout> npm run test:native`, `npm run verify:dshx -- --harness <absolute-checkout>`, `npm run verify:harness-install -- --harness <absolute-checkout>`, DSHX `check <absolute-package-path> --harness <absolute-checkout>`, and `npm pack --dry-run`. Inspect the exact staged paths before committing. A release is ready only when every fixed-tool argv and internal lifecycle hook traverses the allowlist, and provenance, cross-generation route leasing, same-origin Loader recovery, recovery steering, full v0.7 capability attestation, real shipped-Standard install, fresh-install, stamp-stable managed-upgrade, legacy-migration, and package-contract tests pass. Report RC2 static/package acceptance separately from live Host, page-load, and visual acceptance.
+
+## User-confirmed takeover
+
+`dshx_request_takeover({name})` is the only model-facing handoff entry. It uses
+the public `userQuestions` service; an approval/request auto-allow or model
+boolean is not confirmation. A Host-lifetime, durable ownership fence blocks
+all tools in revoked old sessions except status and a new takeover request;
+this is separate from the narrow destructive-shell guard. It persists across
+preset generations, and never deletes session locks or restarts the Host.

package/CHANGELOG.md

@@ -0,0 +1,104 @@
+# Changelog
+
+## 0.3.8 - 2026-09-21
+
+- Add `dshx_request_takeover`: show the actual claim owner in the current conversation and transfer only after an explicit answer through the native user-question service. Cancellation is the default.
+- Stop and await the old session, its runtime-owned children, jobs and terminals before atomic DSHX transfer; keep durable old-session fences across preset reloads.
+- Bind each confirmation to one claim snapshot and one short-lived private CLI grant; reject stale confirmation, grant replay, unknown owners and incomplete stopping.
+- Require DSHX `>=0.7.8 <0.8.0` and attest its takeover capability. Keep all ten model tools schema-bounded.
+- Verify native questions, Core guards, jobs and actual CLI processes with `npm run test:native` against an explicit Harness checkout. Human UI click-through acceptance remains unverified; automated answers are not human acceptance.
+
+## 0.3.7 - 2026-09-15
+
+- Verify the conversational create, activate, server hot-reload and remove flow with DSHX 0.7.7 on the live RC2 Host. Pair new-client cache recovery with that DSHX version.
+
+- Pair self-upgrade with the explicit external DSHX mixed-mount transaction when root and session instances share the Creator module.
+
+- Continue checked server activation through an explicit HOT_RELOAD_READY state and fixed next action; preserve the original CLI code for old evidence-only plans.
+- Scope browser-adapter failures to verification and retain independent activation actions.
+- Rewrite the Agent workflow with branch references, persistent installation authorization and concrete feature acceptance.
+- Preserve the established fixed bridge and native approval guards for ordinary Creator sessions.
+
+## 0.3.6 - 2026-09-11
+
+- Adapt the user preset to Harness 0.1.5-rc.2 persona config: write `prefix`/`suffix` instead of the removed `text` field. A leftover `text` composition is migrated on `--upgrade` and again when the Host plugin loads, so other installs do not have to edit DSH source.
+- Fresh installs from the current Standard preset use the official 0.1.5 persona shape; RC1 `text` Standard copies still install and are rewritten to `prefix`.
+
+## 0.3.5 - 2026-09-11
+
+- Attest DSHX 0.7.6's Harness `dsh-v0.1.5-rc.2` plugin contract (`compat-0.1.5` / `compat-015-*`) on the same Creator Bridge v2 range `>=0.7.5 <0.8.0`.
+- Document the authenticated Web line through `0.1.5-rc.2`. Live Host, page-load, and visual acceptance remain separate evidence.
+
+## 0.3.4 - 2026-09-06
+
+- Require DSHX `>=0.7.5 <0.8.0` and attest the atomic same-Home operation lock, PID/start-time/Home/profile/root binding, post-spawn discovery, and apply/rollback live-Host guard.
+- Keep Creator Bridge v2 and its seven fixed tools unchanged; Host process control and mutating Harness update stages remain external-supervisor-only.
+- Support Harness 0.1.2-rc.1's relocated shipped Standard preset and authenticated Host proofs through the public Connection service. Credentials stay in the child process environment, outside model arguments and output.
+- An already-loaded older server bridge needs the server activation branch; ordinary watched configuration and new-client development do not automatically require Host restarts. Plugin-specific functional correctness remains separately tested.
+
+## 0.3.3 - 2026-09-01
+
+- Require the complete DSHX `>=0.7.4 <0.8.0` surface, including same-Home Web Host discovery/attach, three-state PID/port probes, and temporary-Home `verify-boot` teardown.
+- Teach the managed skill that App, direct `dsh web`, and dshx are launchers for one long-lived Host; collision or unknown visibility is a stop condition and `--keep` is unsafe.
+- Keep the seven-tool bridge unchanged. Managed skill/metadata refresh remains stamp-stable when the user's preset composition is unchanged, so no immediate Host restart is required.
+
+## 0.3.2 - 2026-08-31
+
+- Require the complete DSHX `>=0.7.3 <0.8.0` surface, including the external `dshx plugin remove` profile-bundle transaction and its same-PID/tombstone guards.
+- Teach Creator Mode+ to distinguish its fixed watched-row `dshx_remove_plugin` tool from boot-captured bundle removal, which is handed to the external supervisor without adding an eighth model tool.
+- Keep managed preset composition stamp-stable; a running Host may load the stricter bridge preflight on its next normal App reopen instead of restarting only for this metadata/skill refresh.
+
+## 0.3.1 - 2026-08-26
+
+- Add `dshx_remove_plugin`, the seventh fixed tool. It deactivates the watched Host row, proves same-PID absence, runs official profile cleanup, detaches only target-verified symlinks, and preserves source. RC8 partial removals resume from durable quarantine and safely handle a package-manager orphan link without rerunning removal for an already-absent dependency.
+- Add a preset-scoped monotonic bash guard for claimed plugin-root, Harness-link, and active-profile teardown while leaving ordinary component/file cleanup available.
+- Require DSHX `>=0.7.2 <0.8.0`, including proactive Guardian quarantine when a claimed watched client loses its profile link while the Host is still healthy.
+- Add regression coverage for the exact failure chain that previously left stale patch/profile registration and broke the next DSH cold boot.
+
+## 0.3.0 - 2026-08-26
+
+- Align the standalone bridge with the complete stable DSHX `>=0.7.1 <0.8.0` contract while keeping Creator Bridge v2 at six bounded model-facing tools.
+- Require the RC2-compatible boot-manifest surface that recognizes both `window.__DSH_BOOT__` and `globalThis["__DSH_BOOT__"]` before any bridge or installer mutation.
+- Unblock fresh client creation by enforcing scaffold → implement/build → `dshx_check` → `dshx_activation_plan` → same-PID activation; an unbuilt client scaffold is no longer asked to pass the plan gate.
+- Replace version-only acceptance with a fail-closed capability preflight covering Creator claims/scaffold, Guardian, seven-surface activation, managed-shell policy, Harness Update Assistant, and their knowledge contracts.
+- Make fresh install, managed upgrade, and legacy migration refuse an old or incomplete DSHX before writing user preset state; report the accepted DSHX version, bridge version, and contract id.
+- Add a real-checkout verifier that probes DSHX's CLI version and contract markers, plus a portable `dshx.yml` so DSHX v0.7 can check this package directly on the current RC2 line.
+- Teach the managed preset skill the Harness update state machine: only read-only `update plan` may run inside the session; `prepare`, `verify`, `apply`, `rollback`, and process control remain externally supervised.
+- Expand evidence language with preset roster/session layers and keep candidate verification, local apply, live runtime acceptance, and production activation separate.
+- Document the RC8-to-RC2 compatibility line and the one controlled server-branch restart required when a running Host upgrades from 0.2.x to 0.3.0.
+- Test Node 22.19 and Node 24 in CI and package the compatibility verifier and DSHX manifest.
+
+## 0.2.2 - 2026-08-21
+
+- Fix the Bridge v2 allowlist so the registered `dshx_scaffold` and `dshx_activation_plan` tools can reach their exact four-argument CLI forms.
+- Execute every fixed tool argv and internal session lifecycle hook through the allowlist in release tests.
+- Treat a fixed-tool `outside bridge v2` rejection as a bridge integrity defect that stops the workflow without manual mounting or inferred downstream success.
+- Require DSHX 0.6.2 and scaffold new source in the trusted writable session workspace, with an automatic fail-closed `my-plugins` link when Harness lives elsewhere.
+- Scaffold before planning a new target, consult the DSHX knowledge bundle before broad source exploration, and stop speculative mutation when live behavior is already confirmed.
+
+## 0.2.1 - 2026-08-21
+
+- Share the fixed client-failure route across concurrent preset generations instead of registering one exact Host route per generation.
+- Keep the newest live generation behind the shared route and unregister it only after the last generation is disposed.
+- Preserve the exact `agent.cordis.yml` filesystem stamp when a managed upgrade changes only bundled assets or metadata, avoiding an unnecessary preset generation.
+- Document the one-time external Host restart required when upgrading an already-mounted 0.2.0 or older generation, whose route predates the shared broker.
+
+## 0.2.0 - 2026-08-20
+
+- Upgrade to Creator Bridge v2 and require DSHX `>=0.6.0 <0.7.0`.
+- Add trusted session/call/Host provenance and one-plugin-per-session claims.
+- Allow concurrent Creator+ sessions on different plugins while serializing only live activation.
+- Arm the external Guardian on session start and release claims on disposal without registering or wrapping Host signal handlers.
+- Preserve the adopted App launcher's lifetime across Guardian replacements; launcher exit ends recovery and its replacement.
+- Rely on DSHX's managed-shell boundary so stale Creator conversations cannot invoke raw Host mutation or process control.
+- Deliver quarantined recovery incidents back to the exact persisted session with plugin-source steering and acknowledgement.
+- Add a same-origin browser sentry and Host-stamped fixed route for official Loader failures; reload only after unique attribution, quarantine, and live-manifest absence.
+- Keep all Host recovery external and bounded; no model-facing process control was added.
+
+## 0.1.0 - 2026-08-20
+
+- Publish Creator Mode+ as an independent DSH plugin and user preset.
+- Expose five fixed DSHX bridge operations with no Host process control.
+- Add fail-closed Harness discovery and DSHX `>=0.5.1 <0.6.0` compatibility gating.
+- Preserve safe new-client ordering and layered activation evidence.
+- Add transactional fresh install, managed upgrade, and bundled-DSHX migration.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 aa2246740
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.en.md

@@ -0,0 +1,83 @@
+# Creator Mode+
+
+[中文](README.md)
+
+Pick Creator Mode+ in a normal DeepSeek Harness Web session. Ten fixed tools scaffold, check, mount, and uninstall a file-backed plugin in a safe order.
+
+Creator Mode+ 0.3.8 is paired with DSHX 0.7.8 and adds user-confirmed claim takeover in the current conversation. New-client activation, server hot reload within the same conversation, and removal have been verified on DSH `dsh-v0.1.5-rc.2`. The bridge compatibility range remains [DSHX](https://github.com/aa2246740/dsh-external-plugin-devkit) `>=0.7.8 <0.8.0`; both the version range and the human-confirmed takeover capability are checked before use.
+
+![Open Creator Mode+ in the official WebUI](docs/screenshots/mode-picker.gif)
+
+![Creator Mode+ in the mode list](docs/screenshots/mode-picker.png)
+
+![Creator Mode+ selected](docs/screenshots/mode-selected.png)
+
+## Use it in a conversation
+
+Select a workspace and **Creator Mode+**, then state the feature and delivery target:
+
+> Create a page counter plugin and install it in this DSH. Then add a server tool to it.
+
+The Agent creates source, builds, checks, selects activation and continues. Server changes use same-process hot reload; a new client entry needs a page refresh. Correct build failures before retrying. A missing browser adapter blocks its UI check only. An explicit installation request carries through these steps.
+
+## Install
+
+Do this outside an Agent session, in your Harness checkout:
+
+```sh
+cd /path/to/deepseek-harness
+git clone https://github.com/aa2246740/dsh-creator-mode-plus.git tools/dsh-creator-mode-plus
+pnpm dsh plugin --profile web add link:./tools/dsh-creator-mode-plus
+node tools/dsh-creator-mode-plus/scripts/install.mjs --harness "$PWD"
+```
+
+The installer writes a user preset. It leaves the shipped Standard and Creator presets alone. Open the official WebUI, confirm Creator Mode+ is in the mode list, and try it in a new session. Adding a profile dependency is not by itself a reason to restart the Host.
+
+Contracts: [Bridge v2](docs/bridge-contract.md) and [DSHX v0.7 alignment](docs/dshx-v0.7-alignment.md).
+
+![Installer writing the user preset](docs/screenshots/install.png)
+
+## The ten tools
+
+| Tool | What |
+|---|---|
+| `dshx_browser_open` | Open the authenticated WebUI through the session-approved adapter, then continue UI verification |
+| `dshx_status` | Read supervisor and Host. No process changes |
+| `dshx_claim_plugin` | This session owns one plugin |
+| `dshx_scaffold` | Create a project in the session workspace. Does not overwrite |
+| `dshx_check` | Check interfaces, build artifacts and activation prerequisites |
+| `dshx_activation_plan` | Select activation for the changed component |
+| `dshx_activate_new_client` | Install a new client and verify its entry |
+| `dshx_remove_plugin` | Unload from the current Host, then clear the profile. Source stays |
+| `dshx_hot_reload` | Activate server code changes |
+
+Whole-plugin removal goes through `dshx_remove_plugin` only. Running the installer again on an existing install does not overwrite.
+
+![Duplicate install refused](docs/screenshots/already-installed.png)
+
+Harness `update prepare` / `verify` / `apply` / `rollback` are not among the ten tools. They stay with an external DSHX supervisor. Inside the session, managed shell may only read `update plan`.
+
+## Upgrade
+
+```sh
+cd /path/to/deepseek-harness/tools/dsh-creator-mode-plus
+git pull --ff-only
+node scripts/install.mjs --harness /path/to/deepseek-harness --upgrade
+npm run verify:dshx -- --harness /path/to/deepseek-harness
+```
+
+## Develop
+
+```sh
+npm test
+npm run check
+DSHX_HARNESS=/absolute/path/to/deepseek-harness npm run test:native
+npm run verify:dshx -- --harness /absolute/path/to/deepseek-harness
+npm run verify:harness-install -- --harness /absolute/path/to/deepseek-harness
+```
+
+## License
+
+MIT.
+
+`dshx_request_takeover({name})` asks through the current conversation’s user-question UI, then drains old work and atomically transfers ownership. This requires the `human-confirmed-creator-takeover` capability in addition to the version range.

package/README.md

@@ -0,0 +1,82 @@
+# Creator Mode+
+
+[English](README.en.md)
+
+在 DeepSeek Harness 的普通 Web 会话里选 Creator Mode+，用十个固定工具把一个文件化插件搭起来、检查、挂载，也能按安全顺序卸载。
+
+Creator Mode+ 0.3.8 配套 DSHX 0.7.8，新增当前对话内的用户确认接管。此前已在 DSH `dsh-v0.1.5-rc.2` 上验证新插件加载、同一会话内服务端热更新和卸载。底层桥接兼容范围为 [DSHX](https://github.com/aa2246740/dsh-external-plugin-devkit) `>=0.7.8 <0.8.0`，并在使用前核对用户确认接管能力。
+
+![在官方 WebUI 里打开 Creator Mode+](docs/screenshots/mode-picker.gif)
+
+![模式列表里的 Creator Mode+](docs/screenshots/mode-picker.png)
+
+![已选中 Creator Mode+](docs/screenshots/mode-selected.png)
+
+## 在对话里使用
+
+选择工作区和 **Creator Mode+**，直接说明功能和安装目标，例如：
+
+> 做一个页面计数按钮插件，装到当前 DSH；完成后继续给它加一个服务端工具。
+
+Agent 会创建源码、构建检查、选择激活方式并继续执行。服务端修改使用同进程热更新；新客户端首次加载需要刷新页面。构建失败后先修复再重试，浏览器适配器缺失只影响对应的界面验收。明确的安装请求会沿用到这些步骤。
+
+## 安装
+
+在 Agent 会话外面做。进你的 Harness 仓库：
+
+```sh
+cd /path/to/deepseek-harness
+git clone https://github.com/aa2246740/dsh-creator-mode-plus.git tools/dsh-creator-mode-plus
+pnpm dsh plugin --profile web add link:./tools/dsh-creator-mode-plus
+node tools/dsh-creator-mode-plus/scripts/install.mjs --harness "$PWD"
+```
+
+安装器只写用户 preset，不动随仓库带的 Standard / Creator。打开官方 WebUI，检查 Creator Mode+ 是否出现在模式列表，并在新会话验收。不要仅因增加 profile 依赖就重启 Host。
+
+合同见 [Bridge v2](docs/bridge-contract.md) 和 [DSHX v0.7 alignment](docs/dshx-v0.7-alignment.md)。
+
+![安装器把 preset 写进用户目录](docs/screenshots/install.png)
+
+## 十个工具
+
+| 工具 | 做什么 |
+|---|---|
+| `dshx_browser_open` | 通过当前会话已批准的适配器完成私有认证交接，然后继续界面验收 |
+| `dshx_status` | 读 supervisor 和 Host，不动进程 |
+| `dshx_claim_plugin` | 这个会话独占一个插件 |
+| `dshx_request_takeover` | 在当前对话请用户确认，停止旧任务后接管认领 |
+| `dshx_scaffold` | 在会话工作区建项目，不覆盖已有的 |
+| `dshx_check` | 检查接口、构建产物和激活前置条件 |
+| `dshx_activation_plan` | 确定本次修改的激活方式 |
+| `dshx_activate_new_client` | 安装并验证新客户端插件的入口 |
+| `dshx_remove_plugin` | 先让当前 Host 脱载，再清 profile；只断开链接，保留源码 |
+| `dshx_hot_reload` | 激活服务端代码修改 |
+
+整插件删除只走 `dshx_remove_plugin`。已经装着再跑安装器，它不会覆盖。
+
+![重复安装被拒绝](docs/screenshots/already-installed.png)
+
+Harness 更新的 `prepare` / `verify` / `apply` / `rollback` 不在这十个工具里，交给外部 DSHX supervisor。会话内只允许通过 managed shell 读 `update plan`。
+
+## 升级
+
+```sh
+cd /path/to/deepseek-harness/tools/dsh-creator-mode-plus
+git pull --ff-only
+node scripts/install.mjs --harness /path/to/deepseek-harness --upgrade
+npm run verify:dshx -- --harness /path/to/deepseek-harness
+```
+
+## 开发
+
+```sh
+npm test
+npm run check
+DSHX_HARNESS=/absolute/path/to/deepseek-harness npm run test:native
+npm run verify:dshx -- --harness /absolute/path/to/deepseek-harness
+npm run verify:harness-install -- --harness /absolute/path/to/deepseek-harness
+```
+
+## License
+
+MIT。