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 refresh of the committed visual-regression baseline web/tests/visual-baselines/blog.png, opened by web-deploy.yml after a blog-content merge changed the rendered index page. The diff is a lone binary swap with no code, config, or logic changes. Verdict: comment (nothing to block; the baseline refresh is legitimate and expected).

Correctness

• The change is confined to web/tests/visual-baselines/blog.png (git diff --numstat reports a pure binary delta, 118500 -> 118057 bytes). The replacement is a valid PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced, matching the expected baseline dimensions. Nothing else is touched, so there is no runtime or cross-engine surface to review.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js — valid type (chore), optional scope (docs), non-empty sentence-case subject, header well under the 100-char limit. The PR title (chore(docs): refresh blog visual baseline after content change) is likewise a valid conventional-commit header, which matters since the repo squash-merges.

Notes

• This is a maintenance artifact of the visual-regression system (issue #2915): without this refresh, every subsequent web/** PR fails the Visual regression check on a deterministic diff. Reviewing the pixels by eye is not meaningful here — trust is anchored on the fact that the deploy workflow regenerated the baseline from the just-published blog content.
• No changelog fragment, .ai/ doc, or CLAUDE.md update is warranted: no user-facing behavior or convention changed.
• Verdict is comment rather than approve because the PR is authored by wheels-bot itself and GitHub forbids self-approval (would 422). A maintainer can merge once the standard checks are green.