@mars-sea/dsh-commandcode-provider 0.12.4 → 0.12.6

package/CHANGELOG.md

@@ -4,6 +4,31 @@ 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.12.6] - 2026-10-07
+
+### Added
+
+- 同步官方 command-code@1.75.0 新增的 `mistral/mistral-large-4`（Mistral Large 4）：最低套餐 Go，支持视觉与推理，三档思考强度 `low`/`medium`/`high`，524 288 上下文；价格 $1.36 入 / $4.18 出 / $0.14 缓存读每 1M，月度额度 Go $10 / GOAT $40 / Pro $50（官方「启动价期间的额度提升」已折算在内）。该模型在公开目录、定价页与 CLI 注册表三处同步出现，各记 +1。
+
+### Changed
+
+- 同步官方 command-code@1.77.0：请求头 `x-command-code-version` 升至 `1.77.0`。1.75.0／1.75.1／1.76.0 的官方日志分别是「新增 Mistral Large 4」「hooks 跳过 stdin 与良性写错误不再让 CLI 崩溃」「`/peek` 任务回顾图」；1.77.0 没有 changelog 条目，逐行比对 1.76.0 → 1.77.0 的 `dist/cli.mjs` 后确认变化只落在 CLI 自己的命令行参数层（云会话转正、新增 `--base`、`cloud list/status/stop` 子命令、机器可读参数判定由子串包含改为精确匹配），协议面未动——142 个 API 路径与 13 个请求头集合完全一致，`toWireMessages`／`toWireTools`／`toWirePermissionMode` 的调用点数量与形态不变。
+- 两个既有模型的月度额度跟上官方定价页：`glm-5.3-flash` 的 GOAT/Pro 从 $40/$50 提到 $60/$70，`kimi-k3` 从 $20/$30 提到 $60/$70。这类数字来自定价页的 `planAllowanceUsd` 字段，不在上游审计脚本的提取范围内，本轮靠逐行对照 84 条额度记录才发现；对照后价格表与页面已逐条一致。
+
+### Removed
+
+- 零数据保留例外名单移除 `stealth/pixel-canary` 与 `stealth/space-bunny-alpha`（22 → 20 项）。1.77.0 的 CLI 不再把两者列入 ZDR 排除集合，并把它们放进 `listSelectableModelIds()` 过滤掉的不可选择集合，因此 `supportsZeroDataRetention()` 现在对这两个 id 回答 true，与当前 CLI 一致。这推翻了 0.12.5 那轮「刻意保留」的选择——当时的前提是 1.74.3 仍把它们列在两个锚点里，该前提已随 1.77.0 消失。
+
+## [0.12.5] - 2026-10-06
+
+### Changed
+
+- 同步官方 command-code@1.74.2／1.74.3：请求头 `x-command-code-version` 升至 `1.74.3`。两次发布都没有官方 changelog 条目，证据是 npm 发布时间线（1.74.2 于 2026-10-05T21:55Z、1.74.3 于 23:19Z）加 `dist/cli.mjs` 逐行比对：除打包变量改名与那两条隐身模型外，Effort 表、订阅计划、ZDR 锚点、峰时窗口、促销与协议面全部重核无变化。
+
+### Removed
+
+- 退役 `stealth/space-bunny-alpha` 的全部快照条目（思考档、Vision、最低套餐、免费促销）。官方 2026-10-06 结束该隐身预览：command-code@1.74.3 用 `hidden` 标记把它从模型选择器隐藏，`/provider/v1/models` 由 85 减为 84、定价页也已撤下，官方 Desktop 0.1.48 更新日志写明「Remove Space Bunny Alpha from the model picker」。它仍保留在零数据保留例外名单里——官方 CLI 的 ZDR 集合至今仍列着它，`supportsZeroDataRetention()` 对老会话里残留的 id 依然要说实话；模型输出上限表同样保留（该表由 models.dev 生成，手工删除只会与下次重新生成分叉）。
+
 ## [0.12.4] - 2026-10-04
 
 ### Changed

package/lib/client.js

@@ -3273,7 +3273,7 @@ window.__ModuleLoader__.load({
 		}
 		//#endregion
 		//#region package.json
-		var version = "0.12.4";
+		var version = "0.12.6";
 		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.74.1";
+declare const COMMAND_CODE_CLI_VERSION = "1.77.0";
 declare const DEFAULT_API_BASE = "https://api.commandcode.ai";
 /**
  * The output budget this bundle asks for, and the ceiling it will never exceed.
@@ -978,12 +978,12 @@ declare const KNOWN_EFFORTS: Readonly<Record<string, readonly string[]>>;
 declare const KNOWN_IMAGE_MODELS: ReadonlySet<string>;
 /**
  * Models WITHOUT a zero-data-retention upstream, per the official CLI's own
- * registry (`command-code@1.74.1` `dist/cli.mjs`): `modelSupportsZdr(id)` is
+ * registry (`command-code@1.77.0` `dist/cli.mjs`): `modelSupportsZdr(id)` is
  * exactly `!nonZdrSet.has(canonicalize(id))`, and `knownModelSupportsZdr`
  * carries the same membership in the sibling route table — the UNION of both
  * is this set. Reading only the sibling route table dropped
  * `meituan/LongCat-2.0`, which sat in `modelSupportsZdr` alone through
- * 1.73.0; the 1.74.1 table lists it in NEITHER set, so as of this snapshot it
+ * 1.73.0; the 1.74.3 table lists it in NEITHER set, so as of this snapshot it
  * is no longer excluded. The official docs (commandcode.ai/docs/resources/
  * zdr) put coverage in prose — "99% of our models have ZDR-capable upstreams … only
  * a small handful of models are affected" — so the CLI's exclusion list is
@@ -1007,15 +1007,19 @@ declare const KNOWN_IMAGE_MODELS: ReadonlySet<string>;
  * flags) is upstream-internal routing, not a per-model contract, so this table
  * is the snapshot of the exclusion set and nothing more. It is a rare change:
  * 20 members held across 1.62.0 → 1.64.0, 1.65.0 and 1.66.0 each added exactly
- * one (the two stealth-preview models below), 1.67.0 added one
+ * one (the two stealth-preview models), 1.67.0 added one
  * (`deepseek/deepseek-v4.1-flash-fast`), 1.68.0 changed nothing, and 1.74.1
- * removed one (`meituan/LongCat-2.0`) — 22 members as of 2026-10-03.
+ * removed one (`meituan/LongCat-2.0`). The 1.74.2/1.74.3 pair changed nothing
+ * here either (22 members as of 2026-10-06); 1.77.0 dropped the two retired
+ * stealth previews, back to 20 members as of 2026-10-07.
  *
- * `stealth/pixel-canary` is the one member whose model itself is retired (see
- * `KNOWN_EFFORTS`): the CLI keeps naming it in the ZDR anchors even though it
- * hides the row and dropped it from the catalog, so it stays listed here rather
- * than being pruned with the rest of the tables — `supportsZeroDataRetention`
- * stays truthful for any id a stale session still names.
+ * 1.77.0 also settled the two retired stealth previews (see `KNOWN_EFFORTS`):
+ * 1.74.3 still named both in the ZDR anchors, so they stayed listed here on
+ * purpose — an id a stale session named still got a truthful answer. The 1.77.0
+ * artifact names neither in its exclusion set and filters both out of
+ * `listSelectableModelIds()`, so they are pruned along with the rest of the
+ * tables and `supportsZeroDataRetention` now answers TRUE for them, matching
+ * what the current CLI says.
  */
 declare const KNOWN_NON_ZDR_MODELS: ReadonlySet<string>;
 /**
@@ -1045,9 +1049,11 @@ 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.73.0 (2026-10-01): 86 catalog
- * ids at 53/62/76/84 cumulative, a strict superset chain — every release since
- * 1.49.0 has been additive with no tier move, and per-entry tags below name the
+ * Provider-tier. Re-verified at command-code@1.77.0 (2026-10-07): 85 catalog
+ * ids at 53/62/76/84 cumulative, a strict superset chain. Mistral Large 4
+ * (1.75.0) is the only addition since the 1.74.3 check; the only removals since
+ * 1.49.0 are the two retired stealth previews (Pixel Canary at 1.73.1, Space
+ * Bunny Alpha at 1.74.3). No tier ever moved, and per-entry tags below name the
  * release that added each row.
  *
  * The Provider API exposes no plan metadata, so this snapshot is the source of

package/lib/index.js

@@ -103,7 +103,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.74.1) and
+* bundle's model table (`dist/cli.mjs`, re-verified at command-code@1.77.0) and
 * the official plan/pricing/model docs; see the dsh-commandcode-upstream skill
 * for the extraction procedures. Keeping the snapshot in its own module
 * confines those frequent sync diffs here: src/adapter.ts holds only the stable
@@ -413,12 +413,6 @@ const KNOWN_EFFORTS = {
 		"medium",
 		"high"
 	],
-	"stealth/space-bunny-alpha": [
-		"low",
-		"medium",
-		"high",
-		"max"
-	],
 	"gpt-6.1-sol": [
 		"low",
 		"medium",
@@ -430,6 +424,11 @@ const KNOWN_EFFORTS = {
 		"low",
 		"medium",
 		"high"
+	],
+	"mistral/mistral-large-4": [
+		"low",
+		"medium",
+		"high"
 	]
 };
 /**
@@ -492,13 +491,13 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
 	"meta/muse-spark-1.2-contributor",
 	"meta/muse-spark-1.3",
 	"meta/muse-spark-1.3-contributor",
+	"mistral/mistral-large-4",
 	"moonshotai/Kimi-K2.5",
 	"moonshotai/Kimi-K2.6",
 	"moonshotai/Kimi-K2.7-Code",
 	"moonshotai/Kimi-K2.7-Code-Highspeed",
 	"moonshotai/Kimi-K3",
 	"sakana/fugu-ultra",
-	"stealth/space-bunny-alpha",
 	"stepfun/Step-3.7-Flash",
 	"stepfun/Step-5-Preview",
 	"thinkingmachines/inkling",
@@ -515,12 +514,12 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
 ]);
 /**
 * Models WITHOUT a zero-data-retention upstream, per the official CLI's own
-* registry (`command-code@1.74.1` `dist/cli.mjs`): `modelSupportsZdr(id)` is
+* registry (`command-code@1.77.0` `dist/cli.mjs`): `modelSupportsZdr(id)` is
 * exactly `!nonZdrSet.has(canonicalize(id))`, and `knownModelSupportsZdr`
 * carries the same membership in the sibling route table — the UNION of both
 * is this set. Reading only the sibling route table dropped
 * `meituan/LongCat-2.0`, which sat in `modelSupportsZdr` alone through
-* 1.73.0; the 1.74.1 table lists it in NEITHER set, so as of this snapshot it
+* 1.73.0; the 1.74.3 table lists it in NEITHER set, so as of this snapshot it
 * is no longer excluded. The official docs (commandcode.ai/docs/resources/
 * zdr) put coverage in prose — "99% of our models have ZDR-capable upstreams … only
 * a small handful of models are affected" — so the CLI's exclusion list is
@@ -544,15 +543,19 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
 * flags) is upstream-internal routing, not a per-model contract, so this table
 * is the snapshot of the exclusion set and nothing more. It is a rare change:
 * 20 members held across 1.62.0 → 1.64.0, 1.65.0 and 1.66.0 each added exactly
-* one (the two stealth-preview models below), 1.67.0 added one
+* one (the two stealth-preview models), 1.67.0 added one
 * (`deepseek/deepseek-v4.1-flash-fast`), 1.68.0 changed nothing, and 1.74.1
-* removed one (`meituan/LongCat-2.0`) — 22 members as of 2026-10-03.
-*
-* `stealth/pixel-canary` is the one member whose model itself is retired (see
-* `KNOWN_EFFORTS`): the CLI keeps naming it in the ZDR anchors even though it
-* hides the row and dropped it from the catalog, so it stays listed here rather
-* than being pruned with the rest of the tables — `supportsZeroDataRetention`
-* stays truthful for any id a stale session still names.
+* removed one (`meituan/LongCat-2.0`). The 1.74.2/1.74.3 pair changed nothing
+* here either (22 members as of 2026-10-06); 1.77.0 dropped the two retired
+* stealth previews, back to 20 members as of 2026-10-07.
+*
+* 1.77.0 also settled the two retired stealth previews (see `KNOWN_EFFORTS`):
+* 1.74.3 still named both in the ZDR anchors, so they stayed listed here on
+* purpose — an id a stale session named still got a truthful answer. The 1.77.0
+* artifact names neither in its exclusion set and filters both out of
+* `listSelectableModelIds()`, so they are pruned along with the rest of the
+* tables and `supportsZeroDataRetention` now answers TRUE for them, matching
+* what the current CLI says.
 */
 const KNOWN_NON_ZDR_MODELS = /* @__PURE__ */ new Set([
 	"MiniMaxAI/MiniMax-M3",
@@ -566,8 +569,6 @@ const KNOWN_NON_ZDR_MODELS = /* @__PURE__ */ new Set([
 	"minimax/minimax-m3-free",
 	"poolside/laguna-s-2.1-free",
 	"sakana/fugu-ultra",
-	"stealth/space-bunny-alpha",
-	"stealth/pixel-canary",
 	"stepfun/Step-3.7-Flash",
 	"stepfun/Step-5-Preview",
 	"xai/grok-4.5",
@@ -787,9 +788,11 @@ 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.73.0 (2026-10-01): 86 catalog
-* ids at 53/62/76/84 cumulative, a strict superset chain — every release since
-* 1.49.0 has been additive with no tier move, and per-entry tags below name the
+* Provider-tier. Re-verified at command-code@1.77.0 (2026-10-07): 85 catalog
+* ids at 53/62/76/84 cumulative, a strict superset chain. Mistral Large 4
+* (1.75.0) is the only addition since the 1.74.3 check; the only removals since
+* 1.49.0 are the two retired stealth previews (Pixel Canary at 1.73.1, Space
+* Bunny Alpha at 1.74.3). No tier ever moved, and per-entry tags below name the
 * release that added each row.
 *
 * The Provider API exposes no plan metadata, so this snapshot is the source of
@@ -827,6 +830,7 @@ const KNOWN_PLANS = {
 	"inclusionai/ling-3.1-flash:free": "go",
 	"meta/muse-spark-1.2-contributor": "go",
 	"meta/muse-spark-1.3-contributor": "go",
+	"mistral/mistral-large-4": "go",
 	"moonshotai/Kimi-K2.5": "go",
 	"moonshotai/Kimi-K2.6": "go",
 	"moonshotai/Kimi-K2.7-Code": "go",
@@ -837,7 +841,6 @@ const KNOWN_PLANS = {
 	"stepfun/Step-3.5-Flash": "go",
 	"stepfun/Step-3.7-Flash": "go",
 	"stepfun/Step-5-Preview": "go",
-	"stealth/space-bunny-alpha": "go",
 	"tencent/hy3-paid": "go",
 	"tencent/hy4-preview": "go",
 	"thinkingmachines/inkling": "go",
@@ -1033,10 +1036,6 @@ const KNOWN_DEALS = {
 	"inclusionai/ling-3.1-flash:free": {
 		label: "FREE",
 		free: true
-	},
-	"stealth/space-bunny-alpha": {
-		label: "FREE",
-		free: true
 	}
 };
 /**
@@ -1634,8 +1633,8 @@ const MODEL_PRICE_ROWS = [
 		],
 		allowance: {
 			go: 10,
-			goat: 40,
-			pro: 50
+			goat: 60,
+			pro: 70
 		}
 	},
 	{
@@ -2053,8 +2052,8 @@ const MODEL_PRICE_ROWS = [
 		],
 		allowance: {
 			go: 8,
-			goat: 20,
-			pro: 30
+			goat: 60,
+			pro: 70
 		}
 	},
 	{
@@ -2189,6 +2188,19 @@ const MODEL_PRICE_ROWS = [
 			pro: 57
 		}
 	},
+	{
+		id: "mistral-large-4",
+		rates: [
+			1.36,
+			4.18,
+			.14
+		],
+		allowance: {
+			go: 10,
+			goat: 40,
+			pro: 50
+		}
+	},
 	{
 		id: "muse-spark-1.1",
 		rates: [
@@ -5264,7 +5276,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.74.1";
+const COMMAND_CODE_CLI_VERSION = "1.77.0";
 const DEFAULT_API_BASE = "https://api.commandcode.ai";
 /**
 * The output budget this bundle asks for, and the ceiling it will never exceed.