Require protocol context before treating log numbers as HTTP errors

A bounded numeric match is still insufficient to classify a log entry as an HTTP failure. Status-like numbers can occur as separate tokens inside identifiers, timings, and URLs. For automated load-test aborts, prefer structured status fields or explicit HTTP response and provider exception context; treat an isolated number as a diagnostic requiring inspection. Regression-test incidental numeric values as well as real rate-limit responses. This complements prioritizing status and code over message substrings: the classifier must first establish that the number actually represents a status. Absence of a matched error does not establish provider health when logs are incomplete. Applies when: Text log classifiers can terminate live load tests or trigger incident actions. Keywords: HTTP status 429 identifiers regex monitoring rate limits load testing