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 is an automated, mechanical refresh of the committed visual-regression baseline web/tests/visual-baselines/blog.png after a blog-content merge (the new "Dependency Injection in Wheels 4.0" post). The diff is a single binary PNG with no code, so the correctness/cross-engine/test/security checklists do not apply. I rendered the new baseline and confirmed it is a valid 1280x800 PNG showing the current blog index with the new DI post at top (June 26, 2026), matching commit 968074c. Verdict: comment — the change is clean; one non-blocking commit note below.

Commits: 2a5bfaf chore(docs): auto-refresh blog visual baseline after content change is commitlint-valid (type chore, optional docs scope, header well under 100 chars). Non-blocking note: the commit lacks a DCO Signed-off-by trailer. Per _shared-rails.md this repo has no DCO status check and sign-off is a fix-before-merge convention, not a gate — and this is an auto-generated github-actions bot infra commit opened/merged by web-deploy.yml, so it does not block. Flagging only for completeness.

Nothing else to address. The baseline correctly reflects the merged blog content, which is exactly what keeps subsequent web PRs from failing the Visual regression check on a stale diff (issue 2915).