fix: shorten sub2api native cooldowns

config/platform-infra/sub2api-codex-pool.yaml

@@ -12,48 +12,48 @@ pool:
     rules:
       - statusCode: 400
         keywords: [invalid_encrypted_content, encrypted content, could not be verified, could not be decrypted, bad_response_status_code, model_not_found, no available channel for model, unsupported, not supported, not support, 暂不支持, 可用模型]
-        durationMinutes: 120
+        durationMinutes: 5
         description: Stable upstream 400 model-routing or Responses encrypted-content compatibility failures should use another account.
       - statusCode: 401
         keywords: [unauthorized, invalid api key, invalid_api_key, authentication, recovered upstream error]
-        durationMinutes: 120
-        description: Credential/auth failures should use the longest cooldown.
+        durationMinutes: 5
+        description: Credential/auth failures should briefly cool down this account and use another account.
       - statusCode: 403
         keywords: [forbidden, access denied, quota, billing, capacity, weekly limit, less than 10% of your weekly limit left, run /status for a breakdown, recovered upstream error]
-        durationMinutes: 120
-        description: Permission, quota, or account-state failures should use the longest cooldown.
+        durationMinutes: 5
+        description: Permission, quota, or account-state failures should briefly cool down this account and use another account.
       - statusCode: 429
         keywords: [capacity, rate limit, rate_limit, quota, weekly limit, less than 10% of your weekly limit left, run /status for a breakdown, too many requests, overloaded, resource_exhausted, recovered upstream error]
-        durationMinutes: 10
-        description: Capacity and rate-limit responses are often temporary; start with a ten-minute cooldown and use another account.
+        durationMinutes: 5
+        description: Capacity and rate-limit responses are often temporary; briefly cool down this account and use another account.
       - statusCode: 500
         keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream, recovered upstream error]
-        durationMinutes: 10
-        description: Transient upstream server failures should start with a ten-minute cooldown and prefer another account.
+        durationMinutes: 5
+        description: Transient upstream server failures should briefly cool down this account and prefer another account.
       - statusCode: 502
         keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream, bad gateway, upstream request failed, unknown error, context deadline exceeded, context canceled, websocket dial, handshake response, recovered upstream error]
-        durationMinutes: 30
-        description: Gateway upstream failures, including recovered upstream error wrappers, should cool down longer.
+        durationMinutes: 5
+        description: Gateway upstream failures, including recovered upstream error wrappers, should briefly cool down this account.
       - statusCode: 413
         keywords: [openai_error, payload too large, request too large, context length, context window, maximum context]
-        durationMinutes: 30
+        durationMinutes: 5
         description: Large-context upstream failures should cool down the selected account so a larger-context channel can handle the request.
       - statusCode: 503
         keywords: [capacity, overloaded, temporarily unavailable, temporary, upstream, recovered upstream error, model_not_found, no available channel for model]
-        durationMinutes: 30
-        description: Service unavailable and upstream model-routing failures should cool down longer than one-off transient failures.
+        durationMinutes: 5
+        description: Service unavailable and upstream model-routing failures should briefly cool down this account.
       - statusCode: 504
         keywords: [gateway timeout, timeout, upstream, upstream request failed, unknown error, context deadline exceeded, context canceled, recovered upstream error]
-        durationMinutes: 30
+        durationMinutes: 5
         description: Gateway timeout responses should cool down the selected account so another account can handle the next request.
       - statusCode: 524
         keywords: [timeout, a timeout occurred, cloudflare, gateway timeout, upstream, upstream request failed, unknown error, context deadline exceeded, context canceled, recovered upstream error]
-        durationMinutes: 30
+        durationMinutes: 5
         description: Cloudflare 524 timeout responses should cool down the selected account so another account can handle the next request.
       - statusCode: 529
         keywords: [capacity, overloaded, temporarily unavailable, temporary, recovered upstream error]
-        durationMinutes: 30
-        description: Provider overloaded responses should cool down longer than generic transient failures and use another account.
+        durationMinutes: 5
+        description: Provider overloaded responses should briefly cool down this account and use another account.
 profiles:
   entries:
     - profile: HY