@logicseek/hello-cc 1.0.0 → 1.0.2-dsh.3

package/CHANGELOG.md

@@ -16,6 +16,155 @@ the release description from the current changelog section. Use
 `npm run release:github` with `GH_TOKEN` or `GITHUB_TOKEN` only for local
 backfills.
 
+## 1.0.2-dsh.3
+
+### Summary
+
+This preview keeps the DeepSeek Harness integration introduced in `1.0.2-dsh.2`
+and fixes session cleanup when a temporary database failure interrupts shutdown.
+It remains an npm `dsh` preview and a GitHub prerelease.
+
+### Highlights
+
+- Revoking a Cordis Agent immediately blocks its tools while allowing database
+  retirement to retry after storage becomes available again.
+- Preserve failed cleanup records across plugin reloads. Recovery requires the
+  exact disposed Agent, provider session, and project; active owners cannot be
+  replaced based on another Agent's disposal event.
+- Retain the pinned Harness `0.2.0-rc.2`, Node.js 24+, and Linux/macOS/WSL support
+  boundaries. Every candidate has independent package and acceptance receipts.
+
+## 1.0.2-dsh.2
+
+### Summary
+
+This preview integrates DeepSeek Harness sessions with the hello-cc task,
+message, lock, and handoff services. It adds project hooks, an installed Cordis
+bundle, and owned ACP workers, including session recovery and explicit approval
+handling. The preview is intended for the `dsh` npm dist-tag and a GitHub
+prerelease; publication and business acceptance are separate delivery gates.
+
+### Highlights
+
+- `hcc dsh setup`, `status`, and `web` manage project hooks or a Cordis overlay.
+  Setup verifies its managed files before migrating paths from a source checkout
+  to an installed package and preserves user-edited configuration.
+- The Cordis bundle exposes collaboration tools using each Agent's complete
+  provider session ID and project root. Inbox acknowledgements follow the
+  committed model context; simultaneous sessions retain separate ownership.
+- A resumed Cordis session can reclaim ownership after a crashed owner only
+  when complete process identity evidence confirms that owner is dead. Live or
+  uncertain owners, competing transports, and changed bindings remain protected.
+- Native ACP workers use a dedicated `dsh --profile acp` process with scoped MCP
+  tools. Queue admission and completed delivery are distinct; close, resume,
+  interruption, and approval responses retain the owning session boundary.
+- ACP approval requests correlate tool-call IDs with their tool input, including
+  out-of-order updates. Requests with missing or truncated context cannot be
+  accepted; rejection remains available.
+- Release tooling derives GitHub prerelease status from the version and exposes
+  it during dry runs, so preview releases do not receive stable release status.
+
+### Compatibility Notes
+
+- Node.js 24 or newer and matching DeepSeek Harness `0.2.0-rc.2` runtime packages
+  are required. The Cordis integration checks the actual Agent, AgentLoop, Tools,
+  and Sessions package versions before loading.
+- Supported host environments are Linux and macOS; Windows users must use WSL.
+  Native Windows shells are not supported. The existing macOS arm64 acceptance
+  results do not establish Linux, WSL, or other-device acceptance for this preview.
+- Choose one injection method per Harness process: profile bundle or project
+  overlay. Harness manages profile bundle installation; `setup --mode off`
+  disables a managed project overlay.
+- Existing schema v7 and Runtime API v2 boundaries still apply. Real model
+  acceptance requires a provider route that permits Harness; a route restricted
+  to an official client remains restricted.
+
+### Validation
+
+Earlier local macOS arm64 candidates completed official plugin installation and
+removal, real Cordis collaboration calls, ACP session lifecycle and approval
+denial, and an isolated order-report workflow. Those dated receipts belong to
+their recorded candidate hashes. This version requires its own frozen-package
+installation receipt and release checks before publication. Other-device
+installation and genuine business signoff remain separate, incomplete gates.
+
+## 1.0.1
+
+### Summary
+
+hello-cc 1.0.1 is a file-lock determinism, buffer-GC safety, fresh-install, and
+release-reliability patch. It makes worker shutdown reclaim kernel lock
+endpoints deterministically when an identity probe keeps its client write half
+open, restores real PTY startup in fresh macOS npm installations, and keeps
+automatic GC fail-closed when optional buffer paths disappear or change.
+
+### Highlights
+
+- The socket-lock worker now tracks each locally accepted socket and destroys
+  those accepted handles during server shutdown, so release no longer depends
+  on the peer closing its writable half after reading the lock banner.
+- A real half-open identity-probe regression verifies that release returns
+  promptly, a nonblocking reacquisition succeeds immediately, and the probe is
+  explicitly stopped and awaited during final cleanup.
+- `node-pty` is exactly pinned to `1.2.0-beta.15`. The stable `node-pty 1.1.0`
+  npm artifact contains non-executable Darwin helpers, which makes a fresh
+  macOS install fail with `posix_spawnp failed`; the selected artifact publishes
+  both Darwin helpers with executable modes.
+- Linux, macOS, and WSL installation instructions now list Node.js 24, tmux
+  commands for the major system package managers, CLI verification, and safe
+  handling for npm global-install permission errors.
+- `hcc down` now waits for the exact Runtime process identity to exit before it
+  reports success, including safe handling for PID reuse and a bounded timeout
+  when shutdown cannot be confirmed.
+- Background Web startup keeps its immediate child-exit failure but allows a
+  bounded 60-second health window, avoiding false failures on loaded macOS CI
+  hosts where process identity and project restoration can exceed 30 seconds.
+- Manual buffer GC allows a bounded 30-second window for runtime evidence
+  planning and apply, while still deferring all eligible files if the runtime
+  remains unavailable.
+- Automatic GC now treats a missing `.hello-cc/bufs` leaf as empty without
+  recreating it. A missing state directory, a symlinked path component, an
+  inode replacement, or a retargeted project-root alias fails closed with
+  `PROJECT_PATH_FORBIDDEN` before buffer, clock, lock, or history mutation.
+- Buffer path identity is retained through evidence collection, lease
+  acquisition, planning, clock reads, and database transactions. GC uses a
+  no-create lease while existing file-lock callers retain their original
+  parent-creation behavior.
+- Per-connection Web action tokens now require their issuing terminal socket to
+  still be open, closing the handshake race before asynchronous token cleanup.
+- Runtime request deadlines now reach the underlying HTTP transport, and peer
+  start/attach preflight and mutation requests use a bounded 60-second window
+  while stop and terminal-input operations use 30 seconds, instead of all
+  inheriting the shorter read-request default.
+
+### Compatibility Notes
+
+- No CLI command or package-surface behavior changes are intended. Schema v7,
+  Runtime API v2, the authenticated browser's ability to choose any existing
+  server directory as a project root, and the 1.0.0 accepted-risk boundaries
+  are unchanged.
+- Stable project-root aliases remain supported. Only path disappearance,
+  replacement, symlink traversal, or alias retargeting during GC is rejected.
+- The existing five-second fail-closed deadline and cleanup-error behavior are
+  unchanged.
+- `node-pty@1.2.0-beta.15` is a bounded prerelease dependency risk. The exact
+  pin prevents unreviewed beta movement, and release tests verify the installed
+  version, regular-file identity, executable modes, and a real PTY. There is no
+  postinstall or CI-only `chmod` workaround.
+
+### Validation
+
+The 1.0.1 release gate includes repeated macOS Node 24 tests; a no-cache Linux
+Node 24/tmux image build followed by three complete `npm test` runs in that same
+image, each ending with `FULL_REGRESSION_OK`; and a fourth clean container that
+installs the same 1.0.1 package tarball and passes PTY, database, Web, and
+missing-buffer GC smoke checks. Fresh macOS consumer installs pass both normal
+and `--ignore-scripts` installation, proving that executable helper modes come
+from the package artifact rather than lifecycle-script mutation. GC regression
+coverage includes absent optional leaves, symlink and ancestor replacement,
+alias retargeting, no-create lock acquisition, and path guards around clock and
+history writes.
+
 ## 1.0.0
 
 ### Summary

package/README.md

@@ -70,10 +70,42 @@ currently supported; use WSL for a Linux-like environment.
 Linux has richer process auto-discovery through `/proc`. On macOS, use
 hello-cc shims or `hcc peer start` for reliable tmux-managed terminal sessions.
 
+Install Node.js 24 or newer from the official Node.js packages or a Node
+version manager. Then install `tmux` for your platform:
+
+```bash
+# Debian / Ubuntu
+sudo apt-get update && sudo apt-get install -y tmux
+# Fedora / RHEL
+sudo dnf install -y tmux
+# Older RHEL / CentOS
+sudo yum install -y tmux
+# Alpine
+sudo apk add tmux
+# Arch Linux
+sudo pacman -S --needed tmux
+# openSUSE
+sudo zypper install tmux
+# macOS only
+brew install tmux
+```
+
+On Linux, use the distribution package manager; Homebrew is only the macOS
+command above. Root shells can omit `sudo`. In WSL, run the matching Linux
+distribution commands inside WSL. Then install and verify hello-cc:
+
 ```bash
 npm install -g @logicseek/hello-cc
+node --version
+npm --version
+tmux -V
+hcc --version
+hcc --help
 ```
 
+If npm reports `EACCES`, use a Node version manager or a user-owned npm prefix;
+do not work around it with `sudo npm install -g`.
+
 Update an existing global install:
 
 ```bash
@@ -175,6 +207,10 @@ generic session-isolation assumptions.
 - [User Guide](docs/guide.md): setup, Web console, workflows, coordination
   semantics, and environment behavior.
 - [Command Reference](docs/commands.md): compact public command list.
+- [DeepSeek Harness](docs/dsh.md): hooks/Cordis collaboration, ACP workers,
+  project setup and Web launch, with real-model and local-package acceptance evidence.
+- [Native Workers](docs/native.md): HCC-owned Codex, Claude SDK, and dsh ACP
+  workers, delivery receipts, permissions, and saved-session ownership.
 - [Changelog](CHANGELOG.md): release notes for published versions.
 - [Design Notes](docs/design.md): product boundaries and coordination model.
 - [Implementation Notes](docs/implementation.md): architecture and internal

package/README.zh-CN.md

@@ -57,10 +57,41 @@ hello-cc 支持 Linux 和 macOS。需要 Node.js 24 或更新版本；可被浏
 Linux 可以通过 `/proc` 做更完整的进程自动发现。macOS 上建议通过 hello-cc
 shim 或 `hcc peer start` 启动会话，以获得可靠的 tmux 托管终端。
 
+先通过 Node.js 官方软件包或 Node 版本管理器安装 Node.js 24 或更新版本，再按
+系统安装 `tmux`：
+
+```bash
+# Debian / Ubuntu
+sudo apt-get update && sudo apt-get install -y tmux
+# Fedora / RHEL
+sudo dnf install -y tmux
+# 旧版 RHEL / CentOS
+sudo yum install -y tmux
+# Alpine
+sudo apk add tmux
+# Arch Linux
+sudo pacman -S --needed tmux
+# openSUSE
+sudo zypper install tmux
+# 仅 macOS
+brew install tmux
+```
+
+Linux 必须使用当前发行版的系统包管理器，而不是 Homebrew。root shell 可以省略
+`sudo`。WSL 用户应在 WSL 内部执行对应 Linux 发行版的命令。然后安装并验证：
+
 ```bash
 npm install -g @logicseek/hello-cc
+node --version
+npm --version
+tmux -V
+hcc --version
+hcc --help
 ```
 
+如果 npm 报 `EACCES`，请使用 Node 版本管理器或用户自有的 npm prefix，不要用
+`sudo npm install -g` 绕过权限问题。
+
 更新已有的全局安装：
 
 ```bash
@@ -155,6 +186,10 @@ hcc task done --id 1 --summary "Done"
 - [文档目录](docs/README.zh-CN.md)：全部用户文档和实现文档入口。
 - [用户指南](docs/guide.zh-CN.md)：安装、Web 控制台、协作流程、协作语义和环境变量行为。
 - [命令参考](docs/commands.zh-CN.md)：紧凑公共命令清单。
+- [DeepSeek Harness 接入](docs/dsh.zh-CN.md)：hooks/Cordis 协作、ACP worker、
+  项目配置与 Web 启动；附真实模型和本地包验收记录。
+- [Native 后台 worker](docs/native.zh-CN.md)：HCC 持有的 Codex、Claude SDK、dsh ACP
+  worker，以及投递回执、权限和保存会话的所有权边界。
 - [更新日志](CHANGELOG.md)：已发布版本的 release notes。
 
 ## 测试

package/docs/README.md

@@ -17,6 +17,10 @@ authenticated selection of any existing server directory are accepted risks.
   workflow, stable peer identity, and environment behavior.
 - [Command Reference](commands.md): compact list of public commands and the
   intended use of each command group.
+- [DeepSeek Harness](dsh.md): project setup, hooks/Cordis collaboration, ACP workers,
+  installable bundles, and session routing boundaries.
+- [Native Workers](native.md): owned background workers, provider adapters,
+  delivery receipts, permission handling, and resume boundaries.
 - [Changelog](../CHANGELOG.md): release notes for published versions.
 - Release notes: run `npm run release:check` and
   `npm run release:github:dry-run` before publishing. Pushing a `v*` tag runs
@@ -26,6 +30,11 @@ authenticated selection of any existing server directory are accepted risks.
 
 ## Design And Implementation
 
+- DeepSeek Harness integration plan (Chinese) (source checkout: `docs/plans/2026-10-02-dsh-integration.md`): implementation stages, module contracts, and completion gates.
+- DeepSeek Harness acceptance (Chinese) (source checkout: `docs/verification/2026-10-02-dsh-cordis-native.md`): real models, bundle loading, regression and browser evidence.
+
+- [Web task handoff (Chinese)](web-handoff.zh-CN.md): browser control, draft recovery, persistent detachment, and opt-in Codex App Server sessions.
+- [Executor-scoped MCP](mcp.md): project-bound coordination tools, ownership checks and local result evidence.
 - [Design Notes](design.md): product boundary, project boundary, capability
   levels, coordination semantics, and provider-session binding.
 - [Implementation Notes](implementation.md): architecture, protocol, command

package/docs/README.zh-CN.md

@@ -14,6 +14,10 @@ provider peer ID 已变更且不会映射旧 ID；受保护接口使用 Runtime
 - [用户指南](guide.zh-CN.md)：安装、启动、Web 控制台、协作语义、工作流、稳定
   peer 身份和环境变量行为。
 - [命令参考](commands.zh-CN.md)：公共命令的紧凑清单，以及每组命令的用途。
+- [DeepSeek Harness 接入](dsh.zh-CN.md)：项目配置、hooks/Cordis 协作、ACP worker、
+  可安装 bundle 与会话路由边界。
+- [Native 后台 worker](native.zh-CN.md)：后台 worker 所有权、provider adapter、
+  投递回执、权限处理和 resume 边界。
 - [更新日志](../CHANGELOG.md)：已发布版本的 release notes。
 - 发行说明：发布前运行 `npm run release:check` 和
   `npm run release:github:dry-run`。推送 `v*` tag 会触发
@@ -23,6 +27,11 @@ provider peer ID 已变更且不会映射旧 ID；受保护接口使用 Runtime
 
 ## 设计和实现
 
+- DeepSeek Harness 接入计划 (源码目录: `docs/plans/2026-10-02-dsh-integration.md`)：三个实现阶段、模块契约与完成门槛。
+- DeepSeek Harness 验收 (源码目录: `docs/verification/2026-10-02-dsh-cordis-native.md`)：真实模型、包加载、回归与浏览器证据。
+
+- [Web 接手本地任务](web-handoff.zh-CN.md)：控制租约、草稿恢复、暂停接管、Codex App Server 与历史交接边界。
+- [MCP 协作工具](mcp.zh-CN.md)：固定项目、peer 与执行器身份的任务、消息、锁和结果证据工具。
 - [设计说明](design.md)：产品边界、项目边界、能力层级、协作语义和 provider
   session 绑定。
 - [实现说明](implementation.md)：架构、协议、命令面、技术栈、shim 行为和实现计划。

package/docs/commands.md

@@ -21,6 +21,24 @@ hcc uninstall [--purge --yes]
 hooks, shims, and the shell PATH entry; add `--purge --yes` only when you also want to remove the
 current project's `.hello-cc` data and guidance blocks.
 
+## Read-only Diagnostics
+
+```text
+hcc doctor [--codex] [--json]
+```
+
+By default, doctor only checks project database integrity and schema compatibility;
+corruption or an unsupported schema returns a nonzero exit code. `--codex` additionally
+runs bounded `codex --version` and `codex app-server --help` probes in temporary
+HOME/CODEX_HOME directories and removes their startup files. Hook checks read the
+original Codex home's `hooks.json` and existing project hook invocation events. Help
+advertises startup arguments; it does not prove a protocol handshake or model availability.
+Hook configuration, historical invocation, stdout delivery, and provider acceptance
+are separate facts. No explicit stdout receipt is recorded, so delivery, acceptance,
+and trust remain `unknown`. Diagnostics never start a model/session, execute hooks, or
+change accounts, trust, or shims. Unknown optional diagnostics do not fail a healthy
+database. JSON adds `data.codex`; the default report remains unchanged.
+
 ## Start And Stop
 
 ```text
@@ -39,6 +57,41 @@ want coordination without the Web console or shims. Provider shims only join
 projects with a local `.hello-cc/runtime.json` from `hcc web`; they do not use a
 global runtime to manage arbitrary directories.
 
+## Native Workers
+
+```text
+hcc native up
+hcc native start --peer NAME --provider codex|claude|dsh [--cwd DIR] [--model MODEL] [--binary PATH] [--resume last]
+hcc native send --peer NAME --body TEXT [--from NAME] [--task ID]
+hcc native status
+hcc native deliveries [--peer NAME]
+hcc native events --peer NAME [--after ID]
+hcc native requests --peer NAME
+hcc native respond --peer NAME --request ID --decision accept|decline|cancel [--response-file JSON]
+hcc native interrupt --peer NAME [--turn ID]
+hcc native close --peer NAME
+hcc native down
+```
+
+These commands manage HCC-owned background workers through Codex app-server,
+the optional Claude Agent SDK, or dsh ACP. A successful send queues a message;
+inspect delivery receipts for submission, acceptance, and completion. Only saved
+sessions owned by the same HCC peer/provider can resume. Existing TUI/Desktop
+sessions keep their own transport. Hosted permission requests and questions wait
+for an explicit Web or local CLI response bound to the current worker/session/turn.
+See [Native Workers](native.md) for response-file examples, SDK installation, receipt meanings,
+and current integration boundaries.
+
+## DeepSeek Harness
+
+```text
+hcc dsh setup [--mode hooks|cordis|off]
+hcc dsh status [--dsh-bin PATH]
+hcc dsh web [--mode hooks|cordis|off] [--dsh-bin PATH] [--dsh-home PATH] -- [dsh arguments]
+```
+
+Use `@deepseek-ai/dsh@0.2.0-rc.2` and Node.js 24+. Setup defaults to hooks on first use; `--mode cordis` provides native `hcc_*` tools and ACK after context commit, while `--mode off` disables overlay injection. Later calls retain the saved mode. Status checks content and the executable without model calls. Harness flags follow `--`. Harness Web owns its conversations; use native commands above for HCC-owned workers. See the [integration guide](dsh.md) for routing, bundles and real-model acceptance.
+
 ## Peers And Status
 
 ```text

package/docs/commands.zh-CN.md

@@ -19,6 +19,21 @@ hcc uninstall [--purge --yes]
 只有在确定也要删除当前项目的 `.hello-cc` 数据和指导块时，才加
 `--purge --yes`。
 
+## 只读诊断
+
+```text
+hcc doctor [--codex] [--json]
+```
+
+默认只检查项目数据库完整性和 schema 兼容性；损坏或不支持的 schema 返回非零退出码。
+加 `--codex` 才执行有时限和输出大小限制的 `codex --version`、`codex app-server --help`，
+两个探测使用临时 HOME/CODEX_HOME 并清理启动文件；hooks 检查读取原 Codex home 的
+`hooks.json` 并查看本项目已有 hook 调用事件。help 只能证明
+启动参数被声明，不能证明协议握手或模型可用；hook 配置存在、历史调用记录、stdout 投递
+和 provider 接收分别报告。当前无明确 stdout 回执，投递、接收和 trust 均保持 `unknown`。
+诊断不启动模型或会话、不执行 hooks，不修改账号、信任或 shim；可选诊断未知不会使健康
+数据库返回失败。`--json` 在现有报告中增加 `data.codex`，默认报告结构不变。
+
 ## 启动和停止
 
 ```text
@@ -36,6 +51,39 @@ runtime 生成 URL token。用 `--local` 可只绑定 `127.0.0.1`，用 `--token
 已经由 `hcc web` 生成本地 `.hello-cc/runtime.json` 的项目，不会使用全局 runtime
 去管理任意目录。
 
+## Native 后台 worker
+
+```text
+hcc native up
+hcc native start --peer NAME --provider codex|claude|dsh [--cwd DIR] [--model MODEL] [--binary PATH] [--resume last]
+hcc native send --peer NAME --body TEXT [--from NAME] [--task ID]
+hcc native status
+hcc native deliveries [--peer NAME]
+hcc native events --peer NAME [--after ID]
+hcc native requests --peer NAME
+hcc native respond --peer NAME --request ID --decision accept|decline|cancel [--response-file JSON]
+hcc native interrupt --peer NAME [--turn ID]
+hcc native close --peer NAME
+hcc native down
+```
+
+这些命令通过 Codex app-server、可选 Claude Agent SDK 或 dsh ACP 管理 HCC 持有的
+后台 worker。send 成功只代表消息入队，需要查看投递回执区分提交、接受和完成。
+resume 只允许同一个 HCC peer/provider 持有的保存会话；已有 TUI/桌面会话继续使用
+原 transport。托管权限请求与问题等待当前 Web 控制窗口或本地 CLI 明确应答，
+并检查当前 worker/session/turn 身份。响应文件示例、SDK 安装、回执和接入边界见
+[Native 后台 worker](native.zh-CN.md)。
+
+## DeepSeek Harness
+
+```text
+hcc dsh setup [--mode hooks|cordis|off]
+hcc dsh status [--dsh-bin PATH]
+hcc dsh web [--mode hooks|cordis|off] [--dsh-bin PATH] [--dsh-home PATH] -- [dsh arguments]
+```
+
+验证基线为 `@deepseek-ai/dsh@0.2.0-rc.2`、Node.js 24+。Setup 生成项目局部配置，首次默认 hooks；`--mode cordis` 提供原生 `hcc_*` 工具和提交后 ACK，`--mode off` 关闭 overlay 注入，以后不带模式会沿用保存的选择。Status 校验文件与可执行文件，不调用模型。Harness 参数放在 `--` 后。Harness Web 会话通过自身界面交互；HCC 托管会话使用上方 native 命令控制。路由、bundle 和真实模型验收见[接入指南](dsh.zh-CN.md)。
+
 ## Peers 和状态
 
 ```text

package/docs/dsh.md

@@ -0,0 +1,137 @@
+# DeepSeek Harness Integration
+
+English | [中文](dsh.zh-CN.md)
+
+DeepSeek Harness (`dsh`) shares hello-cc project tasks, messages, advisory locks and handoffs with Claude Code and Codex. The integration has three entry points: the official hooks bridge, a native Cordis collaboration plugin, and HCC-owned ACP workers.
+
+The tested runtime is `@deepseek-ai/dsh@0.2.0-rc.2`, with matching plugin versions. Use Node.js 24+ on `PATH` as well as for the parent CLI: the dsh executable uses `/usr/bin/env node`. This preview ships Web/headless/SDK/ACP profiles and no built-in TUI.
+
+Supported hosts are Linux and macOS; on Windows use WSL. Native Windows shells are not supported. Device acceptance must be recorded separately from container verification.
+
+The source and real DeepSeek model acceptance are complete locally; no new npm release has been published. Use this checkout's CLI when testing:
+
+```bash
+node /absolute/path/to/hello-cc/bin/hcc.mjs --root /path/to/project dsh setup --mode cordis
+node /absolute/path/to/hello-cc/bin/hcc.mjs --root /path/to/project dsh status
+node /absolute/path/to/hello-cc/bin/hcc.mjs --root /path/to/project dsh web -- --port 8080
+```
+
+Below, `hcc` means a CLI containing these changes. An older global installation may not include them.
+
+## Choose An Entry Point
+
+| Entry | Use | Lifecycle owner |
+| --- | --- | --- |
+| `hcc dsh web --mode cordis` | Converse in Harness Web; the model uses `hcc_*` tools | Harness, with multiple independent Agents/workspaces per service |
+| `hcc dsh web --mode hooks` | Use the official Claude hooks bridge and identity-bound CLI commands | Harness; the default compatibility mode |
+| `hcc native start --provider dsh` | Submit prompts, inspect receipts, interrupt and close through HCC CLI/Web | One dedicated ACP process per HCC worker |
+
+Use one collaboration injector per session. Native workers have their own scoped MCP capability and lifecycle; do not additionally mount the Cordis/hooks collaboration injector in that process.
+
+## Harness Web And Cordis
+
+Configure Harness credentials first. The launcher preserves an existing `DEEPSEEK_API_KEY` and provider-routing environment. Use your installed dsh, or install the tested preview yourself:
+
+```bash
+npm install -g @deepseek-ai/dsh@0.2.0-rc.2
+cd /path/to/project
+hcc dsh setup --mode cordis
+hcc dsh status
+hcc dsh web -- --port 8080
+```
+
+Open the URL printed by Harness and create a real Agent using the project as its workspace. Starting the service alone creates no Agent peer. Start `hcc web --local` separately for the HCC dashboard; its dsh filter shows raw session IDs and lets you inspect state and send project messages.
+
+The Cordis plugin awaits `agent/created`, delegates the `agent/pre-step` decision chain, observes Agent status/disposal and tool events, and fixes each execution's authority from `exec.agent`. It never borrows service-level `HCC_PEER` identity.
+
+| Tools | Purpose |
+| --- | --- |
+| `hcc_state`, `hcc_task_list`, `hcc_inbox` | Read project state, tasks and this peer's inbox |
+| `hcc_task_next` | Continue an owned task or claim pending work; never complete it automatically |
+| `hcc_message_send` | Send a project message as this Agent |
+| `hcc_handoff` | Record a handoff for an owned task |
+| `hcc_lock_acquire`, `hcc_lock_release` | Acquire/release this peer's scoped locks |
+| `hcc_result_list`, `hcc_result_record` | Read/record local verification evidence, without claiming publication or business acceptance |
+
+The plugin reuses CLI/MCP transactions and task/lock ownership rules. Context and tool output are each bounded to 16,000 characters by default. Truncation is explicit; incompletely delivered messages remain unread. The shared service also validates argument bounds and authority. ACK occurs only when Harness commits the exact context as a `user/message`; rejected admission, preparation failure and cancellation do not ACK early.
+
+`next()` delegation preserves deny/ask policy. Closing an Agent expires only its own peer. Unloading removes listeners/tool registrations and revokes stale authority; an existing Agent initializes again at its next awaited pre-step after reload. After an unclean exit, the same session can recover its Cordis owner only when the recorded process is verified dead or its PID has been reused. Live or unverifiable owners and conflicting hooks/native bindings remain protected. A project message does not wake an indefinitely idle Harness conversation. It enters at the next model step, or at an active turn's stop boundary.
+
+## Modes, Arguments And Routing
+
+```text
+hcc dsh setup [--mode hooks|cordis|off]
+hcc dsh status [--dsh-bin PATH]
+hcc dsh web [--mode hooks|cordis|off] [--dsh-bin PATH] [--dsh-home PATH] -- [dsh arguments]
+```
+
+First setup defaults to `hooks`; later invocations without `--mode` retain the saved mode. Status verifies managed content and the executable without making a model request.
+
+```bash
+hcc dsh setup --mode hooks
+hcc dsh setup --mode cordis
+hcc dsh setup --mode off
+hcc dsh web --dsh-bin '/opt/harness/bin/dsh' --dsh-home '/path/to/dsh-home' -- --port 8080 --no-open
+hcc dsh web --help       # HCC wrapper help
+hcc dsh web -- --help    # Harness Web help
+```
+
+`--dsh-bin` selects an executable file. `--dsh-home` sets child `DSH_HOME`; relative paths resolve from the invoking directory. Harness arguments go after `--` and retain order and values, including extra overlays. Mode changes apply to subsequent launches: close your owned runtime and relaunch. Existing hooks/native sessions are not forcibly rebound to Cordis; use a new session when switching and retain old collaboration records.
+
+| Managed file | Purpose |
+| --- | --- |
+| `.hello-cc/dsh/hooks.json` | Dedicated HCC hooks for the five supported events |
+| `.hello-cc/dsh/cordis.patch.yml` | Loads the selected injector only; off is an empty overlay |
+| `.hello-cc/dsh/managed.json` | Mode, ownership, paths, baseline and SHA256 hashes |
+
+Setup/disable/re-enable are idempotent. Re-run setup after moving/upgrading source to refresh absolute paths. Edited/foreign files, links and ownership conflicts are preserved and reported. Put custom configuration in a separate overlay. Setup does not install dsh, edit user homes, copy keys or import all Claude/Codex hooks.
+
+The real session ID and absolute Agent cwd route to that workspace's `.hello-cc/mesh.db`, without searching parent projects. Raw non-UUID IDs remain intact. Hash collisions, aliases and another live transport's ownership are rejected. Hooks/Cordis peers cannot be stopped/restarted through detected-peer controls or converted to tmux terminals; a service-log pane remains an independent shell peer.
+
+The rc.2 hooks bridge awaits SessionStart before the first turn. PreToolUse tracks activity; PostToolUse/Stop can deliver context. The official bridge does not consume PreToolUse additionalContext. Hook ACK follows successful hook output, while Cordis ACK follows the corresponding committed context record.
+
+## ACP Workers
+
+```bash
+hcc native up
+hcc native start --peer dsh-reviewer --provider dsh
+hcc native send --peer dsh-reviewer --from coordinator --body 'Review the current diff and report verification evidence'
+hcc native deliveries --peer dsh-reviewer
+hcc native events --peer dsh-reviewer
+hcc native interrupt --peer dsh-reviewer
+hcc native close --peer dsh-reviewer
+hcc native start --peer dsh-reviewer --provider dsh --binary /absolute/path/to/dsh --resume last
+```
+
+The default launcher is `dsh` on PATH; use `--binary /absolute/path/to/dsh` when necessary. A worker owns a dedicated `dsh --profile acp` process. Send returns an admission receipt; only authoritative prompt completion commits a delivery. Resume retains provider session identity and memory. ACP does not replay the full transcript or offer fork/steer. Use native Web controls and approval responses, rather than detected-peer registration actions. See [Native Workers](native.md).
+
+## Bundle And Verification
+
+The package declares `dsh.bundle`, ships `lib/integrations/dsh.bundle.yml` and `dsh-cordis.d.ts`, and declares `engines.dsh=0.2.0-rc.2`. The plugin also checks the actual agent/agent-loop/tools/session package versions before registration.
+
+Project overlays work directly from source. The managed manifest records the Cordis module location, allowing setup to verify and migrate unedited overlays when switching between source and npm installation directories; edited files are preserved. For profile installation, generate a tarball containing these changes and use the official package-management entry point:
+
+```bash
+npm pack --ignore-scripts
+dsh plugin --profile web add /absolute/path/to/logicseek-hello-cc-1.0.1.tgz
+```
+
+Harness requires explicit approval for native dependency builds. If add returns `ERR_PNPM_IGNORED_BUILDS`, merge the following into the selected profile's `pnpm-workspace.yaml` and rerun the same add command. The default path is `~/.dsh/profiles/web/pnpm-workspace.yaml`; use the configured DSH_HOME when different. Preserve existing settings and approve only the candidate's pinned native dependency:
+
+```yaml
+allowBuilds:
+  node-pty@1.2.0-beta.15: true
+```
+
+Harness selects bundles through the profile's `dsh.profile.bundles`; do not also load the project Cordis/hooks overlay. Actual npm installation, official add/repeated add/remove, profile resolution and real-model collaboration calls have passed. The actual macOS desktop profile was installed and hot-loaded on 2026-10-02. Its paired ACP worker completed real collaboration calls using the existing DeepSeek route. The initially configured desktop sub2api model returned HTTP 403 because that account only accepts official Codex clients. After the desktop default was observed to have changed to official DeepSeek, a new session completed hcc_state, hcc_message_send and a real completed turn with that existing selection. The original sub2api route restriction remains. npm publication was not performed. Harness manages profile package removal; project-overlay integration is disabled with `setup --mode off`.
+
+See Cordis/native acceptance (source checkout: `docs/verification/2026-10-02-dsh-cordis-native.md`), bridge acceptance (source checkout: `docs/verification/2026-10-02-dsh-official-bridge.md`), and the integration plan (source checkout: `docs/plans/2026-10-02-dsh-integration.md`). Real-model checks used temporary projects and owned processes, without replacing existing user sessions. The isolated order fixture passed artifact/evidence/handoff/lock-release/task-completion checks. See the Mac device receipt (source checkout: `docs/verification/2026-10-02-dsh-device-install.md`). Publication, deployment, other-device installation and genuine business acceptance remain separate delivery stages.
+
+The installed acceptance script performs npm installation, official `plugin add` / repeated add / remove, and runs the installed public CLI. `--run-live` retains the existing DeepSeek authentication to test ACP approval denial and an isolated order-summary workflow. Without it, no real model is called. All homes, profiles, projects and processes belong to the acceptance run.
+
+```bash
+node scripts/dsh-installed-acceptance.mjs /absolute/path/to/isolated-dsh-install \
+  --run-live --output-dir /absolute/path/to/acceptance-output
+```
+
+The output contains a candidate tarball, its SHA256 and installation receipt, redacted command logs and the verified order report. The approval probe adds an ask policy for one test-owned file in a private profile, rejects the actual ACP request and verifies the file was not created. The fixture demonstrates a local task workflow; it does not establish genuine business acceptance.