GitLab

Catch up was off by default and needed turning on beside the history window it
depends on.  It can do nothing at all without that window, and the window is
off by default, so the second switch protected nobody from anything: a fresh
install behaves the same either way.

Somebody who sets a window has already said their histories do not fit in a
single run.  Finishing the job that starts is not a separate decision, so it is
no longer a separate switch.  It stays visible and still turns off, for an
installation that wants scans only at times it chose.