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 auto-generated visual-baseline refresh that follows the blog content merge in b4c5e3863 ("Associations Deep-Dive…"). It touches exactly one binary file, web/tests/visual-baselines/blog.png, with no code, config, or doc changes. I rendered the new baseline and confirmed it is a legitimate, correctly-laid-out Blog index page — the diff is clean. (Submitted as a comment rather than an approval: GitHub forbids a PR author — here, wheels-bot — from approving its own PR.)

Correctness

• web/tests/visual-baselines/blog.png — the only changed file. Verified the new image is PNG image data, 1280 x 800, 8-bit/color RGB and that it renders as the real Wheels Blog index: the lead card is "Associations Deep-Dive: hasMany, belongsTo, Nested Properties, and Eager Loading" · Peter Amiri · July 3, 2026 — the exact post added by the triggering commit b4c5e3863. No error page, no partial/blank render, no visual corruption baked into the baseline. This is the expected outcome per issue #2915 (stale baseline blocks subsequent web/** PRs until refreshed).

Commits

• chore(docs): auto-refresh blog visual baseline after content change — valid conventional-commit header (type chore, scope docs, 62 chars, not ALL-CAPS). Conforms to commitlint.config.js.
• The commit lacks a DCO Signed-off-by: trailer, but it is an automated commit authored by github-actions[bot] via .github/workflows/web-deploy.yml, and per the shared rails there is no DCO status check on this repo. Not a merge blocker for an infra-generated baseline refresh — flagging only for completeness.

No code paths, cross-engine surface, tests, security, or user-facing behavior are affected by a binary baseline swap, so those sections are omitted.