Score maintenance runs on two passes: one that rescores a score across its segments, and one that rescores a model directly. The hourly scheduled job was running only the second. The setting that enables the score-level pass was pinned on the API but not on the job image that actually executes the sweep, so the job read its own default and logged the pass as disabled every hour.
Manual rescores were unaffected throughout, because they run on the API rather than in the job. What was missing was the scheduled path: a score whose rules route records to different models had its segment routing applied on demand and not on the schedule.
The job image now carries the setting, and the score-level pass runs on every scheduled sweep.