Brooklyn Nicholson 36e2228a4c fix(desktop): latch a confirmed remote reauth failure so the overlay stays clickable ... shouldLatchBackendStartFailure deliberately never latches a remote failure: remote faults are usually transient and must stay retryable without an app restart. A confirmed reauth rejection is the exception — it cannot self-heal, because nothing changes until the user signs in again. Worse, not latching actively prevents the recovery it was protecting. A non-latching remote boot failure re-runs startHermes on every getConnection/api call, re-emits running: true, and the boot-failure overlay (visible = Boolean(boot.error) && !boot.running) hides itself — so the "Sign in" button flickers out from under the user before it can be clicked. Add shouldLatchRemoteReauthFailure as a separate predicate rather than changing the existing one, so transient remote failures keep self-healing. The two latches are complementary and never fire for the same failure.		2026-07-25 21:52:45 -05:00
..
bootstrap-installer	ci(js-tests): split check into parallel matrix shards per workspace (#70252)	2026-07-23 18:45:16 -04:00
desktop	fix(desktop): latch a confirmed remote reauth failure so the overlay stays clickable	2026-07-25 21:52:45 -05:00
shared	ci(js-tests): split check into parallel matrix shards per workspace (#70252)	2026-07-23 18:45:16 -04:00