Improve auto-triage: always include drafts, close stale ones, prefetc…

[potiuk]

…h next page, show reviews

• Remove --include-drafts flag; draft PRs always enter the triage pipeline
• Non-stale draft PRs are filtered out from candidates and display
• Stale drafts (triaged >7 days, no author response) are auto-closed with a comment inviting the author to reopen after addressing feedback
• Add skip action (s) to workflow approval diff review prompts
• Show review instructions before batch workflow approval
• Wait for user confirmation before starting diff review
• Background prefetch of next page at 75% of current batch in sequential mode
• Show approval/rejection count and reviewer names in PR headers (both sequential and TUI modes)
• Fetch review decisions via GraphQL and add ReviewDecision model
• LLM prompt: treat generated files as auto-generated (CI checks handle them)

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-2-test

You can attempt to backport this manually by running:

cherry_picker d4007e5 v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.