Lataa WinTUI 2.9.1

Hardening & correctness — a security and robustness pass over the paths that elevate, self-update, run external commands, and mutate shared settings. No new features and no breaking changes; settings.json and cache.json are unchanged and normal install/upgrade/uninstall behavior is identical.

- Elevated-helper hardening. The elevated helper now requires a per-session token on every request and validates winget arguments against a strict allowlist (known verb + the exact flag shapes WinTUI emits), rejecting unknown actions and installer-escalation flags (--override, --custom, --location, --manifest).
- Pinned binaries. winget and powershell.exe are resolved to absolute system paths before every spawn, with winget validated under a known WindowsApps location; the elevated path errors rather than running an unpinned binary.
- Self-update fails closed. The self-upgrade handoff aborts with an actionable error if winget can't be resolved to a trusted path, and the canary-only rehearsal override is compiled out of release builds.
- Correctness fixes. Removed a 1000-package list cap that silently truncated large inventories; settings mouse clicks route to the correct row in both header layouts; deterministic winget error messages; a new doctor "State dirs" row surfaces previously-silent config/cache directory failures.
- Internal robustness. Fixed a UI-loop vs background-refresh data race on shared settings; serialized the elevation pipe with cancellable contexts (stuck elevated actions can be cancelled; a dropped connection no longer leaks a handle); validate import ids/versions and cleanup roots before use.