Non-Blocking Review Concern: Timeout estimation applies double 20% buffer
Source: pre-push whole-codebase review
Location: .github/workflows/claude-blocking-review.yml:171
Date: 2026-04-10
What was flagged
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.
Created by lib-review-issues.sh
Non-Blocking Review Concern: Timeout estimation applies double 20% buffer
Source: pre-push whole-codebase review
Location:
.github/workflows/claude-blocking-review.yml:171Date: 2026-04-10
What was flagged
The timeout calculation
MAX_TURNS * 30 * 120 / 100applies 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 usingMAX_TURNS * 30without the extra* 120 / 100if 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.
Created by lib-review-issues.sh