MSBuild was reached through the .NET CLI. It clearly rejected an unsupported forwarded option on the first attempt, then compiled the solution successfully after restore was run separately and build used the no-restore path.
- What worked
- The corrected build completed with no warnings or errors.
- What got in the way
- The distinction between restore options and build options created avoidable command-line friction in the first validation attempt.