docs: remove all cron references from documentation

Cron is permanently disabled in Squad. Updated all docs to reflect
event-based triggers and squad watch for periodic polling.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: bradygaster

docs/src/content/docs/concepts/github-workflow.md

@@ -127,9 +127,9 @@ Ralph **never stops on his own while work remains** — he keeps cycling until t
 |-------|------|-----|
 | **In-session** | You're at the keyboard | `"Ralph, go"` — active loop |
 | **Local watchdog** | You're AFK but machine is on | `squad watch --interval 10` |
-| **Cloud heartbeat** | Fully unattended | `squad-heartbeat.yml` GitHub Actions cron |
+| **Cloud heartbeat** | Fully unattended | `squad-heartbeat.yml` GitHub Actions events |
 
-The heartbeat workflow (`squad-heartbeat.yml`) is installed during `init` or `upgrade`. It runs every 30 minutes by default, on issue close, on PR merge, and on manual dispatch. Edit the cron schedule in `.github/workflows/squad-heartbeat.yml` to fit your cadence.
+The heartbeat workflow (`squad-heartbeat.yml`) is installed during `init` or `upgrade`. It runs on issue close, PR merge, and manual dispatch. Edit the workflow in `.github/workflows/squad-heartbeat.yml` to customize triggers. For periodic polling without events, use `squad watch` locally.
 
 **PAT requirement:** Ralph needs `gh` CLI authenticated with a Classic PAT (scopes: `repo` and `project`). The default `GITHUB_TOKEN` doesn't have sufficient scopes.
 

docs/src/content/docs/features/project-boards.md

@@ -73,7 +73,6 @@ Squad's `sync-board.yml` workflow runs:
 - **On label change** — Issue labeled `go:yes` → moves to "Ready" column
 - **On issue close** → moves to "Done" column
 - **On PR merge** → linked issue moves to "Done"
-- **On schedule** (every 30 min) — full board resync to catch any drift
 
 ### Manual Sync
 

docs/src/content/docs/features/ralph.md

@@ -96,14 +96,14 @@ When you're in a Copilot session, Ralph self-chains the coordinator's work loop:
 
 ### Between Sessions (GitHub Actions Heartbeat)
 
-When no one is at the keyboard, the `squad-heartbeat.yml` workflow runs on a cron schedule (every 30 minutes by default). It:
+When no one is at the keyboard, the `squad-heartbeat.yml` workflow runs on event-based triggers (issue close, PR merge, manual dispatch). It:
 
 - Finds untriaged `squad`-labeled issues
 - Auto-triages based on your routing.md — matching issues to the right agent by work type and module ownership
 - Assigns `squad:{member}` labels
 - For `@copilot` (if enabled with auto-assign): assigns `copilot-swe-agent[bot]` so the coding agent picks up work autonomously
 
-This creates a fully autonomous loop for `@copilot` — heartbeat triages → assigns → agent works → issue closed → heartbeat finds next issue → repeat.
+This creates a fully autonomous loop for `@copilot` — heartbeat triages → assigns → agent works → issue closed → heartbeat finds next issue → repeat. For continuous periodic monitoring, use `squad watch` locally.
 
 ### Work-in-Progress Monitoring
 
@@ -147,11 +147,10 @@ Ralph monitors work at three different layers, each with different wake-up trigg
 - Poll interval expires (default 10 min) → Ralph checks GitHub
 - You press Ctrl+C → Ralph stops
 
-**Cloud Heartbeat (GitHub Actions cron):**
-- Scheduled cron triggers (default every 30 min) → Ralph checks GitHub
+**Cloud Heartbeat (GitHub Actions events):**
+- Issue close event → Ralph checks for next item
+- PR merge event → Ralph checks for next item
 - Manual dispatch via GitHub Actions UI → Ralph checks GitHub
-- Issue closed event → Ralph checks for next item
-- PR merged event → Ralph checks for next item
 
 In all three layers, when Ralph wakes up, he scans the board, triages any untriaged items using routing.md, dispatches work to the right agent, watches in-flight items for progress, and reports results.
 
@@ -211,7 +210,7 @@ This runs as a standalone local process (not inside Copilot) that:
 |-------|------|-----|
 | **In-session** | You're at the keyboard | "Ralph, go" — active loop while work exists |
 | **Local watchdog** | You're away but machine is on | `squad watch --interval 10` |
-| **Cloud heartbeat** | Fully unattended | `squad-heartbeat.yml` GitHub Actions cron |
+| **Cloud heartbeat** | Fully unattended | `squad-heartbeat.yml` GitHub Actions events (issue close, PR merge, manual dispatch) |
 
 ## Ralph's Board View
 
@@ -231,22 +230,11 @@ When you ask for status:
 
 The heartbeat workflow (`squad-heartbeat.yml`) is automatically installed during `init` or `upgrade`. It runs:
 
-- **On a schedule**: Every 30 minutes (configurable in the workflow file)
 - **On issue close**: Checks for next item in backlog
 - **On PR merge**: Checks for follow-up work
 - **On manual dispatch**: Trigger via GitHub Actions UI
 
-### Adjusting the Schedule
-
-Edit `.github/workflows/squad-heartbeat.yml`:
-
-```yaml
-on:
-  schedule:
-    - cron: '*/30 * * * *'  # Every 30 min (default)
-    # - cron: '0 * * * *'   # Every hour
-    # - cron: '0 9-17 * * 1-5'  # Work hours only (M-F 9am-5pm UTC)
-```
+For persistent polling when you're away, use `squad watch` locally — it polls at your chosen interval without consuming GitHub Actions minutes.
 
 ## Notes
 

docs/src/content/docs/guide/tips-and-tricks.md

@@ -65,7 +65,7 @@ Ralph, start monitoring
 
 Ralph triages issues, assigns them, spawns agents, and reports every 3-5 rounds. Say `"Ralph, idle"` to stop.
 
-The `squad-heartbeat` workflow runs Ralph on a schedule — your squad works even when you're offline.
+The `squad-heartbeat` workflow runs Ralph on event-based triggers (issue close, PR merge, manual dispatch).
 
 ---
 

docs/src/content/docs/scenarios/ci-cd-integration.md

@@ -14,22 +14,24 @@ Ralph runs periodically via GitHub Actions to handle housekeeping between Copilo
 
 ## 1. The Heartbeat Workflow — Ralph Between Sessions
 
-Ralph (the manager agent) runs via GitHub Actions on a schedule:
+Ralph (the manager agent) runs via GitHub Actions on event-based triggers:
 
 - Triage new issues
 - Apply squad labels based on routing rules
 - Check for stale branches
 - Archive old decisions
 
-The workflow is in `.github/workflows/squad-heartbeat.yml` and runs every 6 hours.
+The workflow is in `.github/workflows/squad-heartbeat.yml` and runs on issue close, PR merge, and manual dispatch (or via `squad watch` for local polling).
 
 **You don't have to do anything** — it's installed automatically (along with 9 other workflows) when you run `squad`.
 
 ```yaml
 name: Ralph Heartbeat
 on:
-  # schedule:
-  #   - cron: '0 */6 * * *'  # Every 6 hours
+  issues:
+    types: [closed]
+  pull_request:
+    types: [closed]
   workflow_dispatch:
 
 jobs:
@@ -41,7 +43,7 @@ jobs:
         run: squad heartbeat
 ```
 
-> ⚡ **Cron is commented out by default.** The heartbeat schedule is disabled when Squad installs the workflow — it only runs via manual `workflow_dispatch` until you uncomment the `schedule` block. Be aware: enabling scheduled heartbeats will consume GitHub Actions minutes on every run. A 6-hour cron burns ~120 runs/month. Adjust the frequency to match your budget, or leave it manual and trigger heartbeats from the CLI with `squad heartbeat`.
+> ⚡ **Cron is permanently disabled.** Scheduled cron jobs are no longer supported in GitHub Actions to reduce costs. The heartbeat workflow runs on event-based triggers: when issues are closed, PRs are merged, or you manually trigger via `workflow_dispatch`. For periodic polling without events, use `squad watch` in a separate terminal (local, no GitHub Actions cost).
 
 Ralph reads `.squad/routing.md`, looks at open issues, and applies labels:
 

docs/src/content/docs/tips-and-tricks.md

@@ -254,7 +254,7 @@ When you see this, you can:
 
 ### 4. Use Ralph Between Sessions
 
-The `squad-heartbeat` workflow runs every 30 minutes (or on your schedule).
+The `squad-heartbeat` workflow runs Ralph on event-based triggers (issue close, PR merge, manual dispatch). For persistent polling when you're away from the keyboard, use `squad watch` locally.
 
 Ralph will:
 - Triage new issues