Skip to content

fix(cli): Report final per-file finding counts#293

Merged
dcramer merged 1 commit intomainfrom
codex/final-finding-counts
May 6, 2026
Merged

fix(cli): Report final per-file finding counts#293
dcramer merged 1 commit intomainfrom
codex/final-finding-counts

Conversation

@dcramer
Copy link
Copy Markdown
Member

@dcramer dcramer commented May 6, 2026

Warden now derives per-file finding counts from the final post-processed findings array, so rejected verification candidates no longer survive into completed CLI output. This keeps interrupted or verification-rejected runs from showing a stale per-file finding marker next to a final "No findings" report.

Final Finding Counts

Shared report-file helpers count final findings against primary and additional locations while preserving per-file timing and usage metadata. Both the SDK and CLI report paths now use the same helper.

Ink Completion Output

The Ink runner refreshes completed file state from the final skill report before printing the static summary, preventing raw hunk candidates from leaking after post-processing.

Validated with pnpm lint, pnpm run typecheck, pnpm test, and pnpm build.

Use post-processed findings when building per-file report counts and when printing completed Ink file summaries. This keeps rejected or interrupted verification candidates from appearing after the final skill report says no findings.

Co-Authored-By: GPT-5 Codex <noreply@anthropic.com>
@dcramer dcramer marked this pull request as ready for review May 6, 2026 22:17
@dcramer dcramer merged commit 4d1cc16 into main May 6, 2026
14 checks passed
@dcramer dcramer deleted the codex/final-finding-counts branch May 6, 2026 22:20
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