Refactor IssueHandler from supervisor to issue_verification_agent

Makefile

@@ -283,6 +283,14 @@ process-erratum:
 	$(COMPOSE_SUPERVISOR) run --rm \
 		supervisor python -m ymir.supervisor.main $(DEBUG_FLAG) $(IGNORE_NEEDS_ATTENTION_FLAG) $(DRY_RUN_FLAG) process-erratum $(ERRATA_ID)
 
+.PHONY: run-issue-verification-agent-standalone
+run-issue-verification-agent-standalone:
+	$(COMPOSE_AGENTS) run --rm \
+		-e JIRA_ISSUE=$(JIRA_ISSUE) \
+		-e DRY_RUN=$(DRY_RUN) \
+		-e IGNORE_NEEDS_ATTENTION=$(IGNORE_NEEDS_ATTENTION) \
+		issue-verification-agent
+
 .PHONY: run-preliminary-testing-agent-standalone
 run-preliminary-testing-agent-standalone:
 	$(COMPOSE_AGENTS) run --rm \

README-agents.md

@@ -11,6 +11,7 @@ Three agents process tasks through Redis queues:
 - **Triage Agent**: Analyzes JIRA issues and determines resolution path. It uses title, description, fields, and comments to find out root cause of the issue. It can ask for clarification, create tasks for other agents or may take no action if not needed.
 - **Rebase Agent**: Updates packages to newer upstream versions. A Rebase is only to be chosen when the issue explicitly instructs you to "rebase" or "update". It looks for upstream references that are linked, attached and present in the description or comments in the issue.
 - **Backport Agent**: Applies specific fixes/patches to packages. It looks for patches that are linked, attached and present in the description or comments in the issue. It tries to apply the patch and resolve any conflicts that may arise during the backport process.
+- **Issue Verification Agent**: Manages the post-fix lifecycle of a JIRA issue — from merged MR through errata creation, testing analysis, and status transitions to RELEASE_PENDING. Migrated from the supervisor's `IssueHandler`.
 
 
 ## Dry run mode

README-supervisor.md

@@ -38,6 +38,10 @@ This will have to be repeated when the ticket expires. (Exporting the kcm-cache
 socket to the container seems better, but I wasn't able to get it to work due
 to various difficult to work around permission issues.)
 
+## Note on IssueHandler migration
+
+The `IssueHandler` has been migrated to `ymir/agents/issue_verification_agent.py` as part of the BeeAI Framework refactoring. The supervisor still handles errata processing via `ErratumHandler`. For processing individual issues, prefer using the new agent directly (see README-agents.md).
+
 ## Processing a single issue or erratum
 
 To process a single issue or erratum, you can run:

agents_as_skills/README.md

@@ -16,6 +16,24 @@ This directory contains Ymir workflows packaged as **AI coding assistant skills*
 
 For installation instructions (skill setup and MCP tool configuration), see the [Skills Installation Guide](https://github.com/packit/ai-workflows/blob/main/skills_installation.md).
 
+## Available skills
+
+- `backport/` — Backport fix agent
+- `preliminary_testing/` — Preliminary testing agent
+- `rebase/` — Rebase fix agent
+- `rebuild/` — Rebuild agent
+- `triage/` — Triage agent
+- `issue_verification/` — Issue verification agent (post-fix lifecycle management)
+
+## Available skills
+
+- `backport/` — Backport fix agent
+- `preliminary_testing/` — Preliminary testing agent
+- `rebase/` — Rebase fix agent
+- `rebuild/` — Rebuild agent
+- `triage/` — Triage agent
+- `issue_verification/` — Issue verification agent (post-fix lifecycle management)
+
 ## How to build
 
 ```bash

compose.yaml

@@ -164,6 +164,13 @@ services:
     command: ["python", "-m", "ymir.agents.preliminary_testing_agent"]
     profiles: ["agents"]
 
+  issue-verification-agent:
+    <<: *beeai-agent-c10s
+    environment:
+      <<: *beeai-env
+    command: ["python", "-m", "ymir.agents.issue_verification_agent"]
+    profiles: ["agents"]
+
   triage-agent-e2e-tests:
     <<: *beeai-agent-c10s
     environment: