Enforce the documented [0, 1] upper bound for both reversal NATR multiplier
fractions at the configuration boundary:
- reject config values above 1 (warn and fall back per component)
- fail fast with ValueError when canonical defaults exceed max_value
- canonicalize the out-of-range component warning to the single
"<= {max_value}" form, dropping the wrong "[-inf, x]" notation
- clarify the strict min < max ordering in the README tunables table with
symmetric "(< upper bound)" / "(> lower bound)" hints