Add issue triage agentic workflow

[friggeri]

This workflow automatically triages newly opened issues by:

• Adding appropriate labels (SDK, type, priority, area)
• Posting acknowledgment comments
• Requesting clarification when issues lack detail
• Detecting and closing duplicate issues

Supports manual triggering via workflow_dispatch with an issue_number input.

[Copilot]

Pull request overview

This PR adds an automated issue triage workflow that uses an AI agent to process newly opened issues. The workflow analyzes issues and aims to add labels, post acknowledgment comments, request clarification when needed, and detect/close duplicates.

Changes:

• Adds a new agentic workflow definition file (issue-triage.md) with AI agent instructions
• Includes the auto-generated compiled workflow file (issue-triage.lock.yml) for GitHub Actions

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/issue-triage.md	Workflow definition with AI agent prompt and instructions for triaging issues
.github/workflows/issue-triage.lock.yml	Auto-generated GitHub Actions workflow file compiled from the .md definition

Comments suppressed due to low confidence (3)

.github/workflows/issue-triage.md:15

• The top-level workflow permissions are read-only, which is correct for the agent job. However, the workflow's primary task is to add labels and modify issues, which would require issues: write permission. This aligns with the safe_outputs job which does have issues: write (line 1108 of .lock.yml), but the GitHub MCP server used by the agent is configured as read-only. Consider documenting this design choice or adjusting permissions if label addition is to be implemented.

permissions:
  contents: read
  issues: read
  pull-requests: read

.github/workflows/issue-triage.md:1

• The concurrency group references github.event.issue.number, which will be undefined when the workflow is triggered via workflow_dispatch. This could cause multiple manual workflow runs to conflict or run simultaneously when they should be serialized. Consider using github.event.issue.number || inputs.issue_number to handle both trigger types properly.

---

.github/workflows/issue-triage.md:72

• The acknowledgment guideline instructs the agent to mention which labels were applied, but since no labeling capability exists, this will result in misleading comments. The agent would need to either report the missing label tool or provide acknowledgment without mentioning labels. Update the guidelines to reflect the actual available capabilities.

1. **Labeling**: Always apply at least one type label. Apply SDK labels when the issue clearly relates to specific language implementations. Use `needs-info` when the issue is unclear or missing reproduction steps.

2. **Acknowledgment**: Post a friendly comment thanking the author for opening the issue. Mention which labels you applied and why.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The workflow instructs the AI agent to add labels to issues, but no tool is available to perform this action. The safe-outputs section only defines add-comment, update-issue, and close-issue tools, none of which support adding labels. The GitHub MCP server is also configured with GITHUB_READ_ONLY=1 (line 405 of .lock.yml), preventing write operations. Either add a label management tool to safe-outputs or remove the labeling instructions from the prompt.

This issue also appears in the following locations of the same file:

• line 12
• line 70

[Copilot]

The GitHub MCP server is configured in read-only mode, which prevents the agent from making any write operations including adding labels or modifying issues. This conflicts with the workflow's stated purpose of 'labeling, acknowledging, requesting clarification, and closing duplicates.' The safe-outputs tools (add_comment, update_issue, close_issue) will handle writes, but the agent cannot use the GitHub MCP server to add labels. Either enable write mode or clarify that labeling must be done through an alternative mechanism.

Suggested change

	"GITHUB_READ_ONLY=1",
	"GITHUB_READ_ONLY=0",