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
The timeout calculation MAX_TURNS * 30 * 120 / 100 applies a 20% buffer on top of MAX_TURNS which already includes a 20% buffer from the turn estimation (line 159). This compounds to ~44% total buffer over the raw estimate. Consider using MAX_TURNS * 30 without the extra * 120 / 100 if the intent was a single 20% buffer across both, or document that the double buffer is intentional.
Context
This issue was automatically created from a non-blocking concern identified
during pre-push whole-codebase review. It was flagged for tracking.
Activity
docs: clarify that timeout uses 44% buffer (1.20 × 1.20), intentional