harness update fails: harness: text file busy

$ harness update
[notice] A new release of harness cli is available: v0.0.25-Preview → v0.0.29
https://github.com/harness/harness-cli/releases/tag/v0.0.29
To update, run: harness update
New version v0.0.29 is available.
? Do you want to update? Yes
Downloading the following - https://github.com/harness/harness-cli/releases/download/v0.0.29/harness-v0.0.29-linux-arm64.tar.gz
Unpacking the contents and extracting to - /home/unop/.local/bin
Extracting harness cli to - /home/unop/.local/bin/harness
FATA[2025-04-14T09:48:16+02:00] open /home/unop/.local/bin/harness: text file busy

The updater is attempting to overwrite the same binary (~/.local/bin/harness) that is being used to perform the update - I wonder - Is this even possible?

As an aside, on update failures, it'd be nice if the updater informed the user of the location of the downloaded binaries, so they could re-use them to manually correct the failed update. e.g.

$ harness update
...
Downloading the following - https://github.com/harness/harness-cli/releases/download/v0.0.29/harness-v0.0.29-linux-arm64.tar.gz
Unpacking the contents and extracting to - /home/unop/.local/bin
Extracting harness cli to - /tmp/harness.AE1F94CD/harness
FATA[2025-04-14T09:48:16+02:00] open /home/unop/.local/bin/harness: text file busy

In place update failed. Please run the following commands to complete update.

   mv /tmp/harness.AE1F94CD/harness /home/unop/.local/bin

Start at the harness update entry point and reproduce the failure on Linux ARM64 using the reported in-place update path. Trace how the downloaded binary is extracted and installed, then verify that an update does not fail while replacing the running binary and that failures report the downloaded file and a usable manual recovery command.