Triage agent cannot check for existing PRs (missing pull_requests:read)

Summary

The fullsend triage agent cannot list open PRs when triaging an issue. Its Mint token only grants contents:read, issues:write, metadata:read — no pull_requests permission.

This means the triage agent can't check whether a PR already addresses the issue before recommending implementation work.

Evidence

Run 29110421338 on rhdh-agentic#89:

Triage output:

PR listing was inaccessible due to repo permissions; no duplicate PR check was possible.

Mint token scope from logs:

permissions=contents=read,issues=write,metadata=read repo_selection=selected

Root cause

reusable-triage.yml in fullsend-ai/fullsend does not request pull_requests:read from Mint when minting the sandbox token.

Expected

The triage Mint token should include pull_requests:read so the agent can cross-check open PRs before triaging.

Upstream

Needs a fix in fullsend-ai/fullsend → reusable-triage.yml.

Inspect fullsend-ai/fullsend's reusable-triage.yml and compare the Mint token permissions with the evidence in this issue. Ensure the triage token can read pull requests, then verify a triage run can check for an existing open PR before recommending implementation work.