Record haskelseed runner smoke state

workplans/FORGE-WP-0003-actions-runner-substrate.md

@@ -58,7 +58,7 @@ messages that created the blocker are marked read.
 
 ```task
 id: FORGE-WP-0003-T02
-status: wait
+status: done
 priority: high
 state_hub_task_id: "87181d63-049e-4a2b-a5e3-bf16763246d7"
 ```
@@ -97,6 +97,14 @@ service from `runner/act-runner-haskelseed.openrc.example`, and started
 declared successfully with labels `self-hosted`, `haskelseed`, `linux`,
 `linux_amd64`, `x86_64`, `container-build`, and `registry-publish`.
 
+**2026-06-08:** Completed current-state inventory. Gitea created
+`forge-runner-smoke.yaml #1` for commit `19ee47fe82`, but the run remains
+`Waiting` with duration `0s`. Haskelseed login shell has the deploy tools needed
+by inter-hub (`skopeo`, `helm`, `kubectl`, `nix`, `git`, `curl`). Registry
+inspection from haskelseed shows inter-hub tags `91037a4`, `ae9e497`,
+`fa96fb8`, `7cc3173`, and `latest` are all `manifest unknown`, confirming the
+blocked inter-hub workflow did not publish those images.
+
 ---
 
 ## T03 - Decide runner placement, labels, and capacity rules
@@ -194,6 +202,10 @@ until an approved runner is registered and visible to Gitea.
 execution is still pending until the workflow exists in the remote Gitea repo
 and is dispatched or triggered.
 
+**2026-06-08:** The workflow exists in Gitea and run `#1` was created from the
+push, but it is still `Waiting`. This task now waits on authenticated Gitea
+Actions inspection to approve, rerun, or diagnose runner assignment.
+
 ---
 
 ## T06 - Unblock the inter-hub deployment path