What problem does it solve? Running and debugging VS Code smoke tests involves knowing the right npm scripts, grep filters, and CI artifact layouts, and intermittent CI-only failures are hard to reproduce without a structured approach. ## Core Features & Use Cases - Test Execution: Run smoke tests via npm run smoketest or smoketest-no-compile, with grep filtering (-g), tracing, web/remote modes, and packaged-build targeting. - Flaky Test Hunting: Apply a temporary repeat-loop technique in GitHub Actions or Azure DevOps steps to reproduce intermittent CI failures and capture traces. - CI Log Analysis: Download and interpret smoke test log artifacts from GitHub Actions (gh run download) or Azure DevOps (az pipelines runs artifact download), including Copilot runtime logs and Playwright screenshots. - Use Case: A smoke suite fails only in CI. Add a temporary 20-iteration loop step targeting that suite with -g, push a throwaway branch, and inspect the failing run's traces and screenshots from the logs artifact. ## Quick Start Run the VS Code smoke tests filtered to a specific suite with tracing enabled and show me how to debug any failures from the CI logs artifact.