Function has_error_severity_issues 

pub fn has_error_severity_issues(
    results: &AnalysisResults,
    rules: &RulesConfig,
    config: Option<&ResolvedConfig>,
    promote_warns: bool,
) -> bool

Check whether any issue type with Severity::Error has remaining issues.

The severity of each finding comes from the rule table in crate::effective_severity, the same table that writes the effective_severity of each finding for the CI formats and that the audit ledger reads. When overrides are configured, file-scoped findings resolve the rules for their own path. Circular dependencies resolve against every file in the cycle. Project-level findings read rules.

promote_warns mirrors --fail-on-issues: rules is expected to arrive already promoted, and the per-file override path promotes each resolved severity after override resolution so an explicit per-path warn fails the run just like the base rules would.