Run a task

Run the existing build task named BuildProject now. Use the Run Task command, ensure the integrated terminal shows the full build log, and if the task fails, capture the last 200 lines into build-failure.log at the workspace root. Do not run any clean or deploy steps—only the BuildProject task.

Before I run BuildProject for QA, make it easy to spot failure: surface the exact command and cwd the task will use, highlight any preLaunchTask it depends on, and flag environment variables that affect the build. Point out the three things that would make a reviewer hesitate to approve running this on a shared branch.

I kicked off the BuildProject task and the terminal opens then closes with no output. The task used to run fine last week. I suspect the task's command or problemMatcher is misconfigured or the task is launching in the wrong shell. I can't tell whether an extension update changed the default shell or whether the task is marked as background. What's the likely cause and the safest next step to get the build log without breaking anything for other developers?

Across the team, people are avoiding the configured build task and running ad-hoc build scripts instead. That loses build flags and makes CI mismatches. I want a single habit change that reduces friction and makes the shared build task the default. What should I change first so everyone trusts and uses the task instead of hand-run scripts?