@mars-sea/dsh-commandcode-provider 0.16.1 → 0.16.3

package/CHANGELOG.md

@@ -4,6 +4,23 @@ All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.16.3] - 2026-10-31
+
+### Changed
+
+- **同步 Command Code CLI `1.88.1` → `1.88.2`（纯请求头同步）。** npm `latest` 于 `2026-10-29T02:05Z` 前进到 `1.88.2`。CLI 的变更日志在 npm 包内 `CHANGELOG.md`（官网 `/changelog` 只覆盖 Desktop 应用），该版本只有一条 patch：「修复全新安装或更新后启动崩溃」。产物级比对：包内 80 个文件只有 `CHANGELOG.md`、`dist/cli.mjs`、`package.json`（仅版本号）与 VSIX 变化，依赖零变化；请求路径（193）、自定义请求头（13）、环境变量（48）集合相同，`/alpha/generate` 调用点在屏蔽混淆标识符后相似度 1.0，`promptCache`（5）／`reasoning_effort`（7）／`max_tokens`（12）／`cache_control`（1）计数相同，审计 `cliDiff`（模型、档位、订阅、ZDR 例外集）为空。服务端目录未动（`?view=client` 的 `catalogVersion` 仍 `7f405e24…`，默认 94、client 106 行），所有能力快照零变化，`COMMAND_CODE_CLI_VERSION` 只随请求头更新，运行时行为不变。
+- **同步定价页两条模型额度（`planAllowanceUsd`）。** 官网把 DeepSeek V4.1 Flash 与 GLM-5.3 Flash 的加成月度额度从 GOAT `$80`／Pro `$90` 上调到 GOAT `$100`／Pro `$110`（Go `$10` 不变），per-token 价格、Peak 时段与套餐可用性均未变；设置页「模型额度」随之显示新值。价格表由 `node scripts/sync-model-prices.mjs` 重新生成，全表只有这两行变化。GLM-5.3 Flash 仍标注 `while capacity lasts`；V4.1 Flash 的文案从「with no end date」改为「comes with bigger monthly credits」，官方未给结束时间，若之后回调按同一脚本再同步。**验证**：`typecheck` 退出码 0，`npm test` 1142／1142，`build` 两段 `Build complete`；未做真实账号登录与付费生成验证。
+
+### Fixed
+
+- **探活丢路径前缀、断连与保存失败提示不可诊断（#111、#110）。** 探活原先用 `new URL('/', apiBase)` 探 API base 根，会丢掉带路径前缀的反向代理前缀（如 `http://127.0.0.1:18797/bili/https://api.commandcode.ai`），状态行必然误报「本机无法连接」；现在改探真实端点 `${apiBase}/alpha/whoami` 并用与真实请求相同的字符串拼接保留前缀，未认证的 401/403 计为「可达」（探活刻意不带凭据），404/429/5xx 仍判异常，超时与传输失败继续分开。用量报告的每条端点失败在原文后追加中文原因与目标 `scheme://host:port`（映射 fetch `error.cause` 的 `ECONNREFUSED`／`ENOTFOUND`／连接超时等，原始错误码入括号），反代换端口、代理未启动与 API 故障因此可区分。设置保存的「配置提交未获确认」不再固定说「密钥未写入」：只有本次提交带密钥时才提密钥，否则只报配置未写入；宿主拒绝的原文（如 profile 写锁超时）以「宿主返回：…」附在提示后，折叠为一行并限长 240 字符。**验证**：`typecheck` 退出码 0，`npm test` 1153／1153，`build` 两段 `Build complete`；另在隔离 `DSH_HOME` + 真实宿主（`dsh 0.2.2-alpha.2`）+ 带路径前缀反代 + 无头 Chrome 下端到端复现：反代在线时状态行「本机 连通正常 · 781 ms」（旧探测目标反代根 `/` 返回 404），停反代后「本机无法连接」且失败详情带目标与 `ECONNREFUSED`，写锁超时保存提示带宿主原文；再用真实密钥复验：只读接口全部 200、状态行「连通正常」、真实生成 `POST /alpha/generate` 返回 200（会话费用 `≈$0.0015` 与上游扣减 `0.001471284` 一致）；最后复验浏览器登录链路：隔离宿主用凭据库中不存在的引用起步（界面「未配置」），点「网页登录」后按 Studio 回调契约提交真实密钥，回调 `200 {"success":true}`、校验请求经反代 `/alpha/whoami` 200、凭据落库且界面转为「已登录为 mars-sea」。Studio 页面本身的账号登录与 Cloudflare 挑战需真人完成，不在自动验证范围内。
+
+## [0.16.2] - 2026-10-30
+
+### Changed
+
+- **补入 DSH `0.2.1-rc.5` 兼容记录（无代码改动）。** npm `latest` 与 `next` 从 `0.2.1-rc.4` 前进到 `0.2.1-rc.5`，发布说明只有一条社区改进「优化对话中思考内容的展示」。源码 delta 采集到 368 个变更路径、349 份包清单（错误为空）：包清单只有版本号变化，依赖与 peer 区间零变化；19 个非清单文件集中在推理展示——`client/ui-chat` 新增 `reasoning-text.ts` 并给 `conversation.chat.reasoning.body` 的 owner props 加上 `rawText`、`text` 改为显示文本，`experimental/client-ui-cot-translation` 跟随适配，其余是 slot 目录与测试/文档。**破坏面只在该推理插槽，插件不使用它**；插件导入的 16 个宿主包仅版本号变化，`ui-primitives` 的 `Switch` 未变。`dsh.compatibility.dshReleases` 补入 `0.2.1-rc.5`，引擎矩阵 5/5 通过；准入区间不变，用户升级到 rc.5 无需更新插件。
+
 ## [0.16.1] - 2026-10-30
 
 ### Changed

package/README.md

@@ -18,8 +18,8 @@ Unofficial [DeepSeek Harness](https://deepseek-harness.github.io/deepseek-harnes
 
 | | |
 |---|---|
-| Verified engines | dsh `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.2-alpha.2` |
-| Node.js | **`>=24.9`** — raised from 22 in this release, see [Node.js 24.9 or newer](#nodejs-249-or-newer-is-required) |
+| Verified engines | dsh `0.2.1-rc.2`, `0.2.1-rc.3`, `0.2.1-rc.4`, `0.2.1-rc.5`, `0.2.2-alpha.2` |
+| Node.js | **`>=24.9`** — raised from 22 in 0.16.0, see [Node.js 24.9 or newer](#nodejs-249-or-newer-is-required) |
 | Install — web | `dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest` |
 | Install — terminal | `dsh plugin --profile dsh-tui add @mars-sea/dsh-commandcode-provider@latest` |
 | Config file | `$DSH_HOME/settings.yaml` → `llm-commandcode:` |
@@ -62,11 +62,11 @@ Unofficial [DeepSeek Harness](https://deepseek-harness.github.io/deepseek-harnes
 dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest
 ```
 
-This build admits **dsh `>=0.2.1-rc.2 <0.2.2-0`** — every RC of the `0.2.1` channel from `0.2.1-rc.2` onward — **and `>=0.2.2-alpha.2 <0.2.3-0`**, the `0.2.2` channel from its current alpha. `0.2.1-rc.2` is what npm `latest` runs, `0.2.1-rc.4` ships on `next`, and `0.2.2-alpha.2` is on `alpha`. All four are covered by the full engine matrix (`npm run test:engine`, `npm run test:install`). A later release of either channel is admitted without a plugin update, but stays unverified until a record is added to `dsh.compatibility.dshReleases`. `0.2.3` and later are deliberately excluded — the upper bounds are written `<0.2.2-0` / `<0.2.3-0` for exactly that reason. A profile on `0.2.0-rc.2`, `0.2.1-alpha.5` or older must upgrade its engine first. Compatibility details — the `engines.dsh` admission rule, package pairings, evidence — live in [engine compatibility](docs/agent-reference/engine-compatibility.md).
+This build admits **dsh `>=0.2.1-rc.2 <0.2.2-0`** — every RC of the `0.2.1` channel from `0.2.1-rc.2` onward — **and `>=0.2.2-alpha.2 <0.2.3-0`**, the `0.2.2` channel from its current alpha. `0.2.1-rc.5` is what npm `latest` and `next` run, and `0.2.2-alpha.2` is on `alpha`. All five are covered by the full engine matrix (`npm run test:engine`, `npm run test:install`). A later release of either channel is admitted without a plugin update, but stays unverified until a record is added to `dsh.compatibility.dshReleases`. `0.2.3` and later are deliberately excluded — the upper bounds are written `<0.2.2-0` / `<0.2.3-0` for exactly that reason. A profile on `0.2.0-rc.2`, `0.2.1-alpha.5` or older must upgrade its engine first. Compatibility details — the `engines.dsh` admission rule, package pairings, evidence — live in [engine compatibility](docs/agent-reference/engine-compatibility.md).
 
 ### Node.js 24.9 or newer is required
 
-**This release raises the Node.js floor from 22 to 24.9. On Node 22 or 23, upgrade Node before updating this plugin.**
+**The Node.js floor was raised from 22 to 24.9 in 0.16.0. On Node 22 or 23, upgrade Node before updating this plugin.**
 
 dsh `0.2.2-alpha.2` declares `engines.node >=24.9.0` and this plugin admits that engine, so the package-wide floor had to follow: a plugin that claims to support an engine must not be installable on a Node version that engine cannot start on. What that means in practice:
 

package/README.zh-CN.md

@@ -18,8 +18,8 @@
 
 | | |
 |---|---|
-| 已验证引擎 | dsh `0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.2-alpha.2` |
-| Node.js | **`>=24.9`** —— 本版从 22 提高，见[需要 Node.js 24.9 或更高版本](#需要-nodejs-249-或更高版本) |
+| 已验证引擎 | dsh `0.2.1-rc.2`、`0.2.1-rc.3`、`0.2.1-rc.4`、`0.2.1-rc.5`、`0.2.2-alpha.2` |
+| Node.js | **`>=24.9`** —— 0.16.0 起从 22 提高，见[需要 Node.js 24.9 或更高版本](#需要-nodejs-249-或更高版本) |
 | 安装 —— 网页端 | `dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest` |
 | 安装 —— 终端端 | `dsh plugin --profile dsh-tui add @mars-sea/dsh-commandcode-provider@latest` |
 | 配置文件 | `$DSH_HOME/settings.yaml` → `llm-commandcode:` |
@@ -62,11 +62,11 @@
 dsh plugin --profile web add @mars-sea/dsh-commandcode-provider@latest
 ```
 
-本构建准入 **dsh `>=0.2.1-rc.2 <0.2.2-0`** —— `0.2.1` 通道中 `0.2.1-rc.2` 及以后的每个 RC —— **以及 `>=0.2.2-alpha.2 <0.2.3-0`**，即 `0.2.2` 通道从当前 alpha 起的每个版本。`0.2.1-rc.2` 是 npm `latest` 指向的版本，`0.2.1-rc.4` 挂在 `next`，`0.2.2-alpha.2` 挂在 `alpha`；这四个版本都跑过完整引擎矩阵（`npm run test:engine`、`npm run test:install`）。两个通道中更晚的版本无需更新插件即可准入，但在 `dsh.compatibility.dshReleases` 补上记录之前不算已验证。`0.2.3` 及以后被刻意排除 —— 两个区间上界分别写成 `<0.2.2-0` 与 `<0.2.3-0` 正是为了这一点。使用 `0.2.0-rc.2`、`0.2.1-alpha.5` 或更早版本的配置需先升级引擎，再安装本构建。兼容性细节 —— `engines.dsh` 准入规则、按引擎配对的包版本、验证证据 —— 见[引擎兼容](docs/agent-reference/engine-compatibility.md)。
+本构建准入 **dsh `>=0.2.1-rc.2 <0.2.2-0`** —— `0.2.1` 通道中 `0.2.1-rc.2` 及以后的每个 RC —— **以及 `>=0.2.2-alpha.2 <0.2.3-0`**，即 `0.2.2` 通道从当前 alpha 起的每个版本。`0.2.1-rc.5` 是 npm `latest` 与 `next` 指向的版本，`0.2.2-alpha.2` 挂在 `alpha`；这五个版本都跑过完整引擎矩阵（`npm run test:engine`、`npm run test:install`）。两个通道中更晚的版本无需更新插件即可准入，但在 `dsh.compatibility.dshReleases` 补上记录之前不算已验证。`0.2.3` 及以后被刻意排除 —— 两个区间上界分别写成 `<0.2.2-0` 与 `<0.2.3-0` 正是为了这一点。使用 `0.2.0-rc.2`、`0.2.1-alpha.5` 或更早版本的配置需先升级引擎，再安装本构建。兼容性细节 —— `engines.dsh` 准入规则、按引擎配对的包版本、验证证据 —— 见[引擎兼容](docs/agent-reference/engine-compatibility.md)。
 
 ### 需要 Node.js 24.9 或更高版本
 
-**本版把 Node.js 下界从 22 提到 24.9。如果你在用 Node 22 或 23，请先升级 Node，再更新本插件。**
+**Node.js 下界已在 0.16.0 从 22 提到 24.9。如果你在用 Node 22 或 23，请先升级 Node，再更新本插件。**
 
 dsh `0.2.2-alpha.2` 自己声明 `engines.node >=24.9.0`，而本插件准入这个引擎，所以整包的 Node 下界必须跟着抬到同一水位：一个声称支持某引擎的插件，不该能被装到一个那个引擎根本起不来的 Node 上。实际影响：
 

package/lib/client.js

@@ -76,6 +76,13 @@ window.__ModuleLoader__.load({
 		}
 		//#endregion
 		//#region src/client/settings-scope.ts
+		/** 组装报告；没有原文时不带 `message` 键（`exactOptionalPropertyTypes`）。 */
+		function mutationReport(result, message) {
+			return message === void 0 ? { result } : {
+				result,
+				message
+			};
+		}
 		/**
 		* Backoff before re-reading a directory whose FIRST read failed, in millis.
 		*
@@ -328,19 +335,20 @@ window.__ModuleLoader__.load({
 					const response = await this.mutateRemote(ownedOps, revision);
 					if (!response.ok) {
 						await this.recover(generation);
-						return response.error?.message?.includes("SETTINGS_CONFLICT") ? "conflict" : "failed";
+						const message = response.error?.message;
+						return message?.includes("SETTINGS_CONFLICT") ? mutationReport("conflict", message) : mutationReport("failed", message);
 					}
 					const row = response.value;
 					if (row?.ns !== this.namespace || decodeRow(row.value) === void 0 || typeof row.revision !== "number") {
 						await this.recover(generation);
-						return "failed";
+						return mutationReport("failed");
 					}
-					if (this.disposed) return "accepted";
+					if (this.disposed) return mutationReport("accepted");
 					if (generation === this.writeGeneration) {
 						this.pendingRevision = void 0;
 						this.mirror.acceptView(row);
 					} else this.pendingRevision = typeof row.revision === "number" ? row.revision : void 0;
-					return "accepted";
+					return mutationReport("accepted");
 				});
 			}
 			async mutateRemote(ops, revision) {
@@ -406,9 +414,9 @@ window.__ModuleLoader__.load({
 			}
 			/** Queue operations one at a time; disposal makes the queue inert. */
 			enqueue(operation) {
-				if (this.disposed) return Promise.resolve("cancelled");
+				if (this.disposed) return Promise.resolve(mutationReport("cancelled"));
 				const task = this.tail.then(async () => {
-					if (this.disposed) return "cancelled";
+					if (this.disposed) return mutationReport("cancelled");
 					return operation();
 				});
 				this.tail = task.then(() => {}, () => {});
@@ -780,22 +788,26 @@ window.__ModuleLoader__.load({
 				return success;
 			}
 			async commit(ops, baseline) {
-				if (this.closed) return "cancelled";
+				if (this.closed) return { result: "cancelled" };
 				const snapshot = this.scope.getSnapshot();
-				if (!snapshot.writable || this.scope.mutate === void 0) return "failed";
-				if (baseline && [...baseline].some(([field, before]) => !sameValue(before, fieldBaseline(snapshot, field)))) return "conflict";
+				if (!snapshot.writable || this.scope.mutate === void 0) return { result: "failed" };
+				if (baseline && [...baseline].some(([field, before]) => !sameValue(before, fieldBaseline(snapshot, field)))) return { result: "conflict" };
 				try {
 					return await this.scope.mutate(ops, snapshot.revision);
-				} catch {
-					return "failed";
+				} catch (error) {
+					return {
+						result: "failed",
+						message: readableErrorText(error)
+					};
 				}
 			}
 			async configure(outcome, ops, baseline) {
 				if (ops.length === 0) return true;
 				const confirmation = await this.commit(ops, baseline);
-				outcome.config = confirmation === "accepted" ? "confirmed" : confirmation === "conflict" ? "conflict" : "unconfirmed";
-				if (confirmation === "cancelled" || this.closed) outcome.issue = "closed";
-				return confirmation === "accepted" && !this.closed;
+				outcome.config = confirmation.result === "accepted" ? "confirmed" : confirmation.result === "conflict" ? "conflict" : "unconfirmed";
+				if (confirmation.result === "failed" && confirmation.message !== void 0) outcome.hostError = confirmation.message;
+				if (confirmation.result === "cancelled" || this.closed) outcome.issue = "closed";
+				return confirmation.result === "accepted" && !this.closed;
 			}
 			async changeCredential(outcome, ref, value, defaultRef) {
 				outcome.credential = "not-issued";
@@ -963,9 +975,15 @@ window.__ModuleLoader__.load({
 					path: ["credentialCleanupRefs"],
 					value: this.cleanupRefs().filter((entry) => entry !== ref)
 				}])) {
-					if (outcome.config === "none") outcome.config = cleanup.config;
+					if (outcome.config === "none") {
+						outcome.config = cleanup.config;
+						if (cleanup.hostError !== void 0) outcome.hostError = cleanup.hostError;
+					}
 					outcome.issue = cleanup.issue ?? "cleanup-pending";
-				} else if (outcome.config === "none") outcome.config = cleanup.config;
+				} else if (outcome.config === "none") {
+					outcome.config = cleanup.config;
+					if (cleanup.hostError !== void 0) outcome.hostError = cleanup.hostError;
+				}
 			}
 		};
 		//#endregion
@@ -3243,7 +3261,9 @@ window.__ModuleLoader__.load({
 			saved: "设置已保存",
 			saveFailed: "保存失败，请重试。",
 			writeConflict: "待提交字段已被其他操作修改，配置未写入；请核对后再保存。",
-			writeConfigUnconfirmed: "配置提交未获确认；密钥未写入，请核对宿主状态后重试。",
+			writeConfigUnconfirmed: "配置提交未获确认，未写入宿主；请核对后重试。",
+			writeConfigUnconfirmedKey: "配置与密钥均未写入宿主；请核对后重试。",
+			writeHostError: "宿主返回：{message}",
 			writeConfigSaved: "配置已保存。",
 			writeKeyNotIssued: "密钥操作尚未发出；请核对后重试。",
 			writeKeyUnconfirmed: "密钥操作未获确认；请核对后手动重试。",
@@ -3514,7 +3534,9 @@ window.__ModuleLoader__.load({
 			saved: "Settings saved",
 			saveFailed: "Save failed, please retry.",
 			writeConflict: "Pending fields were modified by another operation; the configuration was not written. Please review and save again.",
-			writeConfigUnconfirmed: "The configuration submission was not confirmed; the key was not written. Please check the host state and retry.",
+			writeConfigUnconfirmed: "The configuration submission was not confirmed and was not written. Please review and retry.",
+			writeConfigUnconfirmedKey: "Neither the configuration nor the key was written. Please review and retry.",
+			writeHostError: "Host returned: {message}",
 			writeConfigSaved: "Configuration saved.",
 			writeKeyNotIssued: "The key operation has not been issued; please review and retry.",
 			writeKeyUnconfirmed: "The key operation was not confirmed; please review and retry manually.",
@@ -3699,7 +3721,7 @@ window.__ModuleLoader__.load({
 			else if (result.issue === "target-changed") key = result.credential === "not-issued" ? "writeTargetBefore" : "writeTargetAfter";
 			else if (result.issue === "cleanup-pending") key = "writeCleanupPending";
 			else if (result.config === "conflict") key = "writeConflict";
-			else if (result.config === "unconfirmed") key = "writeConfigUnconfirmed";
+			else if (result.config === "unconfirmed") key = result.credential === "not-issued" ? "writeConfigUnconfirmedKey" : "writeConfigUnconfirmed";
 			else if (result.credential === "unconfirmed") key = "writeKeyUnconfirmed";
 			else if (result.credential === "not-issued") key = "writeKeyNotIssued";
 			const messages = key ? [t(key)] : [];
@@ -3709,8 +3731,18 @@ window.__ModuleLoader__.load({
 			}
 			if (key && result.config === "confirmed" && result.issue !== "cleanup-pending") messages.unshift(t("writeConfigSaved"));
 			if (result.refreshFailed) messages.push(t("writeRefreshFailed"));
+			const hostError = result.hostError;
+			if (hostError !== void 0 && hostError.trim() !== "") messages.push(t("writeHostError").replace("{message}", () => hostErrorText(hostError)));
 			return messages.join(" ");
 		}
+		/**
+		* 宿主原文压成一行并限长：锁超时、写权限这类诊断足够；换行会撑高提示区，
+		* 超长正文（整页 HTML、大对象）也不该被原样铺到设置页上。
+		*/
+		function hostErrorText(message) {
+			const oneLine = message.replace(/\s+/g, " ").trim();
+			return oneLine.length > 240 ? `${oneLine.slice(0, 240)}…` : oneLine;
+		}
 		//#endregion
 		//#region src/plan-tiers.ts
 		/** Shared plan-tier presentation facts; safe to inline into the browser bundle. */
@@ -3864,7 +3896,7 @@ window.__ModuleLoader__.load({
 		}
 		//#endregion
 		//#region package.json
-		var version = "0.16.1";
+		var version = "0.16.3";
 		var repository = {
 			"type": "git",
 			"url": "git+https://github.com/Mars-Sea/dsh-commandcode-provider.git"

package/lib/index.d.ts

@@ -61,7 +61,7 @@ type CommandCodeProtocol = 'cli' | 'openai' | 'messages';
 declare const DEFAULT_MAX_OUTPUT_TOKENS = 131072;
 //#endregion
 //#region src/adapter.d.ts
-declare const COMMAND_CODE_CLI_VERSION = "1.88.1";
+declare const COMMAND_CODE_CLI_VERSION = "1.88.2";
 declare const DEFAULT_API_BASE = "https://api.commandcode.ai";
 /**
  * The output budget this bundle asks for, and the ceiling it will never exceed.
@@ -1232,7 +1232,7 @@ declare const KNOWN_THINKING_MODELS: ReadonlySet<string>;
  * `/docs/plans/max` and `/docs/resources/pricing-limits`). Each plan's model
  * list is a superset of the one below it: Go ⊂ GOAT ⊂ Pro ⊂ Provider/Max.
  * Models absent from every plan list (Claude Opus/Fable, Fugu Ultra) are
- * Provider-tier. Re-verified at command-code@1.88.1 (2026-10-28) against the
+ * Provider-tier. Re-verified at command-code@1.88.2 (2026-10-31) against the
  * live `?view=client` catalog: 106 ids, still a strict superset chain. Mistral
  * Large 4 (1.75.0) was the only addition at the 1.77.0 check; the 1.78.0/1.79.0 pair
  * added Claude Haiku 5.5 at Pro and the free Glyph Cluster preview at Go.

package/lib/index.js

@@ -123,7 +123,7 @@ const PLAN_ORDER = Object.fromEntries(PLAN_TIER_ORDER.map((tier, index) => [tier
 * subscription-plan labels, deals, and hourly (peak/off-peak) pricing.
 *
 * Everything here is synced from official sources — the command-code CLI
-* bundle's model table (`dist/cli.mjs`, re-verified at command-code@1.88.1), the
+* bundle's model table (`dist/cli.mjs`, re-verified at command-code@1.88.2), the
 * live model catalog (`GET /provider/v1/models?view=client`, the authority for
 * capability fields since 1.82.4), and the official plan/pricing/model docs; see
 * the dsh-commandcode-upstream skill for the extraction procedures. The
@@ -145,7 +145,11 @@ const PLAN_ORDER = Object.fromEntries(PLAN_TIER_ORDER.map((tier, index) => [tier
 * step and `$2/$7.5` beyond. The 2026-10-28 check moves the constant to 1.88.1,
 * whose registry now names both catalog-only rows (Kimi K3.1 Pro and GPT-6.1
 * Terra) with efforts and context identical to this snapshot, so no table
-* changes. Keeping the snapshot in its own module
+* changes. The 2026-10-31 check moves it to 1.88.2 — the npm package's own
+* CHANGELOG names its sole change as a launch-crash fix after a fresh install
+* or update — and again leaves every table here identical; that round's only
+* data change is two per-model allowances in ./model-prices.ts. Keeping the
+* snapshot in its own module
 * confines those frequent sync diffs here: src/adapter.ts holds only the stable
 * wire/runtime logic. The read helpers live here too, for the same reason.
 *
@@ -948,7 +952,7 @@ const MODEL_OUTPUT_TOKEN_LIMITS = /* @__PURE__ */ new Map([
 * `/docs/plans/max` and `/docs/resources/pricing-limits`). Each plan's model
 * list is a superset of the one below it: Go ⊂ GOAT ⊂ Pro ⊂ Provider/Max.
 * Models absent from every plan list (Claude Opus/Fable, Fugu Ultra) are
-* Provider-tier. Re-verified at command-code@1.88.1 (2026-10-28) against the
+* Provider-tier. Re-verified at command-code@1.88.2 (2026-10-31) against the
 * live `?view=client` catalog: 106 ids, still a strict superset chain. Mistral
 * Large 4 (1.75.0) was the only addition at the 1.77.0 check; the 1.78.0/1.79.0 pair
 * added Claude Haiku 5.5 at Pro and the free Glyph Cluster preview at Go.
@@ -1651,8 +1655,8 @@ const MODEL_PRICE_ROWS = [
 		],
 		allowance: {
 			go: 10,
-			goat: 80,
-			pro: 90
+			goat: 100,
+			pro: 110
 		}
 	},
 	{
@@ -1852,8 +1856,8 @@ const MODEL_PRICE_ROWS = [
 		],
 		allowance: {
 			go: 10,
-			goat: 80,
-			pro: 90
+			goat: 100,
+			pro: 110
 		}
 	},
 	{
@@ -3934,6 +3938,76 @@ function readableErrorText(error) {
 	}
 	return String(error);
 }
+//#endregion
+//#region src/transport-failure.ts
+/**
+* Transport failure reasons for the usage and settings diagnostics.
+*
+* Node's fetch rejects with `TypeError('fetch failed')` and keeps the real
+* cause one level down (`error.cause`): `ECONNREFUSED` when nothing listens on
+* the port, `ENOTFOUND` on DNS, a connect timeout behind a dead proxy. That
+* message alone cannot tell "the reverse proxy changed port" from "the proxy is
+* not running" from "the API is down", so per-endpoint failure lines and the
+* settings notice append a short Chinese reason plus the raw code (issue #111).
+*
+* Only the code is quoted back, never the system message: those may embed
+* internal paths, and the original message stays available through
+* `readableErrorText` for the detail line. An error with no code yields no
+* reason — the caller still renders what it has instead of an invented guess.
+*
+* @module dsh-commandcode-provider/transport-failure
+*/
+/** 原始错误码 → 界面原因；未列出的码只回显错误码，不做猜测。 */
+const REASONS$1 = {
+	ECONNREFUSED: "连接被拒绝",
+	ECONNRESET: "连接被重置",
+	ENOTFOUND: "域名解析失败",
+	EAI_AGAIN: "域名解析临时失败",
+	EHOSTUNREACH: "主机不可达",
+	ENETUNREACH: "网络不可达",
+	ETIMEDOUT: "连接超时",
+	UND_ERR_CONNECT_TIMEOUT: "连接超时",
+	UND_ERR_SOCKET: "连接中断",
+	UND_ERR_CLOSED: "连接已关闭",
+	CERT_HAS_EXPIRED: "证书已过期",
+	DEPTH_ZERO_SELF_SIGNED_CERT: "自签名证书不受信任",
+	SELF_SIGNED_CERT_IN_CHAIN: "证书链中有自签名证书",
+	UNABLE_TO_VERIFY_LEAF_SIGNATURE: "无法验证证书"
+};
+/** 取错误链上的第一个错误码：先看自身，再看 AggregateError 子项，最后看 cause。 */
+function codeOf(value, depth = 0) {
+	if (depth > 4 || value === null || typeof value !== "object") return void 0;
+	const entry = value;
+	if (typeof entry.code === "string" && entry.code !== "") return entry.code;
+	if (Array.isArray(entry.errors)) for (const nested of entry.errors) {
+		const code = codeOf(nested, depth + 1);
+		if (code !== void 0) return code;
+	}
+	return codeOf(entry.cause, depth + 1);
+}
+/**
+* One diagnostic clause for a transport failure, or undefined when the error
+* carries no recognizable code.
+*/
+function transportFailureReason(error) {
+	const code = codeOf(error);
+	if (code === void 0) return void 0;
+	const reason = REASONS$1[code];
+	return reason === void 0 ? `网络错误（${code}）` : `${reason}（${code}）`;
+}
+/**
+* `scheme://host:port` of a base, with path and query dropped: enough to name
+* the endpoint a failed request aimed at without echoing proxy prefixes, and
+* without any chance of a token riding along in a path.
+*/
+function httpOrigin(base) {
+	try {
+		const url = new URL(base);
+		return `${url.protocol}//${url.host}`;
+	} catch {
+		return;
+	}
+}
 const THROTTLED_CODE = "THROTTLED";
 const boundedCodes = /* @__PURE__ */ new Set([
 	"EMPTY_RESPONSE",
@@ -6535,7 +6609,7 @@ var GatewayFacts = class {
 * per-request options thunk and an API-key resolver from the plugin entry
 * (src/index.ts), so a settings change reaches the very next request.
 */
-const COMMAND_CODE_CLI_VERSION = "1.88.1";
+const COMMAND_CODE_CLI_VERSION = "1.88.2";
 const DEFAULT_API_BASE = "https://api.commandcode.ai";
 /**
 * The output budget this bundle asks for, and the ceiling it will never exceed.
@@ -8719,7 +8793,9 @@ var CommandCodeAdapter = class CommandCodeAdapter extends LlmAdapter {
 				}
 				return record;
 			} catch (error) {
-				failures.push(`${path}: ${readableErrorText(error)}`);
+				const reason = transportFailureReason(error);
+				const origin = httpOrigin(base);
+				failures.push(`${path}: ${readableErrorText(error)}${reason === void 0 ? "" : `；${reason}`}${origin === void 0 ? "" : `；目标 ${origin}`}`);
 				failed.push({ kind: "transport" });
 				return;
 			}
@@ -9923,13 +9999,18 @@ function applyUsageRemote(ctx, deps) {
 		remoteCtx.effect(() => () => void unregister(), "dsh-commandcode-provider: usage remote");
 	});
 }
+/** The endpoint whose answer proves the API's auth layer is reachable. */
+const PROBE_PATH = "/alpha/whoami";
 /**
-* HTTP statuses Upptime's default monitor accepts as `up` (from
-* `uptime-monitor`'s `expectedStatusCodes` fallback). Kept in sync with the
-* page's monitor rather than invented here: a 401 or 404 means the endpoint
-* answered but is not the surface the official check calls healthy.
+* HTTP statuses that prove the probed endpoint answered.
+*
+* 2xx/3xx are the positive answers. 401/403 belong here because the probe is
+* deliberately credential-less: the expected answer to an unauthenticated GET
+* of `/alpha/whoami` IS 401, and treating it as a failure would report every
+* healthy host as down. Everything else (404 from a wrong base path, 429, 5xx)
+* means the endpoint the plugin actually uses did not answer as a live API.
 */
-const UP_STATUSES = /* @__PURE__ */ new Set([
+const REACHABLE_STATUSES = /* @__PURE__ */ new Set([
 	200,
 	201,
 	202,
@@ -9948,25 +10029,27 @@ const UP_STATUSES = /* @__PURE__ */ new Set([
 	305,
 	306,
 	307,
-	308
+	308,
+	401,
+	403
 ]);
 /** Turn the response status into the outcome the row renders. */
 function probeOutcomeForStatus(status) {
-	return UP_STATUSES.has(status) ? "ok" : "http-error";
+	return REACHABLE_STATUSES.has(status) ? "ok" : "http-error";
 }
 /**
 * Probe the configured API base once. Never rejects: an invalid base, a
 * timeout and a transport failure all resolve to an outcome.
 *
-* `redirect: 'manual'` keeps the classification on the FIRST response, exactly
-* like the monitor's HTTP client; following a redirect would report the final
-* destination's status as if it were the API's own.
+* `redirect: 'manual'` keeps the classification on the FIRST response; the
+* probe reports what this Host reached, not where a redirect chain ends up.
 */
 async function probeCommandCode(options) {
 	const now = options.now ?? Date.now;
 	let url;
 	try {
-		url = new URL("/", options.apiBase).toString();
+		if (!URL.canParse(options.apiBase)) throw new TypeError("invalid api base");
+		url = `${options.apiBase}${PROBE_PATH}`;
 	} catch {
 		return {
 			outcome: "unreachable",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mars-sea/dsh-commandcode-provider",
-  "version": "0.16.1",
+  "version": "0.16.3",
   "description": "Unofficial DeepSeek Harness LLM provider plugin for Command Code, ported from pi-commandcode-provider (MIT). Registers the 'commandcode' provider route with a Models-page card and live model catalog.",
   "icon": "./icon.svg",
   "type": "module",
@@ -26,6 +26,7 @@
         "0.2.1-rc.2": "compatible",
         "0.2.1-rc.3": "compatible",
         "0.2.1-rc.4": "compatible",
+        "0.2.1-rc.5": "compatible",
         "0.2.2-alpha.2": "compatible"
       },
       "dsh": ">=0.2.1-rc.2 <0.2.2-0 || >=0.2.2-alpha.2 <0.2.3-0"