Add contributor-input-needed triage workflow

[tidy-dev]

Introduce a new GitHub Actions workflow (.github/workflows/triage-contributor-input-needed.yml) that auto-applies a contributor-input-needed label when changes are requested, removes it when the PR author responds, posts warning comments after configured inactivity, and auto-closes stale PRs. Update README to document the new workflow and label, and adjust example usage files to wire the workflow into pull request and scheduled task flows (add PR synchronize/review triggers and a scheduled job). This automates follow-up on requested changes and reduces manual triage work.

[Copilot]

Pull request overview

Adds a new reusable triage workflow to manage a contributor-input-needed label on PRs (auto-apply on CHANGES_REQUESTED, remove on author activity, warn/close on inactivity), and wires it into the documented example workflows.

Changes:

• Added .github/workflows/triage-contributor-input-needed.yml reusable workflow to apply/remove labels and warn/close stale PRs.
• Updated example usage workflows to trigger on PR synchronize and to call the new workflow from scheduled/comment-driven automation.
• Updated README to list the new workflow/label; removed the “acknowledging comment” step from triage-ready-for-review.

Reviewed changes

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

Show a summary per file

File	Description
example-usage/triage-scheduled-tasks.yml	Calls the new contributor-input-needed workflow from scheduled/comment triggers.
example-usage/triage-prs.yml	Adds synchronize trigger and calls contributor-input-needed workflow for PR updates/label events.
README.md	Documents the new workflow and required label.
.github/workflows/triage-ready-for-review.yml	Removes the automatic acknowledging PR comment step.
.github/workflows/triage-contributor-input-needed.yml	New reusable workflow implementing labeling, warning, and auto-close behavior.

Comments suppressed due to low confidence (3)

.github/workflows/triage-contributor-input-needed.yml:166

• BOT_WARNING is computed from the first page of issue comments only; on PRs with >30 comments the prior warning comment may not be returned, leading to duplicate warnings and preventing closure. Paginate the comments request and/or embed a stable marker in the warning comment body so it can be reliably detected.

            # Check if the bot has already left a warning comment
            BOT_WARNING=$(gh api "repos/{owner}/{repo}/issues/$PR_NUM/comments" --jq "[.[] | select(.user.login == \"github-actions[bot]\" and (.body | contains(\"we haven't heard back\")))] | last | .created_at // \"\"")

.github/workflows/triage-contributor-input-needed.yml:185

• The closing comment body also has leading indentation before "If you'd like to continue…", which will render as a code block in Markdown. Remove the indentation from the multi-line string (or build the body via heredoc/printf) to keep formatting consistent.

                gh pr comment "$PR_NUM" --body "Closing this PR due to inactivity. Thank you for your contribution, @$PR_AUTHOR!

          If you'd like to continue working on this, feel free to reopen the PR and we'll be happy to review it again."
                gh pr close "$PR_NUM"

README.md:24

• This workflow’s behavior expects pull_request_target: [labeled, synchronize] (it has a job gated on github.event.action == 'labeled'), but the README trigger summary only mentions pull_request_target: [synchronize]. Update the trigger description to include labeled so adopters wire it correctly.

| [`triage-contributor-input-needed.yml`](.github/workflows/triage-contributor-input-needed.yml) | Auto-labels PRs with changes requested, warns after inactivity, auto-closes | `pull_request_target: [synchronize]` + `issue_comment` + `schedule` |

---

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

[Copilot]

The warning comment body includes lines with significant leading indentation (e.g. the "This PR will be automatically closed…" line). In GitHub-flavored Markdown, 4+ leading spaces render as a code block, so the message formatting will be off. Construct the multi-line body without leading indentation (heredoc/printf) so it renders as intended.

This issue also appears on line 182 of the same file.

[tidy-dev]

While testing the other workflow, I found this comment a bit over the board and making the PR history unnecessarily noisy.