Lotus CIandClaude Opus 5.5
67253d02f8
Build Lotus Chat Desktop / prepare (push) Successful in 7s
Build Lotus Chat Desktop / build-windows (push) Successful in 34m32s
Build Lotus Chat Desktop / build-linux (push) Successful in 36m5s
Build Lotus Chat Desktop / build-arch (push) Successful in 19s
Build Lotus Chat Desktop / update-manifest (push) Successful in 4s
- Launch-on-login now starts the app with `--autostart`. With "Start minimized" on (the default), that launch begins "settled", so neither the page-load reveal nor the 8 s failsafe shows the window: it stays in the tray with sync and notifications running. The tray, a second launch or a deep link reveals it. - The choice is a file in the app config dir (`start-minimized`), read before the web client loads; `get_start_minimized` / `set_start_minimized` back the new Settings switch. - Existing registrations made without args are rewritten at startup (re-enable), so current launch-on-login users get `--autostart` too. - window-state no longer restores VISIBLE: it show()ed the window at creation whenever it was last closed visible (or on first run), before the page painted and even on a login start. Visibility is owned by the page-load reveal + failsafe. Verified on Linux under Xvfb with the debug build: normal launch → shown; --autostart → hidden (past the failsafe) and still running; --autostart with the setting off → shown; --autostart after quitting visible → hidden; normal launch after quitting visible → shown; a second launch reveals the hidden instance; an existing autostart entry gets `--autostart` added. Bump cinny (the Settings switch and the SW protocol guard). Closes #3 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA