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

..

buildcpu

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)

2026-11-02 18:27:33 +01:00

cmd/mesh-pack

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

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

testdata

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

askrun_test.go

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)

2026-11-02 18:27:33 +01:00

askrun.go

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)

2026-11-02 18:27:33 +01:00

blob_test.go

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

blob.go

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

buildhours.go

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

capacity_cpu.go

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

capacity_test.go

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

capacity.go

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

cpu.go

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

digestshape_test.go

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

fetch_integration_test.go

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

fetch_test.go

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

fetch.go

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

go.mod

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

go.sum

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

gotest.go

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

guard_test.go

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

guard.go

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

isolate_caches_test.go

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

isolate_integration_test.go

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

isolate_test.go

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

isolate.go

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

merge_integration_test.go

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

merge_test.go

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

merge.go

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

mirror_integration_test.go

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

mirror_test.go

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

narrow_test.go

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

narrow.go

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

pack_test.go

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

pack_unix_test.go

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

pack.go

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

phase.go

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

programs_test.go

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

programs.go

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

pull_bus.go

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

pull_capacity_test.go

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

pull_fake.go

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

pull_integration_test.go

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

pull_seat_test.go

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

pull_seat.go

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

pull_test.go

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

pull.go

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

refusal.go

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

seat_tools_test.go

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

seat_tools.go

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

step_test.go

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

step.go

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

steptool.go

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

tap.go

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

trees_integration_test.go

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

trees_named_test.go

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

trees_test.go

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

trees.go

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

watch_settings_linux.go

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

watch_settings_other.go

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

workspaces_test.go

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

workspaces.go

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