Contributes towards #279402
Make test/sanity NPM-install independent for faster initialization in the pipeline.
Fixed pipeline and tests ro fully pass on Windows x64 and MacOS x64.
Updated suite/test names to report nicely in ADO.
Ensure temp dir name is expanded on Windows to avoid ~ expansion from CLI.
Removed custom log file now that XML report is supported.
Added option to turn headless browsing on/off.
* vscode mcp: support specifying workspace path; enable restart tool
* fix: include workspace path in launch options for browser
* fix: ensure workspace path is set for tests requiring a workspace
* Address PR review comments: support optional workspace path
* fix: standardize workspace path variable naming in tests
* fix: fallback to rootPath for workspacePath in CI environments
Added option to skip code signing validation.
Fixed portable tests to create and use user data directory.
Remove unnecessary env variable in case of x64 macOS.
* Introduce compilation error
* Engineering - limit the tasks that we run
* Limit available memory to simulate an OOM
* Try to update the task
* Remove the use of npm-run-all
* Fix script
* Another try
* Try npm-run-all2
* Restore tasks, keep npm-run-all2
* Switch from npm-run-all to npm-run-all2
* Revert changes that were used for testing
* feat: create versioned resources for windows setup
* chore: use inno_updater to remove old installation
* chore: remove old installation as part of setup
* chore: update explorer-command
* chore: prefer session-end
* chore: uninst delete updating_version
* chore: make session-ending write synchronous
* chore: cleanup updateService.win32.ts
* chore: invoke inno_updater gc path for non background update
* chore: move session-end path to runtime
* chore: use commit for updating_version
* chore: fix invalid string
* chore: set appUpdate path
* chore: update inno_updater
* chore: empty commit for testing
* chore: some cleanups
1) Check for session-ending flag in appx and tunnel callsites
2) Move gc for background update to cleanup phase in updateservice
3) Set update state to ready when there is a running inno_setup
* chore: disallow same version update
* chore: disallow application launch in the middle of update
* chore: empty commit for testing
* chore: bump inno_updater
* chore: empty commit for testing
* chore: move gc to update startup
* chore: move feature behind insider only check
* chore: bump inno_updater
* chore: bump explorer-command
* fix: build
* fix: gc for background update in system setup
* chore: create separate cli entrypoints for build
* fix: check for setup mutex created by inno
* chore: remove problematic updatingVersionPath deletion
* chore: remove redundant update check
* chore: bump inno_updater
* chore: fix build
* chore: bump inno updater
1. the mcp server wasn't working... perhaps due to our js -> ts build move... or a bump in a npm package. Either way, good now.
2. I list out all tools across Copilot CLI & VS Code that would apply in this case... there's some overlap for sure... but I want to make sure we're golden for any renamed tools situations.
