8ee0103ea2
Addresses both review findings from @egilewski on #89134: - Non-finite values: _coerce_int now degrades int(inf) (OverflowError previously ABORTED gateway config loading); the clamp requires math.isfinite plus sane upper bounds (interval <=3600s, timeout <=600s, strikes <=1000), falling back to the shutdown_watchdog constants. - Loader wiring: load_gateway_config builds gw_data FLAT and never forwarded the yaml gateway: section, so loop_watchdog* keys — including the PRE-EXISTING loop_watchdog bool documented in config_defaults — were silently ignored on the real startup path. Bridged with the established top-level-wins/nested-fallback pattern. E2E: config.yaml with loop_watchdog:false + strikes:12 + interval:.inf now yields False/12/30.0 through the real loader.