[davidmckayv]

Three bugs the Windows pass of merged work found.

A Bot's orb is one color everywhere. The Personal Assistant's orb was green in the sidebar, the Bots list and the command menu, and blue, teal and pink at the top of its page and of its conversation. Both came from the same palette (orbPalette), drawn two ways: still at avatar sizes, and as AgentOrb's mesh when larger, where the palette's third stop, a violet in most palettes, lay across the top, and the idle state muted it. Now the live orb draws the still orb's sphere (.bot-orb-still and .bot-orb-live side by side in styles.css), with its sweep turning, and a Bot's orb keeps its palette in every state (trueColors). The onboarding pictures' Bot orbs and the OpenBot for Business orb, which say they are drawn as a Bot's, follow.

OpenBot Desktop draws its app from the published server images it runs, so Desktop shows the one-color orb once those images include this commit; the web app has it on merge.

A maximized window reopens maximized. After tray Quit with the window maximized on Windows, it came back at 1000 by 800 in the middle of the screen, and the log said "put back off every screen; moved onto the primary one". The saved state was right (maximized, with its place before it was maximized). Windows hangs a maximized window's frame past the screen by its resize border, so its outer position is -8,-8 on a 1920 by 1080 screen and the top 8 pixels of its title bar are above the work area. Launch read that as off every screen and moved it, which un-maximized it; its height fit would have resized it too. A maximized or full-screen window is now left as the system placed it, which also keeps a zoomed Mac window zoomed. A window that really is off every screen still comes onto the primary one. tauri-plugin-window-state (2.5.0, the current release) already saves and restores the state; it has no fallback onto the primary screen for a screen that is gone, so the launch fit stays ours and is fixed.

The Windows installer's status line says plain lines only. The Install section's "Output folder:", "Create folder: C:\Users...\AppData\Local\OpenBot\cli-bundle...", "Extract: ...", "Created uninstaller:" and "Create shortcut:" lines go to the details list, under "Copying OpenBot's files.", as the old version's removal already does. A leftover WebView2 bootstrapper is deleted under the plain line. FileFunc's GetSize, which Tauri uses to size the uninstaller, says "Size:190 Kb Files:1 Folders:" on the status line and switches it back on when it ends, so "Create shortcut: C:\Users...\OpenBot.lnk" showed after it on the first live run; the uninstaller's size is now read quietly and GetSize skipped. (The WebView2 "Execute:" line was already fixed by #1544.)

Tests, red before and green after

• app/tests/bot-orb-one-color.test.tsx (real Chromium, in the CI browser job): the real sidebar row, Bot page header and conversation intro, all eight palettes, light and dark; each orb's mean color in OKLab. Before: 14 of 16 comparisons per theme apart, the Personal Assistant's hue turned 47°, the furthest 116°. After: every palette within 4.3 and 5°.
  The same test run in Playwright WebKit (headless) is red on main the same way and green on this branch.
• a_maximized_window_reopens_maximized_where_the_system_put_it (Rust): Windows maximized geometry (-8,-8, 1936 by 1056 on 1920 by 1080), maximized on a second screen, zoomed on a MacBook, a window really off every screen, and the saved maximized place. Before: the maximized window was moved Onto(0,0).
• desktop/scripts/installer-update.test.ts: runs the Install section and the WebView2 download and install in order, tracking SetDetailsPrint, and fails on any NSIS instruction that would put a path on the status line. It follows a Goto and counts GetSize and Locate as status lines. Before: 9 such lines in the Install section; on the first fix, GetSize and the 2 shortcut calls after it, as the live run showed.