rhythm bridge: installed by founder; fix script exec bit, add health check note

Crontab line active (weekdays 08:23). chmod +x had been lost when the
original install command was denied — without it every cron run would
have failed silently.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

OperatingRhythm.md

@@ -35,20 +35,21 @@ Rules:
 
 ## Bridge scheduler (workstation cron)
 
-**Status: prepared, not installed** — installing a self-running agent loop is
-a founder action (the Claude Code permission layer rightly refuses to let an
-agent install its own persistence). Everything else is ready:
+**Status: installed 2026-07-16** (founder-approved; agents may not install
+their own persistence). Runs weekdays 08:23 local:
 `scripts/rhythm-session.sh` runs a headless, lane-restricted Claude Code
 session that does queue hygiene, writes the daily brief, and pulls one
 autopilot item (agent name `agt-rhythm-bridge`; flock guard, logs to
 `~/.cache/binky-control/rhythm/cron.log`).
 
-**Enable (founder, one line):**
-```bash
-( crontab -l; echo '23 8 * * 1-5 /home/worsch/binky-control/scripts/rhythm-session.sh # binky rhythm bridge' ) | crontab -
+**Installed line:**
+```
+23 8 * * 1-5 /home/worsch/binky-control/scripts/rhythm-session.sh # binky rhythm bridge
 ```
 
 **Disable:** `crontab -e` and delete the `binky rhythm bridge` line.
+**Health check:** `tail ~/.cache/binky-control/rhythm/cron.log` — every run
+appends a finish line; a silent weekday morning means the bridge failed.
 
 This is explicitly a **bridge**: once activity-core definitions (T05) and an
 llm-connect executor (T06 follow-up) are live, the cron line is removed and