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(docs) PR that refreshes the stale visual-regression baseline at web/tests/visual-baselines/blog.png after a blog-content merge. The diff is a single binary PNG swap, generated and guarded by .github/workflows/web-deploy.yml (issue #2915). It is genuinely clean with no findings; my verdict is approve (submitted as a comment because GitHub forbids wheels-bot approving its own PR — HTTP 422 fallback).

Review

The change is one binary file:

web/tests/visual-baselines/blog.png | Bin 123003 -> 118288 bytes
1 file changed, 0 insertions(+), 0 deletions(-)

Verification performed:

• Valid asset — file reports PNG image data, 1280 x 800, 8-bit/color RGB, non-interlaced; nothing but the baseline is touched (gh pr view --json files shows exactly one MODIFIED entry).
• Mechanism is sound — web-deploy.yml pre-refreshes the blog baseline (node scripts/visual-regression.mjs --update --site blog) and only commits it when the regression test passes, so a refreshed baseline cannot silently mask a real regression (see the "Commit the pre-refreshed baseline only when the regression test..." step and issue #2915 rationale in the workflow comments).
• No code paths, no CFML — nothing under vendor/wheels/**, app/**, or cli/**; cross-engine, security, and test-coverage checklists are all N/A for a binary baseline.

Commits

chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type chore, valid scope docs, subject is not ALL-CAPS and is well under the 100-char header limit. The PR title matches.

No changelog fragment is expected — this is CI infra, not a user-facing feat/fix.