feat: publish ControlFS in Windows Package Manager (WinGet) #273

Problem

ControlFS has a Windows installer, but users cannot discover, install, or update it through Windows Package Manager (WinGet).

Goal

Publish ControlFS in the public WinGet catalog and keep the package current with stable ControlFS releases.

Requirements

• Select a stable package identifier and accurate publisher, description, license, project URL, and release metadata for ControlFS.
• Use the official published Windows installer from a stable release URL, with the correct architecture, installer behavior, and SHA-256 hash.
• Create and validate the WinGet package manifest against the current Windows Package Manager requirements.
• Verify clean installation, application launch, upgrade from an older packaged version, and uninstall on supported Windows versions.
• Submit the manifest to the public Windows Package Manager repository and address validation or review feedback.
• Define how new ControlFS releases will update the WinGet manifest without publishing a package before its official installer is available.
• Document the WinGet install and upgrade commands after the package is accepted.
• Preserve the existing direct installer, portable build, and in-app update behavior.

Acceptance Criteria

• ControlFS is discoverable in the public WinGet catalog by name and stable package identifier.
• A clean WinGet installation launches the released ControlFS build successfully.
• WinGet upgrade detects and installs a newer stable release without changing user settings unexpectedly.
• WinGet uninstall removes the installed app through the supported installer path.
• Manifest metadata, installer URL, architecture, version, and SHA-256 hash match the official release.
• The release process includes a documented step to maintain the package for future stable versions.
• Existing installation methods remain functional.

Dependencies

• Requires a stable official Windows installer and release URL.
• Related to chore: set up code signing for releases #84 — chore: set up code signing for releases.
• Related to epic: 1.0 readiness #94 — epic: 1.0 readiness.

References

• https://learn.microsoft.com/en-us/windows/package-manager/package/manifest
• https://learn.microsoft.com/en-us/windows/package-manager/package/repository

MoSCoW: Could have · Milestone: 9 · 1.0 Readiness