docs: adopt AGENTS.md standard for agent instructions

Rename CLAUDE.md to AGENTS.md to align with the community AGENTS.md
convention (https://agents.md/). This standardized format makes the
repository's agent instructions more discoverable and consistent with
other projects using AI coding assistants.

My real motivation here is I want to support other agentic systems
and not having this project hardcoded to Claude Code, which is proprietary
software.

Assisted-by: Claude Code (Sonnet 4.5)
Signed-off-by: Colin Walters <walters@verbum.org>

Author: cgwalters

.claude/CLAUDE.md

@@ -0,0 +1 @@
+../AGENTS.md

.claude/amber-config.yml

@@ -132,7 +132,7 @@ automation_policies:
 # Constitution compliance checks
 constitution_checks:
   enabled: true
-  reference_file: "CLAUDE.md"
+  reference_file: "AGENTS.md"
 
   principles:
     - id: "principle_v_modularity"

.github/ISSUE_TEMPLATE/amber-refactor.yml

@@ -50,7 +50,7 @@ body:
         - Must maintain backward compatibility
         - No breaking changes to API
         - All existing tests must pass
-        - Follow patterns in CLAUDE.md
+        - Follow patterns in AGENTS.md
     validations:
       required: true
 
@@ -70,7 +70,7 @@ body:
     attributes:
       label: Confirmation
       options:
-        - label: I have reviewed CLAUDE.md standards
+        - label: I have reviewed AGENTS.md standards
           required: true
         - label: Backward compatibility is required
           required: true

.github/ISSUE_TEMPLATE/amber-test-coverage.yml

@@ -66,7 +66,7 @@ body:
     attributes:
       label: Confirmation
       options:
-        - label: Tests should follow patterns in CLAUDE.md
+        - label: Tests should follow patterns in AGENTS.md
           required: true
         - label: Table-driven tests for Go, pytest for Python
           required: true

.github/workflows/amber-issue-handler.yml

@@ -134,7 +134,7 @@ jobs:
           ### For `test-coverage` type:
           1. Analyze current test coverage for specified files
           2. Identify untested code paths
-          3. Write contract tests following project standards (see CLAUDE.md)
+          3. Write contract tests following project standards (see AGENTS.md)
           4. Ensure tests follow table-driven test pattern (Go) or pytest patterns (Python)
           5. Verify all new tests pass
 
@@ -146,7 +146,7 @@ jobs:
 
           ## Requirements
 
-          - Follow all standards in `CLAUDE.md`
+          - Follow all standards in AGENTS.md
           - Use conventional commit format: `type(scope): message`
           - Run all linters BEFORE committing:
             - Go: `gofmt -w .`, `golangci-lint run`
@@ -362,7 +362,7 @@ jobs:
             ### Pre-merge Checklist
             - [ ] All linters pass
             - [ ] All tests pass
-            - [ ] Changes follow project conventions (CLAUDE.md)
+            - [ ] Changes follow project conventions (AGENTS.md)
             - [ ] No scope creep beyond issue description
 
             ### Reviewer Notes

.github/workflows/claude-code-review.yml

@@ -90,11 +90,11 @@ jobs:
             Perform a comprehensive code review with the following focus areas:
             
             1. **Code Quality & Best Practices**
-               - Follow repository's CLAUDE.md guidelines
+               - Follow repository's AGENTS.md guidelines
                - Clean code principles and design patterns
                - Proper error handling and edge cases
                - Code readability and maintainability
-               - TypeScript/Go best practices (see CLAUDE.md)
+               - TypeScript/Go best practices (see AGENTS.md)
             
             2. **Security**
                - Potential security vulnerabilities

.specify/memory/constitution.md

@@ -334,7 +334,7 @@ Replace usage of "vTeam" with "ACP" (Ambient Code Platform) where it is safe and
 
 **Incremental Approach**:
 
-- Update documentation first (README, CLAUDE.md, docs/)
+- Update documentation first (README, AGENTS.md, docs/)
 - Update UI text in new features
 - Use ACP naming in new code modules
 - Do NOT perform mass renames - update organically during feature work
@@ -409,7 +409,7 @@ npm run build  # Must pass with 0 errors, 0 warnings
 
 Runtime development guidance is maintained in:
 
-- `/CLAUDE.md` for Claude Code development
+- `/AGENTS.md` for Claude Code development
 - Component-specific README files
 - MkDocs documentation in `/docs`
 

.specify/memory/constitution_update_checklist.md

@@ -10,7 +10,7 @@ When amending the constitution (`/memory/constitution.md`), ensure all dependent
 - [ ] `/templates/tasks-template.md` - Update if new task types needed
 - [ ] `/.claude/commands/plan.md` - Update if planning process changes
 - [ ] `/.claude/commands/tasks.md` - Update if task generation affected
-- [ ] `/CLAUDE.md` - Update runtime development guidelines
+- [ ] `/AGENTS.md` - Update runtime development guidelines
 
 ### Article-specific updates:
 

.specify/scripts/bash/update-agent-context.sh

@@ -58,8 +58,8 @@ eval $(get_feature_paths)
 NEW_PLAN="$IMPL_PLAN"  # Alias for compatibility with existing code
 AGENT_TYPE="${1:-}"
 
-# Agent-specific file paths  
-CLAUDE_FILE="$REPO_ROOT/CLAUDE.md"
+# Agent-specific file paths
+CLAUDE_FILE="$REPO_ROOT/AGENTS.md"
 GEMINI_FILE="$REPO_ROOT/GEMINI.md"
 COPILOT_FILE="$REPO_ROOT/.github/copilot-instructions.md"
 CURSOR_FILE="$REPO_ROOT/.cursor/rules/specify-rules.mdc"