Brooklyn Nicholson e1ccd674c0 fix(desktop): apply the stale-installer marker guard to both hand-offs ... Both hand-off sites pre-write the update marker: the in-app Update button (applyUpdates) and the Windows bootstrap-recovery path (handOffWindowsBootstrapRecovery). Either one can strand a user on a pre-#74782 staged installer, and the recovery path is worse — it fires when the install is already unhealthy, so a refused claim there wedges the very repair meant to heal it. Route both through stagedUpdaterSupportsPrewrittenMarker and log the skip so the reason is visible in desktop.log instead of looking like a missing write. Also document on copy_self_to_hermes_home that its --update no-op is what lets an installer-protocol change strand the entire installed base on a binary that predates it — the root enabler of this class of bug.		2026-08-01 20:43:08 -05:00
..
public	…
src	fmt(js): `npm run fix` on merge (#65229)	2026-07-15 21:40:56 +00:00
src-tauri	fix(desktop): apply the stale-installer marker guard to both hand-offs	2026-08-01 20:43:08 -05:00
.gitignore	…
eslint.config.mjs	refactor(lint): hoist shared eslint + prettier config to root	2026-07-16 01:42:02 +05:30
index.html	…
package.json	fix: fix @nousresearch/ui version, update to npm 12	2026-08-01 17:05:42 -04:00
tsconfig.json	…
tsconfig.node.json	…
vite.config.ts	…