[community] Update community contributions in README

[github-actions]

Summary

Maintains the 🌍 Community Contributions section in README.md by attributing all resolved community-labeled issues using the five-tier attribution strategy.

Changes

• 252 confirmed community members with resolved issues (Tiers 0-2)
• 5 attribution candidates requiring manual PR linkage review (Tier 3-4)
• Updated through July 5, 2026

Attribution Strategy

Issues were attributed in the following order:

1. Tier 0: Direct issue contributions (stateReason = COMPLETED) — no PR linkage required
2. Tier 1: GitHub-native closing references via close-with-keyword
3. Tier 2: PR body keyword parsing
4. Tier 3: Follow-up/split issue linkage chains
5. Tier 4: Unlinked candidates requiring manual verification

Pending Review

The following 5 community issues could not be automatically linked to a merged PR and are flagged for manual review:

• [@austenstone] #42874 — [bug] Intake Triage agent job MODULE_NOT_FOUND (closed 2026-07-04)
• [@martinbriley] #42842 — Request sentiment event emission (closed 2026-07-05)
• [@github-actions] #41256 — [deep-report] Unanswered issues (closed 2026-06-26)
• [@github-actions] #41255 — [deep-report] Needs-triage bugs (closed 2026-06-26)
• [@theletterf] #39904 — docs-pr-ai-menu GitHub API 502 transient failure (closed 2026-06-18)

Generated by 🏆 Daily Community Attribution Updater · 48.8 AIC · ⌖ 14.8 AIC · ⊞ 7.9K · ◷

• expires on Jul 12, 2026, 7:38 PM UTC-08:00

[github-actions]

Hey team 👋 — thanks for the automated community attribution update! This PR keeps the 🌍 Community Contributions section of README.md current through July 5, 2026, which is great for community visibility.

A couple of things worth a quick look before merging:

• No tests — this is a README-only change, so automated tests may not be applicable. If there's a script or workflow that generates these attributions, consider whether it has its own test coverage to verify the attribution logic (tier assignments, deduplication, etc.).
• On-topic signal — the project's CONTRIBUTING.md doesn't define explicit focus areas or acceptance criteria for automated maintenance PRs. A brief note in the PR (or a linked issue) confirming this automation is part of the approved core-team workflow would help reviewers confirm it fits the project's agentic development model.

If you'd like a hand validating or extending the attribution workflow, here's a ready-to-use agent prompt:

Review the community attribution automation that generated PR #45031 in github/gh-aw.
Specifically:
1. Locate the workflow or script responsible for updating the '🌍 Community Contributions' section in README.md.
2. Verify it has test coverage for the five-tier attribution strategy (Tiers 0–4).
3. If tests are missing, add unit tests covering: correct tier assignment, deduplication of contributors, and handling of Tier 3–4 candidates that require manual review.

Generated by ✅ Contribution Check · 84.8 AIC · ⌖ 10.4 AIC · ⊞ 6.2K · ◷