Close forge runner substrate workplan

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

@@ -4,7 +4,7 @@ type: workplan
 title: "Gitea Actions runner substrate for Railiance workloads"
 domain: railiance
 repo: railiance-forge
-status: active
+status: finished
 owner: codex
 topic_slug: railiance
 planning_priority: high
@@ -218,7 +218,7 @@ self-hosted`, and `forge-runner-smoke.yaml #4` for commit `de6178764c` reports
 
 ```task
 id: FORGE-WP-0003-T06
-status: wait
+status: done
 priority: high
 state_hub_task_id: "53929202-40aa-4470-a249-9d0ee02d3213"
 ```
@@ -246,6 +246,16 @@ 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.
 
+**2026-06-08:** Reproduced the non-secret inter-hub build step on haskelseed
+from a committed-only `git archive` of inter-hub `84ee797`. `nix build
+.#docker` fails before any registry push or Helm deployment with GHC-87543 in
+`Web/Controller/Api/V2/Annotations.hs`: `createAnnotation` is ambiguous between
+`Generated.Types.createAnnotation` and the local
+`Web.Controller.Api.V2.Annotations.createAnnotation`. Registry tags `84ee797`,
+`7cc3173`, `fa96fb8`, and `latest` remain `manifest unknown`. The forge runner
+substrate is no longer the blocker; inter-hub now has a source build failure to
+fix before deployment can proceed.
+
 ---
 
 ## T07 - Publish runner evidence and ongoing health checks