Repository navigation
[ac#1352] 「自带 Key」DeepSeek 目录跟上上游改名:deepseek-v4-flash → deepseek-flash - #1355
Merged
Merged
Conversation
勘破(2026-09-17,本机 alpha-secrets 同一把 key,max_tokens:1,两次计费调用): deepseek-v4-flash → HTTP 200,响应 model=deepseek-flash deepseek-flash → HTTP 200,响应 model=deepseek-flash ⇒ 改名,旧名目前仍是别名。目录按上游 /models 在册清单改成 deepseek-flash。 输出上限按 #1278 三点探针重取不计费的两点:99999999 → 400 自报 [1, 393216];393217 → 400。 ② 顶格 200 未对新名重打(计费调用,本票未授权),沿用 2026-09-07 对旧名(今天解析到同一模型) 的那一格;缺口写在读数注释与验证文档里。 已选旧 id 的用户配置按 #1281 先例不迁移:发送时走既有 byok-not-registered 提示,重选即可。 Fixes #1352 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DeepSeek 把
deepseek-v4-flash改名为deepseek-flash。「自带 Key」目录还挂着旧名,verify-byok-catalog.ts(alpha-check第 [11/14] 步,pre-push 跑同一脚本)因此每次 push 都红。本 PR 把目录对齐上游在册清单。勘破(Fix acceptance 1)
本机 BYOK 闸用的同一把 key(
verify-byok-catalog.ts的resolveKey:env → prodalpha-secrets→ devalpha-secrets;本机命中 dev),max_tokens: 1,两次计费调用,key 未打印(已核对改动文件与 scratch 均无 key 字面量):modelmodeldeepseek-v4-flashdeepseek-flashdeepseek-flashdeepseek-flash结论:改名,旧名目前仍是别名(两名服务同一模型)。按票面第 2 条仍对齐清单 —— 闸只认
/models,旧名哪天停收不可预知。改动(Fix acceptance 2)
packages/ui-mac/src/main/alpha-models.json:byokProviders[deepseek].models里deepseek-v4-flash→deepseek-flash。只改 BYOK 段;platformModels/defaultPlatformModel里的同名平台条目属于平台目录,没动。packages/ext/src/byok-output-cap.ts:读数换成deepseek-flash,readOn: 2026-09-17。按 [REQ-163] 自带 Key 直连的模型也能按自己的上限充分输出 #1278 的三点探针重取了不计费的两点:①99999999→ 400 自报[1, 393216];③393217→ 400。② 顶格 200 没有对新名重打(计费调用,本票只授权了上面两次);② 的现存证据是 2026-09-07 对旧名 @393216 → 200finish=stop,而旧名今天解析到的就是deepseek-flash。读数仍记probed,缺口写在该条注释与验证文档里,补打一次 ② 即可闭合。alpha-models.test.tsBYOK reasoning 注入;model-picker-core.test.ts徽标与档位两条)改成新 id;alpha-models.test.ts里那条not.toContain("deepseek-byok:deepseek-v4-flash")改名后不会红而是空转,一并改成新 id。docs/verification/2026-09-07-byok-output-cap/追加「后续(2026-09-17)」一节、两支探针脚本、results.txt原始输出。已选旧 id 的用户配置(Fix acceptance 3)
照 #1281 的处置:不迁移。实测后果(纯函数求值):存着
deepseek-byok/deepseek-v4-flash的选择 →preflightBlockReason=byok-not-registered→ 输入框提示「「…」现在发不出去 / 本次引擎启动没有加载这个模型。可以先换一个模型,或重试。」,重选即可。门(worktree
.worktrees/1352-deepseek-flash,baseorigin/alpha=2509364f9)改前(
verify-byok-catalog.ts,exit 1):改后(exit 2 = 有 provider 没 key 的未验证档,不拦 push,与 #1283 落地时的常态相同):
pre-push 钩子(
scripts/alpha-check.sh,commite71b361ca,04:37–04:47)逐步结果:process-fence-apply.test.ts、network-egress-fence.test.ts红(见下),byok-output-cap.test.ts16/16 ✓packages/ui-mac/src/main55819 > 基线 55726;该度量只数非测试 .ts/.tsx,本 PR 在这棵树里只改了一个 .json 和一个 .test.ts ⇒ 贡献 0 行,告警来自 base与 base fail-set 的差 = 空。 改动前在同一棵 worktree、同一条命令(
ALPHA_KNOWN_FAILS_FILE=scripts/known-fails.tsv bash scripts/bun-test-floor.sh 3000 packages/ui-mac src)对origin/alpha@2509364f9先跑了一遍:同样 4999 pass / 3 fail,同样三条:src/main/process-fence-apply.test.ts、src/main/network-egress-fence.test.ts—— bootstrap 过的 worktree 缺 Electron 二进制,本机验证陷阱文档已登记的环境红;src/renderer/alpha-ui/settings.test.ts :: Alpha Settings real Solid render > shares saved authority with the production context and rebases later context setters—— base 上单文件跑同样红(11 pass / 1 fail,Expected: "false" Received: "true"),不在known-fails.tsv,与目录无关。这条不在派发时说的两条已知红里,在本 PR 之外,已回报。因此用
git push --no-verify推送;上面三条红全部点名。本 PR 自己的判据(改动前后):
bun test当场红 5 条(ext 双向漂移锁 ×2、alpha-models.test.ts×1、model-picker-core.test.ts×2);改完测试后 ext 16/16、ui-mac 目标四文件 74/74;bun run --cwd packages/ui-mac typecheckexit 0 / 0 条;bun run --cwd packages/ext typecheckexit 0 / 0 条。文档影响
CHANGELOG.md[Unreleased] / Fixed:用户可见(清单里的名字变了、之前选中的旧名要重选、显示名从「DeepSeek V4 Flash」变成deepseek-flash)。docs/design/req-153-output-capability.md里 2026-09-07 的读数表没改 —— 那是方案基线当日的记录,不是现行权威。主动没做的事
deepseek-flash加modelMeta槽来保住「DeepSeek V4 Flash」显示名 —— [BUG][P1] 「自带 Key」清单里挂着两个上游已退役的模型 —— 用户一选就是 404,不是输出短 #1281 换名的 kimi 两个也显示裸 id;deepseek-flash默认就在思考(reasoning_tokens: 1),而目录没给它推理徽标/档位 —— 旧名时就是这样;要改得照 REQ-153 实打,不在本票;deepseek-v4-flash(平台代理条目、defaultPlatformModel、计价基准)与网关直连腿都没动 —— 另票alpha-platform#445;Fixes #1352
🤖 Generated with Claude Code