You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.1.8 Beta7: Bound request-local retries without circuit breaking #256
Freeze the request-local retry contract before the Beta7 candidate is published and RC qualification begins, without adding circuit breaking. Main generation may retry only a proven-safe pre-transmission transport failure within fixed attempt and delay budgets; qualification cases never hide retries.
Acceptance criteria
Third-party main generation uses at most two total attempts.
Retry eligibility is limited to a proven-safe DNS/connect/TLS failure before request-body transmission.
Cumulative retry delay is at most 15 seconds.
No retry occurs after response headers, body bytes, SSE events, or downstream-visible output.
Idempotent catalog/model GET retry remains a separate bounded policy.
Qualification cases perform no hidden retry and report degraded/recovered attempts explicitly.
Responses and Chat regressions prove no duplicate tool execution or terminal event.
changed the title [-]0.1.8 RC1: Bound request-local retries without circuit breaking[/-][+]0.1.8 Beta6: Bound request-local retries without circuit breaking[/+]on Aug 2, 2026
changed the title [-]0.1.8 Beta6: Bound request-local retries without circuit breaking[/-][+]0.1.8 Beta7: Bound request-local retries without circuit breaking[/+]on Aug 4, 2026
Activity
[-]0.1.8 Beta3: Bound request-local retries without circuit breaking[/-][+]0.1.8 RC1: Bound request-local retries without circuit breaking[/+][-]0.1.8 RC1: Bound request-local retries without circuit breaking[/-][+]0.1.8 Beta6: Bound request-local retries without circuit breaking[/+][-]0.1.8 Beta6: Bound request-local retries without circuit breaking[/-][+]0.1.8 Beta7: Bound request-local retries without circuit breaking[/+]