[Ready for review] Add contributors page with data collection pipeline

[Hangzhi]

Summary

• Add /contributors page as a top-level route (parallel to /registry) with three sections: Harbor Contributors, Harbor Adapter Contributors, and Acknowledgments
• Add utils/contributors/ pipeline to collect and aggregate contributor data from laude-institute/harbor via GitHub API
• Add ctbcli CLI tool to manage the data refresh workflow

How it works

Data pipeline (utils/contributors/)

Three Python scripts collect and merge data:

1. collect_pr_data.py — fetches all merged PRs from laude-institute/harbor, classifies each as adapter, task, engineering, or other, writes raw_pr_data.json
2. collect_user_data.py — fetches GitHub profiles for each unique PR author, writes raw_github_users_data.json
3. generate_contributions.py — merges PR data with user data (verified data takes precedence over raw GitHub data), aggregates per contributor, and writes harbor_contribution.json

Verified data (verified_github_users_data.json)

Manually curated file that overrides raw GitHub profile data. Supports role (displayed on card), rank (sort priority for Harbor section), and adapter_rank (sort priority for Adapter section). Contributors in verified data with no PRs (e.g. advisors) are included automatically.

Ranking

• Harbor Contributors: rank (desc) → non-adapter PR count (desc) → last name (asc)
• Adapter Contributors: adapter_rank (desc) → adapter PR count (desc) → last name (asc)

CLI (ctbcli)

./utils/contributors/ctbcli refresh           # Full refresh from GitHub API
./utils/contributors/ctbcli refresh-prdata    # Re-collect PR data only
./utils/contributors/ctbcli refresh-userdata  # Re-collect user profiles only
./utils/contributors/ctbcli generate          # Regenerate from existing data when verified github users data is updated (no API calls)

Contributor card

Shows contributor name as title, with GitHub handle and role as subtitle. Falls back to @handle when no name is available.

harbor_contributor_page.mp4

[netlify]

👷 Deploy request for harborframework pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	4eaaeba

[Slimshilin]

Thanks for collecting this! lgtm 💯

We can update later once we have more contributor onboard.

Just a question: will the contributor page automatically sync as we merge more github PRs, or we need to manually run some script and submit new PRs to the doc to reflect the changes?

[Hangzhi]

@Slimshilin

we need to manually run some script and submit new PRs to the doc to reflect the changes?

It's not automated yet. It's complicated and not necessary to implement this data update automation as a part of the web app.

A proper approach should be a github Action cron job. I can do it in a followup PR.