Dev fixes script that wasted 3 API calls per run by misreading quota errors as bad output

A developer discovered that their automated article-generation script was misidentifying Claude's quota-limit messages as low-quality article output for four consecutive days between September 13 and 16. Because the quality checker only measured character count, it repeatedly concluded the short limit message was simply an article that needed rewriting, triggering two additional wasted API calls per run. The root cause was the script's failure to distinguish between a fixable failure and an unfixable one — a quota limit cannot be resolved by retrying until the reset window passes. The fix involved adding a grep check immediately after each generation pass to detect known quota-limit message patterns and abort on the first match. With the patch in place, the script now consumes exactly one API call before exiting cleanly, and the same fix is being applied to three other scripts sharing the same retry structure.