fix: enforce rate limits in maintainer actions

[AbhishekMauryaGEEK]

Summary

Enforces rate limits in maintainer actions that previously called rateLimit() but ignored the result.

Related Issue

Closes #265

Type of Change

• Bug fix
• Security / Abuse prevention
• Test coverage improvement

What Changed?

The following maintainer actions were calling rateLimit() but did not check limited.ok, allowing requests to continue even after the configured limit was exceeded:

• getRepoHealthOverview()
• getStaleIssues()
• getTopContributors()
• getFlaggedAccounts()

Updated each function to:

• Capture the rateLimit() result
• Return err('rate_limited', 'slow down', true) when the limit is exceeded
• Stop further processing when rate limiting is triggered

Added regression tests covering all four actions to ensure rate limits are enforced consistently.

Why?

Most maintainer actions correctly enforce rate limits by checking limited.ok.

These four functions were inconsistent and effectively bypassed rate limiting because the result of rateLimit() was discarded.

This change makes rate-limit enforcement consistent across maintainer actions and prevents unnecessary database work after limits have been exceeded.

Validation

• npx vitest run src/app/actions/maintainer.test.ts ✅
• npm run typecheck ✅
• npm test ✅

Checklist

• My code follows the project structure and conventions
• I tested the changes locally
• Added regression tests
• No breaking changes introduced

[vercel]

@AbhishekMauryaGEEK is attempting to deploy a commit to the codersogs-3057's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
mergeship	Ready	Preview, Comment	Jun 6, 2026 9:54am

[jakharmonika364]

LGTM! Correctly enforces the rate-limiting result on the maintainer actions and adds solid unit test coverage for it. All tests and checks pass cleanly.