[tmakatos]

Durations are now integer seconds in settings ending in _secs:

scale_poll_secs, cooldown_secs (now integers, were floats)
scale_down_sustain_polls -> scale_down_sustain_secs
scale_validation_sample_polls -> scale_validation_delay_secs
scale_validation_sample_polls_per_thread -> scale_validation_delay_per_thread_secs
post_revert_up_grace_polls -> post_revert_up_grace_secs
post_revert_up_recovery_polls -> post_revert_up_recovery_secs
post_revert_up_backoff_max_polls -> post_revert_up_backoff_max_secs
scale_down_backoff_max_polls -> scale_down_backoff_max_secs

Every duration must be a multiple of scale_poll_secs. The engine
receives the poll period when it is built and converts its durations to
polls once, so engine logic is unchanged. The daemon refuses to start if
any duration, controller or engine, is not a multiple, listing all of
them with the nearest valid values.

The round_up_durations config option and --round-up-durations flag
(both off by default) instead round such durations up with a warning,
so that a new poll period can be tried without rewriting the config.
The daemon now logs the effective controller, engine, and backend
configuration at startup, which shows rounded values.

The daemon also prints errors with Display rather than Debug.

AI-generated: everything.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[lforchini]

Can you mention in the commit message why we're doing this change? Currently it just says how to cope with the restrictions it adds.

Still working on full review.

[tmakatos]

Can you mention in the commit message why we're doing this change? Currently it just says how to cope with the restrictions it adds.

Still working on full review.

Updated the commit message.