Publish Inquiry CLI to WinGet

[ccisnedev]

Goal

Publish Inquiry CLI to the Windows Package Manager (winget) so Windows users can install it with:

winget install ccisnedev.Inquiry

Package identity

Use ccisnedev as the package publisher namespace unless WinGet validation requires a different casing/form.

Proposed manifest identity:

• PackageIdentifier: ccisnedev.Inquiry
• PackageName: Inquiry CLI
• Publisher: ccisnedev
• Moniker: iq

Distribution model

Use the existing GitHub Release artifact as the installer source:

• Asset: inquiry-windows-x64.zip
• Installer model: ZIP portable package
• Expected WinGet manifest shape: InstallerType: zip with NestedInstallerType: portable

The release ZIP must expose both command names:

• bin/inquiry.exe
• bin/iq.exe

iq.exe may be a copy of the compiled inquiry.exe so WinGet can create a first-class portable command alias for iq without relying on iq.cmd from the current install script.

Implementation tasks

• Update the Windows release packaging workflow so inquiry-windows-x64.zip contains both bin/inquiry.exe and bin/iq.exe.
• Verify the packaged layout still supports runtime asset discovery for assets/ when launched as either inquiry.exe or iq.exe.
• Add or stage WinGet manifests for local validation.
• Compute and record the release ZIP SHA256 using winget hash.
• Validate locally with winget validate.
• Test local install with winget install --manifest.
• Submit the manifest PR to microsoft/winget-pkgs.

Acceptance criteria

• winget install ccisnedev.Inquiry installs Inquiry on Windows.
• iq version works after install.
• inquiry version works after install.
• iq doctor can find bundled assets and does not fail because of WinGet portable alias path resolution.
• WinGet upgrade/uninstall paths are documented or do not conflict with iq upgrade / iq uninstall.