Changelog

Render GitHub release notes on the Dashboard as Markdown. The "Release Notes" panel that pops out from the update banner used to display the raw Markdown source (bold, # headings, link). It now renders proper formatting — headings, lists, bold/italic, links, tables, task lists, syntax-highlighted code blocks (via highlight.js with GitHub-dark colors), and GitHub-style autolinks for @username and #issue references — all sanitized through DOMPurify so untrusted release-body content can never inject script. Links open in a new tab so the Dashboard never gets navigated away from.

About page with diagnostics, accessible from the navigation. A new read-only page that surfaces, in copy-friendly form: version / commit / branch, GPU vendor and VRAM, driver versions and dates, encoder probe results (H.264 / HEVC / AV1 with YUV444), reference-frame-invalidation support, virtual display backend status, HDR state on each connected display, Windows OS version and edition, and the Windows Insider channel and ring when applicable. Designed to be screenshotted or copied straight into a support ticket or GitHub issue.

High Performance Streaming card on the Dashboard. New one-click profile that retunes virtual display, display automation, double-refresh workaround, encoder preset, NVENC HAGS, and minimum CPU thread count for high-end host setups. Vendor-aware: NVENC settings on NVIDIA, AMF analogs on AMD, QuickSync analogs on Intel. Snapshots the user's prior settings to local storage on enable, with explicit "Restore Previous User Settings" and "Restore to Default" actions on the card. Tested on an NVIDIA Blackwell 5080-class GPU, Intel Core i9-12900KS, 64 GB RAM, Wi-Fi 6E to Wi-Fi 5 Moonlight clients, and 10 Gbps host networking.

Correct "Windows 11" labeling in diagnostics. On Windows 11 hosts, the About page (and any other consumer of the platform product-name metadata, including support bundles) was showing "Windows 10 Pro" / "Windows 10 Enterprise" / etc. because Microsoft deliberately leaves the registry's ProductName value as "Windows 10 X" on Windows 11 for application-compatibility reasons. The product name now disambiguates by build number (≥ 22000 → Windows 11) and rewrites the marketing prefix accordingly. Idempotent: if Microsoft ever updates the registry value natively, the rewrite becomes a no-op.

Web UI dark palette swap. Dark theme accent moved from Indigo to Alexa Cyan to align with the LuminalShine brand identity.

Wix bootstrapper sticky-footer layout. The Install / Update / Uninstall / Close buttons in the installer's bootstrapper window are now always visible. Previously, when the install section grew (driver chooser, currently-installed banner, tips, status), the content card pushed the footer row past the visible window bottom. Content above now scrolls; the footer stays pinned. Window minimum width was bumped 760 → 880 px (target 920 px) so the worst-case button row no longer clips the rightmost actions.

Wix bootstrapper UI accent. The installer's accent color is swapped from Indigo to Alexa Cyan to match the web UI's brand direction.

Streamlined installer downloads. The standalone .msi is no longer published as a separate release artifact. The bootstrapper .exe already contains the MSI as its embedded payload, so end users get a single installer (LuminalShine-Windows-AMD64-installer.exe) and the portable archive (LuminalShine-Windows-AMD64-portable.zip). No behavior change — installing the .exe writes the same Windows Installer database that the MSI did.

Critical fix: admin credentials and Moonlight pairings no longer reset on service restart. Two separate failure modes were corrupting the host state file: a write race between the credentials-save path (saveusercreds) and the pairings-save path (savestate), both targeting sunshinestate.json with inconsistent locking, and non-atomic file writes that could leave a truncated file behind if a concurrent operation interrupted the write. Concurrent pair events landing in the window between the credentials handler's read and write would silently roll back any pairings added in that window, and a partial write would cause the next startup to reject the file outright — wiping credentials, the unique host ID, and every paired device.

Atomic writes. State and credentials file writes now go through a temp-file-plus-rename path (MoveFileExW on NTFS). Concurrent readers and crash recovery see either the full prior contents or the full new contents — never a partial file.

Mutex coverage. saveusercreds, reloadusercreds, and the password-change HTTP handler now all serialize against the same lock that save_state already used. Pair events and credential changes can no longer interleave destructively.

Defensive read-back. After saving a new password the host immediately re-hashes the supplied password against the salt it just wrote, compares it to in-memory state, and returns a 500 "Failed to persist new credentials" if they don't match — so a write that succeeded on the API surface but failed at the filesystem (permissions, antivirus quarantine, etc.) is now reported at save time instead of silently failing at the next login.

Separate credentials file. Admin credentials now live in their own sunshinecredentials.json next to sunshinestate.json instead of sharing the file with pairings. Existing installs are migrated automatically on first launch: any legacy username/salt/password at the top of sunshine_state.json is moved to the new file and stripped from the state file. Idempotent — once the dedicated file exists, the migration is skipped forever.

Regression coverage. New unit suite locks down the atomic-write contract (replaces target, leaves no .tmp, creates parent dirs), the migration round-trip (creds moved, legacy keys removed, paired devices under root.named_devices preserved), and migration idempotency.