dsh-codex-connect 0.1.0-alpha.4.42 → 0.1.0-alpha.4.44

package/INSTALL.md

@@ -1,10 +1,10 @@
 # Installation Runbook for CLI Agents
 
-Published Alpha 4.41 is verified with DSH `0.1.2-rc.1` and pi-ai `0.84.4` within `^0.84.2`, and with each exact DSH `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` model-runtime pairing using pi-ai `0.85.1`.
+Published Alpha 4.43 is verified with the exact DSH `0.1.7-rc.1` model-runtime pairing and pi-ai `0.85.1`. Earlier DSH pairings retain their separately published plugin versions below.
 
 Install `dsh-codex-connect` into one requested DeepSeek Harness profile without changing its current default model, search route, global configuration, or OAuth state.
 
-Channel snapshot on 2026-09-23: npm `alpha` points to `0.1.0-alpha.4.41`; `latest` remains on `0.1.0-alpha.4.40`. Use the exact-version commands below for 4.41. Publishing an Alpha and promoting the default installation channel are separate actions.
+Channel snapshot on 2026-09-24: npm `alpha` points to `0.1.0-alpha.4.43`; `latest` remains on `0.1.0-alpha.4.41`. Use the exact-version command for the installed DSH version. Publishing an Alpha and promoting the default installation channel are separate actions.
 
 ## Safety requirements
 
@@ -30,10 +30,13 @@ Check `dsh --version` before changing the requested profile. Use `dsh --help` to
 | `0.1.5-alpha.1` | `0.1.0-alpha.4.41` |
 | `0.1.5-rc.1` | `0.1.0-alpha.4.41` |
 | `0.1.5-rc.2` | `0.1.0-alpha.4.41` |
+| `0.1.7-rc.1` | `0.1.0-alpha.4.43` |
 
 If your exact DSH version is unknown or not listed, preserve the installed host, report that the combination is unverified, and verify it before making installation changes. A missing record does not prove incompatibility, and the catalog's latest verified DSH version is not the latest upstream release. Do not recommend upgrading or downgrading DSH merely to match a row. Investigate any specific failure and seek verification of the installed combination. Do not blindly install `dsh-codex-connect@alpha`: `alpha` is a moving tag, not a compatibility guarantee. Do not infer support for newer DSH versions from these rows.
 
-Alpha 4.41 requires one consistent DSH plugin API version: `0.1.2-rc.1` with `@earendil-works/pi-ai` `^0.84.2`, or one of `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` with pi-ai `0.85.1`; Node.js remains `^22.19.0 || >=24.0.0`. Mixed host versions and other DSH/pi-ai combinations remain unverified. Alpha 4.25 remains the verified choice for DSH `0.1.2-alpha.5`, Alpha 4.23 remains the verified choice for DSH `0.1.2-alpha.2`, Alpha 4.21 remains the verified choice for DSH `0.1.1-rc.2`, and staying on DSH `0.1.0-rc.7` means selecting Alpha 4.14. Changing DSH is a separate operation requiring the user's explicit request; a plugin update request does not authorize it. The repository's `pnpm --silent run check:compatibility` remains a strict development/release dependency gate, not a recommendation to change a user's host.
+Alpha 4.43 requires one consistent DSH `0.1.7-rc.1` plugin API and pi-ai `0.85.1`; Node.js remains `^22.19.0 || >=24.0.0`. It does not support the older DSH rows. Alpha 4.41 remains the choice for DSH `0.1.2-rc.1` with pi-ai `^0.84.2`, or `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` with pi-ai `0.85.1`. Mixed host versions and other DSH/pi-ai combinations remain unverified. Alpha 4.25 remains the verified choice for DSH `0.1.2-alpha.5`, Alpha 4.23 for DSH `0.1.2-alpha.2`, Alpha 4.21 for DSH `0.1.1-rc.2`, and Alpha 4.14 for DSH `0.1.0-rc.7`. Changing DSH is a separate operation requiring the user's explicit request; a plugin update request does not authorize it. The repository's `pnpm --silent run check:compatibility` remains a strict development/release dependency gate, not a recommendation to change a user's host.
+
+The Alpha 4.43 recommendation follows [exact-release main CI](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35887810404) on Node 22/24, Chromium and Windows checks, plus the stock DSH `0.1.7-rc.1` same-artifact installation matrix. The [original publish run](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35888766215) uploaded the verified npm package but timed out waiting for public registry readback; do not rerun publication. Once npm exposed the exact version and `alpha` tag, the [recovery-only run](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35889959811) verified the archive against that original artifact and created the matching Git tag and prerelease without republishing. These checks used synthetic providers, not a real ChatGPT account. Stock rc.1 keeps Task controls paused; migration of old Task grants across a Harness upgrade remains unverified.
 
 The Alpha 4.41 recommendation follows successful [exact-release main CI](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35817909046) on Node 22 and 24 (1,282 unit tests each), 52 Chromium tests, and a four-host same-artifact installation matrix. After npm processing completed, the [recovery verification](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35819017165) matched the public npm archive byte-for-byte to the original verified release artifact, then created the matching Git tag and GitHub prerelease. The [original release run](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35818489220) remains failed because npm's public readback was not available within its bounded retry period; do not rerun publication. These are synthetic-provider installation/lifecycle checks, not new real-account acceptance or a newly exercised published-package upgrade. Task-level model control remains opt-in; a new grant preselects only GPT-5.6 Sol / Medium and displays its scope and request limit before Start. Existing grants are not silently narrowed. Stock DSH 0.1.6-alpha.1 and alpha.2 remain undeclared; their separate compatibility trackers are not broadened by this release.
 
@@ -70,13 +73,19 @@ Alpha 4.33 omits the `modelErrors` profile field required by RC model packages,
    dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
    ```
 
+   For the exact DSH `0.1.7-rc.1` pairing, use Alpha 4.43:
+
+   ```sh
+   dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.43
+   ```
+
    For DSH `0.1.2-alpha.5`, use Alpha 4.25:
 
    ```sh
    dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.25
    ```
 
-   If npm is unavailable after the matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.21'` only for the DSH `0.1.1-rc.2` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.23'` only for the DSH `0.1.2-alpha.2` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.25'` only for the DSH `0.1.2-alpha.5` combination, or `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.41'` only for the DSH `0.1.2-rc.1`, `0.1.5-alpha.1`, `0.1.5-rc.1`, or `0.1.5-rc.2` combinations.
+   If npm is unavailable after the matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.21'` only for the DSH `0.1.1-rc.2` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.23'` only for the DSH `0.1.2-alpha.2` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.25'` only for the DSH `0.1.2-alpha.5` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.41'` only for the DSH `0.1.2-rc.1`, `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` combinations, or `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.43'` only for DSH `0.1.7-rc.1`.
 
 3. Run `dsh web --help` once to compose the installed profile without starting the server. DSH `0.1.2-rc.1` prepares profile plugin dependency fallback during this step.
 4. Run `dsh --profile web --dump-config` and require exactly one `llm-openai-codex` row loading `dsh-codex-connect`.

package/MIGRATION.md

@@ -1,5 +1,21 @@
 # Migrating from `dsh-codex`
 
+## Alpha 4.43 candidate: upgrade the Harness together
+
+This candidate targets DeepSeek Harness `0.1.7-rc.1` only. Upgrade the Harness
+and its profile runtime first, then install the matching Codex Connect release;
+this candidate is not compatible with the previously declared `0.1.2-rc.1` or
+`0.1.5` hosts. Keep the existing `llm-openai-codex` row and OAuth store. The DSH
+settings lifecycle, message-source types, and native-compaction integration have
+changed, but the migration does not require signing in again or editing
+credentials. This candidate is not published; do not use a public install
+command until its exact package/host pair is verified and released.
+DSH `0.1.7-rc.1` also changes the Session log format. Migration of an active
+task from the previously supported Harness versions to this target has not
+passed acceptance; do not treat same-host task recovery below as proof of a
+cross-Harness upgrade. Finish or safely stop active delegated tasks before
+changing the Harness until that migration is verified.
+
 ## Next release candidate: public task orchestration paused
 
 Task-level automatic model selection and read-only delegation are being withheld
@@ -9,7 +25,8 @@ published, installed, and loaded.
 
 A new ordinary conversation has no collaboration activation options. Cached
 clients cannot start, resume, upgrade or authorize delegation through the closed
-server route. Existing tasks keep authenticated readback, Stop and manual takeover;
+server route. On a supported same-version host, existing tasks keep authenticated
+readback, Stop and manual takeover;
 grants, original history and spent request counts are not deleted or reset.
 Manual model selection (including GPT-6/Astra), accounts, existing optional tools
 and native compaction settings are unchanged. Internal orchestration source and

package/NOTICE

@@ -18,3 +18,9 @@ This product also includes OAuth login and refresh code from earendil-works/pi
 (@earendil-works/pi-ai 0.84.4), under the MIT license reproduced in
 docs/licenses/pi-ai-oauth.txt. JWT payload decoding, callback connection cleanup
 and structured refresh rejection handling are modified.
+
+The standalone CLI bundles selected code from host and provider dependencies so
+it can run from an isolated DSH plugin-exec process without copying host peers.
+The bundled third-party package attributions and license texts are in
+docs/licenses/standalone-cli.txt. Runtime plugin imports continue to use the
+host's packages rather than these standalone CLI copies.

package/README.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   git hash-object README.md docs/README.zh.md
-README.md: fa12308fc1124ec0edc183a088fcdff77323bc3a
-docs/README.zh.md: 9ec30155f320aae3d9ed33d091304624ff70943b
+README.md: 38b900237ec1219376edba97fb1265903d48b9b7
+docs/README.zh.md: 9ae847d4b82d0af3eaf63819119dd1f394a075a4

package/README.md

@@ -12,23 +12,23 @@ Codex Connect adds the `openai-codex` model provider to the normal Harness agent
 
 ## Quick start
 
-This guide describes the published pairings below. Check `dsh --version` first and use `doctor --json` to inspect the installed model-runtime packages: an rc.1 CLI can resolve rc.2 packages. For other versions, use [Installation and upgrades](INSTALL.md). A moving npm tag such as `alpha` is not a compatibility guarantee.
+This guide describes the published pairing below. Check `dsh --version` first and use `doctor --json` for local diagnostics; the CLI version alone does not prove which model-runtime packages are installed, and missing metadata is reported as unknown. For other versions, use [Installation and upgrades](INSTALL.md). A moving npm tag such as `alpha` is not a compatibility guarantee.
 
 | Requirement | Verified pairing |
 |---|---|
-| Codex Connect | `0.1.0-alpha.4.41` |
-| DeepSeek Harness | `0.1.2-rc.1`, `0.1.5-alpha.1`, `0.1.5-rc.1`, or `0.1.5-rc.2` |
+| Codex Connect | `0.1.0-alpha.4.43` |
+| DeepSeek Harness | `0.1.7-rc.1` |
 | Node.js | `^22.19.0 \|\| >=24.0.0` |
 | Account | ChatGPT OAuth with access to the requested Codex model; availability is decided by OpenAI |
 
-As of 2026-09-23, npm `alpha` points to 4.41 while `latest` remains on 4.40. Use the exact version below for 4.41; publishing an Alpha and changing the default installation channel are separate actions.
+As of 2026-09-24, npm `alpha` points to 4.43 while `latest` remains on 4.41. Use the exact version below for this DSH pairing; publishing an Alpha and changing the default installation channel are separate actions.
 
-Task-level model choice remains off until enabled for a new conversation. In 4.41, a new grant preselects only GPT-5.6 Sol / Medium and shows the exact scope and request limit before Start. Existing task grants are preserved; take over manually and start a new task to choose a narrower scope.
+On stock DSH `0.1.7-rc.1`, ordinary Composer works, but Task controls remain paused: activation is rejected and fresh Sessions do not show them. Migration of earlier Task grants across a Harness upgrade is not verified. Older supported pairings and their task behavior are documented in [Installation and upgrades](INSTALL.md).
 
 ### 1. Install
 
 ```sh
-dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.43
 dsh web
 ```
 
@@ -67,7 +67,7 @@ dsh plugin --profile web exec dsh-codex-connect doctor --json
 
 ## Optional capabilities
 
-**New in Alpha 4.40:** task-level model control is off by default. After explicit task authorization, GPT-5.6 Sol/Medium starts the task, and the active model may continue, change effort, or hand off the main task within the granted scope. The task shares one request ledger and budget; stopping, manual takeover, and restart recovery retain the grant boundary. Phase 2 read-only delegation requires separate consent and does not grant workers write access. These are opt-in task capabilities, not parallel Think/Split/Remember switches. See [Phase 1](docs/experiments/adaptive-task-phase1.md) and [Phase 2 consent](docs/experiments/adaptive-task-phase2-consent.md).
+**Earlier Alpha 4.40/4.41 pairings:** task-level model control is off by default. After explicit task authorization, GPT-5.6 Sol/Medium starts the task, and the active model may continue, change effort, or hand off the main task within the granted scope. The task shares one request ledger and budget; stopping, manual takeover, and restart recovery retain the grant boundary. Phase 2 read-only delegation requires separate consent and does not grant workers write access. Stock DSH `0.1.7-rc.1` with Alpha 4.43 keeps these Task controls paused; do not infer they are available from an older pairing. See [Phase 1](docs/experiments/adaptive-task-phase1.md) and [Phase 2 consent](docs/experiments/adaptive-task-phase2-consent.md).
 
 Alpha 4.40 also supplies `gpt-6-sol` and `gpt-6-luna` when older provider catalogs omit them, retaining native metadata when present. Both expose Low through Max (including Xhigh); Default omits an explicit effort. Codex Sol's Ultra orchestration mode is not implemented. New task grants can explicitly include these models, but existing grants, GPT-5.6 Sol/Medium startup and Luna Reserve remain unchanged. A catalog entry is not proof of account access. See [compatibility scope and validation](docs/experiments/gpt6-sol-luna-compatibility.md).
 

package/compatibility.json

@@ -4,12 +4,13 @@
     "node": "^22.19.0 || >=24.0.0"
   },
   "dshPluginApi": {
-    "version": "0.1.2-rc.1",
-    "versions": ["0.1.2-rc.1", "0.1.5-alpha.1", "0.1.5-rc.1", "0.1.5-rc.2"],
+    "version": "0.1.7-rc.1",
+    "versions": ["0.1.7-rc.1"],
     "packages": [
       "@deepseek-ai/dsh-agent",
       "@deepseek-ai/dsh-atomic-write",
       "@deepseek-ai/dsh-attachment",
+      "@deepseek-ai/dsh-compaction",
       "@deepseek-ai/dsh-home-paths",
       "@deepseek-ai/dsh-host-webserver",
       "@deepseek-ai/dsh-invariants",
@@ -25,6 +26,6 @@
   },
   "piAi": {
     "package": "@earendil-works/pi-ai",
-    "version": "^0.84.2 || 0.85.1"
+    "version": "0.85.1"
   }
 }

package/docs/README.zh.md

@@ -12,23 +12,23 @@ Codex Connect 为标准 Harness agent loop 添加 `openai-codex` 模型提供方
 
 ## 快速开始
 
-本指南介绍下方已发布的组合。请先运行 `dsh --version`，并用 `doctor --json` 检查实际安装的模型运行库：rc.1 CLI 可能解析到 rc.2 包。其他版本请查阅[安装与升级](../INSTALL.md)。`alpha` 等会移动的 npm tag 不代表兼容性保证。
+本指南介绍下方已发布的组合。请先运行 `dsh --version`，再用 `doctor --json` 做本地诊断；单凭 CLI 版本无法证明实际安装的模型运行库版本，缺少版本元数据时会报告未知。其他版本请查阅[安装与升级](../INSTALL.md)。`alpha` 等会移动的 npm tag 不代表兼容性保证。
 
 | 要求 | 已验证组合 |
 |---|---|
-| Codex Connect | `0.1.0-alpha.4.41` |
-| DeepSeek Harness | `0.1.2-rc.1`、`0.1.5-alpha.1`、`0.1.5-rc.1` 或 `0.1.5-rc.2` |
+| Codex Connect | `0.1.0-alpha.4.43` |
+| DeepSeek Harness | `0.1.7-rc.1` |
 | Node.js | `^22.19.0 \|\| >=24.0.0` |
 | 账户 | 通过 ChatGPT OAuth 使用所请求的 Codex 模型；可用性由 OpenAI 决定 |
 
-截至 2026-09-23，npm `alpha` 指向 4.41，`latest` 仍指向 4.40。安装 4.41 请使用下方精确版本命令；发布 Alpha 与提升默认安装渠道是两项独立操作。
+截至 2026-09-24，npm `alpha` 指向 4.43，`latest` 仍指向 4.41。安装此 DSH 组合请使用下方精确版本命令；发布 Alpha 与提升默认安装渠道是两项独立操作。
 
-任务级模型选择仍需在新会话中主动开启。4.41 的新授权默认只选择 GPT-5.6 Sol / Medium，开始前会显示准确的模型范围和请求上限。已有任务授权不会被自动收窄；如需改用较窄范围，请先切回手动，再在新任务中选择。
+在原版 DSH `0.1.7-rc.1` 上，普通 Composer 可用，但 Task 控件仍暂停：激活请求会被拒绝，新 Session 不显示这些控件。跨 Harness 升级迁移旧任务授权尚未验证。较旧组合及其任务行为见[安装与升级](../INSTALL.md)。
 
 ### 1. 安装
 
 ```sh
-dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.43
 dsh web
 ```
 
@@ -67,7 +67,7 @@ dsh plugin --profile web exec dsh-codex-connect doctor --json
 
 ## 可选能力
 
-**Alpha 4.40 新增：**任务级模型安排默认关闭。用户明确授予任务权限后，由 GPT-5.6 Sol／Medium 起步；当前模型可以在授权范围内继续、调档或交接主任务。请求共用同一任务账本与预算；停止、手动接管和重启恢复都保留授权边界。Phase 2 的只读委派需要单独同意，不会给委派工作者写入权限。它们是按任务开启的能力，不是并列的 Think／Split／Remember 开关。参见 [Phase 1](experiments/adaptive-task-phase1.md) 与 [Phase 2 同意边界](experiments/adaptive-task-phase2-consent.md)。
+**较早的 Alpha 4.40/4.41 组合：**任务级模型安排默认关闭。用户明确授予任务权限后，由 GPT-5.6 Sol／Medium 起步；当前模型可以在授权范围内继续、调档或交接主任务。请求共用同一任务账本与预算；停止、手动接管和重启恢复都保留授权边界。Phase 2 的只读委派需要单独同意，不会给委派工作者写入权限。原版 DSH `0.1.7-rc.1` 配合 Alpha 4.43 时，这些 Task 控件仍暂停；不能从旧组合推断它们可用。参见 [Phase 1](experiments/adaptive-task-phase1.md) 与 [Phase 2 同意边界](experiments/adaptive-task-phase2-consent.md)。
 
 Alpha 4.40 还会在旧提供方目录缺失时补充 `gpt-6-sol` 和 `gpt-6-luna`，已有原生定义时保留其元数据。两者提供 Low 到 Max（含 Xhigh），Default 不指定推理档位；尚未实现 Codex Sol 的 Ultra 编排模式。新任务可明确授权使用它们，但已有授权、GPT-5.6 Sol／Medium 起步与 Luna Reserve 不变。模型出现在目录中不代表账户具有调用资格。参见[兼容范围与验证](experiments/gpt6-sol-luna-compatibility.md)。
 

package/docs/agent-notes/dsh-017-stock-plugin-exec.md

@@ -0,0 +1,9 @@
+# DSH 0.1.7-rc.1 stock plugin-exec compatibility
+
+The stock `dsh plugin ... exec` launcher runs the installed plugin command in a separate Node process without DSH's process-local profile resolver. Codex Connect's previous `bin` output shared an eagerly imported chunk with its runtime entry, so even `doctor` failed during ESM linking on the first inaccessible host peer, `@deepseek-ai/schemastery`. The peer was present in the exact host; adding a package declaration, copying host packages into the profile, or retrying authentication would not repair that lookup. The earlier DSH alpha.2 local launcher patch used a fallback operation removed by rc.1, so this release does not depend on that patch or an upstream change.
+
+The command entry is now built separately and carries the libraries it needs in its own CLI output. The runtime entry still imports host peers externally, retaining Cordis and service identity. `doctor --install-anchor` reads version metadata relative to an explicitly named DSH `package.json` without loading host modules or returning the path; absent an anchor and visible peer metadata it reports `unknown`, not a false compatibility verdict. The isolated checker passes the exact host anchor to `doctor` and initializes DSH's own `PluginPackages` resolver before importing the installed runtime plugin. Neither checker creates manual peer links.
+
+Standalone diagnostics read the Codex model catalog without importing the runtime adapter. That keeps DSH's other model adapters and pi-ai's unrelated provider loaders out of the published CLI; the package check rejects their generated chunks. The remaining CodeQL password-hash alert also existed on `main` as alert #23: Reserve hashes an account/user identity pair for a private return-target match, not a password or credential verifier. It cannot authorize a backend request without the freshly captured OAuth token and server response. Alert #23 was dismissed as a false positive with this specific rationale; security scanning remains enabled.
+
+The exact stock DSH `0.1.7-rc.1` installation passed the Node 22 matrix using one packed plugin artifact. It verified ten prepared models, unchanged defaults, provider disposal, synthetic Reserve transitions, ten distinct native-compaction process phases across none/zstd, and synthetic image generation/download visibility; no real OAuth or provider request was made. The Node 22 complete source check passed 116 files and 1,307 tests; Chromium passed 60 tests. The source check under default Node 26 initially failed because that version rejects a probe's `--experimental-transform-types` option, while its sandboxed socket failures were caused by `listen EPERM`; the supported Node 22 host-permission run passed. The replacement installed Session gate targets rc.1 and verifies that the stock page shows the ordinary Composer without Task controls and that the signed Task route rejects activation. It does not claim migration of old Task grants across a Harness upgrade, real-account acceptance, merge, publication, or deployment.

package/docs/licenses/standalone-cli.txt

@@ -0,0 +1,115 @@
+Standalone CLI third-party notices
+
+The generated lib/bin.js and its helper chunks include portions of the
+packages listed below, except where marked as retained notices. The retained
+notices cover dependencies bundled by earlier Alpha 4.43 candidates but
+removed from the final standalone CLI. They do not change package licenses.
+
+MIT-licensed packages:
+- @deepseek-ai/dsh-atomic-write, dsh-home-paths, dsh-typert-protocol,
+  dsh-util-values, dsh-timeout, dsh-llm, and dsh-web: Copyright (c) 2026 DeepSeek.
+- @deepseek-ai/cosmokit, @deepseek-ai/cordis, and
+  @deepseek-ai/schemastery: Copyright (c) 2021-present Shigma.
+- @earendil-works/pi-ai: Copyright (c) 2025 Mario Zechner. Its OAuth
+  source notice is also retained in docs/licenses/pi-ai-oauth.txt.
+- partial-json: Copyright (c) 2023 Promplate Dev Team.
+
+Retained notices for packages no longer included in this CLI build:
+- @deepseek-ai/dsh-attachment, dsh-llm-pi-ai, and dsh-compaction:
+  Copyright (c) 2026 DeepSeek (MIT).
+- @anthropic-ai/sdk: Copyright 2023 Anthropic, PBC (MIT).
+- @stablelib/base64: Copyright (C) 2016 Dmitry Chestnykh (MIT).
+- standardwebhooks: Copyright Standard Webhooks (MIT).
+- openai: Copyright OpenAI (Apache-2.0).
+- neoqs: Copyright (c) 2014 Nathan LaFreniere and other contributors (BSD-3-Clause).
+- zod-to-json-schema: Copyright (c) 2020 Stefan Terdell (ISC).
+- fast-sha256: Unlicense.
+
+MIT License
+
+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.
+
+openai is Copyright OpenAI and is licensed under Apache-2.0; the full license
+is included in this package's root LICENSE file.
+
+The OpenAI and Anthropic SDKs include portions of neoqs, Copyright (c) 2014
+Nathan LaFreniere and other contributors, under the BSD 3-Clause License:
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice,
+   this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+3. Neither the name of the copyright holder nor the names of its contributors
+   may be used to endorse or promote products derived from this software
+   without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+The OpenAI SDK includes portions of zod-to-json-schema, Copyright (c) 2020
+Stefan Terdell, under the ISC License:
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
+SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION
+OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
+CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+
+fast-sha256 1.3.0 is released under the Unlicense:
+
+This is free and unencumbered software released into the public domain.
+
+Anyone is free to copy, modify, publish, use, compile, sell, or distribute
+this software, either in source code form or as a compiled binary, for any
+purpose, commercial or non-commercial, and by any means.
+
+In jurisdictions that recognize copyright laws, the author or authors of
+this software dedicate any and all copyright interest in the software to the
+public domain. We make this dedication for the benefit of the public at large
+and to the detriment of our heirs and successors. We intend this dedication
+to be an overt act of relinquishment in perpetuity of all present and future
+rights to this software under copyright law.
+
+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 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.
+
+For more information, please refer to <https://unlicense.org>.

package/docs/reference.i18n.yaml

@@ -1,4 +1,4 @@
 # Bilingual-pair consistency record for the operational reference. Re-record with:
 #   git hash-object docs/reference.md docs/reference.zh.md
-docs/reference.md: b6d177da34691432d0c39c27644ef4b083af0d2a
-docs/reference.zh.md: 926b475eb378191b56b9de6c386b7a03a9292d30
+docs/reference.md: c88cc935a90c206117a0497289f3fc885d61da85
+docs/reference.zh.md: 57da6063a2ea2663fcbdd50168558b944ef54c0d

package/docs/reference.md

@@ -142,6 +142,8 @@ Published Alpha 4.33 can fail to list or prepare Codex models on DSH `0.1.5-rc.1
 
 Run `dsh plugin --profile web exec dsh-codex-connect doctor --json` to inspect local installation metadata without a network request. Compatibility statuses mean: `compatible` matches the declared version requirements, not a behavioral test; `unverified` identifies package versions outside the declared support set; `unknown` means required version metadata is missing or unreadable; `incompatible` identifies a Node version outside the declared engine requirement. The aggregate prioritizes `incompatible`, then `unknown`, then `unverified`. Doctor exits `1` for any non-compatible result or unsafe credential-file metadata; this does not authorize or recommend changing DSH.
 
+For DSH `0.1.7-rc.1`, `plugin exec` starts a separate process without exposing the host's peer packages to ordinary module resolution. Alpha 4.43's CLI is self-contained, so all commands can start in that process. To make `doctor` assess the exact host package versions, pass `--install-anchor` with the absolute path to that DSH installation's `@deepseek-ai/dsh/package.json`; the flag reads package metadata only and does not print the path. Without an anchor, `doctor` reports `unknown` if it cannot resolve those versions; that is not evidence of runtime incompatibility. The installed-runtime checker independently starts DSH's own profile resolver before importing the plugin, preserving host package identity.
+
 The normal update card checks only Codex Connect releases. It reuses successful plugin-version checks for up to 24 hours and retries unavailable checks every five minutes while mounted; a manual check bypasses the cache. It neither queries host compatibility nor recommends host upgrades or downgrades. An unlisted DSH/plugin combination requires verification, not an assumption of failure.
 
 ### Capability probes

package/docs/reference.zh.md

@@ -142,6 +142,8 @@ Reserve 使用 Luna 目录中的 272,000 token 上下文窗口，不沿用原模
 
 运行 `dsh plugin --profile web exec dsh-codex-connect doctor --json` 可检查本地安装元数据，不会联网。兼容性状态含义：`compatible` 表示符合声明的版本要求，不是行为测试通过；`unverified` 表示包版本超出声明的支持集合；`unknown` 表示缺少必要版本元数据或无法读取；`incompatible` 表示 Node 版本不满足声明的 engine 要求。汇总状态依次优先采用 `incompatible`、`unknown`、`unverified`。任何非 compatible 结果或不安全的凭据文件元数据都会让 doctor 返回 `1`，但这并不授权或建议更改 DSH。
 
+DSH `0.1.7-rc.1` 的 `plugin exec` 会启动独立进程，普通模块解析无法看见宿主的 peer 包。Alpha 4.43 的 CLI 自带所需代码，因此所有命令都能在该进程中启动。若要让 `doctor` 核对确切宿主包版本，给 `--install-anchor` 传入该 DSH 安装中 `@deepseek-ai/dsh/package.json` 的绝对路径；该选项只读包元数据，也不会输出路径。未提供 anchor 且无法解析版本时，`doctor` 报 `unknown`，不能据此认定运行时不兼容。安装运行时检查另行启动 DSH 自身的 profile 解析器后再导入插件，保持宿主包身份一致。
+
 常规更新卡片只检查 Codex Connect 发布版本。插件版本检查成功后最多缓存 24 小时，页面挂载期间每五分钟重试不可用的检查；手动检查会绕过缓存。它不会查询宿主兼容性，也不会建议升级或降级宿主。未列入记录的 DSH/plugin 组合需要验证，不能据此认定无法运行。
 
 ### 能力探针

package/docs/release-notes/alpha-4.43.md

@@ -0,0 +1,17 @@
+# Codex Connect Alpha 4.43 — DSH 0.1.7-rc.1 compatibility
+
+## English
+
+This candidate updates the plugin runtime and UI integration for DeepSeek Harness `0.1.7-rc.1`. It follows the new volatile configuration and settings-form lifecycle, current message-source types, and the native-compaction provider API. DSH `0.1.7-rc.1` is the target pairing, not a verified support claim; older DSH versions are not supported by this candidate.
+
+Upgrade the Harness before installing the matching Codex Connect release. Existing provider configuration and OAuth credentials remain in place; signing in again is not required. This candidate has not been published, so the public installation recommendation remains unchanged.
+
+The unmodified DSH `0.1.7-rc.1` installation now passes `plugin doctor` and the installed runtime check. DSH's [plugin-exec peer-resolution issue](https://github.com/deepseek-ai/deepseek-harness/discussions/5537) remains upstream, but this plugin's standalone CLI no longer needs those peers in that subprocess; the installed-runtime checker uses DSH's own profile resolver and leaves shared runtime imports external. An explicit DSH installation anchor gives `doctor` exact host version metadata without importing host code. The CLI bundle includes third-party notices and excludes unused non-Codex model providers. On Node 22, the local check passes 116 files and 1,307 tests, the Chromium suite passes 60 tests, and the exact stock-host install matrix passes with unchanged defaults, ten process-restart native-compaction phases, and synthetic image checks. The current-host installed Session check passed its paused-Task safety checks; old-task migration across a Harness upgrade remains unverified. The public installation recommendation remains on the published pair until this candidate is released.
+
+## 中文
+
+本候选版更新了插件运行时及界面集成，目标是 DeepSeek Harness `0.1.7-rc.1`：迁移到新的 volatile 配置与设置表单生命周期、当前消息来源类型和原生压缩 Provider API。`0.1.7-rc.1` 是目标组合，不代表已验证支持；本候选版不支持较旧的 DSH 版本。
+
+请先升级 Harness，再安装对应的 Codex Connect 版本。已有 Provider 配置和 OAuth 凭据会保留，无需重新登录。本候选版尚未发布，公开安装建议保持不变。
+
+未修改的 DSH `0.1.7-rc.1` 隔离安装现已通过 `plugin doctor` 和已安装运行时检查。上游的[插件命令 peer 解析问题](https://github.com/deepseek-ai/deepseek-harness/discussions/5537)仍存在，但本插件的独立 CLI 不再需要该子进程能解析宿主 peer；安装运行时检查使用 DSH 自身的 profile 解析器，插件运行时仍复用宿主包。显式 DSH 安装 anchor 可让 `doctor` 只读确切宿主版本，不加载宿主代码。CLI bundle 附带第三方许可说明，且不再打入未使用的非 Codex 模型供应商代码。在 Node 22 上，本地完整检查通过 116 个文件、1,307 项测试，Chromium 套件通过 60 项测试，原版宿主隔离安装矩阵通过，覆盖默认设置保持不变、10 个跨进程原生压缩阶段和合成图片检查。当前宿主的已安装 Session 暂停 Task 安全检查也已通过；跨 Harness 版本的旧任务迁移尚未验证。候选版发布前，公开安装建议仍指向已发布的组合。