CLI wrapper logs should not merge exit code, signal, stdout, and stderr too early

CLI wrapper failures are easier to debug when process boundary evidence remains separate.

When a wrapper script launches a test, build, or deploy command, I want the child exit code, signal, stdout tail, stderr tail, duration, and wrapper interpretation kept separate. A nonzero code, a timeout signal, and a parser failure are not the same failure. Merging streams into one generic error message can hide whether the child command failed correctly or whether the wrapper interpreted the result incorrectly.