refactor: isolate DeepSeek launch boundary - #10
Open
JaylanJerry wants to merge 1 commit into
Open
Conversation
Move DeepSeek launch resolution out of profiles.ts. Production still starts the legacy source ACP example; the official runtime placeholder stays undefined. Co-authored-by: Cursor <cursoragent@cursor.com>
4 tasks
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
1 participant
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.
Summary
src/workers/deepseek-launch.ts.resolveDeepSeekLaunch()now returns{ type: legacy | official | missing, command, args, env }.resolveOfficialDeepSeekAcpRuntime()remainsundefined.Stacked on the status PR. Merge last. After this, freeze DeepSeek work.
Test plan
npm test(legacy command unchanged, missing typed, official unresolved)npm run mcp:smoke