Add agentic issue-intents triage workflow

[alondahari]

What & why

This is a new installation of a gh-aw issue intents triage workflow on primer/react. On issues opened/reopened, the agent reads the issue and its comments, classifies the issue type when it is unset, adds only existing relevant labels, flags likely duplicate/related issues, and asks the author for missing information only when genuinely needed.

Issue intents let the triage agent attach its reasoning to each action it takes (issue type, labels) and surface a confidence level, so maintainers can see why a change was made and approve or reject low-confidence suggestions instead of having them applied silently. A key goal is to minimise the noise of agent-generated comments — rationale and confidence travel with the action itself rather than as a separate triage-report comment on the issue. Learn more: Review and approve Copilot agent actions on issues.

See it in action

issues.agentic.review.mp4

Changes

New workflow, using only built-in safe outputs (no custom GitHub API jobs):

• .github/workflows/issue-triage.md + compiled issue-triage.lock.yml.
• Native intent-capable outputs only: set-issue-type (allowed: Bug/Feature/Task — the primer org's configured issue types) and add-labels, both with issue-intent: true so every action carries a rationale + confidence. A single add-comment is reserved for missing-information requests; no routine triage report is posted.
• Low-confidence changes are routed as suggestions (suggest: true) for maintainer approval rather than applied.
• No set-issue-field — this repo shows no evidence of maintainers using repo/org issue fields, so field mutations are intentionally omitted.
• Existing labels are preserved, sensitive automation labels are blocked, and issues are never closed automatically; the agent calls noop when no visible change is needed.
• Repo variable GH_AW_RUNTIME_FEATURES=issue_intents — set on primer/react.
• gh-aw scaffolding included: .github/aw/actions-lock.json (action-lock), .gitattributes, and the agentic-workflows authoring skill/agent.
• Validated with a trial run against a real closed issue (see below).

Validation

Trialled in logical mode against closed issue #7977 via github/lukewar-gh-aw-trial (capture mode — nothing applied to the live repo). Captured safe output:

{ "type": "set_issue_type", "issue_number": 7977, "issue_type": "Bug", "confidence": "HIGH",
  "rationale": "Issue describes reproducible incorrect behavior: PageHeader.ParentLink silently drops props like 'to' when using polymorphic 'as', breaking client-side routing." }

Full run: https://github.com/github/lukewar-gh-aw-trial/actions/runs/30002450477 — six jobs green; the agent correctly typed the untyped issue as Bug with rationale + HIGH confidence, added no invented labels, and posted no routine comment.

Feature flags

The required flags (update_issue_suggestions, update_issue_confidence_routing) are already enabled org-wide for the github org. primer is a separate org — the onboarding team will enable the flags there; nothing is needed from repo maintainers.

Relates to github/plan-track-agentic-toolkit#467 (rollout tracking). No per-repo sub-issue exists, so this links rather than closes it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 06aea8e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[alondahari]

Closing because this PR was created from a superseded target list; no Primer component repositories are in scope for the stable gh-aw refresh.