fix: clean-lens findings + trim the dogfood swarm to strong reviewers (#4)

emit() now skips findings extraction for a "No material issues found"
lens (its path:line refs are verification notes, not problems), fixing
the FP inflation that penalized thorough clean-pass reviewers. Also trims
the dogfood swarm to the strong reviewers: drops m5/qwen3.6 (last local
lane), gemma4, gpt-oss:120b, and kimi-k2.7-code — leaving 6 cloud +
claude-code/sonnet.

Fittingly, PR #4's own 11-model review produced 43 findings that were ALL
clean-verification bullets (zero real) — a live demonstration of the bug
this fixes. gofmt clean, go vet quiet, go test -race green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-authored-by: Steve Dudenhoeffer <steve@stevedudenhoeffer.com>
Co-committed-by: Steve Dudenhoeffer <steve@stevedudenhoeffer.com>

README.md

@@ -350,9 +350,13 @@ context (`GADFLY_REPO`, `GADFLY_PR`) automatically.
 
 Findings are extracted heuristically from each lens's markdown — a `path:line`
 reference anchors a finding, titled by the nearest preceding heading / numbered
-item / bold lead-in. The emit is strictly best-effort: a short (~10s) timeout,
-any error (or a non-2xx response) is logged to stderr only, and it **never**
-changes the review output or the exit code.
+item / bold lead-in. A lens whose verdict is **"No material issues found"**
+emits **no** findings: its `path:line` references are verification notes
+("verified X is safe"), not problems, so extracting them would record false
+positives and unfairly penalize thorough clean-pass reviewers. The emit is
+strictly best-effort: a short (~10s) timeout, any error (or a non-2xx response)
+is logged to stderr only, and it **never** changes the review output or the exit
+code.
 
 ## Building locally