fix(runner): preserve sub-second minute scheduling

[linkdata]

Summary

• preserve sub-second timing when calculating the next minute boundary
• avoid truncating wait duration too early
• add focused scheduling tests

Tests

• go test ./pkg/runner ./...

[coderabbitai]

Warning

Rate limit exceeded

@linkdata has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 39 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5377cd9a-0dbd-4c13-bc5c-0301463ca198

📥 Commits

Reviewing files that changed from the base of the PR and between b615285 and c6e1e19.

📒 Files selected for processing (2)

• pkg/runner/runner.go
• pkg/runner/time_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 59 minutes and 39 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[linkdata]

Additional context from comment files

These notes were split from the local markdown comment files and attached here because they describe this PR's change.

Minute-Boundary Scheduling

• Bug: The delay until the next minute ignored sub-second time, so a start at 12:30:00.500 waited a full 60 seconds instead of 59.5 seconds.
• Impact: Periodic rotation could drift nearly one second late and keep doing so after every reset.
• Fix: The timer now computes the duration from the current instant to now.Truncate(time.Minute).Add(time.Minute).
• Reasoning: Computing against the actual next minute boundary preserves sub-second precision without changing the intended one-minute cadence.
• Tests: Added fixed-time coverage for exact minute, half-second-after-minute, and one-millisecond-before-minute cases.