2 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	350aca05fb	The Go build module says at a build's end which mesh packages its programs import, so a fingerprint can take their content (ADR 0593 §2) ... A build ask whose job built an artifact asks the new step build_go_imports once: `go list -deps` of each Go bundle's program, no tests, the forge's packages outside the module's own directory (a sibling package of the same repository counts), sorted and each once. The answer carries them as BuildAnswer.Imports. The step is also a tool, to read them by hand. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 18:27:33 +01:00
jschoubben	9c57f7afb3	mesh-build-go publishes the build runner as its own package, so the other build modules share it without mesh-sdk (ADR 0593 §1) ... The runner, the toolchain guard, the fetch, the parsers, buildcpu, the conformance kit and mesh-pack move from mesh-sdk's buildstep into modules/mesh-build-go/buildstep (own go.mod). mesh-build-go, mesh-build-node and mesh-build-image require it by a same-repository replace; what the delivery parts read (the failure contract, the fetch request, the stale sweep, the module tree shape, NewID, CapacitySetting) stays imported from mesh-sdk as sdkstep. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 18:22:41 +01:00