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 — Automated single-file refresh of the blog visual-regression baseline (web/tests/visual-baselines/blog.png) after the 4.0.5 announcement merged, opened by web-deploy.yml to keep the Visual regression check green (issue #2915). The diff is exactly what the body claims and carries no code/test/security surface. Verdict: comment (clean; not approving because the PR author is wheels-bot itself, which GitHub rejects with HTTP 422).

Correctness

• The new baseline is a valid 1280×800 RGB PNG (file confirms) and renders the blog index with the Wheels 4.0.5 post pinned at the top — consistent with eb73cb636 docs(web/blog): announce Wheels 4.0.5. The render is not blank or truncated, so it is a sound replacement baseline.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: type chore, scope docs, lowercase subject, header under 100 chars.

Tests

• N/A — this file is the visual-regression fixture; refreshing it is the test update.

No blocking findings. Safe to merge once the Visual regression check confirms the new baseline matches the live render.