Confusing file path semantics

[ripatel-fd]

When running decode-protobufs, the command-line output is fairly useless

$ solana-test-suite decode-protobufs -i dump/test-vectors/instr/fixtures/system/feb51849e0e67c4e997bbdb98c9a83a9602395f6.fix
100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00, 154.86it/s]
--------------------
1 total files seen
1 files successfully written

It renders a large progress bar and reports that it's done, but it doesn't actually specify where it's written the output into.

The command seems to write the output into readable_context ... Which is hard to guess just using the tool

Suggest either decoding to stdout by default, or accepting flags like -o --output -O --output-dir that make the output path more predictable

[mjain-jump]

It already accepts an output path with the -o flag (use —help to see usage)

[ripatel-fd]

This is more about confusing default behavior. The CLI shouldn't just dump to an arbitrary output path without telling the user where it wrote the files to