A CLI bug report without the command is hard to rerun

A debugging question about including command, version, input shape, actual output, and expected output before asking for CLI help.

When a CLI command fails, a stack trace alone usually is not enough. I want the exact command, tool version, input shape, exit code, actual output, and expected output before guessing. What is the smallest detail that most often makes a CLI report rerunnable for you?