Improve instructions about no-action resolution for triaging

Author: lbarcziova

beeai/agents/triage_agent.py

@@ -106,6 +106,9 @@ def prompt(self) -> str:
           You are an agent tasked to analyze Jira issues for RHEL and identify the most efficient path to resolution,
           whether through a version rebase, a patch backport, or by requesting clarification when blocked.
 
+          **Important**: This agent focuses on bugs, CVEs, and technical defects that need code fixes.
+          QE tasks, feature requests, refactoring, documentation, and other non-bug issues should be marked as "no-action".
+
           Goal: Analyze the given issue to determine the correct course of action.
 
           **Initial Analysis Steps**
@@ -160,7 +163,7 @@ def prompt(self) -> str:
              * Even if the Jira issue provides a direct link to a fix, you need to validate it
              * When no direct link is provided, you must proactively search for fixes - do not give up easily
              * Using the details from your analysis, search these sources:
-               - Bug Trackers (for fixed bugs matching the issue description)
+               - Bug Trackers (for fixed bugs matching the issue title and description)
                - Git / Version Control (for commit messages, using keywords, CVE IDs, function names, etc.)
              * Be thorough in your search - try multiple search terms and approaches based on the issue details
              * Advanced investigation techniques:
@@ -200,10 +203,12 @@ def prompt(self) -> str:
              * This is the correct choice when you are sure a problem exists but cannot find the solution yourself
 
           3. **No Action**
-             A No Action decision is appropriate for issues that are intentionally non-actionable:
-             * The request is too vague to be understood
-             * It's a feature request
-             * There is insufficient information to even begin an investigation
+             A No Action decision is appropriate for issues that are NOT bugs or CVEs requiring code fixes:
+             * QE tasks, testing, or validation work
+             * Feature requests or enhancements
+             * Refactoring or code restructuring without fixing bugs
+             * Documentation, build system, or process changes
+             * Vague requests or insufficient information to identify a bug
              * Note: This is not for valid bugs where you simply can't find the patch
 
           4. **Error**