mirror of
https://github.com/block/buzz.git
synced 2026-11-02 07:22:55 +00:00
555e4c0709
The OpenAiStandard arm was delegating to normalize_effort_for_openai_route, which uses the old hand table and returns the uncorrected effort set for models with F1 corrections. Concretely: normalize_effort_for_databricks_v2(XHigh, "databricks-gpt-5-5") → XHigh (wrong) normalize_effort_for_databricks_v2(None, "databricks-gpt-5-5") → None (wrong) The fix: resolve against cap.supported_efforts (the generated axis carrying the F1 corrections) via the existing resolve_openai_effort clamping function. Same peer-fallback and nearest-supported semantics, one authority. Also apply the same fix to the OpenAiClampMaxToXHigh arm for consistency: values other than max now resolve against supported_efforts rather than passing through unchecked if the generated set happens to exclude them. Add four regression tests pinning the corrected behavior: - xhigh → high for databricks-gpt-5-5 (F1: supported=[low,medium,high]) - none → low for databricks-gpt-5-5 - low/medium/high pass through unchanged - max passes through for databricks-gpt-5-6-sol (F1: supported includes max) Co-authored-by: Will Pfleger <pfleger.will@gmail.com> Signed-off-by: Will Pfleger <pfleger.will@gmail.com>