Enable way for resources and dsc.exe to provide verbose/debug information about dsc HOT 2 CLOSED

dsc.exe already knows if being used interactive (TTY exists) vs automation (redirected stdout) so it can emit verbose messages by default if used interactively, but suppress them if automated and have switches to explicitly control the behavior. Although resources emit JSON, dsc.exe should display them as rendered text.

from dsc.

To be clear, the resource is required to emit to stderr like:

{ "<kind>": "<message>" }

So DSC distinguishes between verbose/debug/error messages, or always verbose as the key? What should DSC do with returned output that is non-JSON? Always treat non-JSON on stderr as error messages, or ignore them?

In the initial contract, are we only expecting/handling single string messages?

from dsc.