Bot for Windows 0.8.0 — redesigned interface

Close the old Bot app. Extract this entire ZIP into a new folder, then open Bot.exe.
Keep the DLL files and runtimes folder alongside Bot.exe. Your remembered login and
pending request are reused from your existing Windows profile.

Requires Windows 10/11, .NET Framework 4.8, and Microsoft Edge WebView2 Runtime.
WebView2 is present on most Windows 10/11 PCs. If Bot asks for it, run the included
MicrosoftEdgeWebview2Setup.exe (Microsoft's official installer), then open Bot again.
The installer needs an internet connection. It is not run automatically.

The new layout uses a neutral dark palette, a bot roster with avatars and sections,
conversation bubbles, formatted replies and code blocks, a compact composer,
and optional panels for bot details and VPS activity. Light and system appearance
are available in Personal workspace settings. Bot avatars are original generated
vector illustrations; the app remains named Bot.

Enter sends. Shift+Enter adds a line. Ctrl+K searches your bots.
Your message appears immediately and remains visible while the VPS works.
Stop appears in place of Send while a task runs. It stops remaining work; it cannot
undo a command that already finished. Closing Bot leaves the VPS task running.
Reopening or signing in on another device recovers running work without resending.

Profile: edit the bot's name, instructions and profile memory; pin or archive it.
New bot: use the + beside Bot at the top of the sidebar.
Search conversation: use the magnifying glass in the conversation header.
Activity: use the monitor icon. Expand an action to see its command/output.
Copy: use the copy action under a reply or above a code block. Links copy their URL.

All model calls and command execution stay on the VPS. The Windows app only
renders the interface and forwards authenticated requests. The interface is
bundled locally and does not download scripts from the internet. Login tokens
and pending requests use Windows DPAPI; the password is not saved. The existing
VPS TLS certificate remains pinned. No model/provider settings or usage reporting
were added or changed. VPS connector remains version 0.6.0, compatible with this client.

The design follows Grok Bot's documented layout, but this is the separate Bot
product. It does not add remote desktop control, routines, attachments, or Grok's
other unimplemented backend features. Imported history remains a partial cache.

Validation: Windows build succeeds; 32 browser UI checks and 21 native bridge
policy checks pass. Browser tests use the packaged HTML/CSS/JS with synthetic
messages and the same content security policy. Windows WebView2 startup still
needs your PC test. The previous 0.6.0 ZIP remains available on the download site.

APP UPDATES

This is the one-time download needed to add the updater to older Bot clients.
Afterward, click Check for updates at the bottom of the sidebar, then Update and
restart. The app also checks once when it opens and highlights a newer version.
If no release is newer, it tells you that you are up to date.

Downloads come from the Bot release site and are checked against a signed release
manifest and SHA-256 hashes. The download completes before the app closes. A small
local updater replaces the application files, opens the new version, and waits
for its interface to load. It restores the previous files if copying or startup
fails. Your login, drafts and selected bot are preserved for the restart; an
encrypted one-time login handoff expires after 10 minutes. Tasks keep running on
the VPS. The updater never installs automatically or asks for administrator rights.

Keep Bot in a writable folder you own. The last two successful recovery backups
are kept under LocalAppData/Bot/updates. Failed update folders are retained for
recovery. A power loss or forced termination during file replacement can require
manual recovery from that backup.

The updater is the only local application-maintenance process launched by Bot;
model tools and shell commands continue to run exclusively on the VPS.
No model calls are made by checking for or installing an update.

Validation: update signature/archive validation, filesystem install and rollback,
and browser update/draft-restoration tests pass. Windows process restart and
WebView2 startup must still be tested on a Windows PC.
