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

package/CHANGELOG.md

@@ -4,6 +4,16 @@ 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.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.5";
 		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.74.3";
 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.74.3` `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
@@ -1009,13 +1009,15 @@ declare const KNOWN_IMAGE_MODELS: ReadonlySet<string>;
  * 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
  * (`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.
  *
- * `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.
+ * `stealth/pixel-canary` and `stealth/space-bunny-alpha` are the members whose
+ * models themselves are retired (see `KNOWN_EFFORTS`): the CLI keeps naming both
+ * in the ZDR anchors even though it hides their rows and dropped them from the
+ * catalog, so they stay listed here rather than being pruned with the rest of
+ * the tables — `supportsZeroDataRetention` stays truthful for any id a stale
+ * session still names.
  */
 declare const KNOWN_NON_ZDR_MODELS: ReadonlySet<string>;
 /**
@@ -1045,10 +1047,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
- * release that added each row.
+ * Provider-tier. Re-verified at command-code@1.74.3 (2026-10-06): 84 catalog
+ * ids at 52/61/75/83 cumulative, a strict superset chain — 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
  * truth for the picker's plan annotation — it answers "which plan do I need to

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.74.3) 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",
@@ -498,7 +492,6 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
 	"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 +508,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.74.3` `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
@@ -546,13 +539,15 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
 * 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
 * (`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.
 *
-* `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.
+* `stealth/pixel-canary` and `stealth/space-bunny-alpha` are the members whose
+* models themselves are retired (see `KNOWN_EFFORTS`): the CLI keeps naming both
+* in the ZDR anchors even though it hides their rows and dropped them from the
+* catalog, so they stay listed here rather than being pruned with the rest of
+* the tables — `supportsZeroDataRetention` stays truthful for any id a stale
+* session still names.
 */
 const KNOWN_NON_ZDR_MODELS = /* @__PURE__ */ new Set([
 	"MiniMaxAI/MiniMax-M3",
@@ -787,10 +782,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
-* release that added each row.
+* Provider-tier. Re-verified at command-code@1.74.3 (2026-10-06): 84 catalog
+* ids at 52/61/75/83 cumulative, a strict superset chain — 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
 * truth for the picker's plan annotation — it answers "which plan do I need to
@@ -837,7 +833,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 +1028,6 @@ const KNOWN_DEALS = {
 	"inclusionai/ling-3.1-flash:free": {
 		label: "FREE",
 		free: true
-	},
-	"stealth/space-bunny-alpha": {
-		label: "FREE",
-		free: true
 	}
 };
 /**
@@ -5264,7 +5255,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.74.3";
 const DEFAULT_API_BASE = "https://api.commandcode.ai";
 /**
 * The output budget this bundle asks for, and the ceiling it will never exceed.