# dsh-grok-provider v1.0.4 `1.0.4` 修复 `1.0.3` 在 DeepSeek Harness `0.1.2-rc.1` 中启用后 Runtime 无法到达 ready 的问题。根因是发布产物仍 named import 已删除的 `installSettingsSection`。 ## 主要变化 - Host 不再从 `@deepseek-ai/dsh-settings` named import `installSettingsSection` 或 `settingsNamespace`。 - 改用 settings service 的 `installSection`,namespace 为合法字符串常量 `llm-grok`。 - settings service 缺失或重载时继续回退组合配置;Provider 与 Search 开关注册保持 `applies:"live"`。 - required peer 提升到实际支持 `0.1.2-rc.1` 的版本边界;Web client inject 用 `@deepseek-ai/dsh-client-ui-renderer` 取代已删除的 `dsh-client-runtime`。 - 认证恢复、部分输出保留、Search 协议、图片、固定 endpoint 和 Windows 浏览器登录边界不变。启用、停用和失败回滚不删除 receipt、generation 或账号状态。 ## 安装 ```sh dsh plugin --profile web add dsh-grok-provider@1.0.4 dsh web ``` 安装后重启正在运行的 DeepSeek Harness / DeepSeek YukiRyou。Runtime 应到达 ready,设置页出现 `llm-grok` namespace 与 Grok Provider。 ## 验证 - 聚焦回归证明 `@deepseek-ai/dsh-settings@0.1.2-rc.1` 不再导出 `installSettingsSection` / `settingsNamespace`,而 Host 仍可注册并清理 `llm-grok`。 - 打包后的全部 `dist/**` 不得引用已删除的 settings helper。 - 精确 Node `24.19.0` 全量测试、生产依赖审计与 `pack:check` 在合并前完成。 - 代码 PR [#41](https://github.com/yoshino-xiao7/dsh-grok-provider/pull/41) 已合并为 `61c80fff0841e44c16dabb2cc803a80c1bdf5456`;main CI run [`33870741679`](https://github.com/yoshino-xiao7/dsh-grok-provider/actions/runs/33870741679) 的 macOS 14 / Windows 2022 均通过。 - 发布证据 PR [#43](https://github.com/yoshino-xiao7/dsh-grok-provider/pull/43) 形成最终 release commit `62df21df08053d293ebb59c6e67597402c2305af`;main CI run [`33873037630`](https://github.com/yoshino-xiao7/dsh-grok-provider/actions/runs/33873037630) 的 macOS 14 / Windows 2022 均通过。 - 仓库所有者授权的唯一制品含 78 个文件,为 274,332 bytes packed、850,183 bytes unpacked;SHA-256 `464045290b06ce71b78285571c6968e6268fa403fa2350834d2dc479e88fd001`,SRI `sha512-axCBVXQ9BI9boYrlIsa+TWURMo8tQ5GdHpcQVfXUz2OLg+5rbg3XUZSv3ZRQVYQNmyXSQ+frIBDMsbZUGaXJ6w==`。 - Annotated tag `v1.0.4` peel 到最终提交;Trusted Publisher run [`33873873314` attempt 1](https://github.com/yoshino-xiao7/dsh-grok-provider/actions/runs/33873873314/attempts/1) 成功。npm `latest=1.0.4`,候选、Release 与 Registry tarball 逐字节一致;Registry 签名、attestations、锁定安装及精确绑定 tag/workflow/commit/run 的 SLSA provenance 均已回读。这些证据不替代真实 Web profile 手工对话或 Windows 外部浏览器验收。
English Version `1.0.4` repairs the `1.0.3` startup failure on DeepSeek Harness `0.1.2-rc.1`. The published Host still named-imported the removed `installSettingsSection` helper. ## Highlights - The Host no longer named-imports `installSettingsSection` or `settingsNamespace` from `@deepseek-ai/dsh-settings`. - Registration uses the settings service `installSection` API with the legal string constant `llm-grok`. - Composition config remains the fallback when the settings service is missing or reloaded. Search controls stay `applies:"live"`. - Required peers move to the Harness `0.1.2-rc.1` boundary. The Web client inject list uses `@deepseek-ai/dsh-client-ui-renderer` instead of the removed `dsh-client-runtime`. - Authentication recovery, partial-output preservation, Search protocol, images, fixed endpoints, and the Windows browser-login boundary are unchanged. Enable, disable, and failed-enable rollback keep receipts, generations, and account state. ## Install ```sh dsh plugin --profile web add dsh-grok-provider@1.0.4 dsh web ``` Restart any running DeepSeek Harness / DeepSeek YukiRyou process. Runtime should reach ready, and the settings page should expose the `llm-grok` namespace and Grok provider. ## Verification - A focused regression proves `@deepseek-ai/dsh-settings@0.1.2-rc.1` no longer exports `installSettingsSection` / `settingsNamespace`, while the Host still registers and removes `llm-grok`. - Packed `dist/**` must not mention the deleted settings helpers. - The exact Node `24.19.0` suite, production audit, and `pack:check` complete before merge. - Code PR [#41](https://github.com/yoshino-xiao7/dsh-grok-provider/pull/41) merged as `61c80fff0841e44c16dabb2cc803a80c1bdf5456`; main CI run [`33870741679`](https://github.com/yoshino-xiao7/dsh-grok-provider/actions/runs/33870741679) passed on macOS 14 and Windows 2022. - Release-evidence PR [#43](https://github.com/yoshino-xiao7/dsh-grok-provider/pull/43) produced final release commit `62df21df08053d293ebb59c6e67597402c2305af`; main CI run [`33873037630`](https://github.com/yoshino-xiao7/dsh-grok-provider/actions/runs/33873037630) passed on macOS 14 and Windows 2022. - The explicitly authorized unique artifact contains 78 files and is 274,332 bytes packed / 850,183 bytes unpacked; SHA-256 is `464045290b06ce71b78285571c6968e6268fa403fa2350834d2dc479e88fd001`, and SRI is `sha512-axCBVXQ9BI9boYrlIsa+TWURMo8tQ5GdHpcQVfXUz2OLg+5rbg3XUZSv3ZRQVYQNmyXSQ+frIBDMsbZUGaXJ6w==`. - Annotated tag `v1.0.4` peels to the final commit; Trusted Publisher run [`33873873314` attempt 1](https://github.com/yoshino-xiao7/dsh-grok-provider/actions/runs/33873873314/attempts/1) succeeded. npm reports `latest=1.0.4`; candidate, Release, and Registry tarballs are byte-identical; Registry signature, attestations, locked installation, and SLSA provenance bindings to the tag, workflow, commit, and run all verify. These checks do not substitute for a real Web-profile conversation or physical Windows browser-launch acceptance.