Vercel rate limit message can be improved

[yamcodes]

It could use an additional pass. It currently says "has exceeded the limit for the number of commits that can be reviewed per hour". But that action has nothing to do with reviewing commits...

[arkenv-bot]

🤖 Hi @yamcodes, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[yamcodes]

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Enhance DX by providing actionable error messages for Vercel rate limits

Current behavior:
Vercel deployment failures due to rate limits result in generic exit codes or cryptic error logs that don't clearly explain the 24-hour restriction.

Desired behavior:
The deployment pipeline should intercept rate-limit specific error strings from the Vercel CLI and wrap them in a user-friendly message that explains the limit and provides a link to Vercel's documentation on rate limits.

Key interfaces:

• Deployment script error handler — needs to parse stderr for rate limit keywords.
• Workflow logging — should use GitHub Actions' ::error formatting for high visibility.

Acceptance criteria:

• Rate limit errors are identified during the deployment step.
• A clear, human-readable error message is printed to the console.
• The build fails with a specific error message rather than a generic timeout.

Out of scope:

• Retrying the deployment automatically.
• Bypassing the Vercel rate limit.