Wire llm-connect runtime for daily triage

k8s/railiance/20-runtime.yaml

@@ -11,7 +11,7 @@ data:
   TEMPORAL_NAMESPACE: default
   NATS_URL: nats://actcore-nats:4222
   STATE_HUB_URL: http://actcore-state-hub-bridge:8000
-  LLM_CONNECT_URL: ""
+  LLM_CONNECT_URL: http://llm-connect.activity-core.svc.cluster.local:8080
   LLM_CONNECT_TIMEOUT_SECONDS: "300"
   REPO_SCOPING_URL: http://repo-scoping.repo-scoping.svc.cluster.local:8020
   ISSUE_CORE_URL: http://issue-core.issue-core.svc.cluster.local:8010

k8s/railiance/README.md

@@ -32,8 +32,10 @@ Europe/Berlin schedule, verify both runtime dependencies:
 
 - `actcore-state-hub-bridge` can reach the State Hub API through the node-local
   tunnel expected at `127.0.0.1:18000`.
-- `LLM_CONNECT_URL` is set to an operator-approved llm-connect endpoint that can
-  serve the `custodian-triage-balanced` profile.
+- `LLM_CONNECT_URL` points at the verified in-namespace llm-connect Service,
+  `http://llm-connect.activity-core.svc.cluster.local:8080`, and the
+  operator-owned provider Secret lets that Service serve the
+  `custodian-triage-balanced` profile.
 
 If `LLM_CONNECT_URL` is missing or broken, report-sink instructions write a
 visible `execution_failed` diagnostic instead of silently producing no report.