feat(ops): run artefacts in API/UI + llm-connect host access design

ACTIVITY-WP-0027: document durable ClusterIP host access for llm-connect;
join activity_runs to ops_runs; surface Forgejo artefact links on
/ops/ui automation detail and new run detail pages.

docs/ops-run-queue.md

@@ -89,6 +89,23 @@ queue empty.
 
 Never requires Forgejo or issue-core for the claim path.
 
+## Run artefacts (ACTIVITY-WP-0027)
+
+`GET /ops/automations/{id}/runs` joins each `activity_run` to related
+`ops_runs` and exposes deliverable links for the ops UI:
+
+| Field | Source |
+| ----- | ------ |
+| `ops_runs[]` | matched by `triggering_event_id == run_id` (or contains), else time window |
+| `artifacts[]` | from `ops_runs.result` (`path`, `head_after`, `target_repo`) |
+| Forgejo URL | `FORGEJO_WEB_BASE` (default `https://forgejo.coulomb.social`) + org + repo + path + ref |
+
+Run detail: `GET /ops/automations/{id}/runs/{run_id}` and
+`/ops/ui/automations/{id}/runs/{run_id}`.
+
+Executor `result` should include at least: `ok`, `path`, `head_after`,
+`target_repo`, `committed`. No prompts or raw model output.
+
 ## Auth
 
 - **Worker:** `ACTIVITY_CORE_WORKER_TOKEN` via `X-Worker-Token` or