Package for winget

[vstrelnikof]

winget install poltertype should work — the MSI we already ship is exactly what winget wants (per-user, no UAC prompt, silent-install capable).

Steps:

1. Generate the manifest with wingetcreate against the latest release MSI and submit the PR to microsoft/winget-pkgs. Suggested identifier: JustCode.PolterType.
2. See whether automated validation accepts the unsigned MSI. It may — MSI + Mark-of-the-Web handling is gentler than for .exe — but if SmartScreen reputation blocks it, we park the PR and retry the moment signed installers ship (in progress separately).
3. Once merged, add the winget install line to the README install table and the site's Windows download card, and wire manifest updates into the release flow (wingetcreate update is scriptable from CI; a follow-up PR to release.yml is welcome as part of this).

Worth knowing: winget upgrades and the built-in self-updater coexist fine — the updater only swaps installs it owns, and an MSI-over-MSI upgrade keeps the per-user layout. No special handling needed, just honest docs.

[vstrelnikof]

Manifests staged in PR #17 — packaging/winget/, the standard trio
(version, installer, locale.en-US) under JustCode.PolterType as you
suggested.

Hand-written rather than wizard-generated so the metadata — description,
tags, support URLs — is reviewed like code. wingetcreate update takes over
from there and is the documented way to bump; packaging/README.md has the
exact invocation.

Two things pinned deliberately in the installer manifest: Scope: user,
because the MSI is per-user by design (installers/wix/main.wxs) and that is
what lets it install without elevation — if it ever becomes per-machine,
Scope has to change with it or winget promises something the installer does
not do. And UpgradeBehavior: install, since MSI-over-MSI keeps the per-user
layout.

You were right that the built-in updater and winget coexist without special
handling — the updater only replaces installs it recognises as its own.

The open question is still open: the unsigned MSI. Nothing here can answer
whether automated validation accepts it; that is what submitting finds out. If
SmartScreen reputation blocks the PR, park it and retry when signed installers
ship — do not work around it.

Not submitted. That is a PR to microsoft/winget-pkgs under your account,
and it stays a deliberate human step. Once merged, the README install table
and the site's Windows card get the winget install line — not before.