docs: Update AGENTS.md and README.md for current project state

AGENTS.md:
- Add setup section (make init, pre-commit hooks)
- Fix k8s client-go version (v0.25 → v0.35)
- Fix Docker runtime image reference (distroless/static:nonroot)
- Add go fix convention

README.md:
- Fix run command (go run . → go run ./cmd/agent)
- Add make init to first-time setup instructions

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: philprime

AGENTS.md

@@ -54,13 +54,19 @@ Co-Authored-By: (the agent model's name and attribution byline)
 - Enhancers enrich Sentry events with K8s metadata
 - Supports custom DSNs via `k8s.sentry.io/dsn` annotation
 
+## Setup
+
+- First-time setup: `make init` (installs Brew deps, Go modules, pre-commit hooks)
+- Pre-commit hooks run: build, test, go fix, vet, lint, and dprint formatting
+
 ## Key Conventions
 
 - Logging: `github.com/rs/zerolog`
-- K8s client: `k8s.io/client-go` v0.25
+- K8s client: `k8s.io/client-go` v0.35
 - Error reporting: `github.com/getsentry/sentry-go`
-- Docker: multi-stage build, `gcr.io/distroless/static-debian12` runtime
+- Docker: multi-stage build, `gcr.io/distroless/static:nonroot` runtime
 - RBAC: read-only (`watch`, `list`, `get` only)
+- Run `go fix ./...` to apply Go modernizations (also in pre-commit)
 
 ## Environment Variables
 

README.md

@@ -185,13 +185,13 @@ In the Sentry Crons tab of the corresponding project, we may see the following:
 
    b. Pass a valid Sentry DSN to an environment variable named `SENTRY_DSN` ([https://docs.sentry.io/product/sentry-basics/concepts/dsn-explainer/](https://docs.sentry.io/product/sentry-basics/concepts/dsn-explainer/))
 
-   c. At the root of the repository directory, build the Go module with the command
+   c. At the root of the repository directory, initialize the project and build
 
-   `make build`
+   `make init && make build`
 
    d. Run the module outside of the k8s cluster by executing the command
 
-   `go run .`
+   `go run ./cmd/agent`
 
    which now starts up the process that automatically detects the cluster configuration in order to detect events