@chatcode/chatcode-cli 3.0.2-rc.2 → 3.0.2-rc.3
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.
- package/README.i18n.yaml +2 -2
- package/README.md +1 -1
- package/README.zh.md +1 -1
- package/lib/{dist-DxjlHHph.js → dist-w_sIm4VD.js} +203 -197
- package/lib/{plugin-jvd9PCVt.js → plugin-ChwScT9e.js} +12 -7
- package/lib/tui-compat.js +1 -1
- package/package.json +26 -26
- package/runtime/manifest.json +1 -1
- package/runtime/node_modules/@deepseek-ai/dsh-client-ui-settings-account/lib/client.js +2 -2
- package/runtime/node_modules/@deepseek-ai/dsh-client-ui-settings-general/lib/client.js +1 -1
- package/runtime/node_modules/@deepseek-ai/dsh-client-ui-sidebar/lib/client.js +1 -1
- package/runtime/node_modules/@deepseek-ai/dsh-session-log-export/lib/client.js +1 -5
- package/runtime/node_modules/@deepseek-ai/dsh-web-app/presets/cordis.patch.yml +2 -1
- package/runtime/node_modules/@deepseek-ai/dsh-web-app/presets/ptc.patch.yml +2 -1
- package/runtime/node_modules/@deepseek-ai/dsh-web-app/presets/standard.patch.yml +2 -1
package/README.i18n.yaml
CHANGED
package/README.md
CHANGED
|
@@ -71,7 +71,7 @@ Production runs require built package and frontend artifacts. From the repositor
|
|
|
71
71
|
|
|
72
72
|
The published CLI directly pins every Harness runtime package referenced by the base/Web bundles and every required peer of its bundled ChatCode plugins. Keep those entries on the same Harness release when publishing: npm's global installer does not preserve pnpm workspace peer unification, and otherwise may hoist an older ABI beside the current runtime.
|
|
73
73
|
|
|
74
|
-
The npm artifact carries fork-owned JavaScript packages under `runtime/node_modules` and lists them in `runtime/manifest.json`. Platform-specific `node-addon-system` binaries remain exact-version optional npm dependencies, selected for the installation host; they are excluded from the embedded runtime. It also carries the TUI admission registry under `lib/dsh-ecosystem-spec`, where command authorization reads its permission defaults before applying the user's grants file. Profile startup includes the complete runtime package list when resolving presets and plugins, including packages absent from the slim npm dependency list. The launcher resolves embedded packages in memory for both ESM and CommonJS, including imports from external plugins. Startup does not modify the installation directory, so a root-owned installation can be launched by an ordinary user with read access; the user still needs a writable ChatCode CLI home. CLI and Web share the [startup model preference](../../packages/core/agent-default-model/README.md); already running frontends do not switch each other's model.
|
|
74
|
+
The npm artifact carries fork-owned JavaScript packages under `runtime/node_modules` and lists them in `runtime/manifest.json`. Platform-specific `node-addon-system` binaries remain exact-version optional npm dependencies, selected for the installation host; they are excluded from the embedded runtime. It also carries the TUI admission registry, protocols, and schemas under `lib/dsh-ecosystem-spec`, where command authorization reads its permission defaults before applying the user's grants file. Profile startup includes the complete runtime package list when resolving presets and plugins, including packages absent from the slim npm dependency list. The launcher resolves embedded packages in memory for both ESM and CommonJS, including imports from external plugins. Startup does not modify the installation directory, so a root-owned installation can be launched by an ordinary user with read access; the user still needs a writable ChatCode CLI home. CLI and Web share the [startup model preference](../../packages/core/agent-default-model/README.md); already running frontends do not switch each other's model.
|
|
75
75
|
|
|
76
76
|
The `@chatcode/chatcode-cli/profile-boot` export provides the shared profile lifecycle to the Desktop host. A resolved application profile supplies its own installation anchor for runtime package resolution while retaining the ChatCode CLI home patch, proxy environment, telemetry switch, patch reload, and bounded shutdown.
|
|
77
77
|
|
package/README.zh.md
CHANGED
|
@@ -71,7 +71,7 @@ profile 目录包含一个 `package.json`，其中记录树外插件依赖，以
|
|
|
71
71
|
|
|
72
72
|
发布版 CLI 会直接固定 base/Web 组合包实际引用的所有 Harness 运行时包，以及随附 ChatCode 插件的全部必需 peer。发布时必须让这些依赖保持在同一个 Harness 版本：npm 全局安装不会保留 pnpm workspace 对 peer 的统一解析，否则可能把旧 ABI 提升到顶层并与当前运行时混用。
|
|
73
73
|
|
|
74
|
-
npm 产物把分支自有的 JavaScript 包放在 `runtime/node_modules`，并通过 `runtime/manifest.json` 列出它们。各平台的 `node-addon-system` 二进制使用固定版本的 npm 可选依赖，由安装器按目标机器的平台选择，不加入内嵌 runtime。产物还在 `lib/dsh-ecosystem-spec` 中携带 TUI
|
|
74
|
+
npm 产物把分支自有的 JavaScript 包放在 `runtime/node_modules`，并通过 `runtime/manifest.json` 列出它们。各平台的 `node-addon-system` 二进制使用固定版本的 npm 可选依赖，由安装器按目标机器的平台选择，不加入内嵌 runtime。产物还在 `lib/dsh-ecosystem-spec` 中携带 TUI 准入注册表、协议和 schema；命令授权先从该目录读取权限默认值，再应用用户的授权文件。Profile 启动解析预设和插件时使用完整的运行时包列表，包括精简 npm 依赖列表中没有的包。启动器在内存中统一解析内嵌包的 ESM 与 CommonJS 导入，也覆盖外部插件的导入。启动不会修改安装目录，因此普通用户只需对 root 安装的目录具有读取权限；用户自己的 ChatCode CLI home 仍须可写。CLI 与 Web 共用[启动模型偏好](../../packages/core/agent-default-model/README.zh.md)；已运行的两端不会互相切换模型。
|
|
75
75
|
|
|
76
76
|
`@chatcode/chatcode-cli/profile-boot` 导出向 Desktop Host 提供共享 profile 生命周期。已解析的应用 profile 为运行时包解析指定自己的安装锚点，同时沿用 ChatCode CLI home patch、代理环境、遥测开关、patch 热重载和有界关闭。
|
|
77
77
|
|