BINKY-WP-0006: close with three clean railiance mail cycles

Host LLM_CONNECT_URL discovery uses ClusterIP when DNS is unreachable;
mail path fails hard if triage fails. Mark T06 done and workplan finished;
update residual docs (OperatingRhythm, cutover runbook, llm-rhythm).

OperatingRhythm.md

@@ -58,11 +58,13 @@ all `enabled: true`). Execution on Railiance:
 `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.
 
-**Known residual (BINKY-WP-0006):** finish **llm-connect / OpenRouter** path
-for mail triage + briefs on Railiance (structured LLM output + deterministic
-apply). **Do not** install Claude Code or another coding agent on railiance01.
-Mail-scan is already deterministic and proven there; see
-`integrations/railiance-llm-rhythm.md`.
+**Railiance executor (BINKY-WP-0006 finished 2026-07-22):** mail path is
+**mail-scan → mail-triage** via **llm-connect / OpenRouter** (structured JSON
++ deterministic apply). Daily brief uses `brief-daily` the same way.
+**Do not** install Claude Code or another coding agent on railiance01. Host
+timers resolve `LLM_CONNECT_URL` via port-forward or Service ClusterIP (see
+`integrations/railiance-llm-rhythm.md`). Optional residual: `brief-weekly`
+subcommand for Friday review prep.
 
 ## Weekly review (founder, ~15 min)