Release 1.1.0: Windows executable downloads

[williajm]

Prepare v1.1.0 with a Windows x64 executable that runs without Python or uv. Version tags build and smoke-test the Nuitka folder bundle and single executable, then attach glidepath-X.Y.Z-windows-x64.exe to the GitHub Release alongside the Python packages. A failed Windows build blocks publication; ordinary pushes and PRs do not compile binaries.

• Bundle the existing Glidepath icon, UK data and distribution metadata; verify relocated executables with real spawned Monte Carlo workers, GUI rendering and plan save/load.
• Keep the Windows artifact out of the PyPI upload and include it in GitHub build provenance. The executable remains unsigned for Windows publisher trust, which the download instructions explain.
• Bump the project and lockfile to 1.1.0, prepare the dated changelog, and update the README, getting-started guide, packaging guide, release process and GitHub Pages installation section. The site links to the releases page and retains the uv fallback while the first executable release is pending.
• Lock Nuitka and compression tooling under the existing seven-day cooldown; verify the required Windows Dependency Walker download by checksum and audit all dependency groups.

Validation: make check, make audit, and actionlint; a native Windows 1.1.0 onefile build and versioned release smoke-test rehearsal; Chromium previews at desktop/mobile sizes in light and dark mode. Build tests use an inert compiler stand-in to exercise failures without compiling in PR CI.

After merge, tag the merge commit v1.1.0 and approve the existing PyPI deployment gate to publish the release. Authenticode signing remains follow-up work.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
95.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud