chore: simplify AGENTS.md / CLAUDE.md (#3692)

Removes redundant and verbose sections from `AGENTS.md` and `CLAUDE.md`
to keep the agent instructions concise.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated repository contribution guidance to reflect the Go workspace
setup and `make`-based workflows.
* Standardized pre-commit checks to use `make fmt`, `make lint`, and
`make test`.
* Clarified commit signing requirements and now call for signed commits.
* Consolidated one guidance file into a single reference to the main
repository instructions.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: dmihalcik-virtru

AGENTS.md

@@ -2,10 +2,11 @@
 
 ## Project Structure & Module Organization
 
-This repo is a Go workspace (`go.work`) containing multiple Go modules:
+This repo is a Go workspace (`go.work`) containing multiple Go modules, built using make.
 
 - `service/`: main OpenTDF server and platform services (binary entrypoint: `service/main.go`).
 - `sdk/`: Go SDK and generated clients.
+- `otdfctl/`: Command line for interacting with server, providing CLI for all SDK operations.
 - `lib/*/`: shared libraries (e.g., `lib/ocrypto`, `lib/identifier`).
 - `protocol/` and `service/`: protobuf sources; generated Go lives under `protocol/go/` and docs under `docs/grpc/` + `docs/openapi/`.
 - `tests-bdd/`: BDD/integration-style tests (Godog) and feature files (`tests-bdd/features/`).
@@ -26,22 +27,21 @@ Prefer `make` targets at repo root:
 - Go formatting is enforced: run `make fmt` (uses `golangci-lint fmt`; Go uses tabs for indentation).
 - Imports should be goimports-compatible; keep package names lowercase; exported identifiers use `PascalCase`.
 - Protobuf changes must pass `buf lint` and should be regenerated via `make proto-generate`.
-- Always run `gofumpt` on Go files after making changes
-- The project uses `gofumpt` (stricter than `gofmt`) for formatting
-- Before completing Go-related tasks, run: `~/go/bin/gofumpt -w <files>`
+- Always run `make fmt` on Go files after making changes.
+- Always use signed commits with 'conventional commit' messages.
 
 ## Testing Guidelines
 
 ### Required Tests Before Committing
 
 **CRITICAL**: All Go code changes must pass these checks before being marked as complete:
 
-1. **Linting**: `golangci-lint run ./path/to/changed/files.go`
-   - Must pass with 0 issues
+1. **Linting**: `make lint`
+   - Must pass with 0 new issues
    - Fixes common issues: formatting, shadowing, unused code, suspicious constructs
    - Never let the user discover linting issues from CI
 
-2. **Unit Tests**: `go test ./...` (or `make test` from repo root)
+2. **Unit Tests**: `make test` from repo root
    - All existing tests must continue to pass
    - Add tests for new functionality
 
@@ -59,7 +59,7 @@ Prefer `make` targets at repo root:
 ## Commit & Pull Request Guidelines
 
 - Commit messages follow Conventional Commits (e.g., `feat(sdk): ...`, `fix(core): ...`).
-- DCO sign-off is required: use `git commit -s -m "feat(scope): summary"`. See `CONTRIBUTING.md`.
+- DCO sign-off is required: use `git commit -S -s -m "feat(scope): summary"` (`-S` = cryptographic signing, `-s` = DCO). See `CONTRIBUTING.md`.
 - PRs should describe changes, include testing notes, and update docs/tests when applicable (see `.github/pull_request_template.md`).
 
 ## Security & Configuration Tips

CLAUDE.md

@@ -1,43 +1 @@
-# Claude Code Instructions
-
-## Overview
-
-This file provides instructions for AI agents working on the OpenTDF Platform codebase.
-
-**For complete repository guidelines, coding standards, and development workflow, see [AGENTS.md](AGENTS.md).**
-
-## Critical Requirements
-
-### Before Completing ANY Go Code Changes
-
-**MANDATORY CHECKS** - Run these before marking work as complete:
-
-1. **Linting**: `golangci-lint run ./path/to/changed/files.go`
-   - Must pass with 0 issues
-   - User should NEVER discover linting issues from CI
-
-2. **Unit Tests**: `go test ./...` or `make test`
-   - All existing tests must pass
-   - Add tests for new functionality
-
-3. **README Tests** (if SDK changes): `cd sdk && go test -run TestREADMECodeBlocks`
-   - Ensures documentation examples remain compilable
-
-### Formatting
-
-- Run `gofumpt -w <files>` on all changed Go files before completing
-- Use tabs for indentation (Go standard)
-
-### Key Guidelines from AGENTS.md
-
-- **Project Structure**: Go workspace with multiple modules (service, sdk, lib/*)
-- **Build Commands**: Use `make` targets (build, test, lint, fmt)
-- **Commit Style**: Conventional Commits with DCO sign-off (`git commit -s`)
-- **Testing**: Unit tests, BDD tests, integration tests - see AGENTS.md for details
-
-## Remember
-
-✅ Run linting checks proactively - don't let CI catch issues
-✅ Test changes locally before marking complete
-✅ Follow patterns and conventions in AGENTS.md
-✅ Update documentation when changing APIs
+@AGENTS.md