Skip to content

feat: rename hawk binary, module, and config surface to graycode - #272

Open
Patel230 wants to merge 5 commits into
mainfrom
feat/rename-hawk-to-graycode
Open

feat: rename hawk binary, module, and config surface to graycode#272
Patel230 wants to merge 5 commits into
mainfrom
feat/rename-hawk-to-graycode

Conversation

@Patel230

@Patel230 Patel230 commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Full hard-break rename of the product surface from hawk to graycode:

  • Binary hawkgraycode (Makefile, goreleaser, Dockerfile, install.sh, npm packages)
  • Module github.com/GrayCodeAI/hawkgithub.com/GrayCodeAI/graycode-cli (matches repo remote)
  • HAWK_*GRAYCODE_* env vars, ~/.hawk~/.graycode, cmd/hawkcmd/graycode, internal/hawkerrinternal/graycodeerr
  • No back-compat shims (hard break, per review)
  • Normalized compounds: GRAYCODE_CODE_*GRAYCODE_*, graycode-code service names→graycode, checkout-dir refs→graycode-cli (ecosystem.yaml, clone/cd docs, contracts-parity script)

Verification: go build ./..., go vet ./..., golangci-lint run ./... (0 issues), scripts/smoke-graycode.sh, contracts/ecosystem/peer/internal-layer/package/eyrie boundary guards — all green.

Binary hawk->graycode, module github.com/GrayCodeAI/hawk->github.com/GrayCodeAI/graycode-cli, HAWK_*->GRAYCODE_* env vars, ~/.hawk->~/.graycode, cmd/hawk->cmd/graycode, internal/hawkerr->internal/graycodeerr. Hard break, no back-compat shims. Normalize GRAYCODE_CODE_*/graycode-code compounds and graycode-cli checkout-dir references.
checkout-eyrie/setup-deps probe before cloning (missing repos warn+skip instead of killing the job); manifest validate skips filesystem checks for absent checkouts (fields/dupes/count stay strict); generate-workspace fixes latent graycode-cli self-skip/init-dir bugs and skips missing dirs. Single-repo CI is an expected mode, not a failure.
GOPRIVATE forced direct-git resolution, which fails for removed repos and bypasses the warm proxy cache (all 5 pinned ghost modules verified proxy-resolvable). Default GOPROXY (proxy first, direct fallback) is strictly more capable. Removed from ci.yml, Dockerfile, Dockerfile.daemon.
Premise disproven: clean-cache probes show proxy.golang.org 404s the eagle/harrier/kestrel/merlin/shrike pins (original fetches were direct-VCS under GOPRIVATE, so the proxy never cached them). Only eyrie resolves via proxy. GOPRIVATE removal changed nothing functionally; reverting to keep the diff truthful. Dead-repo resolution remains an owner-side ecosystem action.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant