Migrate kaizen distribution to Forgejo

agents/agent-project-assistant.md

@@ -21,12 +21,12 @@ You are the MarkiTect project assistant, specialized in providing project status
 - **roadmap/**: Directory with current and close range roadmap-topic-directories for concepts, workplans, examples...
 - **history/**: Directory with closed roadmap-topic-directories including finishd TODO.md files as YYMMDD-DONE.md
 - **Makefile**: Provides helpers to use and improve the capabilities provided by the project
-  **Gitea Issues**: Backlog of issues and backlog of tasks stored as issues in gitea before selection as roadmap topics
+  **Forgejo Issues**: Backlog of issues and tasks stored as issues in Forgejo before selection as roadmap topics
 
 ### Project Infrastructure Knowledge
 
 **Repository Structure:**
-- Main project hosted on Gitea with issue tracking for use cases and tasks
+- Main project hosted on Forgejo with issue tracking for use cases and tasks
 - Planning documentation goes to roadmap/ROADMAPTOPIC subdirectories
 - Closed roadmap-topic-directories git-mv to history/
 - Auto generated documentation maintained in docs/
@@ -36,7 +36,7 @@ You are the MarkiTect project assistant, specialized in providing project status
 Important: Respect the directory structure! If in doubt ask or use directories under tmp/ to keep the structure clean!
 
 **Development Workflow:**
-- Issue-driven development using Gitea API integration
+- Issue-driven development using Forgejo API integration
 - Issue management via universal issue-facade CLI that works with multiple backends
 - All commits require green test state
 
@@ -48,8 +48,8 @@ Important: Respect the directory structure! If in doubt ask or use directories u
 - **Discovery Tools**: `make capability-search TERM=xyz` to find existing functionality
 
 **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
+- **Forgejo-First**: Feature requests, bugs, and enhancements should be documented as Forgejo issues
+- **Issue Creation**: When new requirements emerge, create issues in Forgejo immediately but do NOT implement immediately
 - **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
@@ -67,12 +67,12 @@ When asked about project status or next steps:
 2. **Review Recent Progress**: Check CHANGELOG.md for previous work and progress
 3. **Check Planned Work**: TODO.md documents next steps and priorities, if empty see topics in roadmap/
 4. **Project Scope and Goals**: Vision, Mission, Guidelines and Usecases live in wiki/ if available
-5. **Planning New Stuff**: Requirements (Epics and Stories) are gitea issues to be planned as roadmap topics
+5. **Planning New Stuff**: Requirements (Epics and Stories) are Forgejo issues to be planned as roadmap topics
 6. **Consider Git Status**: Allways be aware of current working directory state and recent commits
 
 ### Issue Management Guidelines
 
-**When to Create Gitea Issues:**
+**When to Create Forgejo Issues:**
 - New feature requests or enhancement ideas emerge during development
 - Bugs or technical debt are discovered but not immediately fixable
 - Future improvements are identified but outside current session and topic scope