Schedule-based pause: pause runners during specific hours

[nicktallen]

Problem

Users may want runners to only be active during certain hours — e.g., pause overnight or during work hours when local resources are needed.

Proposed Solution

Add a schedule configuration that pauses/resumes runners on a time-based schedule:

• Define active hours (e.g., 8pm–8am for overnight CI)
• Per-runner or global schedule
• Cron-like syntax or simple time picker in GUI

Acceptance Criteria

• Schedule config in Settings (GUI) and CLI (mac-runner schedule)
• Support daily recurring schedules (start/end time)
• Per-runner override capability
• Graceful pause (wait for current job to finish before pausing)
• Resume automatically when active window starts
• Show schedule status in menubar/runner list

Notes

Listed in README under "Planned Features." Filing to track formally.

[nicktallen]

Triage note — partial scaffolding exists

A QuietHours struct is already defined in Runner.swift (lines 195-199) with enabled, start, and end (HH:mm) fields. Tests exist in AppSettingsTests.swift. However, no scheduling logic or UI has been implemented.

Implementation will need:

• A timer/scheduler service that checks current time against quiet hours
• Pause/resume integration with RunnerManager
• Settings UI with time pickers for start/end
• Edge case handling (overnight ranges like 22:00–06:00)

The data model is ready; this needs service logic and UI work.

---

Automated triage by mac-runner bot

[nicktallen]

Triage note — Data model scaffolding already exists alongside #40.

AppSettings.quietHours is a QuietHours? struct with enabled: Bool, start: String, end: String — already persisted in config JSON. Implementation needed:

• Time picker UI in Settings
• Background scheduler comparing current time against the window
• Calling the existing pauseAll() / resume logic in RunnerManager

Could share a common AutoPauseService with battery-based pausing (#40).