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 committed visual-regression baseline web/tests/visual-baselines/blog.png after the blog-content merge in e6db19f98 ("File Uploads in Wheels 4.0"), so downstream web/** PRs stop failing the Visual regression check on a stale diff (issue #2915). It is a single machine-generated binary asset with no code, no cross-engine surface, and no security implications. Verdict: comment — nothing blocking; the one caveat below is inherent to reviewing a binary baseline.

Correctness

• web/tests/visual-baselines/blog.png — the new blob is a well-formed image (PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced, ~116 KB vs the prior ~120 KB), so this is a genuine re-render, not a truncated or empty file. The one thing a diff review cannot establish is that the pixels actually match the current rendered blog index — that is guaranteed only by the deploy workflow (.github/workflows/web-deploy.yml) that generated it from the live page. Assuming that pipeline ran cleanly, this is correct by construction.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type chore, valid optional scope docs, subject is lowercase and well under the 100-char header limit. No issues.

No other sections apply — the diff touches exactly one binary test fixture. (Section labels rendered bold rather than as ### headings because the review harness blocks newline-prefixed # in the body argument.)