chore: apply template consistency updates from PRs #65-#77

- Rename agent files to match template naming convention (.agent.md suffix)
  - requirements-agent.md → requirements.agent.md
  - software-developer.md → software-developer.agent.md
  - technical-writer.md → technical-writer.agent.md
  - test-developer.md → test-developer.agent.md
- Add tools: frontmatter field to agent files (PR #73)
  - code-review.agent.md: tools: [read, search, edit, execute, github, web, agent]
  - repo-consistency.agent.md: tools: [read, search, edit, execute, github, agent]
  - requirements.agent.md: tools: [read, search, edit, execute, github, web, agent]
  - software-developer.agent.md: tools: [read, search, edit, execute, github, agent]
  - technical-writer.agent.md: tools: [read, search, edit, execute, github, agent]
  - test-developer.agent.md: tools: [read, search, edit, execute, github, agent]
- Update AGENTS.md to align with template
  - Rename 'Project Structure' section to 'Project Structure Template'
  - Update 'Continuous Compliance Requirements' section ending to match template

Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>

.github/agents/code-review.agent.md

@@ -1,6 +1,7 @@
 ---
 name: code-review
 description: Agent for performing formal reviews
+tools: [read, search, edit, execute, github, web, agent]
 user-invocable: true
 ---
 

.github/agents/repo-consistency.agent.md

@@ -3,6 +3,7 @@ name: repo-consistency
 description: >
   Ensures downstream repositories remain consistent with the TemplateDotNetTool
   template patterns and best practices.
+tools: [read, search, edit, execute, github, agent]
 user-invocable: true
 ---
 

.github/agents/requirements-agent.md → .github/agents/requirements.agent.md

@@ -1,6 +1,7 @@
 ---
 name: Requirements Agent
 description: Develops requirements and ensures appropriate test coverage - knows which requirements need unit/integration/self-validation tests
+tools: [read, search, edit, execute, github, web, agent]
 ---
 
 # Requirements Agent - BuildMark

.github/agents/software-developer.md → .github/agents/software-developer.agent.md

@@ -1,6 +1,7 @@
 ---
 name: Software Developer
 description: Writes production code and self-validation tests - targets design-for-testability and literate programming style
+tools: [read, search, edit, execute, github, agent]
 ---
 
 # Software Developer - BuildMark

.github/agents/technical-writer.md → .github/agents/technical-writer.agent.md

@@ -1,6 +1,7 @@
 ---
 name: Technical Writer
 description: Ensures documentation is accurate and complete - knowledgeable about regulatory documentation and special document types
+tools: [read, search, edit, execute, github, agent]
 ---
 
 # Technical Writer - BuildMark

.github/agents/test-developer.md → .github/agents/test-developer.agent.md

@@ -1,6 +1,7 @@
 ---
 name: Test Developer
 description: Writes unit and integration tests following AAA pattern - clear documentation of what's tested and proved
+tools: [read, search, edit, execute, github, agent]
 ---
 
 # Test Developer - BuildMark

AGENTS.md

@@ -151,7 +151,7 @@ Continuous Compliance <https://github.com/demaconsulting/ContinuousCompliance>.
 - **Source filters are critical** - Platform/framework requirements need specific test evidence
 
 For detailed requirements format, test linkage patterns, and ReqStream
-integration, see the Requirements and Test Source Filters sections below.
+integration, call the @developer agent with requirements management context.
 
 ## Tech Stack
 
@@ -207,7 +207,7 @@ ensures the CI evidence comes specifically from the required environment.
 - **String Formatting**: Use interpolated strings ($"") for clarity
 - **No code duplication**: Extract to properties/methods
 
-## Project Structure
+## Project Structure Template
 
 - `docs/` - Documentation and compliance artifacts
   - `reqstream/` - Per-software-unit, platform, and OTS requirements YAML files (included by root `requirements.yaml`)