pub fn unloaded_output_flag(loads: &[BoundaryLoadBinding]) -> Option<String>Expand description
WSL/NaN triage flag: Some(flag) when a circuit’s OUTPUT boundary is left
electrically open — either an analyzed boundary whose disposition is
Unloaded{reason}, or an EMPTY table (no feedback group ever reached the
general-MNA call site, e.g. the whole pedal compiled via blockwise/other
paths — the boundary was never even analyzed). The two absence modes are
surfaced DISTINCTLY because they need different fixes (widen the policy vs
widen the analysis coverage).
WHY this flag rides next to the bias verdict: unloaded output boundaries and marginal op-points travel together — the stage solves against an open circuit, so the compile-time op-point never feels the load-current demand, and the resulting bias sits closer to cutoff/rail than the real circuit’s. Live cases: Klon Centaur (renders +16 dBFS over on macOS and NaN-flushes to silence on x86/WSL), ProCo RAT, Pultec — all with silently-unloaded output boundaries. This table is the triage lever for the ~76 corpus failures.