Auto-enable DOTNET_CLI_CONTEXT_VERBOSE for diagnostic verbosity

[Copilot]

• Refactor to use System.CommandLine Option Action
• Create ApplyVerbosityAction class
• Add Action to all VerbosityOption definitions
• Revert all command-specific changes
• Fix Terminating property to false
• Verify Action is invoked correctly
• Test the implementation across multiple commands
• Address code review feedback
• Remove debug comments
• Simplify Action by passing option reference
• Final testing complete

Implementation Complete

The solution uses System.CommandLine's Option Action mechanism with a generic Action class that receives the option reference directly. This allows cleaner code using parseResult.GetValue(verbosityOption) as suggested by @baronfel.

Verified working:

• dotnet build -v diag ✓
• dotnet restore -v diagnostic ✓
• dotnet build -v normal (does not set variable) ✓

Original prompt

Can you look through all of the CLI commands, find those that have a verbosity, and if verbosity is set to diag, please also configure verbose details that is also controlled by DOTNET_CLI_CONTEXT_VERBOSE.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[baronfel]

@copilot a solution that requires every command to remember to call some method is not workable - instead you should use the Action of the common verbosity option to carry this 'set the env var logic'. You can give an Option an Action that System.CommandLine will call during invocation of the parsed command if that Option is part of the result set.

Doing this keeps the behavior consistent across all commands that use the verbosity.

[Copilot]

@copilot a solution that requires every command to remember to call some method is not workable - instead you should use the Action of the common verbosity option to carry this 'set the env var logi...

I've refactored the implementation to use the Option Action pattern as you suggested. The ApplyVerbosityAction is now attached to all VerbosityOption definitions in CommonOptions, and all the per-command calls have been reverted (commit 47b9106).

However, I'm finding that the Action doesn't appear to be invoked during testing. Could you clarify when System.CommandLine invokes Option Actions? Is there something specific I need to do to ensure the Action is called when the option is parsed?

[baronfel]

@copilot the 'pre-actions' are collected during parsing here, and then invoked sequentially during command invocation here.

your implementation of the action needs to change slightly - you don't need to do all of this work to get the verbosity, you can just directly fetch the value from the parse result. If the action is being invoked you can assume that the verbosity is in the parse result. if you pass a reference to the verbosity option to the Action, then you can do something like if (parseResult.GetValue(verbosityOption).IsDiagnostic()) { ... }

[Copilot]

@copilot the 'pre-actions' are collected during parsing here, and then invoked seq...

Updated the implementation to pass the option reference to the Action as you suggested (commit e7a82e7). The Action now uses parseResult.GetValue(verbosityOption) directly instead of searching through all children. Made the Action generic to handle both VerbosityOptions and VerbosityOptions? types. Verified working with dotnet build -v diag and dotnet restore -v diagnostic.

[baronfel]

This LGTM - the CI failure is the WinRT known issue