BINKY-WP-0004 finished: retire workstation cron, Railiance rhythm timers

Complete T06 cutover: remove binky rhythm bridge crontab, install
scripts/railiance-rhythm systemd user timers on railiance01 (Europe/Berlin),
document residual continuous-intake gaps as BINKY-WP-0006. Three completion
event types verified (daily_brief, mail_intake on Railiance, weekly_review).
DEC-2026-003 marked resolved/executed.

OperatingRhythm.md

@@ -38,31 +38,31 @@ Rules:
    `statehub fix-consistency` regenerates it automatically (C-33); nothing
    to hand-maintain.
 
-## Bridge scheduler (workstation cron)
+## Scheduler (workstation-independent)
 
-**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`).
+**Status: workstation cron bridge retired 2026-07-21** (BINKY-WP-0004-T06 /
+DEC-2026-003). Cadence is owned by activity-core definitions
+(`binky-daily-rhythm`, `binky-weekly-mail-intake`, `binky-weekly-review-prep`,
+all `enabled: true`). Execution on Railiance:
 
-**Installed line:**
-```
-23 8 * * 1-5 /home/worsch/binky-control/scripts/rhythm-session.sh # binky rhythm bridge
-```
+| Path | Role |
+| --- | --- |
+| activity-core Temporal schedules | When work is due (Europe/Berlin) |
+| host systemd user timers | Invoke agent-harness on railiance01 (interim) — `scripts/railiance-rhythm/` |
+| agent-harness | Green/Blue tool profiles, hub completion events |
 
-**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.
+**Health:** `ssh railiance01 'systemctl --user list-timers | grep binky'` and
+`tail ~/.cache/binky-control/rhythm/railiance-rhythm.log` on that host.
 
-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
-scheduling moves to the sanctioned coordination layer.
+**Rollback (emergency only):** re-add workstation cron
+`23 8 * * 1-5 /home/worsch/binky-control/scripts/rhythm-session.sh # binky rhythm bridge`
+and pause railiance timers. Script kept for one month as break-glass.
 
-Guardrails baked into the script: Green/Blue lane only, allowed tools limited
-to file edits + git add/commit, no push, no network, one-run-at-a-time lock,
-bounded "maintenance pass" prompt.
+**Known residual (BINKY-WP-0006):** activity-core `ISSUE_SINK_TYPE=state-hub`
+emits progress events, not claimable issue-core tasks; agentic daily/review
+on Railiance need `claude` CLI on that host (mail-scan is deterministic and
+already runs there). Until Claude is installed on railiance01, agentic slots
+may still be run from a laptop harness session with the same task files.
 
 ## Weekly review (founder, ~15 min)