Fix Groq TPM limits misidentified as context overflow - #16176

Groq uses HTTP 413 for TPM (tokens per minute) limit errors. These were being incorrectly identified as context window overflows, causing OpenClaw to try resetting the session in an infinite loop. This fix excludes errors containing 'tpm' or 'tokens per minute' from being identified as context overflows and correctly classifies them as rate limits.

Greptile Summary

Fixed Groq TPM (tokens per minute) rate limit errors being misidentified as context overflow errors. Groq returns HTTP 413 with "too large" messages for rate limits, which was matching the context overflow pattern (lower.includes("413") && lower.includes("too large")) in isContextOverflowError(). This caused infinite retry loops as OpenClaw attempted to reset sessions for what it thought were context overflows. The fix adds early exclusion checks for "tpm" and "tokens per minute" strings in both isContextOverflowError() and isLikelyContextOverflowError(), and adds these patterns to the rate limit classifier.

• Prevented TPM errors from triggering incorrect context overflow handling
• Ensured TPM errors are properly classified as rate limits in ERROR_PATTERNS.rateLimit
• Applied consistent exclusion logic across both context overflow detection functions

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix is targeted, logical, and solves a specific misidentification bug without introducing new risks. The changes are minimal (adding exclusion checks and updating pattern arrays), the logic is sound (checking for rate-limit-specific terms before general overflow patterns), and the implementation is consistent across related functions. No breaking changes or side effects expected.
• No files require special attention

_{Last reviewed commit: fd20686}

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}