Repository navigation
Remove optional provider configuration discovery - #73
Merged
Merged
Conversation
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.
Remove optional provider-configuration discovery. Startup configuration returns its original four-field snapshot and rejects query parameters; the client opt-in, public schema and unused Runtime provider descriptors are removed. Internal provider validation, Agent defaults and frozen Session execution-configuration reads remain unchanged.
The startup route remains an explicit Core extension. Official documentation and read-only API probes confirmed that OpenAI does not expose this Core route; no replacement discovery API or unrelated protocol changes are introduced. Old Runtime heartbeats with the retired field remain accepted.
Validation: regenerated OpenAPI, identical sqlc output, affected and broad Go/PostgreSQL checks, standalone builds, all 394 client tests, 715 Web unit tests, TypeScript, Claude SDK packaging, MiniMax and Rust checks. Independent blind review found no actionable issues. Browser acceptance on isolated ports passed 123 of 127 cases; the four failures match clean-baseline Dashboard failures.
The full gate is not green: clean baseline 3fb5f87 independently reproduces the KVM-dependent installer failure and cascading fixture-directory error, plus four existing Dashboard browser failures. Initial local toolchain, test-environment and occupied-port issues were corrected without source changes. Production services are unchanged.