Record haskelseed runner smoke state

docs/gitea-actions-runner-evidence.md

@@ -80,6 +80,8 @@ Observed on 2026-06-07:
 | registration labels after activation | `self-hosted:host`, `haskelseed:host`, `linux:host`, `linux_amd64:host`, `x86_64:host`, `container-build:host`, `registry-publish:host` |
 | ephemeral | `false` |
 | runner backup | `/root/.runner.bak-20260607225905` |
+| smoke workflow run | `forge-runner-smoke.yaml #1`, run `/coulomb/railiance-forge/actions/runs/1`, commit `19ee47fe82` |
+| smoke workflow status | `Waiting`, duration `0s` as of 2026-06-08 00:40 Europe/Berlin |
 
 Activation evidence:
 
@@ -147,10 +149,27 @@ done
 Record only image names, tags, digests, and status. Do not record registry
 tokens.
 
+Haskelseed inventory on 2026-06-08:
+
+| Tag | Result |
+| --- | --- |
+| `91037a4` | `manifest unknown` |
+| `ae9e497` | `manifest unknown` |
+| `fa96fb8` | `manifest unknown` |
+| `7cc3173` | `manifest unknown` |
+| `latest` | `manifest unknown` |
+
+This means the blocked inter-hub workflow did not publish the expected image
+tags to the current Gitea registry path.
+
 ## Smoke Evidence Slot
 
 No smoke job has passed yet. Current haskelseed registration labels now match
-the proposed first compatibility contract.
+the proposed first compatibility contract, and Gitea created run
+`forge-runner-smoke.yaml #1`, but the run is still `Waiting` at `0s`.
+
+The next gate needs authenticated Gitea Actions UI/API inspection to determine
+whether the waiting run needs approval, rerun, or runner assignment repair.
 
 Expected evidence after `.gitea/workflows/forge-runner-smoke.yaml` passes: