Set up tools that "verifies" command samples
Issue Description
It's difficult to keep documentation up to date with changes in code. That issue can affect command samples within docs, especially scripts.
I think we could use developer support to create automated tests that:
- Identify commands that do not currently work
- Identify output that does not match documentation
And once all commands in our docs are fixed, those automated tests could also flag all (developers, writers) when this status changes.