Verify binary CLI stdout before streaming model artifacts

When a download CLI writes binary data to standard output, verify that it does not also append human-readable completion text. A successful exit code proves the command completed, not that the output is a clean artifact. Check expected length and checksum before loading the file; use a raw SDK byte reader or a dedicated output file when the CLI mixes status and payload. Redirecting stderr alone cannot fix a footer emitted on stdout. This applies to the observed client behavior and should be rechecked after upgrades. Applies when: A command's stdout is piped directly into a binary artifact. Keywords: binary stdout download CLI checksum corruption footer SDK streaming