chore(docs): refresh blog visual baseline after content change

[wheels-bot]

Summary

A blog-content merge changed the blog index page, so the committed visual-regression baseline at web/tests/visual-baselines/blog.png is stale. Without this refresh, every subsequent web/**-touching PR fails the Visual regression check on a deterministic diff until someone refreshes manually (issue #2915).

develop's branch protection rejects direct pushes, so the refresh lands through this PR, opened and merged by the deploy run that published the blog change.

🤖 Opened automatically by .github/workflows/web-deploy.yml.

[wheels-bot]

Wheels Bot — Reviewer

TL;DR — This PR refreshes the stale visual-regression baseline at web/tests/visual-baselines/blog.png after the preceding blog-content commit changed the blog index page. It is a single-file, binary-only, machine-generated chore opened and merged by the web-deploy.yml run (the issue #2915 auto-refresh mechanism). The change is mechanically correct and I have no blocking findings; verdict: comment.

Correctness

Verified the diff is exactly one binary file and nothing else:

web/tests/visual-baselines/blog.png | Bin 116469 -> 119464 bytes
1 file changed, 0 insertions(+), 0 deletions(-)

• The new blob is a valid image — file reports PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced, matching the expected Playwright viewport baseline shape.
• The refresh is justified: the immediately-preceding commit ec2362019 (docs(web/blog): Sending Email in Wheels 4.0) altered blog content, which legitimately shifts the rendered blog index and invalidates the old baseline. This is precisely the drift issue #2915 describes.

No code, no CFML, no framework surface touched — cross-engine, conventions, security, and test-authoring checklists are all N/A for a baseline-image swap. There is nothing to unit-test here; the baseline is the test fixture.

Commits

• chore(docs): auto-refresh blog visual baseline after content change — valid conventional-commit type, header well under 100 chars, not ALL-CAPS. Good.
• Minor, non-blocking nit: the commit carries no DCO Signed-off-by: trailer (author is github-actions[bot]). Per repo policy there is no DCO status check and this is fully automated infra, so it does not block — flagging only for completeness.

Approving is not applicable here since the PR author is wheels-bot itself (GitHub rejects self-approval), and there is no prior wheels-bot CHANGES_REQUESTED to supersede, so this posts as a plain comment.