Usage 0.22.2

如果你是直接執行打包好的獨立 App（.app），現在產出年度報告時不會再直接當掉了。以前在算年度回顧時，系統會去抓鳳凰或飛龍的圖片，但它找圖片的路徑是用給開發者看的原始碼路徑，所以在打包好的 App 裡根本找不到，導致整個報告出不來。現在它懂得在打包好的資源資料夾裡找圖片了，讓報告能順利生出來。就像你把食譜帶去別人家廚房煮菜，以前一直去原本家裡的位置找鹽巴所以煮不出來，現在懂得在別人家的調味料櫃裡找了。

If you're running the standalone packaged App (.app), generating the annual report will no longer cause it to crash outright. Previously, when calculating the year-in-review, the system tried to fetch the phoenix or dragon images using a source code path meant for developers. This path didn't exist inside the packaged app, causing the entire report generation to fail. Now, it knows to look for the images inside the bundled resources folder, ensuring the report generates smoothly. It's like taking a recipe to cook in someone else's kitchen: you used to fail because you kept reaching for salt in the exact spot it is in your own house, but now you know to look in the host's actual spice cabinet.