The temperature deprecation is a silent no-op right now, not an error — how are people auditing for it?

Something that caught us out, in case it helps anyone else.

temperature / top_p / top_k are deprecated on the 3.x Flash line.
They’re not rejected — they’re accepted and ignored, so requests still return 200. Anything that was setting temperature=0 for consistency lost that guarantee without a single error surfacing.

Grepping for the parameter name isn’t enough either. In our case it turned up wrapper layers and config objects where the value is set nowhere near the call site.

What I don’t have a good answer for: how do you actually verify none are left? Waiting for the eventual 400 in a future model generation isn’t a plan.

Curious how others have audited this — and how often you’re dealing with provider-side changes like this in general.