mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-16 13:21:30 +01:00
* Reviewers state their blocker count in one line, and gstack checks it against the findings it parsed Every blocking /ship reader's brief now asks for REVIEW_VERDICT: blocking=<n>. collect adds a CRITICAL row for each declared blocker it did not parse, marks word-only CRITICAL rows as summary candidates when the count is lower, and never lowers a row on its own except the native voice's unanchored FIXABLE raise. Ledgers rendered before this change replay unchanged. Includes the preregistration for the no-loss replay. Refs: GST-2495 Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Add the verdict-line no-loss replay results Refs: GST-2495 Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Keep a finding line that mentions REVIEW_VERDICT instead of stripping it Only a well-formed verdict line is removed before findings are parsed; prose that names the token, or a malformed attempt, stays in the text so its finding is still collected. Review-Finding: p1/specialist-batched#1 reader=specialist-batched Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Check a stored summary flag against the reply on every ledger, not only ones that asked for the verdict line verify now re-derives summary_candidate for every merged row, so a flag edited onto a real CRITICAL in an older ledger can no longer let judgment lower it while verify reports clean. Review-Finding: v2/outside-voice#1 reader=outside-voice Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Never lower a finding automatically when a reviewer's blocker count is lower than the parse A valid verdict line used to relabel the native voice's unanchored FIXABLE prose to its own label. Beside a denial line such as 'No other CRITICAL issues.' that let a real blocker drop to FIXABLE while the count still agreed. Those rows now stay CRITICAL and become summary candidates the lead lowers with a written reason. Review-Finding: v3/adversarial-native#1 reader=adversarial-native Refs: GST-2495 Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * Split a run-on sentence in the verdict-line changelog entry Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>