The configuration table lists DOCKER_REPO as an override that affects the images deployed to Kind, but the current make install-agentregistry only sets image.registry and image.tag (not image.repository). Either update the Makefile to set image.repository from DOCKER_REPO, or adjust this documentation so it matches the actual behavior.

use-kind-cluster writes a kubeconfig containing client certs/keys to a fixed path in /tmp without setting restrictive permissions or cleaning it up. Use a mktemp file (chmod 600) and remove it after merging to avoid leaking kubeconfig material on multi-user systems.

install-agentregistry hard-codes helm instead of using the Makefile’s HELM variable, and it never sets image.repository. If a developer overrides DOCKER_REPO (as documented in scripts/kind/README.md), the images built/pushed by docker-server won’t match what Helm deploys. Use $(HELM) and pass --set image.repository=$(DOCKER_REPO)/server (or otherwise derive the repository from the same variables used for building).

The Quick Start prerequisites now require a local PostgreSQL+pgvector install, but the default local dev flow (arctl starting the daemon via docker-compose) already runs PostgreSQL in a container (internal/daemon/docker-compose.yml). Consider rewording this prerequisite to clarify that PostgreSQL+pgvector is required for Kubernetes/Helm deployments, not for the default Docker Compose quick start.

KIND_NAMESPACE is presented as configurable, but examples/postgres-pgvector.yaml hard-codes namespace: agentregistry and install-postgresql applies that manifest then waits in -n $(KIND_NAMESPACE). If KIND_NAMESPACE is overridden, the wait will target the wrong namespace and the install will appear to hang/fail. Either make the namespace fixed (remove the override) or template/patch the manifest so it deploys into $(KIND_NAMESPACE) consistently.

If bin/kind is missing and kind is not on PATH, KIND="$(command -v kind)" can resolve to an empty string and the script will later fail with a confusing error. Consider explicitly validating that KIND resolves to an executable and printing a clear install hint before continuing.

${KIND} is executed unquoted here and later in the script. Quoting the command path (and other interpolated variables) avoids word-splitting surprises and makes the script safer if KIND ever contains spaces or additional args.

The help text has a missing space: install-agentregistry- Build... will render as a single word in make help. Update the string to include a space after the target name for readability.

prune-kind-cluster is unlikely to work as written: crictl images --quiet outputs only image IDs (so grep '<none>' | awk '{print $3}' will never match), and xargs -r is not portable (fails on macOS/BSD xargs). Consider using the non-quiet crictl images output to filter dangling images, and avoid -r by guarding the xargs call when the input is empty.

The install-agentregistry target passes the JWT signing key in the helm upgrade command via --set config.jwtPrivateKey="$$JWT_KEY", which exposes this secret in process arguments (e.g., ps output) to other local users while the command runs. A local attacker on the same host could capture this key and forge valid JWTs against the AgentRegistry instance, undermining authentication even after redeploys that reuse the same key. To mitigate this, avoid passing the key on the command line and instead load it from a Kubernetes secret or values file that is not exposed via process arguments.