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

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,28 @@
 # Migrating from `dsh-codex`
 
+## 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. 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/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/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/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/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/lib/bin.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { A as DSH_PLUGIN_API_PACKAGES, B as isSupportedDshPluginApiVersion, Ft as prepareOpenAICodexBackendHeaders, Gt as OpenAICodexCredentialStore, It as loginOpenAICodex, Kt as openAICodexAuthPath, Lt as logoutOpenAICodex, Pt as openAICodexModelCatalog, Rt as openAICodexAuthStatus, V as readInstalledPackageVersion, Wt as OPENAI_CODEX_PROVIDER, c as migrateOpenAICodexSearchHistory, d as OPENAI_CODEX_BASE_URL, jt as normalizeOpenAICodexProxyUrl, l as CODEX_AUTO_REVIEW_MODEL, nt as OpenAICodexTrustedOriginsStore, rt as normalizeTrustedOrigin, u as probeCodexAutoReview, x as CODEX_CONNECT_VERSION, y as diagnoseOpenAICodex, z as evaluateCompatibility, zt as publicAuthError } from "./src-BWvQQwSp.js";
+import { A as DSH_PLUGIN_API_PACKAGES, B as isSupportedDshPluginApiVersion, Ft as prepareOpenAICodexBackendHeaders, Gt as OpenAICodexCredentialStore, It as loginOpenAICodex, Kt as openAICodexAuthPath, Lt as logoutOpenAICodex, Pt as openAICodexModelCatalog, Rt as openAICodexAuthStatus, V as readInstalledPackageVersion, Wt as OPENAI_CODEX_PROVIDER, c as migrateOpenAICodexSearchHistory, d as OPENAI_CODEX_BASE_URL, jt as normalizeOpenAICodexProxyUrl, l as CODEX_AUTO_REVIEW_MODEL, nt as OpenAICodexTrustedOriginsStore, rt as normalizeTrustedOrigin, u as probeCodexAutoReview, x as CODEX_CONNECT_VERSION, y as diagnoseOpenAICodex, z as evaluateCompatibility, zt as publicAuthError } from "./src-CO7Das8x.js";
 import { i as fetch, r as ProxyAgent, t as Agent } from "./undici-runtime-H2uktiw6.js";
 import { createHash } from "node:crypto";
 import { realpathSync } from "node:fs";