kami
fb8b470f78
`make test` failed with `go: no such tool "covdata"` on the two packages that have no test files (cmd/mavenclient, cmd/mavend/seedtest), even though every package passed. A permanently-red test target trains you to ignore the exit code, which is the signal protecting the whole suite. The cause was not a truncated download. Go >=1.24 ships only 7 prebuilt GOROOT tools; covdata, pprof, test2json, nm, objdump and trace ship as source and are built on demand. `go tool covdata` has that build-on-demand fallback, but the `-coverprofile` merge path goes through base.Tool(), which only stats pkg/tool and exits. deps/go was go1.23.4 against a `go 1.25.5` directive, so GOTOOLCHAIN=auto re-exec'd into a downloaded toolchain module and inherited the gap. deps/go now holds a checksum-verified go1.25.5 with those 8 tools built in from its own source. Pin GOTOOLCHAIN=local so a future go.mod bump cannot silently re-exec into a tool-poor module toolchain again, and add a deps-go target so the install is reproducible rather than hand-placed — which was the point of vendoring it. pprof works now too, which matters on a latency-sensitive box. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X5JApcrCRVGmqrxnhynSik