Set up agentic issue triaging

[JennyPng]

migrate to agentic issue triaging

issue-triage.md is based off of

• https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-tools%2Fblob%2Fmain%2Ftools%2Fgithub-event-processor%2FRULES.md&data=05%7C02%7CJeff.Fisher%40microsoft.com%7C82b8cbae657f42eb3a0408ded2d223bd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C639179997147229187%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=k%2FvYoOmgIAAjSht7dK8zISq3UvIWHjItEfJRwRDMIHk%3D&reserved=0
• https://github.com/Azure/azure-sdk-for-net/blob/main/.github/workflows/issue-triage.md

[Copilot]

Pull request overview

This PR migrates the Azure SDK for Python repository's initial issue triage from the rules-based github-event-processor to a gh-aw agentic workflow. It adds a new agentic workflow source (issue-triage.md) describing a multi-step triage decision flow (customer evaluation, label prediction, CODEOWNERS-based owner routing, and analysis comments), its compiled issue-triage.lock.yml, and flips the legacy InitialIssueTriage rule off so the two systems don't both run on issues.opened.

Changes:

• Add issue-triage.md: an agentic triage workflow that runs on issues.opened/workflow_dispatch, predicts Client/Mgmt + service labels, routes via CODEOWNERS, and includes a custom mention_owners safe-output job to preserve real @mentions.
• Add issue-triage.lock.yml: the gh-aw-compiled lock file (read-only GitHub MCP server, safe-outputs after threat detection, firewalled network).
• Update event-processor.config: set InitialIssueTriage to Off while leaving the other issue-automation rules enabled.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/issue-triage.md	New agentic triage prompt + frontmatter (permissions, network, safe-outputs, custom mention_owners job).
.github/workflows/issue-triage.lock.yml	Auto-generated lock file (DO NOT EDIT) compiled from the .md source.
.github/event-processor.config	Disables the legacy InitialIssueTriage rule to avoid overlap with the new workflow.

Notes for the reviewer:

• The .lock.yml is generated by gh aw compile; it should not be hand-edited and appears consistent with the source frontmatter (network allowlist, issues toolset, timeouts, safe-output maxima).
• The custom mention_owners job posts the agent-provided message verbatim, bypassing the sanitization/length-cap that the standard add_comment safe-output applies — see the inline comment.
• This is a security-sensitive workflow that runs on issues opened by anyone (roles: all, min-integrity: none) with write access to issues, so it warrants careful human review.

[xirzec]

The workflow looks good, but what version of gh-aw was used to compile this? From the lock.yml I see "compiler_version":"v0.79.8" but I see the latest is https://github.com/github/gh-aw/releases/tag/v0.80.9 -- can you regenerate with that to make sure the token permissions work?