-
Notifications
You must be signed in to change notification settings - Fork 293
[Klaud Cold] docs: deprecate DeepSeek-V4-Pro Single-turn 8k1k on 2026-09-08, keep AgentX / 弃用 DeepSeek-V4-Pro 单轮 8k1k(2026-09-08),保留 AgentX #2728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 New Sept 8 2026 deprecation entry claims dsv4's agentic coding 'stays active... including its MTP and DSpark arms', but no dsv4 config key in configs/nvidia-master.yaml or configs/amd-master.yaml uses DSpark (grep for 'dspark' in either file returns zero dsv4 hits, unlike kimik3 which has multiple active -agentic-dspark- keys). The pre-existing spec-decode A/B table at MODELS.md lines 27-33 also lists only 'MTP' as dsv4's current agentic spec-decode arm, not DSpark; DSpark for dsv4 is only an 'agreed PoR' (line 123) and a SPEED-Bench golden-AL reference (golden_al_distribution/dsv4-pro-0813-dspark.yaml), not a running master-config arm.
Extended reasoning...
A reader trusts this new notice and expects published dsv4 DSpark agentic results after Sept 8 2026 deprecation of Single-turn 8k1k; no such active arm exists in either master config, so the claim is currently false and will stay false unless a real dsv4-agentic-dspark key is added. Same incorrect claim is duplicated in MODELS_zh.md lines 47 and 51.
Verification: normal — the new Sept 8 2026 entry introduces a false, self-contradictory claim not present on the base branch. MODELS.md:47 and the table row at MODELS.md:51 both state dsv4's agentic coding stays active "including the MTP and DSpark arms." No dsv4 config key uses DSpark: a grep for
dsv4.*dspark/dspark.*dsv4across configs/nvidia-master.yaml and configs/amd-master.yaml returns zero matches,