ci: exception from the open-PR limit in the flood guard - #4091

Related Issues

• None

Proposed Changes:

• Add an EXEMPT_AUTHORS list to .github/workflows/CI_pr_flood_guard.yml with maxdswain in it. The open-PR check skips authors on that list, so the flood guard no longer warns them about having more than two open PRs.
• The duplicate check (another open PR already linked to the same issue) still applies to exempt authors.
• CI_first_pr_limit.yml is unchanged. It only applies to authors with no merged or approved PR, and maxdswain has 23 merged PRs here.

How did you test it?

• Ran actionlint v1.7.10 on the workflow: no findings.
• Ran the workflow's script in Node against a stubbed GitHub API:
  • maxdswain with 3 or 5 open PRs: no open-PR warning, but the duplicate warning is still posted.
  • Other community contributors: still warned once they have 3 open PRs.

Notes for the reviewer

• Mirror of ci: add exception from the open-PR limit in the flood guard haystack#13225
• maxdswain currently has 2 open PRs here (feat: add VLLMMultivectorDocumentEmbedder and VLLMMultivectorTextEmbedder components #4014, feat: add ability to specify qdrant client kwargs #4048), so without this change their next PR would get the warning.
• CONTRIBUTING.md still says community contributors can have only one open PR at a time and doesn't mention exceptions. Maintainers enforce that rule by hand, so this PR only changes the automation.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes — n/a, no issue
• I added unit tests and updated the docstrings — n/a, CI workflow only
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

🤖 Generated with Claude Code