發布日期：2026-06-22
在打包好的獨立 App 裡點擊產出分析報告時，不會再因為遇到一個 bad local file header 錯誤就整個崩潰了。以前報告相關的程式碼是被硬塞在一個壓縮包（zip）裡，要用的時候才解壓縮，所以只要裡面有任何一個檔案壞掉，產生報告的瞬間就會整組壞光光。現在系統直接把它們解開成真實的資料夾來讀取，完全避開了這個風險；同時也順手把壓縮包裡不必要的測試程式清掉，讓出錯的機率變得更低。就像以前你把所有工具都塞在一個打不開的生鏽鐵箱裡，現在直接把它們排在架子上，要用哪個拿哪個，再也不會因為鐵箱卡住而沒戲唱了。
When clicking to generate an analysis report in the packaged standalone App, it will no longer completely crash due to a bad local file header error. Previously, the report-related code was jammed into a zip archive and unpacked lazily, meaning if a single file inside was corrupted, the entire report generation would blow up instantly. Now, the system extracts them into real directories for reading, completely bypassing this risk; at the same time, unnecessary testing programs were stripped from the archive, further lowering the chances of anything going wrong. It's like you used to shove all your tools into a rusty toolbox that wouldn't open — now you just organize them cleanly on a shelf, grab what you need, and never have your work halted by a stuck latch.
**Analysis report no longer crashes with "bad local file header" inside the packaged .app**: the report modules (`analyzer`/`adapters`/`ui`) were compiled into the bundle's `python313.zip` and loaded lazily via `zipimport`, so a single corrupt zip entry surfaced as a `ZipImportError` the moment a report was generated. They are now unzipped into the bundle as real directories (py2app `packages`), bypassing `zipimport` entirely. The bundle's `python313.zip` also no longer ships CPython's test suite, pytest, or setuptools, shrinking it from 1665 to 819 entries and cutting the surface for a corrupt entry. This deepens the packaged-report fix from 0.22.2.