dsh-codex-connect 0.1.0-alpha.4.15 → 0.1.0-alpha.4.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (10) hide show
  1. package/INSTALL.md +2 -2
  2. package/README.i18n.yaml +2 -2
  3. package/README.md +22 -2
  4. package/docs/README.zh.md +22 -2
  5. package/lib/bin.js +1 -1
  6. package/lib/client.js +1243 -46
  7. package/lib/index.d.ts +62 -1
  8. package/lib/index.js +2 -2
  9. package/lib/{src-D5OQGYt6.js → src-C-GNEOjg.js} +511 -21
  10. package/package.json +7 -2
package/INSTALL.md CHANGED
@@ -12,7 +12,7 @@ Install `dsh-codex-connect` into one requested DeepSeek Harness profile without
12
12
 
13
13
  ## Install and validate
14
14
 
15
- The only verified combination is DSH plugin API packages `0.1.1-rc.2`, `@earendil-works/pi-ai` `0.82.1`, and Node.js `^22.19.0 || >=24.0.0`. Alpha 4.15 uses the rc.2 keyed Plugin configuration slot; users of older DSH API packages should upgrade the DSH API packages and pi-ai together, then rerun `dsh-codex-connect doctor --json` and `pnpm --silent run check:compatibility`; the contract does not make claims about future versions.
15
+ The only verified combination is DSH plugin API packages `0.1.1-rc.2`, `@earendil-works/pi-ai` `0.82.1`, and Node.js `^22.19.0 || >=24.0.0`. Alpha 4.16 uses the rc.2 keyed Plugin configuration slot; users of older DSH API packages should upgrade the DSH API packages and pi-ai together, then rerun `dsh-codex-connect doctor --json` and `pnpm --silent run check:compatibility`; the contract does not make claims about future versions.
16
16
 
17
17
  1. Check `dsh --version` or `dsh --help`. From a Harness checkout use `pnpm dsh`.
18
18
  2. Install the package:
@@ -21,7 +21,7 @@ The only verified combination is DSH plugin API packages `0.1.1-rc.2`, `@earendi
21
21
  dsh plugin --profile web add dsh-codex-connect@alpha
22
22
  ```
23
23
 
24
- After `0.1.0-alpha.4.15` is published, pin it exactly with `dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.15`. If npm is unavailable after its matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.15'`.
24
+ After `0.1.0-alpha.4.16` is published, pin it exactly with `dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.16`. If npm is unavailable after its matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.16'`.
25
25
 
26
26
  3. Run `dsh --profile web --dump-config` and require exactly one `llm-openai-codex` row loading `dsh-codex-connect`.
27
27
  4. Confirm the effective `agent-default-model` and `web.searchProvider` values are unchanged from before installation.
package/README.i18n.yaml CHANGED
@@ -2,5 +2,5 @@
2
2
  # side as of the last confirmed-consistent state. Both languages carry equal authority;
3
3
  # after editing either side, bring the other along and re-record with:
4
4
  # git hash-object README.md docs/README.zh.md
5
- README.md: 3100a9d730d2eb072e5afcb5897b548da0e00fab
6
- docs/README.zh.md: a7c3497b9676910b0857e71937241acdcb20b76e
5
+ README.md: f3b46026b1b23633738915667fa6e20c9513c290
6
+ docs/README.zh.md: ec299175d4383a1f07af207378be9aaa0b8edbe2
package/README.md CHANGED
@@ -28,7 +28,27 @@ dsh plugin --profile web add dsh-codex-connect@alpha
28
28
 
29
29
  Expected result: the package is added to that profile. This does not change the profile's default model or global search route.
30
30
 
31
- To reproduce this release exactly, use `dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.15`. If npm is unavailable after the matching GitHub prerelease exists, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.15'`. A local checkout can be installed as `link:/absolute/path/to/dsh-codex-connect`.
31
+ To reproduce this release exactly, use `dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.16`. If npm is unavailable after the matching GitHub prerelease exists, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.16'`. A local checkout can be installed as `link:/absolute/path/to/dsh-codex-connect`.
32
+
33
+ ### Version updates
34
+
35
+ Codex Connect checks public package metadata and this repository's `verified-compatibility.json` periodically through the DSH Web server. The same card reads the locally loaded DSH package version, shows it beside the latest DSH version recorded by this project, and compares the installed and latest plugin versions without repeating equal values. Local version detection uses package metadata already available to the plugin and does not require a DSH Core change.
36
+
37
+ The compatibility record lists exact plugin and DSH versions rather than assuming every later release remains compatible. Maintainers can add a newly verified DSH version to the repository file without publishing another plugin release. A green result means the installed plugin was verified; yellow means the latest plugin was verified and should be installed first; red means neither the installed plugin nor the latest published plugin has been verified yet; gray means the record could not be checked. A red result includes a prefilled GitHub issue link so users can remind the maintainer without composing a report from scratch.
38
+
39
+ When a newer plugin version is available, a frame-wide DSH notice appears even if you switch conversations. It first shows the user-facing changes between your installed version and the newest version; technical release notes are available as a secondary detail, or from the release page. The plugin never runs an upgrade command by itself.
40
+
41
+ The notice first summarizes the user-facing changes between your installed version and the newest version. Technical release notes remain available as a secondary detail. To update, copy the short request shown in the notice to the Agent you use for this DSH project. The Agent can inspect the project instructions and choose the appropriate install or update method; the plugin does not execute anything on your behalf.
42
+
43
+ After the Agent reports completion, return to the notice or settings card and select **Done — check again**. If the running process still reports the old version, restart that profile's DSH Web process and check again.
44
+
45
+ For a manual terminal update, use the command documented for the profile you are running:
46
+
47
+ ```sh
48
+ dsh plugin --profile web update dsh-codex-connect
49
+ ```
50
+
51
+ Replace `web` with your own Harness profile name when needed. If the running process still reports the old version after the check, restart that profile's DSH Web process and check again. If public metadata is unavailable, no update notice is shown; the account and model features continue working normally.
32
52
 
33
53
  ### 2. Start Harness
34
54
 
@@ -203,7 +223,7 @@ Selecting Codex as the profile's global search route is another explicit change:
203
223
 
204
224
  ## Compatibility and security boundary
205
225
 
206
- - The only verified compatibility combination is DSH plugin API packages `0.1.1-rc.2`, `@earendil-works/pi-ai` `0.82.1`, and Node.js `^22.19.0 || >=24.0.0`; see [compatibility.json](compatibility.json). Alpha 4.15 uses the rc.2 keyed Plugin configuration slot; users of older DSH API packages should upgrade to the rc.2 API packages.
226
+ - The only verified compatibility combination is DSH plugin API packages `0.1.1-rc.2`, `@earendil-works/pi-ai` `0.82.1`, and Node.js `^22.19.0 || >=24.0.0`; see [compatibility.json](compatibility.json). Alpha 4.16 uses the rc.2 keyed Plugin configuration slot; users of older DSH API packages should upgrade to the rc.2 API packages.
207
227
  - Upgrade the DSH plugin API packages and `@earendil-works/pi-ai` as one group, then run `dsh-codex-connect doctor --json` and the compatibility check again. This contract does not make claims about future versions.
208
228
  - ChatGPT plan eligibility, model access, quotas, and backend behavior are controlled by OpenAI and may change.
209
229
  - The Codex endpoint does not enforce the ordinary Responses `max_output_tokens` field. Harness compaction still works, but that summary cap cannot be imposed server-side on this route.
package/docs/README.zh.md CHANGED
@@ -28,7 +28,27 @@ dsh plugin --profile web add dsh-codex-connect@alpha
28
28
 
29
29
  预期结果：包被加入该 profile。这个动作不会更改 profile 的默认模型或全局搜索路由。
30
30
 
31
- 如需精确复现这个版本，使用 `dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.15`。对应 GitHub prerelease 已创建但 npm 不可用时，可使用 `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.15'`。本地 checkout 可安装为 `link:/absolute/path/to/dsh-codex-connect`。
31
+ 如需精确复现这个版本，使用 `dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.16`。对应 GitHub prerelease 已创建但 npm 不可用时，可使用 `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.16'`。本地 checkout 可安装为 `link:/absolute/path/to/dsh-codex-connect`。
32
+
33
+ ### 版本更新提醒
34
+
35
+ Codex Connect 会通过 DSH Web 服务定期检查公开的 npm 包信息，以及本仓库维护的 `verified-compatibility.json`。同一张卡片会读取本机实际加载的 DSH 软件包版本，与本项目记录的最新 DSH 版本并列显示，并在不重复相同版本号的前提下比较当前与最新插件版本。本机版本检测只使用插件已经能够取得的软件包元数据，不要求 DSH Core 作出任何修改。
36
+
37
+ 兼容性清单按插件版本和 DSH 版本精确记录，不假设后续版本天然兼容。维护者确认新的 DSH 版本后，只需更新仓库文件，不必重新发布插件。绿色表示当前插件已经通过验证；黄色表示最新插件已经通过验证，应先升级插件；红色表示当前插件和最新发布的插件都尚未通过验证；灰色表示暂时无法检查清单。红色状态会提供预填内容的 GitHub Issue 链接，让用户无需自行组织报告就能提醒维护者。
38
+
39
+ 发现插件新版本后，即使你切换了对话，DSH 界面也会显示全局更新提醒。提醒会先展示从你当前版本到最新版本之间对用户有用的功能；完整技术发布说明放在次级详情或发布页面中。插件不会自动执行升级命令。
40
+
41
+ 完成升级的建议流程是：把提醒里的简短请求复制给你正在使用的 Agent。Agent 会查看项目说明，自行判断合适的安装或更新方式；插件不会替你执行任何操作。
42
+
43
+ Agent 报告完成后，回到提醒或设置卡片，点击 **已完成，重新检查**。如果运行中的 DSH Web 仍显示旧版本，再重启当前 profile 的 DSH Web，然后重新检查。
44
+
45
+ 如果你要手动在终端更新，本指南使用的 profile 命令如下：
46
+
47
+ ```sh
48
+ dsh plugin --profile web update dsh-codex-connect
49
+ ```
50
+
51
+ 如果你使用的是其他 Harness profile，请把 `web` 换成对应的 profile 名称。如果重新检查时仍显示旧版本，请先重启该 profile 的 DSH Web，再检查一次。公开包信息暂时不可用时不会显示更新提醒，账户和模型功能仍可正常使用。
32
52
 
33
53
  ### 2. 启动 Harness
34
54
 
@@ -203,7 +223,7 @@ dsh plugin --profile web exec dsh-codex-connect doctor --json
203
223
 
204
224
  ## 兼容性与安全边界
205
225
 
206
- - 当前唯一已验证的兼容组合是 DSH 插件 API packages `0.1.1-rc.2`、`@earendil-works/pi-ai` `0.82.1` 和 Node.js `^22.19.0 || >=24.0.0`；详见 [compatibility.json](../compatibility.json)。Alpha 4.15 使用 rc.2 的 keyed 插件配置 slot；旧版 DSH API packages 用户应升级到 rc.2 API packages。
226
+ - 当前唯一已验证的兼容组合是 DSH 插件 API packages `0.1.1-rc.2`、`@earendil-works/pi-ai` `0.82.1` 和 Node.js `^22.19.0 || >=24.0.0`；详见 [compatibility.json](../compatibility.json)。Alpha 4.16 使用 rc.2 的 keyed 插件配置 slot；旧版 DSH API packages 用户应升级到 rc.2 API packages。
207
227
  - 升级时请将 DSH 插件 API packages 与 `@earendil-works/pi-ai` 作为一组升级，再运行 `dsh-codex-connect doctor --json` 和兼容性检查。本契约不对未来版本作判断。
208
228
  - ChatGPT 套餐资格、模型权限、额度和后端行为由 OpenAI 控制，可能变化。
209
229
  - Codex 端点不会强制普通 Responses 的 `max_output_tokens` 字段。Harness 压缩仍可工作，但这个摘要上限不能由服务端在该路由上强制。
package/lib/bin.js CHANGED
@@ -1,5 +1,5 @@
1
1
  #!/usr/bin/env node
2
- import { L as diagnoseOpenAICodex, c as migrateOpenAICodexSearchHistory, ct as logoutOpenAICodex, lt as openAICodexAuthStatus, nt as OpenAICodexTrustedOriginsStore, pt as openAICodexAuthPath, rt as normalizeTrustedOrigin, st as loginOpenAICodex, z as CODEX_CONNECT_VERSION } from "./src-D5OQGYt6.js";
2
+ import { L as diagnoseOpenAICodex, c as migrateOpenAICodexSearchHistory, ct as normalizeTrustedOrigin, ft as loginOpenAICodex, mt as openAICodexAuthStatus, pt as logoutOpenAICodex, st as OpenAICodexTrustedOriginsStore, vt as openAICodexAuthPath, z as CODEX_CONNECT_VERSION } from "./src-C-GNEOjg.js";
3
3
  import { fileURLToPath } from "node:url";
4
4
  import { realpathSync } from "node:fs";
5
5
  import { spawn } from "node:child_process";