community attribution run summary

Community Attribution Run Summary

Date: 2026-10-14
Status: ✅ Completed Successfully

Attribution Results

Overall Statistics

• Total Authors: 383 unique community contributors
• Total Issues: 1,256+ resolved community-labeled issues
• PR Created: Yes (community-attribution-update-1791945723 branch)

Attribution Breakdown

Tier 0 (Direct Issues)

• Count: 1,256 issues
• Method: Issues closed as COMPLETED (state reason)
• Type: Direct contributions by issue authors
• Status: All included in README

Tier 1 (GitHub Native Closing References)

• Count: Included in pre-attributed data
• Method: GitHub's native "closed by" feature on merged PRs
• Status: All included in README

Tier 2 (PR Body Keyword Parsing)

• Count: Included in pre-attributed data
• Method: Standard closing keywords in PR descriptions
• Status: All included in README

Tier 3 (GitHub MCP Follow-up)

• Candidates: 2 issues
  • #65058 (niebloomj): "agent image intermittently lacks jq..."
  • #60858 (appbrew-zod): "engine.env can't be shared..."
• Result: No confirmed PR linkage found
• Status: Deferred for maintainer review

Tier 4 (Unresolved)

• Status: No unresolved candidates identified

Files Updated

1. README.md

• Section: ## 🌍 Community Contributions
• Changes: Replaced 374 lines with 388 lines
• Content: 383 author links with issue counts

2. Community Contributors Wiki

• Location: /tmp/gh-aw/repo-memory/default/Community-Contributors.md
• Size: 40,538 bytes
• Content: Top 50 contributors with representative issues
• Format: Organized by author (alphabetical), issues by number (descending)

Pull Request Details

• Title: [community] Update community contributions in README
• Branch: community-attribution-update-1791945723
• Commits: 1
• Patch Size: 25,191 bytes
• Lines Changed: 237

Next Steps

1. Review the pull request for accuracy
2. Address Tier 3 candidates (issues #65058, #60858) if desired
3. Merge when ready
4. Deploy updated README and wiki pages

Notes

• Pre-fetched attribution data was comprehensive and well-structured
• Tier 0 attribution (direct issues) is the strongest signal
• Both README and wiki are now synchronized
• All data files are organized and traceable