chore: mark inter-hub deploy blocked on runner substrate

workplans/IHUB-WP-0018-railiance01-deployment.md

@@ -8,7 +8,7 @@ status: active
 owner: custodian
 topic_slug: inter_hub
 created: "2026-04-29"
-updated: "2026-06-05"
+updated: "2026-06-07"
 depends_on: IHUB-WP-0015
 state_hub_workstream_id: "080d841a-3acd-4adf-b684-2d1890a5e986"
 ---
@@ -273,7 +273,7 @@ current Gitea registry and `hub.coulomb.social`. Remaining gaps: no repo-root
 
 ```task
 id: IHUB-WP-0018-T07
-status: in_progress
+status: blocked
 priority: medium
 state_hub_task_id: "ec25c67c-3cb0-4534-9fb0-9bd6578a2def"
 ```
@@ -319,6 +319,16 @@ the public endpoint. Remote `main` is already current, but production is still
 serving an older API surface, so the workflow needs an attended rerun/inspection
 or a new deployment trigger.
 
+**Runner substrate finding (2026-06-07):** Pushed commits `fa96fb8` and
+`7cc3173` to trigger the workflow, but public `/api/v2/hubs` remained `404`
+while `/` stayed `200`, indicating the current image was not deployed. Repo
+search shows `railiance-forge` owns Actions runner substrate, but its
+2026-06-05 migration plan explicitly lists "No Actions runner deployment" as a
+non-goal and no runner manifest/script/workplan exists there yet. `haskelseed`
+itself is reachable on SSH and historical port 8080, but this workspace cannot
+authenticate non-interactively. Treat R7 as blocked on a forge-owned runner
+prerequisite rather than continuing to push commits as deployment probes.
+
 ### R8 — Staged deployment and smoke test
 
 ```task