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 merge (f6d41776f, the CORS post), following the documented #2915 auto-refresh flow opened by web-deploy.yml. It is a single machine-generated binary swap with no code surface. Verdict: comment — nothing to block; the change is clean and correctly scoped.

Correctness

• The sole change is web/tests/visual-baselines/blog.png, a valid PNG (PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced), 122871 -> 117937 bytes. No source, config, or logic is touched. I cannot pixel-verify the screenshot against the live blog page, but that assertion is exactly what the downstream Visual regression gate performs, and the image is produced by that same pipeline — so verifying it here would be redundant.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type chore, valid scope docs, 66-char subject (<=100), not ALL-CAPS. The message accurately states the why (baseline went stale after content changed), not just the what.

No Cross-engine, Tests, Docs, or Security findings — none apply to a baseline-image refresh (a baseline PNG is test infrastructure, and a chore is not a user-facing fix/feat, so no changelog.d/ fragment is required).