We're probably going to need a breaking change notice/Tactics for this for 10 - watch is less load-bearing from a scripting perspective than the other CLI commands but it's still a major change in behavior.

@baronfel The change redirects all output from watch to stderr. However, dotnet watch invokes dotnet run to run the app and the run command does output strings to stdout, e.g. here:

https://github.com/dotnet/sdk/blob/main/src/Cli/dotnet/Commands/Run/RunCommand.cs#L222

Yep - I don't think we can change run entirely to change to stderr this late in the cycle though. It's one of the first things we were going to change for 11.

cc @marcpopMSFT

People rely on the run output being predictable. I think it's too late for run and I'd do that early in 11 and see if we got feedback.

@baronfel is anything othre than reviews blocking this?

@jaredpar breaking change notice emails/docs?

@baronfel who is intended to do this work: @tmat, you, etc ...? Getting late into .NET 10 so want to make sure that we understand responsibilities.

It's on me - I've finally cleared out some other blocking work.

Doc issue written at dotnet/docs#48628.