How can I configure mise to not log an error message when a --shim spawns a devtool correctly and successfully and the tool returns a non-zero exit code?

$ just foo
error: Justfile does not contain recipe `foo`
mise ERROR command failed: exit code 1
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

In this example, just already logs a useful error, and mise is obscuring it by logging a much less useful message beneath. Importantly, this is not a failure to install just, to locate the just binary, or anything like that. mise behaved correctly and spawned the just executable, which executed as expected. So the extra "command failed" logging is not helpful.

This happens for mise activate --shims. I assume the shim executable is calling the same codepath as mise x -- <tool> and inheriting the same logging behavior. This doesn't happen when mise activate puts the path to each tool directly on the $PATH. This means that the logging behavior of any mise-managed tool invoked directly from the shell -- $ <tool> -- is different depending on if you use shims.

Is it reasonable for the shim executables to omit this additional logging so they behave more like the tools they are shimming? We can keep the logging for mise x and can keep it for spawn-related errors, say if the shim fails to locate the correct .exe to spawn.