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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/lib/index.d.ts CHANGED
@@ -61,7 +61,7 @@ type CommandCodeProtocol = 'cli' | 'openai' | 'messages';
61
61
  declare const DEFAULT_MAX_OUTPUT_TOKENS = 131072;
62
62
  //#endregion
63
63
  //#region src/adapter.d.ts
64
- declare const COMMAND_CODE_CLI_VERSION = "1.74.1";
64
+ declare const COMMAND_CODE_CLI_VERSION = "1.74.3";
65
65
  declare const DEFAULT_API_BASE = "https://api.commandcode.ai";
66
66
  /**
67
67
  * 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[]>>;
978
978
  declare const KNOWN_IMAGE_MODELS: ReadonlySet<string>;
979
979
  /**
980
980
  * Models WITHOUT a zero-data-retention upstream, per the official CLI's own
981
- * registry (`command-code@1.74.1` `dist/cli.mjs`): `modelSupportsZdr(id)` is
981
+ * registry (`command-code@1.74.3` `dist/cli.mjs`): `modelSupportsZdr(id)` is
982
982
  * exactly `!nonZdrSet.has(canonicalize(id))`, and `knownModelSupportsZdr`
983
983
  * carries the same membership in the sibling route table — the UNION of both
984
984
  * is this set. Reading only the sibling route table dropped
985
985
  * `meituan/LongCat-2.0`, which sat in `modelSupportsZdr` alone through
986
- * 1.73.0; the 1.74.1 table lists it in NEITHER set, so as of this snapshot it
986
+ * 1.73.0; the 1.74.3 table lists it in NEITHER set, so as of this snapshot it
987
987
  * is no longer excluded. The official docs (commandcode.ai/docs/resources/
988
988
  * zdr) put coverage in prose — "99% of our models have ZDR-capable upstreams … only
989
989
  * 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>;
1009
1009
  * 20 members held across 1.62.0 → 1.64.0, 1.65.0 and 1.66.0 each added exactly
1010
1010
  * one (the two stealth-preview models below), 1.67.0 added one
1011
1011
  * (`deepseek/deepseek-v4.1-flash-fast`), 1.68.0 changed nothing, and 1.74.1
1012
- * removed one (`meituan/LongCat-2.0`) — 22 members as of 2026-10-03.
1012
+ * removed one (`meituan/LongCat-2.0`). The 1.74.2/1.74.3 pair changed nothing
1013
+ * here either — 22 members as of 2026-10-06.
1013
1014
  *
1014
- * `stealth/pixel-canary` is the one member whose model itself is retired (see
1015
- * `KNOWN_EFFORTS`): the CLI keeps naming it in the ZDR anchors even though it
1016
- * hides the row and dropped it from the catalog, so it stays listed here rather
1017
- * than being pruned with the rest of the tables — `supportsZeroDataRetention`
1018
- * stays truthful for any id a stale session still names.
1015
+ * `stealth/pixel-canary` and `stealth/space-bunny-alpha` are the members whose
1016
+ * models themselves are retired (see `KNOWN_EFFORTS`): the CLI keeps naming both
1017
+ * in the ZDR anchors even though it hides their rows and dropped them from the
1018
+ * catalog, so they stay listed here rather than being pruned with the rest of
1019
+ * the tables — `supportsZeroDataRetention` stays truthful for any id a stale
1020
+ * session still names.
1019
1021
  */
1020
1022
  declare const KNOWN_NON_ZDR_MODELS: ReadonlySet<string>;
1021
1023
  /**
@@ -1045,10 +1047,11 @@ declare const KNOWN_THINKING_MODELS: ReadonlySet<string>;
1045
1047
  * `/docs/plans/max` and `/docs/resources/pricing-limits`). Each plan's model
1046
1048
  * list is a superset of the one below it: Go ⊂ GOAT ⊂ Pro ⊂ Provider/Max.
1047
1049
  * Models absent from every plan list (Claude Opus/Fable, Fugu Ultra) are
1048
- * Provider-tier. Re-verified at command-code@1.73.0 (2026-10-01): 86 catalog
1049
- * ids at 53/62/76/84 cumulative, a strict superset chain — every release since
1050
- * 1.49.0 has been additive with no tier move, and per-entry tags below name the
1051
- * release that added each row.
1050
+ * Provider-tier. Re-verified at command-code@1.74.3 (2026-10-06): 84 catalog
1051
+ * ids at 52/61/75/83 cumulative, a strict superset chain — the only removals
1052
+ * since 1.49.0 are the two retired stealth previews (Pixel Canary at 1.73.1,
1053
+ * Space Bunny Alpha at 1.74.3), no tier ever moved, and per-entry tags below
1054
+ * name the release that added each row.
1052
1055
  *
1053
1056
  * The Provider API exposes no plan metadata, so this snapshot is the source of
1054
1057
  * truth for the picker's plan annotation — it answers "which plan do I need to
package/lib/index.js CHANGED
@@ -103,7 +103,7 @@ const PLAN_ORDER = Object.fromEntries(PLAN_TIER_ORDER.map((tier, index) => [tier
103
103
  * subscription-plan labels, deals, and hourly (peak/off-peak) pricing.
104
104
  *
105
105
  * Everything here is synced from official sources — the command-code CLI
106
- * bundle's model table (`dist/cli.mjs`, re-verified at command-code@1.74.1) and
106
+ * bundle's model table (`dist/cli.mjs`, re-verified at command-code@1.74.3) and
107
107
  * the official plan/pricing/model docs; see the dsh-commandcode-upstream skill
108
108
  * for the extraction procedures. Keeping the snapshot in its own module
109
109
  * confines those frequent sync diffs here: src/adapter.ts holds only the stable
@@ -413,12 +413,6 @@ const KNOWN_EFFORTS = {
413
413
  "medium",
414
414
  "high"
415
415
  ],
416
- "stealth/space-bunny-alpha": [
417
- "low",
418
- "medium",
419
- "high",
420
- "max"
421
- ],
422
416
  "gpt-6.1-sol": [
423
417
  "low",
424
418
  "medium",
@@ -498,7 +492,6 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
498
492
  "moonshotai/Kimi-K2.7-Code-Highspeed",
499
493
  "moonshotai/Kimi-K3",
500
494
  "sakana/fugu-ultra",
501
- "stealth/space-bunny-alpha",
502
495
  "stepfun/Step-3.7-Flash",
503
496
  "stepfun/Step-5-Preview",
504
497
  "thinkingmachines/inkling",
@@ -515,12 +508,12 @@ const KNOWN_IMAGE_MODELS = /* @__PURE__ */ new Set([
515
508
  ]);
516
509
  /**
517
510
  * Models WITHOUT a zero-data-retention upstream, per the official CLI's own
518
- * registry (`command-code@1.74.1` `dist/cli.mjs`): `modelSupportsZdr(id)` is
511
+ * registry (`command-code@1.74.3` `dist/cli.mjs`): `modelSupportsZdr(id)` is
519
512
  * exactly `!nonZdrSet.has(canonicalize(id))`, and `knownModelSupportsZdr`
520
513
  * carries the same membership in the sibling route table — the UNION of both
521
514
  * is this set. Reading only the sibling route table dropped
522
515
  * `meituan/LongCat-2.0`, which sat in `modelSupportsZdr` alone through
523
- * 1.73.0; the 1.74.1 table lists it in NEITHER set, so as of this snapshot it
516
+ * 1.73.0; the 1.74.3 table lists it in NEITHER set, so as of this snapshot it
524
517
  * is no longer excluded. The official docs (commandcode.ai/docs/resources/
525
518
  * zdr) put coverage in prose — "99% of our models have ZDR-capable upstreams … only
526
519
  * 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([
546
539
  * 20 members held across 1.62.0 → 1.64.0, 1.65.0 and 1.66.0 each added exactly
547
540
  * one (the two stealth-preview models below), 1.67.0 added one
548
541
  * (`deepseek/deepseek-v4.1-flash-fast`), 1.68.0 changed nothing, and 1.74.1
549
- * removed one (`meituan/LongCat-2.0`) — 22 members as of 2026-10-03.
542
+ * removed one (`meituan/LongCat-2.0`). The 1.74.2/1.74.3 pair changed nothing
543
+ * here either — 22 members as of 2026-10-06.
550
544
  *
551
- * `stealth/pixel-canary` is the one member whose model itself is retired (see
552
- * `KNOWN_EFFORTS`): the CLI keeps naming it in the ZDR anchors even though it
553
- * hides the row and dropped it from the catalog, so it stays listed here rather
554
- * than being pruned with the rest of the tables — `supportsZeroDataRetention`
555
- * stays truthful for any id a stale session still names.
545
+ * `stealth/pixel-canary` and `stealth/space-bunny-alpha` are the members whose
546
+ * models themselves are retired (see `KNOWN_EFFORTS`): the CLI keeps naming both
547
+ * in the ZDR anchors even though it hides their rows and dropped them from the
548
+ * catalog, so they stay listed here rather than being pruned with the rest of
549
+ * the tables — `supportsZeroDataRetention` stays truthful for any id a stale
550
+ * session still names.
556
551
  */
557
552
  const KNOWN_NON_ZDR_MODELS = /* @__PURE__ */ new Set([
558
553
  "MiniMaxAI/MiniMax-M3",
@@ -787,10 +782,11 @@ const MODEL_OUTPUT_TOKEN_LIMITS = /* @__PURE__ */ new Map([
787
782
  * `/docs/plans/max` and `/docs/resources/pricing-limits`). Each plan's model
788
783
  * list is a superset of the one below it: Go ⊂ GOAT ⊂ Pro ⊂ Provider/Max.
789
784
  * Models absent from every plan list (Claude Opus/Fable, Fugu Ultra) are
790
- * Provider-tier. Re-verified at command-code@1.73.0 (2026-10-01): 86 catalog
791
- * ids at 53/62/76/84 cumulative, a strict superset chain — every release since
792
- * 1.49.0 has been additive with no tier move, and per-entry tags below name the
793
- * release that added each row.
785
+ * Provider-tier. Re-verified at command-code@1.74.3 (2026-10-06): 84 catalog
786
+ * ids at 52/61/75/83 cumulative, a strict superset chain — the only removals
787
+ * since 1.49.0 are the two retired stealth previews (Pixel Canary at 1.73.1,
788
+ * Space Bunny Alpha at 1.74.3), no tier ever moved, and per-entry tags below
789
+ * name the release that added each row.
794
790
  *
795
791
  * The Provider API exposes no plan metadata, so this snapshot is the source of
796
792
  * truth for the picker's plan annotation — it answers "which plan do I need to
@@ -837,7 +833,6 @@ const KNOWN_PLANS = {
837
833
  "stepfun/Step-3.5-Flash": "go",
838
834
  "stepfun/Step-3.7-Flash": "go",
839
835
  "stepfun/Step-5-Preview": "go",
840
- "stealth/space-bunny-alpha": "go",
841
836
  "tencent/hy3-paid": "go",
842
837
  "tencent/hy4-preview": "go",
843
838
  "thinkingmachines/inkling": "go",
@@ -1033,10 +1028,6 @@ const KNOWN_DEALS = {
1033
1028
  "inclusionai/ling-3.1-flash:free": {
1034
1029
  label: "FREE",
1035
1030
  free: true
1036
- },
1037
- "stealth/space-bunny-alpha": {
1038
- label: "FREE",
1039
- free: true
1040
1031
  }
1041
1032
  };
1042
1033
  /**
@@ -5264,7 +5255,7 @@ var GatewayFacts = class {
5264
5255
  * per-request options thunk and an API-key resolver from the plugin entry
5265
5256
  * (src/index.ts), so a settings change reaches the very next request.
5266
5257
  */
5267
- const COMMAND_CODE_CLI_VERSION = "1.74.1";
5258
+ const COMMAND_CODE_CLI_VERSION = "1.74.3";
5268
5259
  const DEFAULT_API_BASE = "https://api.commandcode.ai";
5269
5260
  /**
5270
5261
  * The output budget this bundle asks for, and the ceiling it will never exceed.
@@ -9859,8 +9850,8 @@ function transportBudgetMessage(failureMessage, maxRetries) {
9859
9850
  * Mark one schema field volatile.
9860
9851
  *
9861
9852
  * `.volatile()` is unconditional: it is a schemastery 3.18.3 feature and the
9862
- * only supported engine (`dsh 0.2.0-rc.2`) pins `~3.18.4`, so the method is
9863
- * always present. It is reached through a structural member so the caller's
9853
+ * only supported engine (`dsh 0.2.1-alpha.1`) pins `~3.18.5-alpha.1`, so the
9854
+ * method is always present. It is reached through a structural member so the caller's
9864
9855
  * declared field type survives — the mark changes what the schema PARSES to (a
9865
9856
  * live reference), not the plugin-facing `Config` shape.
9866
9857
  */