Good feedback. I have one comment and one question: 1. I personally prefer to present a terse message to stderr and stack traces to a debug file. This helps a

Good feedback. I have one comment and one question: 1. I personally prefer to present a terse message to stderr and stack traces to a debug file. This helps a user give support more information when they're hitting transient issues. 2. I fully agree with the recommendation for a --dry_run option, but I think the output needs to be actionable. Do people have good examples of actionable --dry_run output that lets the user verify their intent? E.g. The list of files that would be deleted by "rm -rf"