BINKY-WP-0006: wire mail-triage path and mark T01–T04 done

Document live llm-connect smoke + host port-forward; ensure git identity
and LLM_CONNECT_URL defaults for railiance timers.

integrations/railiance-llm-rhythm.md

@@ -74,14 +74,35 @@ No tool-using coding agent required if apply is code-owned.
 
 ## What already runs on railiance01
 
-| Component | Status (2026-07-21) |
+| Component | Status (2026-07-22) |
 | --- | --- |
-| `llm-connect` Deployment in `activity-core` | Running; OpenRouter; ConfigMap model `google/gemini-2.5-flash` (may change) |
+| `llm-connect` Deployment in `activity-core` | Running; OpenRouter; model `google/gemini-2.5-flash` |
 | OpenRouter API key Secret | Present (operator custody) |
 | `agent-harness mail-scan` on host | Proven |
-| Host systemd timers | Interim cadence; must call llm path, not `require_claude` |
+| `agent-harness mail-triage` | **Implemented** (agent-harness `7520a53`); live smoke OK via port-forward |
+| Host systemd timers | Interim cadence; call mail-scan + mail-triage |
 | Claude CLI on host | **Must not** become a dependency |
 
+### Host reachability to llm-connect
+
+In-cluster DNS does not resolve on the bare host. Interim:
+
+```bash
+kubectl -n activity-core port-forward svc/llm-connect 18080:8080 &
+export LLM_CONNECT_URL=http://127.0.0.1:18080
+export STATE_HUB_URL=http://127.0.0.1:18000
+agent-harness mail-triage --target-repo ~/binky-control
+```
+
+Prefer a **CronJob in-cluster** later (native DNS to `llm-connect.activity-core.svc`).
+
+Git identity on the host checkout (required once):
+
+```bash
+git -C ~/binky-control config user.email agent-harness@railiance.local
+git -C ~/binky-control config user.name agent-harness
+```
+
 ## Anti-patterns
 
 - Installing Claude Code / npm agent stacks on railiance for rhythm.