updates screenshot pipeline & baseline

[hediet]

No description provided.

[Copilot]

Pull request overview

This pull request updates the screenshot testing pipeline and adds new screenshot baselines for VS Code's component testing infrastructure. The PR simplifies the GitHub Actions workflow by replacing check runs with commit statuses, which improves security by reducing required permissions but trades off some visibility features.

Changes:

• Simplified screenshot workflow permissions from pull-requests: write and checks: write to only statuses: write
• Replaced check run creation logic with simpler commit status API calls
• Added visual emoji indicators (⚠️/✅) to status titles for better at-a-glance feedback
• Added 64 new screenshot baselines for UI components (updateWidget states, chatQuestionCarousel, and other UI elements)
• Updated 1 existing screenshot baseline (aiStats/AiStatsHover/Dark)

Reviewed changes

Copilot reviewed 3 out of 161 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/screenshot-test.yml	Simplified workflow permissions and reporting mechanism; removed check run logic in favor of commit statuses
.tmp/screenshot-diff/report/*	Generated screenshot comparison report and current screenshots (64 added, 1 changed)
.tmp/screenshot-diff/current/*	Current screenshot outputs from test run

Comments suppressed due to low confidence (1)

.github/workflows/screenshot-test.yml:13

• The removal of pull-requests: write and checks: write permissions is a significant security improvement, limiting the workflow to only the necessary statuses: write permission. However, this change means the workflow can no longer create check runs (which require checks: write). The new approach using commit statuses is appropriate for fork PRs but provides less detailed feedback than check runs. Consider documenting this trade-off in the workflow or commit message.

permissions:
  contents: read
  statuses: write