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 a blog-content merge changed the blog index page, unblocking the Visual regression check on subsequent web PRs (issue #2915). It is a single binary-file change opened/merged automatically by web-deploy.yml. Verdict: comment — nothing reviewable triggers a blocking finding; the change is mechanical and self-consistent.

Commits. 228e86080 chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type (chore), permitted scope (docs), subject is lowercase and the header is ~64 chars (<= 100). No violation.

Notes (non-blocking). The change is a single binary asset (Binary files ... differ); there is no source, route, model, or view diff to evaluate against the cross-engine invariants or anti-patterns, and no tests/docs/changelog fragment are expected for a generated baseline refresh. A baseline PNG cannot be diffed line-by-line in review — its correctness rests on the deterministic capture performed by the deploy workflow that produced it, which is acceptable for an automated baseline-refresh PR. No action needed.