Code generation speed, once the central argument for AI adoption, has proven irrelevant to delivery timelines when review capacity does not scale alongside it. A one-developer case study captures the structure: one engineering team moved from two or three PRs per week to eleven in a single day — the code-writing part accelerated, the review queue did not. GitHub acknowledged this directly with its Stacked PRs release, an infrastructure change that only makes sense if the review queue is now the binding constraint.