fix(native): wait for a dated provider limit reset and keep it out of Sentry (#19775)

Keep native quota cooldowns tied to valid dated reset messages. Parse explicit years and strict month names while preserving already-expired dates. Keep typed native quota and rate-limit failures on their tasks in unexpected Sentry reporting mode. Preserve setup, process, malformed and all-mode reporting.

Verified current-head CI, Greptile 5/5 at Medium impact, local parser/report red-green tests and PostgreSQL integration coverage.

Co-Authored-By: Devin Foley <devin@devinfoley.com>
Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
Devin FoleyandPaperclip authored and GitHub committed 2026-11-12 17:06:22 -08:00
1 parent 2dcfdabc79
commit ad320aeb71
6 files changed
+318 -8

No files matched your search

+6
View File
@@ -1126,6 +1126,12 @@ evidence, unknown binding reasons, secret-provider failures, ambiguous missing
secret-definition lookups remain reportable. This filter does not change task
recovery, credentials, or execution policy.
Native `native_provider_usage_limit` failures also stay on the task when their
typed provider failure is `quota_exhausted` or `rate_limit`. The task keeps its
blocked state and quota cooldown. Setup failures, interrupted processes, missing
or malformed provider evidence, and other failure categories still report.
`all` mode also reports typed native usage limits.
AI account selection also stays local when the selection service proves a
missing responsible user, personal default, or selected connection; an
incompatible selection; an account that needs reconnection; or an active