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 auto-generated PR from .github/workflows/web-deploy.yml that refreshes the stale Playwright visual-regression baseline at web/tests/visual-baselines/blog.png after a blog-content merge (issue #2915). The diff is a single binary PNG with no code, test, doc, or cross-engine surface. Verdict: approve (submitted as a comment-state review because GitHub forbids the bot from approving its own PR — the 422 self-approval fallback).

Correctness

• web/tests/visual-baselines/blog.png is the exact path the harness reads. web/scripts/visual-regression.mjs:240 resolves the baseline path by joining BASELINE_DIR with the site name plus .png, and the blog site is registered at line 45. Refreshing this file is the documented remediation the script itself prints at web/scripts/visual-regression.mjs:297-298 ("If the changes are intentional, refresh baselines: pnpm visual:baseline").
• The committed blob is a valid PNG image data, 1280 x 800, 8-bit/color RGB — a well-formed screenshot baseline, not a corrupt or truncated artifact.

Commits

• chore(docs): auto-refresh blog visual baseline after content change conforms to commitlint.config.js: valid type (chore), optional unrestricted scope, subject is not ALL-CAPS, header well under 100 chars. The PR title is likewise a valid conventional-commit header.

Note (non-blocking): a binary baseline is inherently un-reviewable for pixel content — trust here rests on the deploy workflow being the source of truth, which is the intended design for web/** baselines.