I'm trying to remember why I had the custom pkg_done_message here at all.

My guess is that it's to surface errors when dependencies (libraries) are missing, or the wrong binary is selected for the target machine.

Making a few modifications:

• "$pkg_dst_cmd" must be quoted, otherwise Macs on Windows networks get errors when the Active Directory domain creates a space in the user's home directory. For example: /Users/John Smith/.local/opt/pwsh/pwsh
• Nixing the "installed to" since we already have that in the new install script

I was pretty sure that the command should be in the PATH by virtue of the installer's processing having it in its PATH.

So... I don't think this actually fixed anything. I think the real problem was Microsoft's change to the package internals.