Repository navigation
v1.34.0 — the two-round review cap
Ports stride's two-round review cap (W2128) to the Codex edition.
Two rounds is the whole budget, and the second verifies round one's fixes rather than re-reviewing from scratch — scoping its mission, never its evidence, so it still receives the full diff and still emits the full acceptance_criteria array, every section verdict and project_checks.
A round is redefined in this port's own terms. Stride counts a round as a dispatch that produced a merged result file; this port writes no such file, so a round is a reviewer invocation whose response yielded a fenced JSON block that parsed into an object — the only artifact an invocation here produces. A crashed or unparsable invocation is re-invoked and consumes no round.
After round two, residual important/minor findings are recorded rather than fixed. A critical is exempt and blocks for however many rounds it takes, and a category: "security" finding is never merely recorded at any severity.
Enforced or stated? Both, and the contract says which. The cap's arithmetic is a real round_cap_ok assert in this port's existing Python self-check. Its inputs are self-asserted rather than result-verified — this port persists no per-round reviewer artifact to recount against — and that limit is stated rather than implied.
Test Group 4 adds 47 assertions (suite 545 → 592). Its executed half extracts the pin from the shipped markdown and runs it, rather than restating what it should do.
See CHANGELOG.md for the judgement calls, the four defects found in review, and what was deliberately left out of scope.