refactor: Standardize agent naming convention with 'agent-' prefix

Implemented consistent naming convention for all Claude Code agents:
- Prefix: All agents now start with 'agent-'
- Format: agent-[function]-[specialty].md
- Descriptive: 2-3 words describing primary purpose

Agent Renames:
• claude-expert.md → agent-claude-documentation.md
• fortune-wisdom-guide.md → agent-wisdom-encouragement.md
• kaizen-optimizer.md → agent-kaizen-optimization.md
• priority-assistant.md → agent-priority-evaluation.md
• project-assistant.md → agent-project-management.md
• refactoring-assistant-optimized.md → agent-code-refactoring.md
• repository-assistent.md → agent-repository-structure.md
• tddai-assistant.md → agent-tdd-workflow.md
• test-fixing-agent.md → agent-test-maintenance.md
• tooling-optimizer.md → agent-tooling-optimization.md

Updated References:
- ProjectDiary.md: Updated agent references to new names
- RelevantClaudeIssues.md: Updated agent tracking references

Benefits:
- Improved discoverability with consistent prefix
- Clear functional categorization
- Better organization and maintenance
- Enhanced readability for development team

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

history/ProjectDiary.md

@@ -182,7 +182,7 @@ This diary tracks major work packages, events, and milestones in the MarkiTect p
 **Time Estimate:** ~1-2 hours of refactoring and test cleanup
 **AI Resources:** ~15-20 Claude Sonnet 4 conversations, estimated 30K+ tokens
 
-**FRAMEWORK MATURITY:** Successfully transformed tddai from a MarkiTect-specific tool into a truly project-agnostic Test-Driven Development framework. Removed all MarkiTect-specific references from core tddai modules (`coverage_analyzer.py`, `config.py`, `tddai_cli.py`) and updated the tddai-assistant agent definition to use generic examples applicable to any software project. The framework now uses configurable environment variables (`TDDAI_WORKSPACE_DIR`, `TDDAI_GITEA_URL`, `TDDAI_REPO_OWNER`, `TDDAI_REPO_NAME`) allowing deployment across different projects and platforms.
+**FRAMEWORK MATURITY:** Successfully transformed tddai from a MarkiTect-specific tool into a truly project-agnostic Test-Driven Development framework. Removed all MarkiTect-specific references from core tddai modules (`coverage_analyzer.py`, `config.py`, `tddai_cli.py`) and updated the agent-tdd-workflow agent definition to use generic examples applicable to any software project. The framework now uses configurable environment variables (`TDDAI_WORKSPACE_DIR`, `TDDAI_GITEA_URL`, `TDDAI_REPO_OWNER`, `TDDAI_REPO_NAME`) allowing deployment across different projects and platforms.
 
 **CONFIGURATION SYSTEM:** Implemented flexible project configuration system that defaults to sensible generic values while supporting per-project customization. Created `.env.tddai` and `tddai-setup.sh` for MarkiTect-specific configuration, demonstrating how any project can configure tddai for their needs. The configuration system validates required fields while maintaining clean separation between framework defaults and project-specific settings.
 
@@ -203,11 +203,11 @@ This diary tracks major work packages, events, and milestones in the MarkiTect p
 
 **SIDEQUEST ACHIEVEMENT:** Successfully implemented IssueWriter functionality that emerged as a natural sidequest during development work. Created `tddai/issue_writer.py` with comprehensive authenticated PATCH capabilities for updating Gitea issues via API. Implementation includes full authentication support via `GITEA_TOKEN` environment variable, robust error handling for API failures and authentication issues, and clean API design with specific methods for updating titles, bodies, and issue states. Added 13 comprehensive tests in `tests/test_issue_writer.py` covering all authentication scenarios, PATCH operations, error conditions, and edge cases. All tests pass and integrate seamlessly with existing 45+ test suite.
 
-**METHODOLOGY BREAKTHROUGH:** Formalized the project's actual development workflow as the **TDD8 cycle** - a comprehensive 8-step methodology extending traditional TDD: **ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH**. This framework captures the complete transformation from requirements to production-ready functionality. Created comprehensive tddai-assistant subagent (.claude/agents/tddai-assistant.md) with detailed guidance for each TDD8 step, sophisticated sidequest management strategies, and project-specific knowledge including workspace management, Gitea integration, and test coverage standards.
+**METHODOLOGY BREAKTHROUGH:** Formalized the project's actual development workflow as the **TDD8 cycle** - a comprehensive 8-step methodology extending traditional TDD: **ISSUE-TEST-RED-GREEN-REFACTOR-DOCUMENT-REFINE-PUBLISH**. This framework captures the complete transformation from requirements to production-ready functionality. Created comprehensive agent-tdd-workflow subagent (.claude/agents/agent-tdd-workflow.md) with detailed guidance for each TDD8 step, sophisticated sidequest management strategies, and project-specific knowledge including workspace management, Gitea integration, and test coverage standards.
 
 **WORKFLOW ENHANCEMENT:** The TDD8 framework addresses the reality that development involves more than just RED-GREEN-REFACTOR cycles. It includes upfront issue analysis (ISSUE), comprehensive test design (TEST), traditional TDD core (RED-GREEN-REFACTOR), and crucial production-readiness steps (DOCUMENT-REFINE-PUBLISH). Integrated sidequest management recognizes that blocking and supporting sidequests naturally emerge at different cycle phases and provides specific strategies for each scenario.
 
-**INFRASTRUCTURE MATURITY:** This session demonstrates the project's evolution from basic TDD to a sophisticated development methodology. The IssueWriter implementation showcases clean separation of concerns, comprehensive test coverage, and proper integration patterns. The tddai-assistant provides authoritative guidance for maintaining these standards while adapting to the dynamic nature of software development through intelligent sidequest management.
+**INFRASTRUCTURE MATURITY:** This session demonstrates the project's evolution from basic TDD to a sophisticated development methodology. The IssueWriter implementation showcases clean separation of concerns, comprehensive test coverage, and proper integration patterns. The agent-tdd-workflow provides authoritative guidance for maintaining these standards while adapting to the dynamic nature of software development through intelligent sidequest management.
 
 ---