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, single-file chore that refreshes the stale visual-regression baseline web/tests/visual-baselines/blog.png after a blog-content merge, exactly as documented in issue #2915 and opened by .github/workflows/web-deploy.yml. The diff is a pure binary replacement (Bin 117750 -> 116526 bytes, 0 insertions / 0 deletions). I verified the new PNG renders as a legitimate blog-index screenshot whose top post is "How Wheels Actually Reads Your Configuration" (July 15, 2026), matching the preceding content commit 173e9ea. No code, cross-engine, or security surface is touched. Verdict: approve (posted as a comment — GitHub forbids the bot approving its own PR, which this is).

Docs

• web/tests/visual-baselines/blog.png — baseline refresh is warranted and content-consistent. No changelog fragment or .ai/CLAUDE.md update is required: this is a test-fixture refresh, not a user-facing fix/feat, and the PNG is itself the test artifact so no additional test coverage applies.

Commits

• d50d664 "chore(docs): auto-refresh blog visual baseline after content change" — conforms to commitlint.config.js (valid chore type, docs scope, lowercase subject, header well under 100 chars). The message correctly reflects the "why" (baseline drift after content change).

Nothing blocking. Clean to merge.