Module result 

What one analysis pass produced.

A single pass over a file can produce findings AND fail to fully analyze the file (a truncated response gives a partial list, an unknown severity in one record fails the file, a transport error produces zero findings but still surfaces as a failure). Reporting the findings while forgetting the failure is the exact bug this type exists to prevent — the gate would green-light a commit whenever the LLM endpoint was unreachable, which is worse than having no gate at all.

failed_files is a BTreeMap rather than a Vec because two passes over the same file set must UNION, never sum. Summing counts one unreachable endpoint twice, drifting the failure count up without any matching file to investigate. The map’s value carries the reason so the caller can render something a user can act on, not just a path.

dropped_out_of_range counts rather than silently drops out-of-range findings so that a model which consistently reports wrong lines is observable to the caller — not invisible.

Structs

AnalysisResult

What one analysis pass produced.

ProviderFailure

One provider’s contribution to a file that no provider could analyze.

Enums

FailureReason

Why one file went unanalyzed.

Functions

union_failures

Fold src into dst, keeping the reason already present on a collision.