@mars-sea/dsh-commandcode-provider 0.10.0-alpha.7 → 0.10.1

package/CHANGELOG.md

@@ -6,6 +6,36 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ## [Unreleased]
 
+## [0.10.1] - 2026-09-07
+
+### Added
+
+- **Support the Command Code Provider Chat Completions API** ([#22](https://github.com/Mars-Sea/dsh-commandcode-provider/pull/22)). Accounts with Provider API access now use the documented `POST /provider/v1/chat/completions` transport (a flat OpenAI-compatible request body) instead of the legacy CLI transport. Historical reasoning is replayed as `reasoning_content` for tool-loop continuity, and OpenAI SSE chunks (`reasoning` / `reasoning_content` / `content` / `tool_calls` / `usage`) are parsed into stream output. The legacy `POST /alpha/generate` transport is unchanged (including its no-reasoning-replay behavior) and remains the route for Go-plan accounts plus the automatic fallback when the Provider API answers `upgrade_required`.
+
+### Fixed
+
+- **Switching to Command Code mid-session no longer fails with `input[N].call_id must be <= 64`** ([#23](https://github.com/Mars-Sea/dsh-commandcode-provider/issues/23)). Tool-call ids issued by another provider can exceed the Command Code gateway's 64-character limit and were replayed verbatim, so the stream was rejected once such history existed. Overlong paired ids are now remapped to short per-request aliases (`cc-1`, `cc-2`, …) on both transports, with each call and its result resolving through the same map so the pair stays correlated; ids within the limit still pass through unchanged.
+
+### Changed
+
+- **Synced with the official command-code@1.50.0 CLI** (2026-09-06: re-verified with no snapshot changes). `COMMAND_CODE_CLI_VERSION` is now `1.50.0`. Re-verified against the official sources: wire protocol (both the `/alpha/generate` CLI transport and the `/provider/v1/chat/completions` Provider transport), endpoints, auth flow, model catalog, subscription plan maps, deals, and peak/off-peak windows are all identical to 1.49.1.
+
+## [0.10.0] - 2026-09-04
+
+> **First stable release for the dsh 0.1.2 line.** This release requires **dsh 0.1.2-rc.1 or later** and is published on the `latest` npm tag. It graduates the 0.10.0-alpha.x line (command-code syncs up to 1.47.0) to stable. The previous stable line — 0.9.1 for older Harness releases (the 0.5.0 era) — is no longer under active maintenance; it stays on npm for existing users but receives no further updates.
+
+### Changed
+
+- **Raised the minimum supported DeepSeek Harness version to 0.1.2-rc.1.** Every Harness peer and development package now starts at the rc.1 line — the version `@latest` installs today. Source APIs, the Remote wire, and the Web slot surfaces are unchanged between alpha.2 and rc.1, so this is a metadata-only bump with no code changes.
+
+## [0.10.0-alpha.8] - 2026-09-04
+
+> **Alpha channel for dsh 0.1.2-alpha.2.** This release requires **dsh 0.1.2-alpha.2 or later** and is published under the `alpha` npm tag, so `@latest` stays on 0.9.1 for older Harness releases. Install it explicitly with `@alpha`.
+
+### Changed
+
+- **Synced with the official command-code@1.47.0 CLI** (2026-09-04: marked Grok 4.6 vision-capable). `COMMAND_CODE_CLI_VERSION` is now `1.47.0`. Grok 4.6 now shows the `Image` capability marker in the picker.
+
 ## [0.10.0-alpha.7] - 2026-09-04
 
 > **Alpha channel for dsh 0.1.2-alpha.2.** This release requires **dsh 0.1.2-alpha.2 or later** and is published under the `alpha` npm tag, so `@latest` stays on 0.9.1 for older Harness releases. Install it explicitly with `@alpha`.

package/README.md

@@ -34,19 +34,19 @@ See [Screenshots](#screenshots) below for what the UI looks like.
 
 Pick the release line that matches your DeepSeek Harness version:
 
-- **dsh 0.1.2-alpha.2 or later** (the current alpha line) — use the matching alpha plugin release. Install explicitly with the `alpha` tag:
+- **dsh 0.1.2-rc.1 or later** (the current 0.1.2 line — what `@latest` installs today):
 
   ```sh
-  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@alpha
+  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest
   ```
 
-- **Older dsh releases** (the 0.5.0 line and earlier, which use the rc-era Host/browser APIs) — the 0.9.1 plugin keeps working there and stays on the `latest` tag:
+- **Older dsh releases** (the 0.5.0 line and earlier, which use the rc-era Host/browser APIs) — the last plugin version supporting them is 0.9.1, installed by exact version. That line is no longer under active maintenance:
 
   ```sh
-  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest
+  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@0.9.1
   ```
 
-> The `alpha` tag never moves `latest`: a plain `@latest` install always gets the newest stable release for older Harness versions, and upgrading to the alpha line is always an explicit opt-in.
+> The `latest` tag now always points at the current 0.1.2-line plugin release, so a plain `@latest` install gets the newest stable release for dsh 0.1.2+. Users on the old 0.5.0-era Harness line must pin `@0.9.1` explicitly.
 
 Fresh pnpm 10 marketplace generations are supported directly. Do not add a separate `@deepseek-ai/dsh-invariants` dependency; the plugin declares it as a Host peer so the active dsh profile remains the owner of Harness packages.
 
@@ -55,8 +55,8 @@ Fresh pnpm 10 marketplace generations are supported directly. Do not add a separ
 Update with the same tag you installed with:
 
 ```sh
-dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@alpha      # dsh 0.1.2-alpha.2+
-dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@latest     # older dsh (0.5.0 line)
+dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@latest     # dsh 0.1.2-rc.1+
+dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@0.9.1      # older dsh (0.5.0 line, unmaintained)
 ```
 
 Then restart the web app.
@@ -151,7 +151,7 @@ When your deployment's dsh shell mounts the web capability (`@deepseek-ai/dsh-we
 - **Image input is model-gated** — only Vision models accept images; text-only models refuse them.
 - Switching to a text-only model in an image-bearing session is rejected by dsh — pick a model marked *`Image`* or remove the images first.
 - **No `stop` sequences** — requests carrying one fail.
-- Reasoning blocks are not replayed into later turns; only tool calls with a paired tool result are replayed.
+- On the legacy `/alpha/generate` transport, reasoning blocks are not replayed into later turns; on the `/provider/v1/chat/completions` transport, historical reasoning is passed back as `reasoning_content` so tool-calling loops can keep their chain of thought. Only tool calls with a paired tool result are replayed on both transports.
 - The model catalog is browsable without a key; chat requests need one.
 
 ## Permissions & privacy

package/README.zh-CN.md

@@ -32,19 +32,19 @@
 
 按你的 DeepSeek Harness 版本选择对应的发布线：
 
-- **dsh 0.1.2-alpha.2 或更高版本**（当前 alpha 线）——使用配套的 alpha 插件版本，显式用 `alpha` tag 安装：
+- **dsh 0.1.2-rc.1 或更高版本**（当前 0.1.2 线，即 `@latest` 现在安装的版本）：
 
   ```sh
-  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@alpha
+  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest
   ```
 
-- **更早的 dsh 版本**（0.5.0 线及更早，使用 rc 时代的 Host/浏览器 API）——0.9.1 插件在这些版本上继续可用，并保持在 `latest` tag：
+- **更早的 dsh 版本**（0.5.0 线及更早，使用 rc 时代的 Host/浏览器 API）——支持它们的最后一个插件版本是 0.9.1，按精确版本安装。该线不再积极维护：
 
   ```sh
-  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest
+  dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@0.9.1
   ```
 
-> `alpha` tag 永远不会移动 `latest`：普通的 `@latest` 安装始终为旧版 dsh 拿到最新的稳定版，升级到 alpha 线永远是显式选择。
+> `latest` tag 现在始终指向当前 0.1.2 线的插件版本，普通 `@latest` 安装即可获得 dsh 0.1.2+ 的最新稳定版。旧 0.5.0 时代的 Harness 用户必须显式钉住 `@0.9.1`。
 
 插件可直接在 pnpm 10 的全新插件市场 generation 中安装。不要另行添加 `@deepseek-ai/dsh-invariants` dependency；插件已将其声明为 Host peer，Harness 包仍由当前 dsh profile 统一管理。
 
@@ -53,8 +53,8 @@
 用与安装时相同的 tag 更新：
 
 ```sh
-dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@alpha      # dsh 0.1.2-alpha.2 及以上
-dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@latest     # 更早的 dsh（0.5.0 线）
+dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@latest     # dsh 0.1.2-rc.1 及以上
+dsh plugin --profile web update @mars-sea/dsh-commandcode-provider@0.9.1      # 更早的 dsh（0.5.0 线，不再维护）
 ```
 
 然后重启 Web 应用。
@@ -149,7 +149,7 @@ llm-commandcode:
 - **图片输入按模型能力限制**：仅 Vision 模型接受图片，纯文本模型会直接拒绝。
 - 含图片的会话切换到纯文本模型会被 dsh 拒绝——请改选带 *`Image`* 标记的模型，或先移除图片。
 - **不支持 `stop` 序列**：携带它的请求会报错。
-- 推理块不会重放到后续轮次；只有带配对工具结果的工具调用会被重放。
+- 在旧版 `/alpha/generate` 传输中，推理块不会重放到后续轮次；在 `/provider/v1/chat/completions` 传输中，历史推理会以 `reasoning_content` 回传，以便工具调用循环保留思维链。两种传输都只重放带配对工具结果的工具调用。
 - 模型目录无需 key 即可浏览；对话请求需要 key。
 
 ## 权限与隐私

package/lib/client.js

@@ -1736,7 +1736,7 @@ window.__ModuleLoader__.load({
 		}
 		//#endregion
 		//#region package.json
-		var version = "0.10.0-alpha.7";
+		var version = "0.10.1";
 		var repository = {
 			"type": "git",
 			"url": "git+https://github.com/Mars-Sea/dsh-commandcode-provider.git"