c7e0bdef9a
An over-cap model.max_tokens produces a provider 400 that mentions max_tokens, which trips _CONTEXT_OVERFLOW_PATTERNS and is classified as context_overflow. On providers whose wording isn't recognized by parse_available_output_tokens_from_error() (e.g. DashScope/Qwen: "Range of max_tokens should be [1, 65536]") the smart-retry is skipped and the error falls into the compression fallback, which re-sends the same oversized max_tokens, fails identically, and loops until "cannot compress further" on a tiny conversation (#55546). Root-cause fix for the whole class, not just DashScope: - parse_available_output_tokens_from_error(): recognize the DashScope "Range of max_tokens should be [1, N]" form and return N (smart-retry then caps output and retries WITHOUT compressing). - new is_output_cap_error(): broader yes/no gate for output-cap 400s. In the loop, when the error is output-cap-shaped but unparseable, fail fast with an actionable message (lower model.max_tokens) instead of routing into compression. Mirrors the existing GPT-5 max_tokens guard. Real input overflows and GPT-5 unsupported-param 400s are unchanged.