pub fn explain_selection() -> SelectionReport<BackendCandidate>Expand description
Explain what "auto" selection would decide over the compiled-in registry,
as the shared SelectionReport. The winning candidate is the highest-
priority backend that is both auto-eligible and available; every other
candidate carries the RejectionReason that excluded it.
This is diagnostics only (a wizard/CLI “why this backend?” trace); the
authoritative construction path is resolve_backend. Both agree on the
same winner for "auto" because both rank by descending priority over the
auto-eligible, available set.