From 5861c61c8e0a22b344751d345f382959548b854e Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 8 Jun 2026 10:16:08 +0200 Subject: [PATCH] Close forge runner substrate workplan --- docs/gitea-actions-runner-evidence.md | 24 ++++++++++++++++--- .../FORGE-WP-0003-actions-runner-substrate.md | 14 +++++++++-- 2 files changed, 33 insertions(+), 5 deletions(-) diff --git a/docs/gitea-actions-runner-evidence.md b/docs/gitea-actions-runner-evidence.md index eea8871..52093e8 100644 --- a/docs/gitea-actions-runner-evidence.md +++ b/docs/gitea-actions-runner-evidence.md @@ -189,6 +189,24 @@ passes and Gitea can schedule jobs on haskelseed. The first inter-hub job picked up after org registration failed, according to the authenticated UI observation reported by the operator on 2026-06-08. +Forge reproduced the non-secret build phase on haskelseed from a committed-only +archive of inter-hub `84ee797`. The build fails before publish/deploy: + +```text +Web/Controller/Api/V2/Annotations.hs:20:23: error: GHC-87543 +Ambiguous occurrence `createAnnotation`. +It could refer to Generated.Types.createAnnotation +or Web.Controller.Api.V2.Annotations.createAnnotation. + +Web/Controller/Api/V2/Annotations.hs:29:42: error: GHC-87543 +Ambiguous occurrence `createAnnotation`. +``` + +Registry inspection from haskelseed still reports `manifest unknown` for +`84ee797`, `7cc3173`, `fa96fb8`, and `latest`, matching a failure before or +during publish. Since the reproduced failure happens in `nix build .#docker`, +the next fix belongs in the inter-hub source repo. + Expected evidence after inter-hub rerun: | Field | Value | @@ -196,6 +214,6 @@ Expected evidence after inter-hub rerun: | Inter-hub commit | `TODO` | | Workflow id/url | `TODO` | | Image tag/digest | `TODO` | -| Deployment result | failed after scheduling to the runner | -| `https://hub.coulomb.social/api/v2/hubs` | `TODO` | -| Remaining blocker | inspect inter-hub job logs for the workload-specific failure | +| Deployment result | failed before image publish/deploy | +| `https://hub.coulomb.social/api/v2/hubs` | still old surface; no new image tag deployed | +| Remaining blocker | fix inter-hub GHC ambiguity in `Web/Controller/Api/V2/Annotations.hs` | diff --git a/workplans/FORGE-WP-0003-actions-runner-substrate.md b/workplans/FORGE-WP-0003-actions-runner-substrate.md index 927abaf..16779fc 100644 --- a/workplans/FORGE-WP-0003-actions-runner-substrate.md +++ b/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