The Astro app consumes significant amounts of RAM. Swap and virtual memory on MacOS is handled differently to other systems (namely Windows) so when your system runs critically low on working memory, MacOS’s watchdog service may simply reboot the machine. As a developer, I am constantly working right up against the limitations of my machine’s working memory; Several Chrome tabs, several OpenCode windows, Xcode, VSCodium/VSCode, OpenDesign, etc. all open at once. Memory gets tight.
My suggestion is to separate the Astro front end from the backend updater. The updater process could be slim and run as a service at startup, consuming only a few tens of megabytes of memory while it is waiting for its time to perform its updates. The Astro front end could be closed and not consuming any system memory at all until I open the Astro application.