feat: show live progress while loading the repo list

[facundofarias]

Why

Final follow-up on #23. The reporter suggested a "loading repos from org A…" indicator so the (necessarily slow, for large orgs) repo fetch doesn't look stale. #24 moved the fetch to the background and #26 added add-by-name; this closes the loop with visible progress.

What

• The service worker reports progress as it fetches, writing a pr_radar_available_repos_progress key to chrome.storage: the current platform, plus the current org name for GitHub (threaded through a new optional onProgress callback on github.getUserRepos).
• The popup watches that key via chrome.storage.onChanged and renders:
  • First load: "Loading GitHub repos… (some-org)" under the spinner.
  • Refreshing (cache already shown): the same text inline beneath the repo count.
• Progress is cleared in a finally when the fetch ends, so it can't get stuck.

Verification

• npm run typecheck ✅
• npm run lint ✅
• npm run build ✅

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2b977e42-bd07-4a52-ab9a-339c1b452964

📥 Commits

Reviewing files that changed from the base of the PR and between 7e756a9 and 1972f30.

📒 Files selected for processing (5)

• CLAUDE.md
• src/background/service-worker.ts
• src/popup/pages/Repos.tsx
• src/shared/api/github.ts
• src/shared/storage.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/repo-load-progress

---

_{Comment @coderabbitai help to get the list of available commands.}