dsh-codex-connect 0.1.0-alpha.4.41 → 0.1.0-alpha.4.43

package/INSTALL.md

@@ -1,10 +1,10 @@
 # Installation Runbook for CLI Agents
 
-Published Alpha 4.40 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.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`.
 
 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.40`; `latest` intentionally remains on `0.1.0-alpha.4.34`. Use the exact-version commands below for 4.40. Publishing an Alpha and promoting the default installation channel are separate actions.
+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.
 
 ## Safety requirements
 
@@ -25,17 +25,17 @@ Check `dsh --version` before changing the requested profile. Use `dsh --help` to
 | `0.1.0-rc.7` | `0.1.0-alpha.4.14` |
 | `0.1.1-rc.2` | `0.1.0-alpha.4.21` |
 | `0.1.2-alpha.2` | `0.1.0-alpha.4.23` |
-| `0.1.2-rc.1` | `0.1.0-alpha.4.40` |
+| `0.1.2-rc.1` | `0.1.0-alpha.4.41` |
 | `0.1.2-alpha.5` | `0.1.0-alpha.4.25` |
-| `0.1.5-alpha.1` | `0.1.0-alpha.4.40` |
-| `0.1.5-rc.1` | `0.1.0-alpha.4.40` |
-| `0.1.5-rc.2` | `0.1.0-alpha.4.40` |
+| `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` |
 
 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.40 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.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.
 
-The Alpha 4.40 recommendation follows successful exact-release main CI 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/35809194145) 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/35808472911) 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. Native context management and task-level model control remain opt-in. Stock DSH 0.1.6-alpha.1 and alpha.2 remain undeclared; their separate compatibility trackers are not broadened by this release.
+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.
 
 Historical Alpha 4.35 evidence (not relabeled as 4.37):
 
@@ -64,10 +64,10 @@ 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.23
    ```
 
-   For DSH `0.1.2-rc.1`, `0.1.5-alpha.1`, `0.1.5-rc.1`, or `0.1.5-rc.2`, use Alpha 4.40:
+   For DSH `0.1.2-rc.1`, `0.1.5-alpha.1`, `0.1.5-rc.1`, or `0.1.5-rc.2`, use Alpha 4.41:
 
    ```sh
-   dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.40
+   dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
    ```
 
    For DSH `0.1.2-alpha.5`, use Alpha 4.25:
@@ -76,7 +76,7 @@ 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.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.40'` 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, 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.
 
 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,45 @@
 # 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
+until maintainer acceptance. This change does not retroactively disable npm 4.41
+or already-running installations. It takes effect only after the new package is
+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. 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
+tests remain, but there is no public setting or environment-variable escape hatch.
+Reopening requires a separately reviewed source change and new build after
+acceptance; per-task user authorization will still be required.
+
+Before downgrading an existing delegated task, use the authenticated safety exits
+and let the runtime verify cleanup and delivery. Do not delete the task ledger or
+edit its counters to force recovery. Cross-device/new-cookie task ownership limits
+remain unchanged.
+
+
 `dsh-codex-connect` uses the same provider id (`openai-codex`), OAuth filename (`.openai-codex-auth.json`), Cordis row id (`llm-openai-codex`), and browser auth routes for compatibility. The packages cannot be active together because Harness forbids duplicate provider adapters.
 
 1. Record the effective default model, search route, and `llm-openai-codex` config without reading any OAuth file.

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: de5caa049cdea46800dca79f9c18c00983d1e4c6
-docs/README.zh.md: 4e6ee736540e88f22939a08287df88706c5bb18f
+README.md: fa12308fc1124ec0edc183a088fcdff77323bc3a
+docs/README.zh.md: 9ec30155f320aae3d9ed33d091304624ff70943b

package/README.md

@@ -16,17 +16,19 @@ This guide describes the published pairings below. Check `dsh --version` first a
 
 | Requirement | Verified pairing |
 |---|---|
-| Codex Connect | `0.1.0-alpha.4.40` |
+| 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` |
 | 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.40 while `latest` intentionally remains on 4.34. Use the exact version below for 4.40; this recommendation does not promote the default installation channel.
+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.
+
+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.
 
 ### 1. Install
 
 ```sh
-dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.40
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
 dsh web
 ```
 

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

@@ -16,17 +16,19 @@ Codex Connect 为标准 Harness agent loop 添加 `openai-codex` 模型提供方
 
 | 要求 | 已验证组合 |
 |---|---|
-| Codex Connect | `0.1.0-alpha.4.40` |
+| 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` |
 | Node.js | `^22.19.0 \|\| >=24.0.0` |
 | 账户 | 通过 ChatGPT OAuth 使用所请求的 Codex 模型；可用性由 OpenAI 决定 |
 
-截至 2026-09-23，npm `alpha` 指向 4.40，`latest` 则有意保留在 4.34。安装 4.40 请使用下方精确版本命令；文档推荐更新不代表默认安装渠道已提升。
+截至 2026-09-23，npm `alpha` 指向 4.41，`latest` 仍指向 4.40。安装 4.41 请使用下方精确版本命令；发布 Alpha 与提升默认安装渠道是两项独立操作。
+
+任务级模型选择仍需在新会话中主动开启。4.41 的新授权默认只选择 GPT-5.6 Sol / Medium，开始前会显示准确的模型范围和请求上限。已有任务授权不会被自动收窄；如需改用较窄范围，请先切回手动，再在新任务中选择。
 
 ### 1. 安装
 
 ```sh
-dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.40
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
 dsh web
 ```
 

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/experiments/adaptive-task-publication-gate.md

@@ -0,0 +1,72 @@
+# Pause public task orchestration pending maintainer acceptance
+
+Status: **source-only draft; not merge-ready, published, deployed or a claim that existing public installations are disabled**.
+Baseline: main `41f0fa50b41b129a57c761744fef5db0a80f5031`, inspected on 2026-09-23. This is independent of the channel-documentation-only PR #247.
+
+## Requested product boundary
+
+Temporarily withdraw the public activation entry and options for task-level automatic model choice and read-only delegation until maintainer acceptance. Preserve their implementation and tests. Do not remove ordinary GPT-6/Astra/manual model selection, native compaction, accounts, or unrelated settings. No package publication, channel change, daily service operation or live-provider request is authorized by this PR.
+
+## Source implementation
+
+- A shared, hard-closed source release decision (`ADAPTIVE_TASK_PUBLIC_RELEASE = false`), not another saved user setting. Browser input, old grants, URL parameters, environment variables and model output cannot open it. It is a distribution decision, not a substitute for the existing permission checks.
+- The authenticated public HTTP route rejects `start`, `resume`, `upgrade` and `delegate-enable` before calling the runtime. This also covers stale browser bundles. Reads cannot advertise `canStart: true` while paused.
+- Host authentication, principal binding, command decoding and runtime ownership checks remain in place. `manual`, `stop`, `delegate-disable` and `downgrade` still reach the existing authorization/lifecycle implementation. These are not unconditional grants to execute an exit.
+- The published conversation contribution selects a recovery-only component while paused. A confirmed ordinary conversation renders no collaboration entry, model/effort selectors, request-limit input, Start, Resume or delegation consent. Existing tasks retain readback, Stop and manual takeover. A failed read retains only a recovery path and is not reported as confirmed off.
+- Recovery performs one bounded initial read and explicit user-requested readbacks, with at most two additional GET attempts for the existing live-root-readiness error. There is no periodic polling and no POST retry. Session changes abort and discard stale responses. No task ledger, history, counter or prior grant is deleted or rewritten merely to hide the UI.
+- The original full control and runtime remain available for a separately authorized internal validation build. Reopening public access requires a separate reviewed source change/build; it still does not create a task grant. No general-purpose production escape hatch is added.
+
+## Existing installations and activation state
+
+A source PR cannot revoke a published npm archive or change an already running process. Merge, regenerated artifacts, a new approved release and user upgrade/restart are separate steps. Previously running 4.40/4.41 installations remain unchanged by this draft. Do not present UI removal as a remote kill switch.
+
+Retain the existing runtime's interrupted-restoration/explicit-resume behavior; the public route now refuses that resume while paused. Upgrade/reload, old v1/v2 grants, already-running children, and manual takeover must be exercised on the actual installed new artifact before release. Do not assume that hiding controls proves runtime quiescence.
+
+## Verification performed in this editing environment
+
+- 33 isolated assertions passed against the actual new policy module on Node 22.16.0 using Node type stripping: closed default, four rejected activation actions, four retained exits, strict boolean handling, unknown-command refusal, six preserved lifecycle states, immutable projection and preserved stopping diagnostics.
+- TypeScript transpilation/syntax checks are recorded separately in the PR. They are not a repository typecheck.
+- Added Vitest policy and real-handler unit tests with a stub Connection/runtime. These do not certify signed-cookie verification or full host behavior and have not been executed here.
+- No credentials or real models were used. No user machine, 3080 or 3081 was modified.
+
+The current conversation could not discover the previously used WebCodex execution tools. The isolated editing container has no repository dependencies and cannot resolve GitHub for clone/install. GitHub connector reads/writes remain available. These limitations are not test passes.
+
+## Mandatory work before leaving draft
+
+1. Regenerate and commit the matching `lib/` outputs with the repository's normal build; do not hand-patch generated bundles. Existing committed build bytes are deliberately still the baseline and are not a gate-closed distributable.
+2. Run the new Vitest suite, host/client typecheck, lint and full `pnpm run check`. Existing HTTP/installed-session scenarios that expect public activation must be split into default-closed admission/recovery checks and explicitly scoped internal acceptance; do not skip or globally enable tests to obtain green results.
+3. Add/run browser coverage for no entry on fresh conversations, only safety exits on v1/v2 sessions, delayed session readbacks, unknown state, lost POST replies/no replay, narrow-screen and bilingual controls. Run full browser regression and installed native Session checks against actual rebuilt bytes.
+4. Verify old grants and crash/reload recovery cannot auto-resume, retained counters/history and normal manual models work, and stock compatible hosts can install/start. Do not change existing host workarounds or daily profiles as part of this PR.
+5. Update prospective user-facing release/migration documentation without rewriting historical 4.40/4.41 facts. Preserve README bilingual consistency. Read exact-head CI before review/merge.
+
+## Reopening gate
+
+After separately approved internal/live-account acceptance, use a second PR to propose reopening. Attach exact artifact/environment identity, default-closed non-regression, bounded real-model/handoff/delegation checks, stop/manual/restart results and user comprehension evidence. Quality or savings claims require their own task comparisons. Never equate a green synthetic test count with live acceptance.
+
+## Release completion follow-up (2026-09-23)
+
+The maintainer authorized completing this PR, normal merge, a new Alpha publication,
+and promotion of the verified package to npm latest. This is not authorization to
+bypass CI, install on daily ports, or run a real provider experiment.
+
+The old public HTTP expectations are now replaced by closed-route assertions and
+explicit synthetic prior-task preparation. The actual product still refuses every
+activation command. Runtime-only delegation tests retain their original coverage;
+no environment or browser option opens the shipping gate. Recovery UI regression
+covers both languages, phone width, bounded readiness, unknown state, stale-session
+responses and lost manual-exit replies.
+
+The installed checker uses the immutable public 4.41 archive (SHA-256
+`0823648f3db055a8e12f7bdbac8b23de9d25d4b9f0c6c91794fe21dd3207ed81`) to create genuine
+old grants in its owned temporary profile, then replaces only that fixture's
+package with the candidate's verified bytes and restarts the owned host. All
+credentials and model replies remain synthetic. This is an upgrade/recovery test,
+not live account acceptance or daily-profile deployment. Its result must be read
+from the exact candidate's CI; writing the checker does not mean it passed.
+
+Local Node 22.19.0 complete check passed (116 files / 1,309 tests, typecheck, lint,
+normal build, capability CLI, compatibility and package checks). This report does
+not certify later edits or remote installation/browser gates. Local Chromium 144
+navigation was blocked by the execution environment's browser policy before UI
+acceptance; that run is not passing browser evidence and no policy was changed.
+The repository's existing independent CI remains the merge gate.

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.42.md

@@ -0,0 +1,27 @@
+# Codex Connect Alpha 4.42 — public orchestration paused
+
+## English
+
+This release ships the publication gate from #248. New conversations no longer offer automatic task-level model choice or read-only delegation. The authenticated backend also rejects new activation, automatic resume, task upgrade and delegation enablement, including requests from cached older clients. This is a maintainer-controlled release pause, not another user preference.
+
+Existing task history, grants and request counters are preserved. Existing-task controls retain state readback, Stop and manual takeover. Restart does not replay automatic work; users can take over manually and continue with the ordinary model picker. Manual GPT-6/Astra selection, account settings, other plugin features and native compaction are unchanged. Reopening requires a separately reviewed source change after maintainer acceptance.
+
+The preceding #248 gate passed Node 22/24 checks, 1,309 unit tests, 60 browser tests, declared-host matrices and a seven-group installed synthetic upgrade from public 4.41. Release-candidate checks must independently validate the final 4.42 artifact. These tests do not establish real-account orchestration quality, quota savings, daily-profile acceptance or physical-mobile acceptance. Full installed-page acceptance uses baseline DSH 0.1.2-rc.1 with the documented dependency/installer pins; the separate runtime matrix covers all declared hosts.
+
+After npm publication is independently confirmed, install this exact version on a declared compatible host:
+
+```sh
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.42
+```
+
+Preparing or publishing the package does not upgrade already-running installations. The npm `latest` channel is a separate, explicitly authorized promotion, not implied by `alpha` publication. See `MIGRATION.md` and `docs/experiments/adaptive-task-publication-gate.md` for existing-task recovery.
+
+## 中文
+
+本版交付 #248 的公开发布门禁：新会话不再显示任务级自动选模型和只读委派入口；后端也拒绝新开启、自动恢复、任务升级及启用委派，包括旧缓存页面发来的请求。这是维护者控制的发布暂停，不是另一个用户可以勾开的设置。
+
+已有任务的历史、授权和请求计数保留，仍可查看状态、停止任务和切回手动。重启不会自动重放任务；手动接管后可以继续通过普通模型选择器工作。GPT-6／Astra 手动选择、账户设置、其他插件功能与原生压缩不变。重新开放需在维护者验收后通过另一个明确评审的源码变更。
+
+此前 #248 已通过 Node 22／24、1,309 项单测、60 项浏览器测试、声明宿主矩阵，以及从公开 4.41 升级的七组实际安装模拟验收。最终 4.42 包还需独立通过发布候选检查。这些证据不代表真实账户协同质量、省额度、日常 profile 或实体手机验收。完整页面升级检查使用基线 DSH 0.1.2-rc.1 与已记录的依赖／安装器固定组合；独立运行时矩阵覆盖全部声明宿主。
+
+确认 npm 已发布后，可用上面的精确版本命令安装。准备或发布包不会自动升级正在运行的实例；`latest` 是另行明确授权的渠道提升，不随 `alpha` 发布自动完成。已有任务恢复说明见迁移文档与公开门禁文档。

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 版本的旧任务迁移尚未验证。候选版发布前，公开安装建议仍指向已发布的组合。