BINKY-WP-0006: retarget Railiance rhythm to llm-connect/OpenRouter

Reject Claude Code (or any coding agent) on railiance01. Mail-scan stays
deterministic; triage/briefs use llm-connect HTTP → structured JSON →
deterministic apply. Document in integrations/railiance-llm-rhythm.md and
rewrite WP-0006 tasks accordingly; timers no longer require_claude.

scripts/railiance-rhythm/run-common.sh

@@ -28,10 +28,18 @@ require_repo() {
   git -C "${BINKY_REPO}" pull --ff-only --quiet origin main || log "WARN: pull failed (continuing on local)"
 }
 
-require_claude() {
-  if ! command -v claude >/dev/null 2>&1; then
-    log "ERROR: claude CLI not on PATH — agentic rhythm cannot run on this host"
-    log " residual: install Claude Code (or swap in a hosted agentic adapter) on railiance01"
-    exit 2
+require_llm_connect() {
+  # Server-side rhythm uses llm-connect HTTP (OpenRouter), never Claude CLI.
+  if [[ -z "${LLM_CONNECT_URL:-}" ]]; then
+    # In-cluster default when running inside k8s; host timers may override.
+    export LLM_CONNECT_URL="${LLM_CONNECT_URL:-http://llm-connect.activity-core.svc.cluster.local:8080}"
   fi
+  log "LLM_CONNECT_URL=${LLM_CONNECT_URL}"
+}
+
+require_claude() {
+  # Deprecated for Railiance. Kept only so old docs fail loudly with the right message.
+  log "ERROR: Claude CLI is not the Railiance execution path (BINKY-WP-0006)."
+  log "Use llm-connect/OpenRouter via agent-harness hosted adapters — see integrations/railiance-llm-rhythm.md"
+  exit 2
 }