Starling Windows Shell 0.1.0 — the Windows 11 shell, replaced per user

The Windows 11 shell, replaced per user: dock, Start menu, desktop, file
manager and notification tray, with Explorer kept alive underneath for
packaged apps and file dialogs. No admin rights, no system files touched —
one registry value in your own account, and Explorer comes back the moment
you ask.

Measured on the same PC, filmed side by side (medians of 20):

	Starling	Windows 11
Start menu, key to fully drawn	100 ms	300 ms
Right-click menu, complete	67 ms	267 ms
Win+E to a usable file list	83 ms	1116 ms

Install. StarlingSetup-0.1.0.exe — double-click, confirm, sign out
and back in. It installs to %LOCALAPPDATA%\Programs\Starling and registers
per user; other accounts keep Explorer, and nothing needs administrator
rights. The zip is the same payload with the options: Install.ps1 takes
-Now (switch this session), -NoRegister, and -Destination.

Leave. Uninstall.ps1 un-registers, restores Explorer's taskbar, and
removes the files (-KeepFiles to keep them). If a Starling process is
ever killed rather than closed, WinShellBar.exe --restore-taskbar puts
Explorer's taskbar and tray back — and if the shell crash-loops it
un-registers itself and hands the session back to Explorer on its own.
The full install/uninstall/recovery story: docs/WINDOWS-INSTALL.md.

Unsigned, for now. SmartScreen will warn on first run (More info → Run
anyway); a machine with Smart App Control enforcing will refuse it. Signing
is planned (docs/WINDOWS-SIGNING.md) and 0.1.0 ships before it.

The exact binary in these downloads passed the shell's 28-check gate twice:
on real hardware, and — installed from this very setup exe — on a clean
Windows 11 VM with no toolchain on it. The checks cover the session
processes, the work-area reservation, minimize and restore, the file
explorer (its context menu, and copy/move/rename/cut-paste/delete-to-bin
with their undos), packaged-app launch and identity, close-refusal, and
kill-and-respawn. Built from branch release-winshell-0.1.0, engine pinned
by the same branch name in starling-engine; the commit and engine are in
BUILD-STAMP.txt inside the archive.

sha256:

• StarlingSetup-0.1.0.exe 8c13afc77dd6834f4cc67697f689b56b2335b3dcf841d36c33cd23fecd3c4df5
• Starling-0.1.0-win-x64.zip 2d94092a2369ff99ff170e3447be3579d027f7cd98e937eefa6ecde05b554ce4