Portable application executable is renamed despite absence of rename argument

Brief description of your issue

The Portable/Standalone applications documentation states:

If a command value is specified in the manifest, then the symlink filename will be renamed to match the command value. If the rename argument is provided, then both the symlink filename and the portable exe filename will be renamed to match the rename argument value.

However, the portable exe is renamed even if the rename argument is absent.

In case the behavior is intended and only the documentation is misleading, I still request changing this behavior. Renaming the exe is confusing and seems unnecessary.

Steps to reproduce

Run winget install --exact --id Microsoft.Sysinternals.ProcessExplorer --version 17.05

Note that the manifest includes:

Commands:
- process-explorer

Expected behavior

C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links contains symlink process-explorer.exe.

C:\Users\<username>\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Sysinternals.ProcessExplorer_Microsoft.Winget.Source_8wekyb3d8bbwe\ contains procexp64.exe.

Actual behavior

C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links contains symlink process-explorer.exe.

C:\Users\<username>\AppData\Local\Microsoft\WinGet\Packages\Microsoft.Sysinternals.ProcessExplorer_Microsoft.Winget.Source_8wekyb3d8bbwe\ contains process-explorer.exe.

Environment

Windows-Paket-Manager v1.6.3482
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.19045.3803
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.21.3482.0

Reproduce the issue with winget install --exact --id Microsoft.Sysinternals.ProcessExplorer --version 17.05 and inspect the portable standalone application install path described in the linked documentation. Compare handling of the manifest's Commands value with the absent rename argument; done means the symlink is named process-explorer.exe while the packaged executable remains procexp64.exe.