docs: Add comprehensive development process workflow to AICodingAgent.md (issue #41) (#43)

This commit extends the guidelines document with a detailed step-by-step workflow
that coding agents should follow throughout the development lifecycle. The workflow
covers the complete cycle from branch creation through PR merge and cleanup,
ensuring consistent development practices.

Key additions:
- 9-step development workflow section
- Branch naming conventions
- Review cycle iteration process
- Post-merge cleanup instructions

This structured approach helps maintain code quality and consistency across all
contributions by providing clear guidance on the expected development process.

Co-authored-by: florath-ai-assistant[bot] <Andreas.Florath@telekom.de>

Author: coding-ai-assistant[bot]

AICodingAgent.md

@@ -7,7 +7,62 @@
 
 ---
 
-## 1. Before Making ANY Changes (MANDATORY)
+## 1. Development Process Workflow
+
+Follow this process for ALL development work:
+
+### Step-by-Step Workflow
+
+1. **Start from main branch**
+   ```bash
+   git checkout main
+   git pull origin main
+   ```
+
+2. **Identify the task**
+   - Observe what needs to be done (typically: resolve an issue)
+   - Review the issue details and requirements
+
+3. **Create a feature branch**
+   ```bash
+   git checkout -b fix-issue-<number>  # or feat-<description>
+   ```
+
+4. **Develop, fix, and test**
+   - Make your changes following all coding standards
+   - Write or update tests as needed
+   - Test locally during development
+
+5. **Run all tests**
+   ```bash
+   bash scripts/run-quality-checks.sh
+   ```
+   - ALL checks MUST pass before proceeding
+
+6. **Commit your changes**
+   - Follow conventional commit format (see section 4 below)
+   - Write clear commit messages explaining WHY
+
+7. **Create a Pull Request**
+   - Push your branch to GitHub
+   - Create PR with proper description (see section 4 below)
+   - Link the PR to the issue
+
+8. **Review cycle**
+   - Human reviewer will provide feedback
+   - If there are comments or requested changes: **Go back to step 4**
+   - Address all feedback and repeat steps 4-7 as needed
+
+9. **Post-merge cleanup**
+   - After PR is merged, run cleanup script:
+   ```bash
+   ./scripts/post-pr-merge.sh
+   ```
+   - This cleans up everything locally and prepares for next task
+
+---
+
+## 2. Before Making ANY Changes (MANDATORY)
 
 Read and follow ALL standards in:
 
@@ -24,7 +79,7 @@ Also:
 
 ---
 
-## 2. Pre-Commit Workflow (MANDATORY)
+## 3. Pre-Commit Workflow (MANDATORY)
 
 Before ANY commit, run:
 
@@ -40,7 +95,7 @@ bash scripts/run-quality-checks.sh
 
 ---
 
-## 3. Commit and PR Format
+## 4. Commit and PR Format
 
 ### Commits
 
@@ -64,7 +119,7 @@ Include:
 
 ---
 
-## Summary Checklist
+## 5. Summary Checklist
 
 ✅ **DO:**
 1. Read all `dev-notes/` documentation first