Patch test: correctly interpret Retry-After

Test assignment

Retry policy: correctly interpret Retry-After

The model received a small retry helper with deliberately seeded bugs. Its job was to make the smallest clear repair while keeping both exported functions unchanged and modifying only the allowed source file.

What the repaired code had to do

• Accept Retry-After either as whole, unsigned decimal seconds or as a valid HTTP date, while rejecting signed, fractional, hexadecimal, exponent, empty, and non-string values.
• For a date, calculate the remaining delay from nowMs, never return a negative delay, and reject an invalid date or non-finite current time.
• Require attempt to be a positive integer and nowMs to be finite.
• Let a valid Retry-After override normal backoff; otherwise use exponential delays of 1, 2, 4, 8 seconds, and so on.
• Cap every delay at five minutes, including extremely large retry attempts, so the result always remains finite.