Fixed occasional report failures by moving all modules out of zipped loads
If you occasionally encountered a ZipImportError that crashed your analysis report, this issue is now completely resolved. The problem happened because the reporting system needed three stray files that were still awkwardly trapped inside the python313.zip archive—the exact same root cause behind an earlier UI crash. The engineers have now moved all three of these files safely inside the dedicated report folder, meaning the entire report pipeline no longer needs to unzip anything to run. It's like a factory assembly line where workers previously had to run to an outside warehouse and frantically tear open cardboard boxes just to grab three specific screws, occasionally ripping the box and stalling the line; now, those screws have been moved to the parts bin right next to the conveyor belt, perfectly within reach.