mirror of
https://github.com/stablyai/orca.git
synced 2026-10-19 16:03:26 +00:00
The fallback marker is scoped to appVersion+electronVersion so a new build gets a fresh hardware attempt. That scoping also discarded what we knew about the machine: bundle 3GyOWOzGskzdXqlEG8z4UQ shows an update invalidating the marker, then the full crash burst and relaunch again. With a ladder that is worse -- each update re-walks it from the bottom. Record the strongest tier a machine has needed in a version-independent file. The post-update hardware probe still happens; when it fails the app resumes at the known tier instead of starting over. Monotonic, so a shallower later burst cannot talk a known-bad machine back down a rung, and a hint only -- any read failure degrades to normal escalation.