Provide a Chocolatey package for Windows users

[karlhorky]

Cap has Windows downloads, but no Chocolatey package.

This makes it harder to install and update Cap in Windows setup guides and environments that standardize on Chocolatey.

I already opened a Chocolatey Community Package Request here:

• RFP - cap chocolatey-community/chocolatey-package-requests#1649

Proposed solution

Publish or support a Chocolatey package for Cap, so Windows users can install and update it with Chocolatey.

Ideally, the package would support an install command like:

choco install cap --yes

If the Cap team does not want to maintain the package directly, confirming support for the community RFP would still help package maintainers use the official project and download URLs.

Additional Context

• Software project URL: https://cap.so/home or https://github.com/CapSoftware/Cap
• Windows download URL: https://cap.so/download/windows

[linear]

CAP-680

[tembo]

This is related to #1714, which discusses winget integration. That issue notes that Cap uses CrabNebula Cloud for Windows installer distribution rather than GitHub releases - see .github/workflows/publish.yml.

For Chocolatey package maintenance, the installer details are:

• Filename pattern: Cap_{version}_x64-setup.exe (NSIS installer)
• Product name: Cap (from tauri.prod.conf.json)
• Download URL: https://cdn.crabnebula.app/download/cap/cap/latest/platform/nsis-x86_64 (latest) or versioned via the CrabNebula CDN

The build process in publish.yml shows that Windows installers are code-signed via SignPath before upload. A community-maintained Chocolatey package could pull from the CrabNebula CDN URL, though the discussion in #1714 proposes also uploading installers to GitHub releases which would benefit both winget and Chocolatey automation.