Repository navigation
chore(catalog): sync from gateway — 0 added, 2 corrected, 0 retired - #407
Merged
Merged
Conversation
Every added param and every corrected bound was verified end-to-end through the gateway.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Automated sync between the Manifest gateway and this catalog (modelparams-agent).
How entries are verified: the local gateway loads this branch's catalog; for every declared param and test value the agent configures it through the gateway's model-params API, sends a request through the proxy pinned to the model, and checks the gateway applied the value upstream and got a 200 from that model. Params that fail are removed from the entry before it is filed.
This PR is rebuilt from
mainon every run and merged automatically once CI is green.Corrected (2)
Existing entries re-verified through the gateway (daily rotation). A declared bound was refused by the vendor and one step inside was accepted; or enum values were refused by the vendor and the corrected list (refused values removed, values the vendor lists as supported added) was served to the gateway on a draft catalog and every value passed.
models/google/gemini-3.1-pro-preview.yamlgenerationConfig.thinkingConfig.thinkingLevel: values [minimal, low, medium, high] → [low, medium, high]; defaultminimal→lowlow✅medium✅high✅minimalrefused and the vendor names no default; set tolow(nearest remaining value in the declared order) — a maintainer may prefer the vendor's documented defaultgenerationConfig.maxOutputTokensgenerationConfig.temperaturegenerationConfig.topPgenerationConfig.topKgenerationConfig.thinkingConfig.includeThoughtsgenerationConfig.responseMimeType✅models/groq/gpt-oss-safeguard-20b.yamlreasoning_format: values [hidden, raw, parsed] → [hidden, parsed]; defaultundefined(unchanged)reasoning_format=rawis not supported with this model"hidden✅parsed✅max_completion_tokenstemperaturetop_pfrequency_penaltypresence_penaltyreasoning_effortresponse_format.type✅Removing an enum value is not a parameter removal for
guard:params(it compares param paths per model, not values), and the removed values are refused by the vendor anyway.Needs a human: params now refused (11)
Re-verification found these declared params refused. Not removed — the param guard blocks removals and dropping a param is a maintainer's call.
models/anthropic/claude-opus-4-5-20251101.yamltop_p: top_p=1 → gateway did not apply it upstream (recorded undefined)models/anthropic/claude-opus-4-5-20251101.yamlthinking.typethinking.budget_tokensthinking.display: thinking.type="enabled" → HTTP 400:max_tokensmust be greater thanthinking.budget_tokens. Please consult our documentation at https://platform.claude.com/docs/en/build-with-claude/extended-t (same error for each)models/mistral/codestral-2508.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/mistral/ministral-14b-2512.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/mistral/ministral-14b-latest.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/mistral/mistral-medium-3.5.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Schema response format type requires a json_schemamodels/moonshot/kimi-k3.yamlresponse_format.type: response_format.type="json_schema" → HTTP 400: Invalid request: missing required parameter: 'response_format.json_schema'models/moonshot/kimi-k3.yamltool_choice: tool_choice="required" → HTTP 400: Invalid request: tool_choice 'required' requires at least one toolmodels/xai/grok-4.20-multi-agent-0309.yamltext.format.type: text.format.type="json_schema" → HTTP 422: Failed to deserialize the JSON body into the target type: text.format: missing fieldschema