fix: widen YAML-loaded numbers to the declared numeric field type

[tastybento]

What this fixes

YAML types a number by how it is written: 20 loads as Integer and 20.0 as Double, regardless of the declared field type. A double config field written without a decimal point reached the setter as an Integer; inside a collection, generic erasure hid the mismatch until the first read threw ClassCastException — a long way from the cause.

Changes

• Replaced the ad-hoc Integer→Long promotion in deserialize() with a widen() helper covering Long, Double and Float targets (boxed and primitive).
• Widening only: a decimal written against an int or long field is a config mistake, so it is left alone to fail visibly in the deserialize log rather than being silently truncated. The long branch is gated on integral sources for this reason. Double→float is the one accepted narrowing, since YAML always types decimals as Double and a float field must still load.
• The "float" switch arm in deserializeValue now uses Number.floatValue() instead of casting to Double — widen() delivers a boxed Float there, and the old cast would have thrown ClassCastException for every primitive float field.

Tests

New unit tests cover Integer→Double/Float/Long widening, the refusal to narrow Double→Integer and Double→Long, non-numeric targets being left untouched, and a loadObject round-trip on a primitive float field written both with and without a decimal point (the case that exercises the switch arm).

🤖 Generated with Claude Code

https://claude.ai/code/session_01XkVFZoe4hB2Req885z5ea7

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
87.2% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud