[junjuny0227]

Summary

Ship Repot through winget. The first versions were submitted by hand as two packages, microsoft/winget-pkgs#471175 (junjuny0227.Repot, the .msi) and microsoft/winget-pkgs#471176 (junjuny0227.RepotCLI, repot.exe from the CLI zip, command alias repot). This adds the workflow that submits every later release, and fixes the MSI's publisher name. Spec §14 updated.

Type

• feat
• fix
• refactor / chore
• docs
• ci / build

Changes

• .github/workflows/winget.yml: on release: published (or workflow_dispatch with a tag), vedantmgoyal9/winget-releaser@v2 opens one PR per package from the junjuny0227/winget-pkgs fork, using the previous version as the base. Installers: _x64_en-US.msi for the app, repot-cli-*-x86_64-pc-windows-msvc.zip for the CLI. Token: WINGET_TOKEN (classic PAT, public_repo + workflow, registered by the owner).
• tauri.conf.json: bundle.publisher = "junjuny0227". The 0.9.0 MSI reports its publisher as github (taken from the identifier), which is what Apps & features shows; from the next release it shows the owner's name.
• Spec §14: how winget is published, and that README/site install instructions wait until the first version is accepted.

Checks

• cargo fmt --check
• cargo clippy --workspace --all-targets -- -D warnings
• cargo test --workspace
• pnpm --filter @repot/desktop typecheck / test / build
• Ran the real flow if behavior changed (--example scan / --example export, or tauri dev)
• Not checked locally, CI only (say which, e.g. Windows/Linux providers, shellcheck): the workflow first runs on the next published release; the MSI publisher change shows only in the next Windows build

actionlint, pnpm exec biome ci ., node scripts/check-version.mjs v0.9.0. The hand-made 0.9.0 manifests validated against the winget 1.12.0 JSON schemas (only PyYAML's date parsing differed) and were submitted with komac 2.17.2; MSI fields (ProductCode, UpgradeCode, scope, install location) came from komac analyze on the released file.

Spec and generated files

• Spec updated in this PR if a product decision changed, or no decision changed
• Generated files regenerated from their source, not edited by hand (scan.json, snapshots/, icons/) (not touched)
• Snapshot diffs read and intended (not touched)

Boundaries

• repot-core does not depend on Tauri and does no network calls (not touched)
• Commands and file reads go through Env; tests use FakeEnv and fixtures, not real tools (not touched)
• No new crate or npm dependency, or the plan/spec was updated first
• The app still only reads the device; it writes only to the export folder (not touched)