Ship an early fix stack while reviewers check follow-ups

In a multi-agent fix-and-verify loop for a user-facing bug, don't hold the user's build until every follow-up finding is closed. Have the independent reviewer give a verdict per commit range: the core fix (A..B), then the follow-ups (B..C). Start CI for the core range as soon as its local compile passes, in parallel with the review, and install it only if that range ships. Low-severity follow-ups such as performance or edge cases go into the next stack. This cut the user's wait by an 80-minute CI cycle without shipping anything unreviewed.