update-screenshots

A focused operational procedure for refreshing component screenshot baselines in the VS Code repository from CI, meant to be run as a subagent. It documents a key change in how baselines are managed: screenshot baselines are no longer stored in the repository (the baseline images were removed from test/componentFixtures/.screenshots/baseline/ and Git LFS is no longer used). Instead, an external screenshot service (hediet-screenshots.azurewebsites.net) stores images keyed by commit SHA and performs diffing automatically. The CI workflow uploads screenshots to that service and diffs them, and when the 'Checking Component Screenshots' GitHub Action detects changes it posts a PR comment with before/after comparisons. Because of this design, no manual baseline updates are needed — the screenshots on the main-branch commit automatically become the new baselines after merge. The skill's main value is explaining what to do when screenshots need investigation: check the PR comment posted by the CI workflow for the visual diffs, and download the raw captured images from the CI run's 'screenshots' artifact using the gh run download command with the run id, the screenshots artifact name, and a target directory, then compare locally if needed. The downloaded artifact contains the full set of captured screenshots. It is useful when asked to update, accept, or refresh component screenshot baselines, or after the screenshot-test GitHub Action reports differences, and it primarily corrects the outdated expectation that baselines live in the repo and must be committed by hand, clarifying that the process is now automated through the external service and the main-branch merge rather than through manual commits of image files.