pub fn resolve_scaling_retry_outcome(
original_status: ApplicationReturnStatus,
retry_status: ApplicationReturnStatus,
original_stats: SolveStatistics,
retry_stats: SolveStatistics,
) -> (ApplicationReturnStatus, SolveStatistics)Expand description
Resolve the final (status, statistics) after an MC64 hypersensitivity
re-solve (code review L23).
On promotion the retry is the authoritative solve, so its status and its
statistics are reported together. Otherwise the original local-infeasibility
verdict is kept — and so are the original solve’s statistics, so the
summary / JSON report never pair the original verdict with the failed
retry’s iteration count or objective. The pre-fix code reverted status to
InfeasibleProblemDetected but read app.statistics() after the retry,
leaking the retry solve’s stats into a report labeled with the original
verdict.