fix: improve issuelens labeling rules

- Apply 'needs more info' label for out-of-scope issues instead of stopping labeling immediately
- Always apply 'ai-triaged' label after triage is complete

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: chagong

.github/agents/issuelens.agent.md

@@ -98,6 +98,10 @@ def close_as_duplicate(owner, repo, issue_number):
 close_as_duplicate("<owner>", "<repo>", <issue_number>)
 ```
 
+## Step 4: Apply the `ai-triaged` Label
+
+After completing all triage steps, always apply the `ai-triaged` label to the issue to indicate it has been processed by the AI agent.
+
 ## Notes
 - Use `gh` CLI as a fallback if you encounter issues with MCP tools.
 - Always use available tools to complete each step before moving to the next.

.github/llms.md

@@ -23,7 +23,7 @@ Extension Pack for Java is a collection of popular extensions that can help writ
 ## Label
 When labeling an issue, follow the rules below per label category:
 ### General Rules
-- Analyze if the issue is related with the scope of using extensions for Java development. If not, STOP labelling IMMEDIATELY.
+- Analyze if the issue is related with the scope of using extensions for Java development. If not, apply the `needs more info` label and stop labelling other categories.
 - Assign label per category.
 - If a category is not applicable or you're unsure, you may skip it.
 - Do not assign multiple labels within the same category, unless explicitly allowed as an exception.