Skip to content

Fix revived non-actionable review findings and stale summaries - #292

Merged
tzhouam merged 2 commits into
mainfrom
fix/strict-review-final-findings-20261002
Oct 2, 2026
Merged

tzhouam merged 2 commits into
mainfrom
fix/strict-review-final-findings-20261002

Conversation

@tzhouam

@tzhouam tzhouam commented Oct 2, 2026 •

Copy link
Copy Markdown
Collaborator

Coverage promotion and the second review round could revive concerns the ensemble reducer had rejected, while verification confirmed true code facts without establishing a current defect. This produced unsupported findings and a summary describing an earlier selection.

Carry rejected candidates and their reasons into promotion, the second round, and verification. Require a current trigger and adverse effect or unmet requirement in the verifier guidance, and drop explicit not_actionable verdicts. When refinement, disposition filtering, or comment limits change the selected findings, derive the summary from the final set instead of publishing stale reducer prose.

Validation: 179 review, ensemble, anchor, planner, SDK, and output-contract tests passed, including regressions for revived harmless configuration facts, hypothetical future validation failures, and stale summaries after findings are added or removed. The complete offline suite also passed (2,432 collected; 19 skipped). SPEC freshness passed.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@tzhouam
tzhouam merged commit d40616f into main Oct 2, 2026
2 checks passed
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