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 page, opened by .github/workflows/web-deploy.yml after the preceding blog-content commit (7e65f6108 docs(web/blog): Real-Time Without WebSockets…). It touches exactly one binary file, web/tests/visual-baselines/blog.png (132975 → 128776 bytes), with no code and no source-line additions or deletions. This is precisely the documented flow for issue #2915 — keeping the committed baseline in sync so subsequent web/** PRs don't fail Visual regression on a deterministic, already-merged diff. Verdict: comment (no blocking findings; clean, trivial, mechanical change).

Commits

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

Tests

• No test changes are expected or appropriate: the changed file is the test fixture (the golden baseline the Playwright visual diff compares against), not code under test. There is nothing to add a BDD spec for.

Notes

• A baseline PNG is binary, so its pixel content can't be diff-reviewed here. The trust model rests on provenance: the image was regenerated by the deploy workflow immediately after the content change it reflects, and the file is an internal test artifact (never shipped to users), so there is no correctness, cross-engine, or security surface to evaluate.

No Correctness, Cross-engine, or Security findings. Nothing blocks merge.