chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-06-08:
  - FORGE-WP-0003-T06: progress → wait

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

@@ -9,7 +9,7 @@ owner: codex
 topic_slug: railiance
 planning_priority: high
 created: "2026-06-07"
-updated: "2026-06-07"
+updated: "2026-06-08"
 state_hub_workstream_id: "149a0316-64d1-4664-96d0-274577c32e63"
 ---
 
@@ -175,7 +175,7 @@ referenced by file path only and are never committed.
 
 ```task
 id: FORGE-WP-0003-T05
-status: wait
+status: done
 priority: high
 state_hub_task_id: "9ada5b3e-2ddb-4a55-b9f4-5a6e00fef8b2"
 ```
@@ -206,6 +206,12 @@ and is dispatched or triggered.
 push, but it is still `Waiting`. This task now waits on authenticated Gitea
 Actions inspection to approve, rerun, or diagnose runner assignment.
 
+**2026-06-08:** Haskelseed was re-registered under the `coulomb` organization
+runner scope using an attended Gitea UI token provided by the operator. Public
+Gitea Actions no longer reports `No matching online runner with label:
+self-hosted`, and `forge-runner-smoke.yaml #4` for commit `de6178764c` reports
+`Success`. The runner substrate proof is complete.
+
 ---
 
 ## T06 - Unblock the inter-hub deployment path
@@ -234,6 +240,12 @@ blocker.
 **2026-06-07:** Inter-hub unblock remains gated on T05. Do not rerun production
 push probes until the forge smoke workflow passes.
 
+**2026-06-08:** T05 passed. On runner reconnect, Gitea assigned haskelseed a
+`coulomb/inter-hub` job, proving the inter-hub workflow can schedule on the
+runner. The operator reported that the inter-hub job failed while the forge
+smoke job succeeded, so the remaining work is to inspect the inter-hub job logs
+and classify the workload-specific failure.
+
 ---
 
 ## T07 - Publish runner evidence and ongoing health checks