chore!: rename graycode back to hawk (#301)

* chore!: rename graycode back to hawk

The GitHub repository is GrayCodeAI/hawk again, so the module, binary and
config surface follow it: github.com/GrayCodeAI/hawk, hawk binary, HAWK_*
env vars, ~/.hawk, cmd/hawk, internal/hawkerr, npm/hawk*. The router
dependency is github.com/GrayCodeAI/eyrie again (Eyrie* types,
eyrieengine, EYRIE_* env vars).

graycode-skills, graycode-platform, graycode-cloud and the
graycode-cloud.graph/v1 schema keep their names. Hard break with no
~/.graycode migration. Module-mode builds need a new eyrie release: the
eyrie v0.0.1 tag declares the graycode-router module path.


* refactor!: drop legacy config fallbacks and rename leftovers

ProviderConfigPath mirrors Eyrie's resolution (EYRIE_CONFIG_DIR, then the
user config dir under eyrie) instead of falling back to HAWK_CONFIG_DIR,
and the safety checks no longer block the retired
HAWK_CONFIG_DIR/provider.json path. Removes the graycode rename plan and
the rename narrative in CHANGELOG, fixes the EcosystemReport.Eyre field
name, and updates docs that described the compatibility fallback.


* build(deps): require github.com/GrayCodeAI/eyrie v0.3.0

v0.3.0 is the first eyrie release whose go.mod declares
github.com/GrayCodeAI/eyrie after the rename back from graycode-router.
v0.0.1 declared the old path, which broke every CI job that resolves
modules without the local go.work.


* build(deps): require github.com/GrayCodeAI/eyrie v0.6.0

eyrie v0.3.0 was already recorded in the Go module proxy and checksum
database (May 2026, old module path github.com/hawk/eyrie), so every CI
job that resolved it failed with a checksum mismatch. v0.6.0 is the
rename-back release; its go.sum hashes match sum.golang.org.


---------

Author: Patel230

.dockerignore

@@ -5,8 +5,8 @@
 .factory
 Dockerfile
 .dockerignore
-graycode_bin
-graycode_test_bin
+hawk_bin
+hawk_test_bin
 coverage.out
 coverage.html
 go.work

.env.example

@@ -1,10 +1,10 @@
-# graycode daemon environment variables — copy to .env and fill in.
-# Only GRAYCODE_DAEMON_API_KEY is consumed from the environment.
-GRAYCODE_DAEMON_API_KEY=
+# hawk daemon environment variables — copy to .env and fill in.
+# Only HAWK_DAEMON_API_KEY is consumed from the environment.
+HAWK_DAEMON_API_KEY=
 
-# The following are NOT read by graycode-cli — setting them has no effect:
-#   GRAYCODE_DAEMON_PORT / GRAYCODE_DAEMON_HOST — daemon binds 127.0.0.1:4590;
-#     override with the --host / --port flags (see `graycode daemon start --help`)
-#   GRAYCODE_ROUTER_API_KEY / GRAYCODE_ROUTER_BASE_URL, HARRIER_API_KEY / HARRIER_ADDR —
+# The following are NOT read by hawk — setting them has no effect:
+#   HAWK_DAEMON_PORT / HAWK_DAEMON_HOST — daemon binds 127.0.0.1:4590;
+#     override with the --host / --port flags (see `hawk daemon start --help`)
+#   EYRIE_API_KEY / EYRIE_BASE_URL, HARRIER_API_KEY / HARRIER_ADDR —
 #     consumed by sibling services, not by this binary
 # See docs/user-guide/05-configuration.md for the full precedence chain.

.github/CODEOWNERS

@@ -1,4 +1,4 @@
-# CODEOWNERS for graycode
+# CODEOWNERS for hawk
 #
 # These owners will be the default owners for everything in the repo. Unless
 # a later match takes precedence, they will be requested for review when

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -11,15 +11,15 @@ body:
         of the form as you can — the more we know, the faster we can fix it.
 
         Before submitting:
-        - Search [existing issues](https://github.com/GrayCodeAI/graycode-cli/issues) to avoid duplicates.
+        - Search [existing issues](https://github.com/GrayCodeAI/hawk/issues) to avoid duplicates.
         - If this is a security issue, please **do not** file a public issue. See `SECURITY.md`.
 
   - type: textarea
     id: what-happened
     attributes:
       label: What happened?
       description: A clear, concise description of the bug.
-      placeholder: When I run `graycode ...`, I expected X but got Y.
+      placeholder: When I run `hawk ...`, I expected X but got Y.
     validations:
       required: true
 
@@ -29,7 +29,7 @@ body:
       label: Steps to reproduce
       description: Minimal steps that reliably reproduce the problem.
       placeholder: |
-        1. Run `graycode ...`
+        1. Run `hawk ...`
         2. Type `...`
         3. See error `...`
     validations:
@@ -44,10 +44,10 @@ body:
       required: true
 
   - type: input
-    id: graycode-version
+    id: hawk-version
     attributes:
-      label: graycode version
-      description: Output of `graycode version` (or `graycode --version`).
+      label: hawk version
+      description: Output of `hawk version` (or `hawk --version`).
       placeholder: "0.1.0"
     validations:
       required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
   - name: Security vulnerability
-    url: https://github.com/GrayCodeAI/graycode-cli/security/advisories/new
+    url: https://github.com/GrayCodeAI/hawk/security/advisories/new
     about: Please report security issues privately via a GitHub Security Advisory. See SECURITY.md.
   - name: Question / discussion
-    url: https://github.com/GrayCodeAI/graycode-cli/discussions
+    url: https://github.com/GrayCodeAI/hawk/discussions
     about: Have a question or want to discuss an idea? Open a discussion instead of an issue.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,35 +1,35 @@
 name: Feature request
-description: Suggest an improvement or new capability for graycode.
+description: Suggest an improvement or new capability for hawk.
 title: "feat: <one-line summary>"
 labels: ["enhancement", "triage"]
 
 body:
   - type: markdown
     attributes:
       value: |
-        Thanks for proposing a feature. graycode is built **for developers first**
+        Thanks for proposing a feature. hawk is built **for developers first**
         (one machine, local config, keychain credentials) — teams and enterprise
         come later. We evaluate every request against: _"would a single
         developer on their own machine benefit from this?"_
 
         Before submitting:
-        - Search [existing issues](https://github.com/GrayCodeAI/graycode-cli/issues) to avoid duplicates.
+        - Search [existing issues](https://github.com/GrayCodeAI/hawk/issues) to avoid duplicates.
         - For large changes, consider opening a discussion first.
 
   - type: textarea
     id: problem
     attributes:
       label: What problem are you trying to solve?
       description: Describe the user problem first. Solutions can come later.
-      placeholder: When I'm doing X, graycode makes me do Y, which is painful because Z.
+      placeholder: When I'm doing X, hawk makes me do Y, which is painful because Z.
     validations:
       required: true
 
   - type: textarea
     id: proposal
     attributes:
       label: Proposed solution
-      description: How would you like graycode to behave? CLI flags, output, config, etc.
+      description: How would you like hawk to behave? CLI flags, output, config, etc.
     validations:
       required: true
 
@@ -55,7 +55,7 @@ body:
     id: principles
     attributes:
       label: Developer fit
-      description: graycode avoids enterprise scope for now. Confirm this feature respects that.
+      description: hawk avoids enterprise scope for now. Confirm this feature respects that.
       options:
         - label: Works with zero configuration (sensible defaults).
         - label: Works offline / does not require a cloud account.

…ions/checkout-graycode-router/action.yml .github/actions/checkout-eyrie/action.yml.github/actions/checkout-graycode-router/action.yml renamed to .github/actions/checkout-eyrie/action.yml .github/actions/checkout-graycode-router/action.yml renamed to .github/actions/checkout-eyrie/action.yml

@@ -1,5 +1,5 @@
 name: Checkout ecosystem
-description: Clone graycode-eco sibling repos into the workspace parent for graycode's go.work
+description: Clone graycode-eco sibling repos into the workspace parent for hawk's go.work
 
 inputs:
   ref:
@@ -24,7 +24,7 @@ runs:
         # ecosystem migration; downstream guards skip absent checkouts too).
         ws_parent="$(cd "${GITHUB_WORKSPACE}/.." && pwd)"
         while IFS= read -r repo; do
-          [ "$repo" = graycode-cli ] && continue
+          [ "$repo" = hawk ] && continue
           dest="${ws_parent}/${repo}"
           if [ -d "$dest/.git" ]; then
             echo "$repo already present at $dest"