The README is the product's front door and carries our brand. NOTICE is where a
fork's provenance is legally required to live, and it is the file a licence audit
reads. Naming the upstream in the README put attribution in the one place nobody
checks for it and branding in a place that had to share.
Where the NOTICE already named the same upstream, the moved line was dropped
rather than duplicated, and markdown link syntax was flattened -- NOTICE is plain
text, not a rendered document.
Co-authored-by: Hanzo Dev <[email protected]>
github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.
Co-authored-by: Hanzo Dev <[email protected]>
1 module(s) in this repo declared go < 1.22. Go 1.22 changed for-loop
variable scoping to per-iteration, so raising the directive past 1.22 can
change runtime behaviour. Each module here was scanned for loops whose
loop variable is captured by a func literal / goroutine / defer, or has its
address taken: zero such sites were found, so the bump is behaviour-preserving.
Verified per module with go build, go vet and go test (-mod=readonly).
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev