[FEATURE] /loop should use a random minute in the hour as the offset for its work

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

/loop currently works like cron, so if I tell it to run every hour, it will set the minutes to 0 and run on every hour. This means I will be hitting the Claude server and other services (GitHub PRs, for example) at the same time, creating a spike in load. It would be better if the base minute were selected randomly so that each user would go at a different time. I don't strictly care that it will be at some specific minute. In fact, when I set it to 1 hour, I will find it much better, even if it did the first pass now and then, did it every hour thereafter.

Proposed Solution

Use the current time as base offset for the cron or choose a random one.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_