Ralph heartbeat cron uses excessive GitHub Actions minutes

[bradygaster]

Problem

Ralph's heartbeat GitHub Action (\squad-heartbeat.yml) runs on a 30-minute cron schedule (*/30 * * * *). For users with multiple Squad-enabled repositories, this burns through GitHub Actions minutes rapidly — 48 runs per day per repo.

Impact

Users with 5+ Squad repos are consuming hundreds of unnecessary Actions minutes per month on background polling that rarely finds work.

Fix

Disabled the cron schedule by default in \ emplates/workflows/squad-heartbeat.yml. The heartbeat still fires on:

• Issue close/label events (reactive triage — zero extra cost)
• Pull request close events
• Manual workflow dispatch

Users who need proactive 30-minute polling can:

1. Uncomment the cron schedule in their .github/workflows/squad-heartbeat.yml\
2. Use
   px github:bradygaster/squad watch --interval 30\ for local polling
3. Run in-session Ralph (\Ralph, go) for interactive monitoring

Rollout

• \squad upgrade\ overwrites workflow files from templates, so existing installs get the fix automatically on next upgrade.
• New installs ship with cron disabled by default.

Commits

• \61060d4\ — fix: disable Ralph heartbeat cron by default to reduce Actions minutes