Why This Matters
Onboarding now performs fewer repeated GitHub status checks, which lowers background load and reduces the chance of wasting GitHub API rate limit while keeping setup state current when it matters.
Detailed Changes
- Reduced onboarding panel polling so it checks less often when setup issues remain and stops polling once onboarding is healthy.
- Added server-side caching for onboarding status so repeated requests reuse recent results instead of rechecking GitHub every time.
- Refreshed cached onboarding status when configuration changes, watched repositories are added, or review workflows are installed, so setup progress still updates after important actions.