docs(images): regenerate guide screenshots in the pinned container#416
Merged
Conversation
The committed captures predate the Jul 14 web UI change that added the regulatory crosswalk and AI compliance card, so the guide screenshots no longer matched the shipped UI. Re-run the @capture suite (npm run capture:ui) inside the same pinned Playwright container CI uses (mcr.microsoft.com/playwright:v1.61.1-jammy), refreshing 9 images — notably the conformance section and the New scan form. The animated demo GIF (docs/images/web-ui-demo.gif) has no capture automation and still shows the pre-Jul-14 UI; re-recording it stays a manual follow-up.
This was referenced Jul 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The committed guide screenshots were captured before the Jul 14 web UI change (regulatory crosswalk + AI compliance card), so pages like the conformance section showed a stale UI.
What
Re-ran the
@capturePlaywright suite (npm run capture:ui) inside the same pinned container CI's reseed job uses (mcr.microsoft.com/playwright:v1.61.1-jammy), so rendering matches the visual-baseline environment. 9 PNGs refreshed, includingweb-ui-g7.png(conformance) andweb-ui.png/web-ui-en.png(New scan form with the current toggles).All 14 capture specs passed; the two key images were visually inspected (fonts and layout intact, current UI shown).
Not included
web-ui-demo.gifhas no capture automation (manually recorded) and still shows the pre-Jul-14 UI. Re-recording it is a manual follow-up.