I’m happy to give the beta a try.
What does “the rest” include? Two or three times I’ve had a pattern go bad on my development v3 (I do regular backups, so the first symptom was that the BIN file downloaded from http://pixelblaze-IP.local/p/patternID was malformed and the EPE/JS extraction failed). When I looked at the pattern on the PB itself, I couldn’t even edit, select or export the pattern. The most recent time it happened, I imaged the EEPROM and tried to extract the pattern from the SPIFFS segment, but I couldn’t figure out the right parameters to get MKSPIFFS to mount the volume (I tried -b 4096 -p 256 as they’re the Arduino defaults for ESP32 flash) so I gave up. Haven’t seen it on other v3s, though that may be because they’re used only for display purposes so they have no editing activity and thus less flash wear.
What did you decide about persisting the editor contents into browser local storage? It looks like it would be pretty easy to stash the current pattern code and a compilation ID into local storage after each compilation, and to populate an empty editor from local storage if the PB engine’s compilation ID matches the one in local storage. (And once you’ve got the pattern in local storage, there’s a browser-based GIT client that would only take a handful of lines to integrate into the editor.)