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 the automated visual-regression baseline refresh for the blog index, opened by .github/workflows/web-deploy.yml after the blog-content change in 76185cc35 (docs(web/blog): ... Observability in Wheels 4). It updates exactly one committed binary baseline so subsequent web/** PRs stop failing the Visual regression check on deterministic drift (issue 2915). The diff is mechanical and clean. Verdict: comment (no blocking findings; --approve is not applicable since the PR author is wheels-bot itself).

Correctness

• Diff is a single binary file, web/tests/visual-baselines/blog.png (Bin 117937 -> 117750 bytes). Verified it is a well-formed image: PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced, matching the dimensions/format of its sibling baselines (api.png, guides.png, landing.png). No code paths touched.
• The theoretical risk — an auto-refreshed baseline silently masking a real regression — is out of scope for this PR: web-deploy.yml (comments at lines 287-298) commits the refreshed blog.png only when the regression test passes, and the blog baseline is designed to drift with content per issue 2915.

Commits

• chore(docs): auto-refresh blog visual baseline after content change — valid type (chore), optional scope (docs), header well under 100 chars, sentence-case. The squash-merge subject comes from the PR title chore(docs): refresh blog visual baseline after content change, likewise a valid conventional-commit header. Both conform to commitlint.config.js.
• Note: no DCO Signed-off-by: trailer on the commit (authored by github-actions[bot]). This repo has no DCO status check and this is machine-generated automation, so it is not a merge blocker — flagging for completeness.

No convention, cross-engine, test, docs, or security findings — this diff contains no CFML and no runtime surface.