mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-10-26 21:26:39 +00:00
Serper keeps a private _coerce_max_results in the pre-#5852 shape: a bare int() silently turns max_results: true into 1 and 3.5 into 3, and an invalid value falls back without a warning (#5865). Delegate to deerflow.community.search_max_results.coerce_max_results, which owns what invalid means for the folded providers, and keep Serper's 10-result cap at the call site the way You.com does, because clamping policy is deliberately per-provider. Invalid configured counts now warn under the Serper label and fall back to the default instead of being silently coerced.