Previously the number renderer silently discarded input outside the
min/max range and restored the stored value, forcing users to guess the
limits. Clamp to the nearest bound instead.
The integer check runs before clamping so that non-integer input is
still rejected for integer settings rather than accepted whenever it
happens to clamp to an integral bound.
The focusLoss handler now always stores the resolved value - the clamped
number, or the previous value when the input cannot be parsed. Writing
the setting is what rebuilds the widget, so a value that clamps onto the
value already stored would otherwise leave the raw text on display.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>