Ghost mode continues to intercept commands after POST configuration step within GitHub Actions

Describe the bug

Ghost mode continues to intercept commands, after the POST jfrog/setup-jfrog-cli@v5 step. This causes commands after to continue to be Intercepted resulting in a Server ID 'xxx' does not exist, for the dotnet tool.

Jfrog was called after to avoid requiring Re-Pinning Aliases as stated in the docs

Current behavior

Ghost mode continues to intercept commands, after the POST jfrog/setup-jfrog-cli@v5 step. this causes commands after to continue to be Intercepted resulting in a Server ID 'xxx' does not exist.

As shown in the screen shot below,

• Setup .NET (actions/setup-dotnet@v5)
• Config Artifactory (JFrog)
• Build + Test
• Post JFrog clean up
• Post .NET (This errors out)

Reproduction steps

Run a workflow with actions/setup-dotnet@v5 then jfrog/setup-jfrog-cli@v5

Expected behavior

The dotnet is not intercepted and there are no errors.

Setup JFrog CLI version

5.1.0

JFrog CLI version

Latest (2.124.0)

Workflow operating system type and version

Github Actions (windows)

JFrog Artifactory version (if relevant)

No response

JFrog Xray version (if relevant)

No response

Reproduce the workflow on Windows with actions/setup-dotnet@v5 followed by jfrog/setup-jfrog-cli@v5, then inspect the setup action's POST cleanup behavior; the issue names no source files or tests. Done means commands after the JFrog cleanup no longer intercept dotnet and the post-setup step completes without the missing Server ID error.