{"version":"2.1.196","anchor":"reportfindings-tool","canonical_anchor":"reportfindings-tool","heading":"ReportFindings Tool","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196\/e\/reportfindings-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196","markdown":"### ReportFindings Tool\n\nA new built-in tool called `ReportFindings` enables structured code review output. When a code-review workflow completes, it can report findings as a typed list \u2014 file, line, a one-sentence summary, a concrete failure scenario, verdict (CONFIRMED\/PLAUSIBLE), and optional outcome (fixed\/skipped\/no_change_needed) \u2014 so the host UI can render them as a rich list rather than freeform text.\n\n**Details**\n\n- Accepts up to 32 findings per call, ranked most-severe first.\n- Each finding includes `file`, optional `line` (1-indexed), `summary`, and `failure_scenario`.\n- `verdict` is present when a verify pass ran; absent on inline-only reviews.\n- `outcome` is set only when re-reporting after applying fixes.\n- Tool result echoes the count so the model sees confirmation without re-printing all findings.\n\n**Evidence**\n\nNew `ReportFindings` tool definition (search for `\"ReportFindings\"`)"}