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 visual-regression baseline web/tests/visual-baselines/blog.png after a blog-content merge changed the blog index page, auto-opened by .github/workflows/web-deploy.yml to keep the Visual regression check green (issue #2915). The change is a single binary asset with no code, tests, or config touched. Verdict: comment (clean; nothing to block). I cannot --approve because the PR author is wheels-bot itself and GitHub rejects an author approving its own PR (HTTP 422), and there is no prior wheels-bot CHANGES_REQUESTED to supersede.

Correctness

• The diff is exactly one file: web/tests/visual-baselines/blog.png, Bin 120615 -> 121835 bytes (git show --stat). The new blob is a valid PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced — the standard baseline dimensions — and the ~1.2 KB size delta is consistent with a content edit rather than a corrupted or truncated asset. Nothing else changed, matching the PR's stated purpose.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: chore is an allowed type, scope is optional, the subject is sentence-case (not ALL-CAPS), and the header is well under 100 chars. The PR title (chore(docs): refresh blog visual baseline after content change) — the squash-merge gate — is likewise valid.

Security

• No code paths, no SQL, no view output, no secrets. A binary PNG baseline carries no injection/XSS/CSRF surface.

Nothing actionable. A maintainer can merge once the Visual regression check (which this baseline feeds) passes.