feat: support configurable model names and concurrent Science runtimes - #66
Open
RerrentLinden wants to merge 3 commits into
Open
Conversation
RerrentLinden
marked this pull request as ready for review
July 20, 2026 17:57
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.
Summary
Root cause
Provider model IDs must remain exact for routing, but slug-like IDs can be filtered when reused as Science-facing display names. The configuration UI previously could not edit
display_nameindependently.Current Science consumes its control-plane nonce from
GET /?nonce=..., while CSSwitch only used the olderPOST /api/auth/nonceflow. In addition, browser cookies are scoped by host rather than port, so opening both Science instances onlocalhostcould replace the other session. The old mode switch also coupled UI selection with teardown of the managed third-party runtime.Branch history
This draft supersedes #64. The three functional commits were replayed onto the latest upstream
main, so the PR is 0 commits behind and 3 commits ahead. The two fork-only upstream synchronization merge commits are intentionally excluded.Validation
git diff --check upstream/main...HEADnode --test test/model_catalog_state.test.mjs test/runtime_status_state.test.mjs: 22 passedpython3 -m unittest test.test_skill_runtime_boundary: 11 passedcargois unavailable; the PR remains draft rather than claiming a complete release gate