chore: reorganize repo — move docs to docs/, clean up root, remove AGENTS.md

- Move heavy docs (COMPATIBILITY, ECOSYSTEM-ROADMAP, FEATURES, PARITY,
  VERSIONING, platform-capabilities.json) to docs/
- Move CODEOWNERS to .github/
- Update all internal references (CONTRIBUTING, SECURITY, AGENTS.md)
- Remove go.work/go.work.sum from tracking, add to .gitignore
- Remove stale AGENTS.md (auto-generated by hawk /agents-init)
- Remove empty unused dirs (countdump, engine/context, engine/error)

Author: Patel230

CODEOWNERS .github/CODEOWNERSCODEOWNERS renamed to .github/CODEOWNERS

@@ -51,3 +51,7 @@ cmd/.hawk/
 testdata/compat-test
 bin/
 .shared-templates/
+
+# Go workspace (local dev only — not committed per AGENTS.md)
+go.work
+go.work.sum

.gitignore

@@ -2,7 +2,7 @@
 
 Thanks for your interest! This guide covers the conventions used across the
 GrayCodeAI repositories. The shared standards (versioning, release tooling, repo layout)
-are defined in <https://github.com/GrayCodeAI/hawk/blob/main/VERSIONING.md>.
+are defined in <https://github.com/GrayCodeAI/hawk/blob/main/docs/versioning.md>.
 
 ## Quick start
 

AGENTS.md

@@ -7,7 +7,7 @@ minor versions once `1.x` ships. Older versions receive critical-severity
 fixes only on a best-effort basis.
 
 The current canonical version is the contents of the [`VERSION`](./VERSION)
-file at the repo root. See [`VERSIONING.md`](https://github.com/GrayCodeAI/hawk/blob/main/VERSIONING.md)
+file at the repo root. See [`docs/versioning.md`](https://github.com/GrayCodeAI/hawk/blob/main/docs/versioning.md)
 for the eco-wide versioning scheme.
 
 ## Reporting a vulnerability

CONTRIBUTING.md

@@ -1,12 +1,12 @@
 # Compatibility Matrix
 
-This eco uses **independent SemVer per repo** (see [VERSIONING.md](./VERSIONING.md)).
+This eco uses **independent SemVer per repo** (see [VERSIONING.md](./docs/versioning.md)).
 That gives each component its own release cadence, but raises an obvious
 question: *which combinations of versions are actually tested together?*
 
 The answer lives in [`testdata/compatibility-matrix.json`](./testdata/compatibility-matrix.json).
 
-Platform/provider capability metadata is separate: [`platform-capabilities.json`](./platform-capabilities.json).
+Platform/provider capability metadata is separate: [`platform-capabilities.json`](./docs/platform-capabilities.json).
 
 ## What it records