jschoubben cfde90906f mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966) ...

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

2026-11-05 16:06:24 +01:00

..

captured

mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1)

2026-11-02 18:22:41 +01:00

conformance_test.go

mesh-build-go: the imports the move added sit in the module group (B5i; issue 1966)

2026-11-05 16:06:24 +01:00

conformance.go

Build, image, node, distribution and gitea take parts, buildstep and composer from mesh-delivery-sdk; seatgen's client check allows a client's own packages and its -go-module has no root default; the build module writes its finding through the conditions client (K-4..K-20 part; ADR 0634 §3, §4, ADR 0635 §4; issue 1966)

2026-11-05 14:31:04 +01:00

leftrunning.go

mesh-build-go runs its asks on the Delivery SDK's neutral build ask, step and answer forms instead of mesh-sdk's go/delivery: the Puller takes buildstep.StepAsk (the read bridge is the form's own AskAs), the toolchains value is the build runner's own, the stale-step part is buildrun's, keys and values come from the seats and clients (B5i; ADR 0634 §1, §6; issue 1966)

2026-11-05 16:05:34 +01:00