Skip to content

fix(review): report chunked findings when chunks return empty summaries - #562

Merged
ajianaz merged 1 commit into
developfrom
fix/556-chunked-summary-footer
Oct 4, 2026
Merged

ajianaz merged 1 commit into
developfrom
fix/556-chunked-summary-footer

Conversation

@ajianaz

@ajianaz ajianaz commented Oct 4, 2026

Copy link
Copy Markdown
Collaborator

What

Chunked review mode can emit a contradictory report — header Found 1 issue ... ⚠ BLOCKED with footer No issues found across all chunks. — when chunks return issues with an empty summary field. Extract the merged-summary decision into merged_chunk_summary() with an explicit issue-count branch, and unit-test all five outcomes. Replacement for #559 (auto-closed when its temporary base branch was deleted post-merge of #561; same single commit, rebased onto current develop).

Why

The old fallback keyed only off summaries/any_error and never consulted the collected issues (live: gaira PR #108 run #1388 verdict comment, 2026-10-04). Human readers use the verdict text to judge merges, so it must not contradict the issue count. Gating is unchanged: exit code still derives from should_block. Details in #556.

Testing

Chunked review merged a contradictory report when chunks returned
issues with an empty summary field: the header counted the issues but
the fallback summary printed 'No issues found across all chunks.' (live:
gaira PR #108 run #1388 verdict comment). The fallback keyed only off
summaries/any_error and never consulted the collected issues.

Extract the decision into merged_chunk_summary() with an explicit
issue-count branch (issue_count > 0 and any_error now compose into one
honest message), unit-test all five outcomes. Gating is unchanged:
exit code still derives from should_block.

Fixes #556
@ajianaz
ajianaz merged commit a5bcf6e into develop Oct 4, 2026
14 checks passed
@ajianaz
ajianaz deleted the fix/556-chunked-summary-footer branch October 4, 2026 14:55
ajianaz added a commit that referenced this pull request Oct 8, 2026
)

Covers security hardening (#563, #572, #573), fixes (#553, #561, #562,
#564, #565, #574-#576), and the ignore-pattern semantic changes from
#577 that can alter which files existing configs exclude.

Signed-off-by: ajianaz <ajianaz@users.noreply.github.com>
Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant