chore: cleanup of repository root

.claude/agents/agent-claude-documentation.md

@@ -13,7 +13,7 @@ You are the Claude Code expert, specialized in accessing and interpreting offici
 2. **Feature Guidance**: Provide accurate information about Claude Code capabilities, tools, and workflows
 3. **Configuration Help**: Assist with proper setup and configuration of Claude Code features
 4. **Best Practices**: Share recommended approaches based on official documentation
-5. **Issue Tracking**: Monitor and document Claude Code issues that affect project workflows via RelevantClaudeIssues.md
+5. **Issue Tracking**: Monitor and document Claude Code issues that affect project workflows via history/RelevantClaudeIssues.md
 
 ### Authority and Scope
 
@@ -22,7 +22,7 @@ You have explicit authority to:
 - Fetch information from Claude documentation URLs
 - Interpret and explain Claude Code features and capabilities
 - Provide configuration guidance based on official sources
-- Create and maintain RelevantClaudeIssues.md to track blocking issues
+- Create and maintain history/RelevantClaudeIssues.md to track blocking issues
 - Research GitHub issues affecting Claude Code functionality
 
 ### Documentation Resources
@@ -87,14 +87,14 @@ Note: [Any limitations or uncertainties in the guidance]
 When Claude Code issues are discovered that block intended workflows:
 
 1. **Research Phase**: Search for related GitHub issues and community reports
-2. **Documentation Phase**: Create or update RelevantClaudeIssues.md with:
+2. **Documentation Phase**: Create or update history/RelevantClaudeIssues.md with:
    - Clear problem description and impact on workflow
    - List of related GitHub issue numbers
    - Available workarounds with pros/cons
    - Monitoring instructions for resolution status
 3. **Update Phase**: Regularly check issue status and update documentation
 
-**RelevantClaudeIssues.md Structure:**
+**history/RelevantClaudeIssues.md Structure:**
 ```markdown
 # Relevant Claude Code Issues
 

.claude/agents/agent-project-management.md

@@ -36,7 +36,7 @@ You are the MarkiTect project assistant, specialized in providing project status
 **Issue Management Protocol:**
 - **Gitea-First**: Feature requests, bugs, and enhancements should be documented as Gitea issues
 - **Issue Creation**: When new requirements emerge, create issues in Gitea immediately but do NOT implement immediately
-- **Strategic Planning**: Issues should be prioritized and scheduled based on project roadmap (ROADMAP.md)
+- **Strategic Planning**: Issues should be prioritized and scheduled based on project roadmap (history/ROADMAP.md)
 - **Implementation Discipline**: Only work on issues that are explicitly planned for the current session
 - **Issue Workflow**: Create → Triage → Plan → Schedule → Implement → Close
 

README.md

@@ -18,4 +18,4 @@ MarkiTect transforms markdown from plain text into intelligent, structured data
 
 **Development:** [TDD Workflow](docs/development/tdd-workflow.md) · [Contributing](#contributing)
 
-**Project Status:** [Current Status](ProjectStatusDigest.md) · [Roadmap](ROADMAP.md) · [Next Actions](NEXT.md)
+**Project Status:** [Current Status](history/ProjectStatusDigest.md) · [Roadmap](history/ROADMAP.md) · [Next Actions](NEXT.md)

docs/README.md

@@ -33,8 +33,8 @@ Documentation for contributors and developers extending MarkiTect.
 - [API Documentation](development/api-reference.md) *(coming soon)*
 
 ### Project Management
-- [Project Status](../ProjectStatusDigest.md) - Current development status
-- [Roadmap](../ROADMAP.md) - Strategic development plan
+- [Project Status](../history/ProjectStatusDigest.md) - Current development status
+- [Roadmap](../history/ROADMAP.md) - Strategic development plan
 - [Next Actions](../NEXT.md) - Immediate development priorities
 
 ## Key Concepts