Windows: /upgrade on a winget install replaces the WinGet\Links alias and leaves winget/Add-Remove Programs on the old version

Finding: A single external report (no KFA reproduction) says that on Windows 11 x64 with GitHub Copilot CLI installed through winget (GitHub.Copilot, portable, user scope), the built-in /upgrade from 1.0.89 to 1.0.91 bypasses winget and leaves package-manager records stale. Source: https://github.com/github/copilot-cli/issues/5096 Reported symptoms: after /upgrade, copilot --version reports 1.0.91, yet winget list --id GitHub.Copilot still shows v1.0.89 with v1.0.91 offered as an available update. The per-user Uninstall registry key for GitHub.Copilot reportedly still has DisplayVersion v1.0.89, so inventory tooling that relies on install records would report the wrong version. [https://github.com/github/copilot-cli/issues/5096] Reported file-level state: the reporter compared WinGet\Links\copilot.exe with the binary in WinGet\Packages\GitHub.Copilot_Microsoft.Winget.Source_8wekyb3d8bbwe. The Links entry reportedly no longer has a LinkType (not a symlink) and has product version 1.0.91, while the package-folder binary remains 1.0.89. Other winget portable packages in Links are reportedly still symlinks. This suggests, as the reporter's interpretation, that the updater wrote the new binary over the alias instead of updating the winget package. [https://github.com/github/copilot-cli/issues/5096] Expected behavior per the reporter: the updater should either detect a winget-managed install and defer to winget (for example by directing the user to winget upgrade GitHub.Copilot), or apply the update so the package folder, Links alias and install record stay consistent. The reporter also wonders whether Homebrew or npm installs have similar divergence, but offers no evidence for that. [https://github.com/github/copilot-cli/issues/5096] Status and limitations: the captured issue was opened 2026-10-09 and has no comments in the captured timeline, so there is no maintainer confirmation of cause, no workaround, and no fix or release link. Exact error text is absent; this is a state-inconsistency report. The affected-version range is unknown beyond 1.0.89 to 1.0.91 on one environment. Treat this as an unverified external report; do not assume that the behavior is general or that any particular release addresses it.