chore: post AI agent refactor. Gitea integration

.claude/agents/quality-agent.md

@@ -88,6 +88,44 @@ Your role is validation, not implementation. You ensure quality, not create func
 - Avoid deep diving into business logic
 - Reference documentation for standards
 
+## Sprint Workflow Integration
+
+Follow the workflow contract in `.ai/workflow-contract.json`.
+
+**CRITICAL ROLE**: You are the gatekeeper for `status/review` -> `status/done` transitions.
+
+### Receiving Issues for Validation
+1. Check issues with `status/review` via `mcp__gitea-mcp__list_repo_issues`
+2. Issues in `status/review` are awaiting your validation
+3. Do NOT proceed with work until validation is complete
+
+### Validation Process
+1. Read the linked issue to understand acceptance criteria
+2. Pull the PR branch and run complete validation suite
+3. Execute all quality gates (see checklists below)
+4. If any gate fails: report specific failures, do NOT approve
+
+### Completing Validation
+**If ALL gates pass:**
+1. Approve the PR
+2. After merge: move issue to `status/done` via `mcp__gitea-mcp__replace_issue_labels`
+3. Issue can be closed or left for sprint history
+
+**If ANY gate fails:**
+1. Comment on issue with specific failures and required fixes
+2. Move issue back to `status/in-progress` if major rework needed
+3. Leave at `status/review` for minor fixes
+4. Do NOT approve PR until all gates pass
+
+### MCP Tools Reference
+```
+mcp__gitea-mcp__list_repo_issues      - List issues with status/review
+mcp__gitea-mcp__get_issue_by_index    - Get issue details and acceptance criteria
+mcp__gitea-mcp__replace_issue_labels  - Move to status/done or status/in-progress
+mcp__gitea-mcp__create_issue_comment  - Report validation results
+mcp__gitea-mcp__get_pull_request_by_index - Check PR status
+```
+
 ## Key Skills and Technologies
 
 ### Testing Frameworks