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.

DecisionQueue.md

@@ -30,30 +30,31 @@ fallback_if_no_response: ""
 
 ## Open decisions
 
+_(none)_
+
+## Resolved decisions
+
 ### DEC-2026-003 — Go for executor cutover (retire the cron bridge)
 
 ```yaml
 id: DEC-2026-003
 title: "Execute BINKY-WP-0004-T06: enable harness-scheduled Binky definitions, retire workstation cron bridge"
 lane: yellow
-status: prepared
+status: resolved
+outcome: approved and executed
+resolved_at: "2026-07-21"
+resolved_by: Bernd (prior approve) + agent cutover execution
 state_hub_decision_id: "d47d288f-a76f-4e2f-b039-330028824397"
 created_at: "2026-07-18"
-needed_by: "soft — each day of delay keeps the workstation cron dependency alive"
-attention_cost: "~5 min: skim runbook gates, say go/no-go"
-agent_recommendation: "approve — all three gates cleared as of 2026-07-18
-  (DEC-2026-002 resolved; Red-lane Lanes 2–3 provisioned; harness live on
-  Railiance with tenant #1 onboarded and three definition proof runs)"
+consequence: "Workstation cron line removed 2026-07-21; railiance host timers
+  installed (scripts/railiance-rhythm/); three completion event types verified.
+  Residual continuous intake → BINKY-WP-0006."
 evidence:
   - integrations/executor-cutover-runbook.md
   - integrations/harness-tenant-onboarding.md
-options: [approve, reject, revise, defer]
-fallback_if_no_response: "cron bridge keeps running; no degradation, but
-  workstation-independence milestone stalls"
+  - OperatingRhythm.md
 ```
 
-## Resolved decisions
-
 ### DEC-2026-004 — Qonto MCP: create API key, provision OpenBao lane (read-only use)
 
 ```yaml