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 chore PR that refreshes the committed visual-regression baseline at web/tests/visual-baselines/blog.png after a blog-content merge (the June 30 2026 "Routing Deep-Dive" post). The diff is a single binary PNG swap with no code, test, or cross-engine surface. Rendered, the new baseline is a valid 1280x800 Wheels Blog index showing the new top post — exactly matching the stated purpose. Verdict: approve (submitted as a comment because GitHub forbids the bot author from approving its own PR).

Correctness

• web/tests/visual-baselines/blog.png — git show confirms a single binary change (Bin 120509 -> 123003 bytes, 0 insertions / 0 deletions) and file reports a valid PNG image data, 1280 x 800, 8-bit/color RGB. Rendering the image confirms it is the Wheels Blog index with "Routing Deep-Dive: Resources, Nested Callbacks, and Route Model Binding" (June 30 2026) at the top, consistent with the preceding docs(web/blog) commit. The baseline reflects the actual content change it claims to capture.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type (chore), docs is an accepted optional scope, subject is non-empty / not ALL-CAPS, header well under 100 chars.

No convention, cross-engine, test, security, or docs findings — a binary baseline refresh carries none of that surface.