From c0c9a3da1debb22d56676c3279c525da663982ab Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 19 Jun 2026 15:58:04 +0200 Subject: [PATCH] docs: record railiance01 llm-connect smoke evidence Document the 2026-06-19 deployment and in-namespace fixture smoke on railiance01, where activity-core runs. Clarify that the stable Service URL is cluster-local and point scheduled triage evidence to ACTIVITY-WP-0010. --- docs/activity-core-llm-endpoint.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/activity-core-llm-endpoint.md b/docs/activity-core-llm-endpoint.md index f20e624..b2e2c2d 100644 --- a/docs/activity-core-llm-endpoint.md +++ b/docs/activity-core-llm-endpoint.md @@ -111,5 +111,18 @@ handoff is verified as of 2026-06-18: - The in-namespace smoke passed against the stable Service: `smoke: pass health=ok latency_seconds=2.147 recommendations=1`. +2026-06-19 railiance01 recheck (activity-core production cluster): + +- Deployed the `deploy/k8s/activity-core-llm-connect` overlay into the + `activity-core` namespace on `railiance01`, where the activity-core worker + runs. `coulombcore` retains a separate llm-connect instance for earlier + verification; consumers must call the Service in their own cluster. +- `activity-core/llm-connect-provider-secrets` reports `DATA 1`; no Secret + values were inspected or recorded. +- Restarted `deployment/actcore-worker` so pods consume + `LLM_CONNECT_URL=http://llm-connect.activity-core.svc.cluster.local:8080`. +- In-namespace fixture smoke on `railiance01` passed: + `smoke: pass health=ok latency_seconds=1.681 recommendations=1`. + Scheduled `daily_triage` evidence collection is activity-core ownership under -`ACTIVITY-WP-0006`. +`ACTIVITY-WP-0010`.