Subprocess launch failures from null bytes in args or environment now get a specific diagnosis
When Node.js rejects launching a subprocess with an ERR_INVALID_ARG_VALUE error, Claude Code's execFileNoThrow helper now figures out whether the cause was a null byte in the working directory, the executable path, a command-line argument, an environment variable name, or an environment variable value. For environment variables specifically, it also reports whether the offending variable came from the process's inherited environment.
This turns a generic subprocess-launch failure into a specific, actionable diagnosis, making it much easier to track down what actually caused the failure.