The repeating cost timer ran at the full one-hour cooldown but started
before the first scan recorded its attempt. Its first tick therefore saw
an elapsed time just under an hour, kept the snapshot, and the first
automatic scan came after two hours. Any forced, visible, or range-change
scan shifted the next automatic one the same way, and timer jitter could
skip further hours.

The timer now polls every minute and CostRefreshPolicy still decides when
the hour has elapsed, so automatic scans start within a minute of it.

Documentation: usage guide says scans run about once an hour.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>